Re: Hotplug works, Reboot works, Cold Start - no work

	I can verify I am not getting that giving up error on my system. 
It's Debian (testing).  I'm using the usb-ohci module since I have a
VIA chipset.  I see you are using uhci.  Maybe trying with usb-uhci
would yield different results?  Also where are your plugging the
device in?  Do you have a hub you could try it with?


You wrote:

> On Monday 12 January 2004 5:54 am, CE wrote:
> > 	Hallo David,
> > I believe this is the behavior of the driver, as the modules do
> > not get loaded until the device is brought up with something like
> > ifup wlan0 or hotplug takes over.  Perhaps you could put something
> > like ifup wlan0 in one of the startup scripts?
> >
> No, I don't think that's the case, as it does work without this when
> rebooting the system.   I think the lines which gives it away are:
>    hub.c: new USB device 00:1f.2-1, assigned address 2
>    usb.c: USB device not responding, giving up (error=-110)
> 
> During a reboot, (remember I haven't loaded the drivers manually at
> this stage) the interface is detected automatically:
>    hub.c: new USB device 00:1f.2-1, assigned address 2
>    usb.c: USB device 2 (vend/prod 0xd5c/0xa002) is not claimed by
>    any active driver.
> 
> I thought that maybe the usb adaptor needed to "warm up" but that
> doesn't explain why hotplugging works. This morning, I booted from
> cold with the adaptor disconnected.  When I plugged it in , it
> worked immediately.
> 
> Jan 12 06:40:04 linux kernel: hub.c: new USB device 00:1f.2-1,
> assigned address 2 Jan 12 06:40:04 linux kernel: usb.c: USB device 2
> (vend/prod 0xd5c/0xa002) is not claimed by any active driver. Jan 12
> 06:40:07 linux kernel: usbdfu.c: USB Device Firmware Upgrade (DFU)
> handler v0.11 Jan 12 06:40:07 linux kernel: usb.c: registered new
> driver usbdfu Jan 12 06:40:07 linux insmod: Using
> /lib/modules/2.4.21-166-default/kernel/drivers/usb/usbdfu.o Jan 12
> 06:40:07 linux insmod: Symbol version prefix '' Jan 12 06:40:08
> linux kernel: at76c503.c: Generic Atmel at76c503/at76c505 routines
> v0.11 Jan 12 06:40:08 linux kernel: at76c503-rfmd.c: Atmel at76c503
> (RFMD) Wireless LAN Driver v0.11 Jan 12 06:40:08 linux kernel:
> usbdfu.c: Downloading firmware for USB device 2... Jan 12 06:40:08
> linux kernel: usb.c: registered new driver at76c503-rfmd Jan 12
> 06:40:08 linux insmod: Using
> /lib/modules/2.4.21-166-default/kernel/drivers/usb/at76c503.o Jan 12
> 06:40:08 linux insmod: Symbol version prefix '' Jan 12 06:40:08
> linux insmod: Using
> /lib/modules/2.4.21-166-default/kernel/drivers/usb/at76c503-rfmd.o
> Jan 12 06:40:08 linux kernel: usbdevfs: USBDEVFS_CONTROL failed dev
> 2 rqt 128 rq 6 len 18 ret -71 Jan 12 06:40:08 linux
> /etc/hotplug/usb.agent[1937]: cannot get config descriptor: Protocol
> error Jan 12 06:40:08 linux kernel: usbdevfs: USBDEVFS_CONTROL
> failed dev 2 rqt 128 rq 6 len 18 ret -110 Jan 12 06:40:08 linux last
> message repeated 49 times Jan 12 06:40:08 linux
> /etc/hotplug/usb.agent[1937]: cannot get config descriptor:
> Connection timed out Jan 12 06:40:08 linux kernel: usbdevfs:
> USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -110 Jan 12
> 06:40:08 linux last message repeated 19 times Jan 12 06:40:08 linux
> kernel: hub.c: already running port 1 disabled by hub (EMI?),
> re-enabling... Jan 12 06:40:08 linux kernel: usb.c: USB disconnect
> on device 00:1f.2-1 address 2 Jan 12 06:40:08 linux kernel:
> usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -110
> Jan 12 06:40:08 linux /etc/hotplug/usb.agent[1937]: cannot get
> config descriptor: No such device Jan 12 06:40:08 linux kernel:
> hub.c: new USB device 00:1f.2-1, assigned address 3 Jan 12 06:40:08
> linux kernel: at76c503.c: $Id: at76c503.c,v 1.35 2003/07/30 06:31:51
> jal2 Exp $ compiled Jan 10 2004 17:43:39 Jan 12 06:40:08 linux
> kernel: at76c503.c: firmware version 1.101.2 #84 (fcs_len 4) Jan 12
> 06:40:08 linux kernel: at76c503.c: device's MAC 00:30:bd:63:e3:02,
> regulatory domain ETSI (Europe - (Spain+France) (id 48) Jan 12
> 06:40:08 linux kernel: at76c503.c: registered wlan0
> 
> Any further thoughts?
>