| View previous topic :: View next topic |
| Author |
Message |
nap
n00b
Joined: 18 Aug 2017
Posts: 10
|
 Posted: Tue Dec 05, 2017 6:41 pm Post subject: USB WiFi Adapter gives error -71 on reboot |
 |
|
Linux sonic 2.6.33.9-rt31-aldebaran-rt #1 SMP PREEMPT RT Thu Aug 27 21:42:34 CEST 2015 i686 Intel(R) Atom(TM) CPU Z530 @ 1.60GHz GenuineIntel GNU/Linux
The USB2 WiFi adapter on the embedded system I have (robot) fails to initialise (or be recognised), usually after a warm reboot.
When it works, lsusb gives:
| Code: | 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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
Bus 003 Device 002: ID ffff:0006
|
But when it doesn't work I get:
| Code: | 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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID ffff:0006
|
The specific error messages I get during the boot sequence are:
| Code: | * Early initialization ...
usb 2-1: new full speed USB device using uhci_hcd and address 2
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new full speed USB device using uhci_hcd and address 3
usb 2-1: device descriptor read/64, error -71
usb 2-1: device descriptor read/64, error -71
usb 2-1: new full speed USB device using uhci_hcd and address 4
usb 2-1: device not accepting address 4, error -71
usb 2-1: new full speed USB device using uhci_hcd and address 5
usb 2-1: device not accepting address 5, error -71
hub 2-0:1.0: unable to enumerate USB device on port 1
usb 3-2: new full speed USB device using uhci_hcd and address 2
* Mounting /proc ...
[ ok ]
[ 2.512129] usb 2-1: device descriptor read/64, error -71
* Caching service dependencies ...
[ 2.730083] usb 2-1: device descriptor read/64, error -71
[ 2.938099] usb 2-1: new full speed USB device using uhci_hcd and address 3
[ 3.056350] usb 2-1: device descriptor read/64, error -71
[ 3.275126] usb 2-1: device descriptor read/64, error -71
[ 3.483070] usb 2-1: new full speed USB device using uhci_hcd and address 4
[ 3.900112] usb 2-1: device not accepting address 4, error -71
|
I've tried all kinds of things to get it to work, but nothing seems to.
In addition to using lsusb I have tried all kinds of BIOS setting changes as well as two script based alternatives:
1) A script that unbinds then rebinds the hubs. It never discovers the WiFi, but always disables it if I run the script when the WiFi adapter is working (and I can't get the OS to re-recognise it using lsusb.
2) A small C program that resets a USB device on a given bus/device# using ioctl(fd, USBDEVFS_RESET, 0). Though it correctly resets a device, it is not able to discover one that isn't there.
Is there a way of getting Gentoo to rescan/reinitialise devices that are attached to the usb bus/hubs? A command that scans the USB hubs like the OS/BIOS does during the boot process?
Cheers,
Nap
If more info is needed, please let me know. |
|
| Back to top |
|
 |
lwlvl
n00b
Joined: 12 Dec 2017
Posts: 7
Location: Hamburg (Germany)
|
| Posted: Tue Dec 12, 2017 7:34 pm Post subject: |
|
|
| Does the stick get's enough power? Maybe re-try with an powered USB-Hub. |
|
| Back to top |
|
|
ZeuZ_NG
Guru
Joined: 10 Sep 2008
Posts: 453
Location: Near /dev/urandom | /dev/null
|
| Posted: Wed Dec 13, 2017 10:51 am Post subject: |
|
|
Sufring a little I found something that might help..
https://zedt.eu/tech/linux/restarting-usb-subsystem-centos/
_________________
| Intel Core i7 920. | Intel DX58SO Extreme. |
| 8gb DDR3 1666mHz | 1TB 7200 RPM WD HDD.|
Unix´s guru view of sex:
unzip ; strip ; touch ; grep ; finger ; \
mount ; fsck ; more ; yes ; umount ; sleep. |
|
| Back to top |
|
|
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Wed Dec 13, 2017 9:00 pm Post subject: |
|
|
| Errors like that usually mean a bad physical USB connection. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
