Re: Re: Reliable unreliability with D-Link DWL-122 USB

--- [email protected] wrote:
> Well its not obvious from your log how the prism2_usb module is being
> loaded so early...
<snip>
> 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.

Ah. Guilty as charged! I had the alias in /etc/modprobe.conf, thought I
needed it. Gone now. Here's what now happens on boot, with the sleep
removed, hal and usb.rc still disabled:

usbcore: registered new driver usbfs
usbcore: registered new driver hub
  [ ehci & uhci host controllers load, buses & hubs register ]
usb 2-1: new full speed USB device using uhci_hcd and address 2
prism2usb_init: prism2_usb.o: 0.2.1-pre26 Loaded
prism2usb_init: dev_info is: prism2_usb
usbcore: registered new driver prism2_usb
kernel: Writing 4096 bytes to ram @0x7e2ffe [etc.]
kernel: linkstatus=CONNECTED
  [ hotplug events for usb_host etc ]
usb.agent[2468]: Setup prism2_usb for USB product 2001/3700/132
default.hotplug: add module p80211
default.hotplug: add module prism2_usb
wlan.agent: WLAN startup on null (null)
default.hotplug: add driver prism2_usb
wlan.agent: WLAN register on wlan0 (prism2_usb)
default.hotplug: add net wlan0
usb.agent[2468]: Setup 0x00 0x00 for USB product 2001/3700/132
default.hotplug: invoke /etc/hotplug/net.agent ()
wlan.agent[2608]: WLAN p80211 starting!
wlan.agent[2639]: WLAN wlan0 registered.
modprobe: FATAL: Module wlan0 not found.
wland[2707]: wland daemon init successful
wland[2707]: netlink socket opened and bound successfully

Without the sleep, I still get the network hang, presumably due to all
the usb.agent activity after linkstatus=CONNECTED. That's OK though,
I'll just leave the sleep in.

> 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!

Before, even with the modprobe alias removed (as shown above).

> 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 assumed that the firmware upload was just something that the driver
did on initialisation, I've never had a specific script to do this,
just the distribution hotplug scripts. The only amendment I'd made to
hotplug scripts was to net.agent, adding wlan* to 'interfaces that are
registered after being "up"', which I didn't see documented anywhere
but which made things work.

> 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.

I'll try blacklisting prism2_usb and see if that affects my early
module loading.

Thanks once more Karl for your valued comments,

Dave


	
	
		
___________________________________________________________ 
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com