loss of wireless after joyride-1496 update

[Dan Krejsa]

Hi David & Richard,

David, I'll try your debugging tips next time this occurs, thanks...
Re. the IPv6 RADVD daemon, I don't think the Netgear router supports
that, so I'd have to use another machine; I'll consider it.

Richard, yes, the WPN824v2 is pre-N; the current firmware version is
V2.0.10_1.2.17. (I think incorporates the current and former
firmware versions. I upgraded the firmware to 2.0.10 after receiving
your mail. I did see the problem once with the new router firmware as
well as the old, but after several attempts the XO did associate and get
an IP address from the router's DHCP. I'll try to add some notes to the
wiki page.)

Thanks to both of you for your suggestions!

- Dan



On Sat, 2008-01-05 at 11:11 +0000, David Woodhouse wrote:
> On Thu, 2008-01-03 at 22:09 -0800, Dan Krejsa wrote:
> > Attached are the output from 'iwlist scan' and dmesg. 'quibble' is the
> > router I'm trying to connect to. It's a netgear WPN824v2.
> > 
> > After collecting these logs, and making another unsuccessful attempt to
> > connect to quibble (i.e. clicking on quibble's icon in the neighborhood
> > view, waiting for it to stop blinking; winds up with no white outline),
> > I ran 'iwlist scan' again. Then I went back to the neighborhood view and
> > lo and behold, I was connected to quibble.
> 
> This sounds like GUI confusion to me. First you say it didn't connect,
> and then you say it did. Please, use 'iwconfig' and 'ifconfig' to
> confirm for sure whether you were associated to the AP. And don't rely
> on Legacy IP -- run an RADVD dæmon advertising IPv6 addresses, which
> will be much more reliable at giving you addresses whenever you're
> associated.
> 
> If NetworkManager really is failing to associate, I'd like to see debug
> logs from the driver while it does so.
> 
> First, enable debugging by:
>  echo 0x6184 > /sys/module/libertas/parameters/libertas_debug
> 
> Then, run 'dmesg -c' to clear the kernel's log buffer. Then make the
> attempt to join the network, then run 'dmesg > somefile' to store the
> log buffer again. And mail the log to me, along with 'iwconfig' output
> showing the current state of the device. If you can repeat the process
> to show me both a working and a failing attempt to join the network,
> that would be useful. Thanks.
>