On Wed, 2008-03-12 at 20:37 +0000, Karl Relton wrote:
> On Wed, 2008-03-12 at 14:08 +0000, Richard Kennedy
wrote:
> > Hi Karl,
> >
> > The latest svn with this auto enable doesn't work
very well with
> > network_manager, at least for me anyway.
> >
> > It's ok on boot, but if I unload/load the module
the network interface
> > never gets brought up. The firmware is loaded ok
but nothing else
> > happens. I guess it's some sort of timing issue,
or maybe just the
> > driver state getting confused.
> >
> > I added this patch so I can turn off the auto
enable.
> > Adding p80211 wlan_auto_enable=0 to
/etc/modprobe.conf makes it all work
> > as I expect.
> >
> > However I'm not sure if this is the right
approach,so I'll see if I can
> > work out why the net interface never comes up.
> >
> > cheers
> > Richard
> >
>
> Hi Richard
>
> The code in svn isn't how I would prefer it - it has
the register_netdev
> before the card is first initialised. I would do it the
other way round.
> Solomon has his reasons for the way it currently is,
but it does leave
> us with potentially bad side effects at the moment.
>
> I'm surprised things are working well for you on boot
up. Have you
> checked your log to see that firmware is actually being
loaded on boot
> (e.g. in your syslog can you see the firmware version
that you would
> expect?). With the current code, my suspicion is that
firmware load on
> boot is doomed to fail, unless you have some sleep
statement(s)
> somewhere in your wlan-udev.sh/shared/shared.prism2
scripts.
>
> A module unload/reload should result in the same
process, since the
> driver sees the hardware afresh and goes through the
same sequence.
> Similarly networkmanager ought to have forgot about the
interface and
> then pick it up again (but I've never really used it
myself).
>
> Karl
Hi Karl,
I checked and the firmware _does_ get loaded properly at
boot time, but
it fails on unload/reload! I guess it's just luck that udev
is kind of
late to startup so the usb card is settled before it starts
loading the
firmware.
Also Networkmanager doesn't do much during boot either,
because it has
to wait for the user to log on to get the WEP keys from the
default
keyring. In the reload case NM starts trying to setup the
card
immediately which I think might break things too -- as there
is nothing
to stop the WEXT functions if the card's not ready.
Maybe all(?) the WEXT functions should include a check
something like
this?
if ( wlandev->msdstate != WLAN_MSD_RUNNING ) return
-EBUSY;
disabling the auto enable works for me though 
Richard
_______________________________________________
Linux-wlan-devel mailing list
Linux-wlan-devel lists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-
wlan-devel
|
