Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4

[Patrik Bengtsson]

Hi Everyone!

We have a couple of MultiConnect® Conduit (MTCDTIP-LEU1-267A) and I’m trying to debug an issue where we loose connection randomly and need to restart the devices. We are using LTE for internet connectivity and do the management thru eth0. To help to debug the issue I was trying to enable the WiFi on the GW but it seems that I never can see wlan0 / wlan1 even if I enable it thru the web-interface. Also in the Boot.log I get the following:

Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module onebox_common_gpl.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module wlan.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module wlan_wep.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module wlan_tkip.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module wlan_ccmp.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module wlan_acl.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module wlan_xauth.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module wlan_scan_sta.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module onebox_wlan_nongpl.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module onebox_wlan_gpl.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module onebox_bt_nongpl.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module onebox_bt_gpl.ko: No such file or directory
Tue Mar 13 10:31:14 2018: insmod: ERROR: could not load module onebox_nongpl.ko: No such file or directory 

Any ideas? I have reinstalled the firmware for 1.4.4 and get the same messages.

Patrik

[Jeff Hatch]

Patrik,

On the Conduit, could you list the contents of /opt/rs9113? That is where those modules should be (initially). If they are in that directory, then something is going wrong with the rs9113 initialization (obviously).

Jeff

[Patrik Bengtsson]

Jeff,

In /opt there are only the following folders;
lora
node-red
serial-streamer

If I do a lsmod I get;

admin@mtcdt:/opt# lsmod
Module                  Size  Used by
nf_nat_ftp              1468  0
nf_conntrack_ftp        5583  1 nf_nat_ftp
usb_f_acm               4199  1
u_serial                8936  3 usb_f_acm
g_serial                1738  0
libcomposite           26763  2 usb_f_acm,g_serial
configfs               20798  3 usb_f_acm,libcomposite
bluetooth             194336  0
mac80211              237934  0
cfg80211              183437  1 mac80211
rfkill                 10109  2 cfg80211,bluetooth
option                 27053  1
usb_storage            36961  0
usb_wwan                5438  1 option
qmi_wwan               10487  0
usbserial              19217  4 option,usb_wwan
cdc_wdm                 9527  1 qmi_wwan
usbnet                 17249  1 qmi_wwan
mii                     3429  1 usbnet
mts_io                 50871  0
vizzini                15862  2
cdc_acm                14885  0
tmp102                  2732  0
spidev                  4904  2
atmel_mci              12966  0
atmel_usba_udc         11246  0
udc_core                6158  2 atmel_usba_udc,libcomposite
spi_atmel              10487  0
pps_gpio                2351  0
pps_core                7419  1 pps_gpio
uio_pdrv_genirq         2706  0
uio                     6938  1 uio_pdrv_genirq

[Jeff Hatch]

Patrik,

Was this Conduit upgraded from mLinux? What is the output of the following command:

get-eeprom-device-info
or
get-eeprom-device-config

Jeff

[Patrik Bengtsson]

Jeff,

Not that we are aware of, here’s the output;

[INFO] eeprom_main.c:mts_id_eeprom_inspect:291: sizeof: 512
[INFO] eeprom_main.c:mts_id_eeprom_inspect:292: vendor-id: Multi-Tech Systems
[INFO] eeprom_main.c:mts_id_eeprom_inspect:293: product-id: MTCDTIP-LEU1-267A
[INFO] eeprom_main.c:mts_id_eeprom_inspect:294: device-id: 19463375
[INFO] eeprom_main.c:mts_id_eeprom_inspect:295: hw-version: MTCDTIP-0.0
[INFO] eeprom_main.c:mts_id_eeprom_inspect:302: mac-addr: 00:08:00:4A:2F:93
[INFO] eeprom_main.c:mts_id_eeprom_inspect:303: imei: 359852053813557
[INFO] eeprom_main.c:mts_id_eeprom_inspect:304: capa-gps: yes
[INFO] eeprom_main.c:mts_id_eeprom_inspect:305: capa-din: no
[INFO] eeprom_main.c:mts_id_eeprom_inspect:306: capa-dout: no
[INFO] eeprom_main.c:mts_id_eeprom_inspect:307: capa-adc: no
[INFO] eeprom_main.c:mts_id_eeprom_inspect:308: capa-wifi: yes
[INFO] eeprom_main.c:mts_id_eeprom_inspect:309: capa-bluetooth: yes
[INFO] eeprom_main.c:mts_id_eeprom_inspect:310: capa-lora: no
[INFO] eeprom_main.c:mts_id_eeprom_inspect:318: mac-bluetooth: 00:00:00:00:00:00
[INFO] eeprom_main.c:mts_id_eeprom_inspect:325: mac-wifi: 00:23:A7:CE:EF:78
[INFO] eeprom_main.c:mts_id_eeprom_inspect:331: uuid: 7C8090BD2D3CEBA92670C459399B6EF9
[INFO] eeprom_main.c:mts_id_eeprom_inspect:341: lora-eui: "00:00:00:00:00:00:00:00"
[INFO] eeprom_main.c:mts_id_eeprom_inspect:343: lora-product-id:
[INFO] eeprom_main.c:mts_id_eeprom_inspect:344: lora-hw-version:

[Jeff Hatch]

Patrik,

I have figured out the problem. It is in a script /etc/init.d/remove-rs9113. It is removing the rs9113 driver because the hardware ID is not “MTCDT-0.1”. The intent of the script is to make sure that the rs9113 driver not be installed on hardware that doesn’t have the wifi module (licensing). The MTCDT-0.0 hardware doesn’t have the rs9113 module on-board. The MTCDTIP-0.0 does.

Your serial number (deviceId) looks like it is a later model with wifi so the capa-wifi value is set correctly. I believe that something is messed up coming out of production on this unit (they changed the hw-version). I think that the hw-version being set to MTCDTIP-0.0 has caused a bug when the device first boots, and the aforementioned script is incorrectly removing the rs9113 driver. Please file a portal case at https://support.multitech.com. This is an issue that needs to be fixed. In the mean time, I am not sure that there is a workaround.

Jeff

Jeff

[Jeff Hatch]

Patrik,

We can provide you with a package to install to put the rs9113 driver back on your device. There will be a couple of other steps to follow we will give you through the support portal.

Jeff

[Patrik Bengtsson]

Thank you for the help Jeff!

I’m adding a ticket thru the support portal. I also suspect that the drivers for the GPS is missing in the same way.

Patrik

[Jeff Hatch]

Patrik,

There were a number of bugs in the gps related code that have been fixed since AEP 1.4.4 that is on the IP67 you have. The driver level gps functionality works. It is at the application level where there were a large number of bugs due to the fact that the code used to work with a GPS module, and the module was upgraded to a GNSS module, the difference being in a lot of cases that NMEA strings began with GN instead of GP.

Jeff

[Patrik Bengtsson]

Jeff,

Ok, we’ll se what they can do, the reason I’m thinking that there also might be some missing drivers for GPS is the following from the boot.log;

Tue Mar 13 14:12:50 2018: udevd[422]: failed to execute '/lib/udev/gpsd.hotplug.wrapper' '/lib/udev/gpsd.hotplug.wrapper': No such file or directory
Tue Mar 13 14:12:50 2018: 
Tue Mar 13 14:12:50 2018: udevd[424]: failed to execute '/lib/udev/gpsd.hotplug.wrapper' '/lib/udev/gpsd.hotplug.wrapper': No such file or directory
Tue Mar 13 14:12:50 2018: 
Tue Mar 13 14:12:50 2018: udevd[425]: failed to execute '/lib/udev/gpsd.hotplug.wrapper' '/lib/udev/gpsd.hotplug.wrapper': No such file or directory
Tue Mar 13 14:12:50 2018: 
Tue Mar 13 14:12:50 2018: udevd[427]: failed to execute '/lib/udev/gpsd.hotplug.wrapper' '/lib/udev/gpsd.hotplug.wrapper': No such file or directory
Tue Mar 13 14:12:50 2018: 
Tue Mar 13 14:12:50 2018: udevd[431]: failed to execute '/lib/udev/gpsd.hotplug.wrapper' '/lib/udev/gpsd.hotplug.wrapper': No such file or directory
Tue Mar 13 14:12:50 2018: 

I still haven’t heard from the helpdesk but I think that’s because of our timezones..

Patrik

[Jeff Hatch]

Patrik,

That has more to do with the fact that gpsd is not running, and even if it was, I am not sure that the rule that is causing that is valid anymore. I’ve seen that on devices that are successfully reporting their location. Something that should get addressed, though.

Jeff

[Patrik Bengtsson]

Jeff,

It seems that the LTE got some problem after the firmware update (assuming), the modem does not seem to want to connect anymore but gives no error.

What would be the correct Firmware file for this device (version 1.4.4+) I can’t find it om the support site.

Patrik

[Jeff Hatch]

Patrik,

Did you re-install the device firmware or the modem firmware? Currently there isn’t a version beyond 1.4.4 for the IP67. However, we are in the process of releasing 1.4.13 that might work. It won’t fix your problem with the WiFi module driver though.

Jeff

[Patrik Bengtsson]

Jeff,

It’s the device firmware that I would like to reinstall, I think that I might have uploaded the wrong one when I have tried to debug the issue.

Still no reply from the support portal.

Patrik

[Jeff Hatch]

Patrik,

A support person came to me late yesterday, so he is starting to work on this case. We are trying to either find or re-generate the rs9113 driver package at the moment.

Jeff

[Jeff Hatch]

Patrik,

A support person came to me late yesterday, so he is starting to work on this case. We are trying to either find or re-generate the rs9113 driver package at the moment.

Jeff

[Patrik Bengtsson]

Jeff,

Excellent, thank you.

Could you provide a link for the correct device firmware in the meanwhile, I’d like to debug why LTE stopped working.

Patrik

[Author]

Posts