Wifi config on a Multitech mLinux Conduit


#1

Can anyone help me configure a Multitech mLinux Conduit to work over wifi?

I have set up my interfaces file:

iface wlan0 inet dhcp
wpa-conf /var/config/wpa_supplicant.conf
wpa-driver nl80211

And I have set up /var/config/wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1

network={
key_mgmt=WPA-PSK
ssid=“PlusnetWireless9xxxxx”
scan_ssid=1
psk=“xxxxxxxxxx”
}
…which I think is correct. I’ve got a little USB wifi thingy that works fine on a Raspberry Pi and plugged it into the USB port on the back of the Conduit.

When I try to start up the wifi – ifup wlan0 – I get:

Successfully initialized wpa_supplicant
rfkill: Cannot open RFKILL control device
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
Could not read interface wlan0 flags: No such device
wlan0: Failed to initialize driver interface
ifconfig: SIOCGIFFLAGS: No such device

Grateful for any help.


(Jac Kersing) #2

Obvious question first, do you have a compatible wifi adapter? (Which adapter are you using? Run lsusb and post the output please)
Keep in mind the RPi supports different (more) adapters.


#3

I know of someone that did get wifi working on mLinux. As far as I understood he had to recompile the kernel to get the correct drivers included and working.


#4

Here’s the output from lsusb @kersing. Is there a list of compatible adapters?

Bus 001 Device 002: ID 0424:2534 Standard Microsystems Corp.
Bus 002 Device 002: ID 04e2:1412 Exar Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0403:6014 Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC
Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter


(Jac Kersing) #5

@markstanley
To check if your dongle is recognized, try loading the modules by hand:
cd /lib/modules/3.12.27/kernel/drivers/net/wireless/rtlwifi/rtl8192c modprobe ./rtl8192c-common.ko cd ../rtl8192cu/ modprobe ./rtl8192cu.ko ifconfig -a

If you are lucky the modules load and recognize your hardware. If not you’re out of luck and the dongle is not supported.
People report mixed results with the driver on desktop Linux systems (low speed, dropped connections) so even if supported the results might not be what you expect.


#6

@kersing

Hi Jac,
I followed your instructions to load the modules. I got no error messages so I presume they loaded ok. ifconfig -a shows:

eth0 Link encap:Ethernet HWaddr 00:08:00:4A:06:33
inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:23 Base address:0xc000

gre0 Link encap:UNSPEC HWaddr 00-00-00-00-FF-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1476 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

gretap0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1462 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:187 errors:0 dropped:0 overruns:0 frame:0
TX packets:187 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:22230 (21.7 KiB) TX bytes:22230 (21.7 KiB)

tunl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

…I presume I should expect to see wlan0 in the ifconfig if it was working?

Is there a list of compatible wifi adapters for the Conduits? I couldn’t find one on the Multitech site.


(Jac Kersing) #7

You can check the output of lsmod to see if the modules were loaded and dmesg to check for any output generated by the modules.
I’m not aware of a list of compatible adapters. You could ask MultiTech on their forum…


#8

Thanks very much Jac,
lsmod shows the modules loaded ok. Dmesg gave an interesting clue:

rtl8192cu: Chip version 0x10
rtl8192cu: MAC address: 00:13:ef:30:30:7e
rtl8192cu: Board Type 0
rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
usbcore: registered new interface driver rtl8192cu
rtlwifi: Loading alternative firmware rtlwifi/rtl8192cufw.bin
rtlwifi: Firmware rtlwifi/rtl8192cufw_TMSC.bin not available

I raised a query on the Multitech forum yesterday, and will pursue a list of compatible adapters. We won’t be the only ones keen to connect over wifi. I’ll update here and the wiki when I get an answer.

Thanks for your help, Mark


(Christian Molson) #9

I have a Wi-Fi adapter based on the rt2870 chip. I had a similar error, it detected the card but said it couldn’t find rt2870.bin. I downloaded this bin file from the kernel git repo, placed it in /lib/firmware/rt2870.bin and was able to connect using the same wpa_supplicant.conf and interfaces file. I suspect if you find the firmware for your device and place it in the correct location it should work.


#10

Hello,
I just bought a Belkin wireless USB device, with a Realtek 8192cu chipset inside.
After plugged in the Multitech mlinux conduit, I see that modules are loaded well.
It fails when trying to load the firmware files.

Snipped from dmesg:

usb 1-2.4: new high-speed USB device number 23 using atmel-ehci
usb 1-2.4: New USB device found, idVendor=050d, idProduct=1004
usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2.4: Product: 802.11n WLAN Adapter
usb 1-2.4: Manufacturer: Realtek
usb 1-2.4: SerialNumber: 00e04c000001
rtl8192cu: Chip version 0x11
rtl8192cu: MAC address: c0:56:27:80:28:27
rtl8192cu: Board Type 0
rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
rtlwifi: Loading alternative firmware rtlwifi/rtl8192cufw.bin
rtlwifi: Firmware rtlwifi/rtl8192cufw_TMSC.bin not available

By doing a modinfo on rtl8192cu, I got:

root@mtcdt:/lib/modules/3.12.27/kernel/drivers/net/wireless/rtlwifi# modinfo rtl8192cu | grep firmware
firmware: rtlwifi/rtl8192cufw_TMSC.bin
firmware: rtlwifi/rtl8192cufw_B.bin
firmware: rtlwifi/rtl8192cufw_A.bin
firmware: rtlwifi/rtl8192cufw.bin

I found these files at https://github.com/TI-OpenLink/firmwares/tree/master/rtlwifi.
I followed the advice of @cmolson to create /lib/firmware and putting the 4 firmware files into it, but this did’nt help.

I am stuck now, and suspect that the solution is not so far.
If someone could help me, please.
Louis.


#11

I found a working solution at https://www.debian-fr.org/t/installation-de-clef-usb-wifi-netgear-wna1000m/68643/5

The rtl8192cufw_TMSC.bin file has to be put at /lib/firmware/rtlwifi directory.
Note: this is working in mLinux kernel version 3.12.27

Now ifconfig -a is showing wlan0 device.


#12

That’s awesome, well done @Louis :slight_smile:


#13

You’r welcome.
In addition, note that in the config file /etc/network/interfaces, the “allow-hotplug wlan0” trick does not make wlan0 interface up while booting without manual intervention.
I must use the normal way: “auto wlan0” to make it working


#14

Hello Louis,
I’m not sure the auto wlan0 is really needed as stated in the /etc/network/interfaces :

#Wifi client
#NOTE: udev rules will bring up wlan0 automatically if a wifi device is detected
#and the wlan0 interface is defined, therefore an "auto wlan0" line is not needed.
#If "auto wlan0" is also specified, startup conflicts may result.

#15

in my case, the auto keyword is needed.
Try to remove it, and use “allow hotplug”.
But for me, the wlan0 itf did not if-up


#16

hi Louis,
I have also a belkin wifi dongle seen as a “rtl8192cu” in the dmesg logs; (under mLinux kernel version 3.12.27 too)
I tried to put the FW files as you suggested (in /lib/firmware/rtlwifi) but no success in showing up the WLAN0 :-/

Actually when the module is loaded ,dmesg gives a “Firmware is too big” error.

rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin
rtlwifi:rtl_fw_cb():<0-0> Firmware is too big!

any hints in this ?
cheers
Rico


#17

i guess the firmware file is not the good one, or is altered. Try to cross verify other sources of download for the fw file.
When you remove the firmware file, what is the full path written in the error in the log file ?


(Mark Stanley) #18

Hi Rico - did you solve this? I’m getting the same issue.

Mark


#19

Hi Mark,
sorry for not having replied to your question.
I didn’t succeded in making running the wifi dongle so I kept the GW connected to Eth cable.
yet I’m still interested in getting hints :slight_smile: and from your side ? how did you solve it ?

cheers
Rico


(Osman) #21

Hi,

I tried to configure WiFi according to your method on my multitech conduit which ships with preinstalled WiFi module. But when i ran the command

ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:00:4A:37:2B
inet addr:192.168.0.101 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::208:ff:fe4a:372b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:166 errors:0 dropped:0 overruns:0 frame:0
TX packets:135 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14771 (14.4 KiB) TX bytes:14582 (14.2 KiB)
Interrupt:23 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

This did not show any wifi0. Any help in this matter?