Raspberry Pi B + USB Wifi Dongle not Detecting

Hello Guys,

I have tried all the possible solutions for the latest osmc kernel for Raspberry Pi B+ to make my USB wifi dongle work but unfortunately, the Wireless Tab is not showing up.

Wireless info after connecting the USB:
root@osmc:~# ifconfig
eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
inet 192.168.0.143 netmask 255.255.255.0 broadcast 192.168.0.255
ether b8:27:eb:61:d8:1a txqueuelen 1000 (Ethernet)
RX packets 1839 bytes 721712 (704.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1314 bytes 178926 (174.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@osmc:~#
root@osmc:~# lsusb
Bus 001 Device 004: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
root@osmc:~# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

Logs Uploaded to : https://paste.osmc.tv/mahuwunoma

root@osmc:~# lsmod
Module Size Used by
mt7601u 95899 0
mac80211 762448 1 mt7601u
evdev 14131 1
cfg80211 602612 2 mac80211,mt7601u
rfkill 24099 2 cfg80211
snd_bcm2835 23575 0
snd_pcm 107463 1 snd_bcm2835
snd_timer 28501 1 snd_pcm
snd 77023 3 snd_timer,snd_bcm2835,snd_pcm
8021q 22254 0
garp 7537 1 8021q
stp 2126 1 garp
llc 5535 2 garp,stp
bcm2835_thermal 3538 0
bcm2835_gpiomem 3751 0
iptable_nat 2277 0
nf_conntrack_ipv4 8236 1
nf_defrag_ipv4 2087 1 nf_conntrack_ipv4
nf_nat_ipv4 7325 1 iptable_nat
nf_nat 18522 1 nf_nat_ipv4
nf_conntrack 122723 3 nf_conntrack_ipv4,nf_nat_ipv4,nf_nat
iptable_mangle 1900 0
iptable_filter 2184 0
uio_pdrv_genirq 3846 0
uio 9972 1 uio_pdrv_genirq
fixed 3033 0
ip_tables 13381 3 iptable_mangle,iptable_filter,iptable_nat
x_tables 26011 3 iptable_mangle,ip_tables,iptable_filter
ipv6 452418 36
root@osmc:~#

Dmesg Output:
[ 811.865319] usb 1-1.4: USB disconnect, device number 95
[ 812.158924] usb 1-1.4: new high-speed USB device number 96 using dwc_otg
[ 812.300910] usb 1-1.4: New USB device found, idVendor=148f, idProduct=7601
[ 812.300941] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 812.300958] usb 1-1.4: Product: 802.11 n WLAN
[ 812.300971] usb 1-1.4: Manufacturer: MediaTek
[ 812.300982] usb 1-1.4: SerialNumber: 1.0
[ 812.398939] usb 1-1.4: reset high-speed USB device number 96 using dwc_otg
[ 812.532608] mt7601u 1-1.4:1.0: ASIC revision: 76010001 MAC revision: 76010500
[ 812.535023] mt7601u 1-1.4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146____
[ 812.980824] mt7601u 1-1.4:1.0: EEPROM ver:0c fae:00
[ 813.171768] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.171897] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.171975] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.172158] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.172335] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.172475] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.172647] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.172928] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.173028] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.173129] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.173291] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.173428] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.173526] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.173587] mt7601u 1-1.4:1.0: Error: MCU resp urb failed:-71
[ 813.173685] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.173824] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.173882] mt7601u 1-1.4:1.0: Error: MCU resp evt:0 seq:5-4!
[ 813.173944] mt7601u 1-1.4:1.0: Error: RX urb failed:-71
[ 813.174002] mt7601u 1-1.4:1.0: Error: MCU resp urb failed:-71
[ 813.174053] mt7601u 1-1.4:1.0: Error: MCU resp evt:0 seq:5-4!
[ 813.174232] mt7601u 1-1.4:1.0: Error: MCU resp urb failed:-71
[ 813.174316] mt7601u 1-1.4:1.0: Error: MCU resp evt:0 seq:5-4!
[ 813.174402] mt7601u 1-1.4:1.0: Error: MCU resp urb failed:-71
[ 813.174449] mt7601u 1-1.4:1.0: Error: MCU resp evt:0 seq:5-4!
[ 813.174605] mt7601u 1-1.4:1.0: Error: MCU resp urb failed:-71
[ 813.174688] mt7601u 1-1.4:1.0: Error: MCU resp evt:0 seq:5-4!
[ 813.174773] mt7601u 1-1.4:1.0: Error: mt7601u_mcu_wait_resp timed out
[ 813.469003] mt7601u 1-1.4:1.0: Vendor request req:07 off:0080 failed:-71
[ 813.769022] mt7601u 1-1.4:1.0: Vendor request req:02 off:0080 failed:-71
[ 814.068926] mt7601u 1-1.4:1.0: Vendor request req:02 off:0080 failed:-71
[ 814.069097] mt7601u: probe of 1-1.4:1.0 failed with error -110

Kindly assist to make the USB wifi dongle working.

The stick looks defective, or it may not be getting enough power.

Hello Sam,

The stick works fine in windows 10 and I have checked with powered hub could see that it is not working.

It looks like a kernel bug. The driver is in tree, so should be resolved soon enough when we update the Raspberry Pi kernel.

Sam

Yes, I hope so… Is it possible to get the kernel to test?

I haven’t moved to a new kernel yet as there hasn’t been much motivation to do so. I’ll pick a new LTS soon. I’ll also bump 4.14 soon; which will likely have a backported solution if it’s indeed software related.

I think it will be better if we move to new kernel as soon as possible. It’s because all other Raspberry OSes uses the same kernel as osmc

Any workaround till the new kernel is implemented?

Please check the lsusb -vv result for the adapter:
Bus 001 Device 008: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.01
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x148f Ralink Technology, Corp.
idProduct 0x7601 MT7601U Wireless Adapter
bcdDevice 0.00
iManufacturer 1 (error)
iProduct 2 (error)
iSerial 3 (error)
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 74
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 160mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 8
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x08 EP 8 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x07 EP 7 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x09 EP 9 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)

The chance for regression in doing so is high. It’s not clear if this would even fix your problem yet, but there’s definitely a chance it would break things for other users.

You can build a newer kernel from source; but as I don’t have this hardware you will need to wait for an official update if you are reluctant to do this.