On Fri, 17 Oct 2003, Lauri Ojantakanen wrote:
> Hi
>
> I have the same problem with my actiontec built-in prism2_usb.
>
> Under 2.4.18 it seems to work ok but on 2.6.0-test7 I get folllowing to log
> messages:
>
> drivers/usb/core/usb.c: registered new driver usbfs
> drivers/usb/core/usb.c: registered new driver hub
> drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver
> v2.1
> uhci-hcd 0000:00:07.2: UHCI Host Controller
> uhci-hcd 0000:00:07.2: irq 5, io base 00001020
> uhci-hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 2 ports detected
> hub 1-0:1.0: new USB device on port 1, assigned address 2
> hub 1-1:1.0: USB hub found
> hub 1-1:1.0: 2 ports detected
> hub 1-0:1.0: new USB device on port 2, assigned address 3
> drivers/usb/core/config.c: invalid interface number (1/1)
> usb 1-2: can't read configurations, error -22
> hub 1-0:1.0: new USB device on port 2, assigned address 4
> drivers/usb/core/config.c: invalid interface number (1/1)
> usb 1-2: can't read configurations, error -22
> usbfs: USBDEVFS_CONTROL failed cmd lsusb dev 2 rqt 128 rq 6 len 256 ret -32
> usbfs: USBDEVFS_CONTROL failed cmd lsusb dev 2 rqt 128 rq 6 len 256 ret -32
>
> Two last lines come from lsusb -v.
> I cannot get interface wlan0 up after inserting prism2_usb and p80211 modules.
This device is in violation of the USB 2.0 specification. The line
> drivers/usb/core/config.c: invalid interface number (1/1)
means that the device claims to have only 1 interface and that interface
is number 1. However, the USB spec says in section 9.2.3:
Within each configuration, each interface descriptor contains
fields that identify the interface number and the alternate
setting. Interfaces are numbered from zero to one less than the
number of concurrent interfaces supported by the configuration.
This means that with only 1 interface in the configuration, the interface
should be number 0. Although the old configuration handler in 2.4 doesn't
check for such violations, the new code in 2.6.0 does.
Ultimately the best solution is for the manufacturer to fix the device.
Maybe a firmware upgrade would do the trick.
Alan Stern
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
