Re: USB adapter won't work at boot

I've seen the same kind of behavior w/RH on 2.6.x as well. Seems to me
it's possible your problem with locating the firmware during system boot
is that /usr hasn't been mounted at the time the hotplug subsystem is
trying to load the Orinoco driver, and thus the
/usr/lib/hotplug/firmware/<orinoco fw file> isn't available yet. (At
least, that was the problem I had on 2.6.x, so hopefully this message is
worth something)

 // Thomas

 
On Mon, 2004-02-02 at 13:06, Francisco Martínez wrote:
> Hi everybody,
> 
> I have a Buffalo USB adapter and Red Hat 9 installed on my computer. 
> Then I installed Øystein Olsen RPM for my kernel (2.4.20-8), plugged
> the adapter and I was happy to notice that it worked.  Well, it worked
> until next reboot.
> 
> After the reboot, the LED on my Buffalo did not light up…  So I
> checked /var/log/messages
> 
>  
> 
> Feb  2 00:12:52 [someserver] kernel: usb.c: registered new driver
> usbdevfs
> 
> Feb  2 00:12:52 [someserver] kernel: usb.c: registered new driver hub
> 
> Feb  2 00:12:52 [someserver] kernel: usb-uhci.c: $Revision: 1.275 $
> time 17:59:01 Mar 13 2003
> 
> Feb  2 00:12:52 [someserver] kernel: usb-uhci.c: High bandwidth mode
> enabled
> 
> Feb  2 00:12:52 [someserver] kernel: usb-uhci.c: USB UHCI at I/O
> 0xd800, IRQ 10
> 
> Feb  2 00:12:52 [someserver] kernel: usb-uhci.c: Detected 2 ports
> 
> Feb  2 00:12:52 [someserver] kernel: usb.c: new USB bus registered,
> assigned bus number 1
> 
> Feb  2 00:12:52 [someserver] kernel: usb-uhci.c: USB UHCI at I/O
> 0xdc00, IRQ 10
> 
> Feb  2 00:12:52 [someserver] kernel: usb-uhci.c: Detected 2 ports
> 
> Feb  2 00:12:52 [someserver] kernel: usb.c: new USB bus registered,
> assigned bus number 2
> 
> Feb  2 00:12:53 [someserver] kernel: usb-uhci.c: v1.275:USB Universal
> Host Controller Interface driver
> 
> Feb  2 00:12:53 [someserver] kernel: usb.c: registered new driver
> hiddev
> 
> Feb  2 00:12:53 [someserver] kernel: usb.c: registered new driver hid
> 
> Feb  2 00:12:53 [someserver] kernel: usb.c: USB device 2 (vend/prod
> 0x411/0xb) is not claimed by any active driver.
> 
> Feb  2 00:12:53 [someserver] kernel: usb.c: registered new driver
> Orinoco USB
> 
> Feb  2 00:12:53 [someserver] kernel: orinoco_usb.c: No firmware to
> download
> 
> Feb  2 00:12:54 [someserver] kernel: orinoco_usb.c v0.2.2 (Manuel
> Estrada Sainz <[email protected]>)
> 
>  
> 
> For some weird reason, the driver is recognized after the device.
> 
> So I re-plugged (unplug-plug) the device…
> 
>  
> 
> Feb  2 00:15:45 [someserver] kernel: usb.c: USB disconnect on device
> 00:11.2-1 address 2
> 
> Feb  2 00:15:48 [someserver] kernel: remove_proc_entry:
> usb-00:11.2-1/loading busy, count=1
> 
> Feb  2 00:15:48 [someserver] kernel: remove_proc_entry:
> firmware/usb-00:11.2-1 busy, count=1
> 
> Feb  2 00:15:48 [someserver] kernel: de_put: deferred delete of
> usb-00:11.2-1
> 
> Feb  2 00:15:49 [someserver] kernel: orinoco_usb.c: Orinoco USB device
> now attached wlan0
> 
> Feb  2 00:15:52 [someserver] /etc/hotplug/usb.agent: Setup orinoco_usb
> for USB product 411/b/0
> 
>  
> 
> And now it works!
> 
> I rebooted several times and also did some cold boots, always with the
> same behavior.
> 
> I suspect it has to do with linux cold-plug issue, something I don’t
> quite understand at the moment.  So any advice is welcome.
> 
> I hope someone could give me some hints, even if this issue gets off
> topic.  I’m really lost in this one.
> 
> Thanks,
> 
> Francisco
> 
> 
> 
> ______________________________________________________________________
> _______________________________________________
> orinoco-usb-devel mailing list
> [email protected]
> http://ranty.pantax.net/mailman/listinfo/orinoco-usb-devel
-- 
                                [email protected]
Something funny should appear   110 Spit Brook Rd
in this space any day now...    Nashua, NH 03045
                                Phone: +1 (603)785-9780