Dave
Well its not obvious from your log how the prism2_usb module is being loaded so early, but the fact that you have:
kernel: prism2usb_init: prism2_usb.o: 0.2.1-pre26 Loaded
before
kernel: usb 2-1: new full speed USB device using uhci_hcd and address 2
means there must be some mechanism in your system.
Possibilities are a boot script that force loads certain modules (do you have an /etc/modules or similar?), or the (now old style) 'alias wlan0 prism2_usb' in a modules.alias or modprobe* file or similar.
Is your firmware upload and linkstatus=CONNECTED happening
before or after the net.agent event for wlan0? If its before, then your mechanism is even doing all that good stuff as well!
For me, the net.agent hotplug event results in my own script to do firmware upload (I put in hotplug.d/net), and the distribution scripts then bringing up the card and establishing the use of it.
I'm about to do another post where I can remove the 'sleep', by avoiding prism2_usb being loaded on hotplug and forcibly loading it myself later on when I know it will be 'safe'. That won't help you though - since you somehow seem to have a force loading early on. If you can find it, then we will be back in business.
Karl
>
> From: Dave Jenkins <[email protected]>
> [ syslogd restart, klogd, RAM, PCI resources, CPU, lm_sensors,
> SELinux, PCI, ACPI, pnp ]
> pnp: PnP ACPI: found 12 devices
> kernel: usbcore: registered new driver usbfs
> kernel: usbcore: registered new driver hub
> [ Then various pci, pnp, apm stuff ]
> kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> [ Then acpi, isapnp, agpgart, ide... ]
> kernel: usbcore: registered new driver hiddev
> usbcore: registered new driver usbhid
> [ Then hci, md ]
> kernel: NET: Registered protocol family 2 [then 1, 17]
> [ Then IP, TCP, IPsec ]
> kernel: ACPI wakeup devices:
> kernel: SLPB PCI0 USB0 USB1 USB2 USB6 USB7 USB8 USB9 LAN0 UAR1 ECP1
> [ Then device-mapper, kjournald ]
> [ Next come lots of i2c-related hotplug add events, e.g. ...]
> default.hotplug[4122]: arguments (module) env (SUBSYSTEM=module
> OLDPWD=/ DEVPATH=/module/i2c_isa PATH=/bin:/sbin:/usr/sbin:/usr/bin
> ACTION=add PWD=/etc/hotplug HOME=/ SHLVL=2 DEBUG=yes SEQNUM=608
> _=/bin/env)
> [ Then floppy, then eth0 driver (onboard) ]
> kernel: prism2usb_init: prism2_usb.o: 0.2.1-pre26 Loaded
> kernel: prism2usb_init: dev_info is: prism2_usb
> usbcore: registered new driver prism2_usb
> [ Then ACPI/PCI IRQ stuff ]
> kernel: ehci_hcd 0000:00:10.3: EHCI Host Controller [& bus, hub]
> kernel: USB Universal Host Controller Interface driver v2.2 [& bus,
> hub]
> kernel: usb 2-1: new full speed USB device using uhci_hcd and address 2
> [ Then firmware upload, linkstatus=CONNECTED. ]
>
> I'm still not sure quite how the prism2_usb initialisation is
> triggered, but it happens amidst lots of other hardware initialisation
> and immediately after eth0. Neither eth0 nor wlan0 is set to start on
> boot in /etc/sysconfig .
>
-----------------------------------------
Email provided by http://www.ntlhome.com/
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.