Re: Phantom wireless device

[Rick Jones <rick activeservice co uk>]

Strangely, this problem has gone away as mysteriously as it appeared.

I was away from home last w/e, with netbook (which I almost never shut down, just stays on standby). I opened it up, turned off WiFi, tried to get online with MB dongle, at which point the whole OS locked up. I gave up and powered it down, and didn't in fact use it for 2 days until I was back home. Booted up, and the wireless device was working normally.

On reflection I think it may have been a BIOS screwup. When I tried to recover by re-booting previously, I didn't actually power down, just did a sytem restart. The full power-off/on which I was forced into because of it crashing must have been what fixed it, and is presumably a deeper initialisation of BIOS, ACPI etc than just a restart.

I think Linux is off the hook!

-- 
Cheers
Rick

--On Friday, August 21, 2009 10:07:08 -0500 Dan Williams <dcbw redhat com> wrote:

> On Thu, 2009-08-20 at 13:38 +0100, Rick Jones wrote:
> > I've suddenly started getting strange behaviour with my WiFi device.
> > It's appearing twice in the NM applet with different names.
> > 
> > It's actually a RaLink RT2860, but it's additionally being identified
> > as Intel 82801G. Looking in the logs both IDs are device ra0, which is
> > getting NM a bit confused. Sometime it connects, sometimes it fails
> > and hangs. The NM daemon also dies periodically which I suspect is
> > related.
> 
> Maybe, any chance you can run with --no-daemon in gdb (remember to
> 'handle SIGCHLD nostop pass' and 'handle SIGTERM nostop pass') and get a
> backtrace?
> 
> Also, please run 'nm-tool' to get the definitive device list when you
> see this happening to ensure that it's not a bug in libnm-glib.  I've
> seen something like this with mobile broadband adapters in the past few
> days that I haven't been able to characterize yet (don't have a reliable
> reproducer) so it may actually be libnm-glib's fault.
> 
> Dan
> 
> 
> > I can't think of any system change that's induced this, it's
> > definitely not related to updating NM. I'm running
> > 0.7.1.git.5.272c6a626-0ubuntu1~nm1~jaunty from Launchpad, and it's
> > been working fine since I installed this version until a few days ago.
> > Re-booting doesn't fix it.
> > 
> > I suspect it may be a udev issue, but I don't know where to look. Any
> > ideas?
> > 
> > Typical extract of the log file is attached, with everything happening
> > twice on ra0.
> > _______________________________________________
> > NetworkManager-list mailing list
> > NetworkManager-list gnome org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> 
>