Re: Phantom wireless device
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 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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Phantom wireless device
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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Phantom wireless device
--On Thursday, August 20, 2009 13:01:10 -0500 Larry Finger wrote: What do you have in /etc/udev/rules.d/70-persistent-net.rules? See attached What does the command iwconfig show? excluding stuff on non-wireless devices: ra0 RT2860 Wireless ESSID:"Jones" Nickname:"RT2860STA" Mode:Managed Frequency=2.437 GHz Access Point: 00:13:33:09:A0:88 Bit Rate=54 Mb/s RTS thr:off Fragment thr:off Encryption key:8DBC-897E-37C0-758A-07A4-02BF-9DA3-EBAF Link Quality=100/100 Signal level:-56 dBm Noise level:-81 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 I'm wondering if your rename rules are tripping over the master device. FWI, the master0 wireless device will disappear in 2.6.32. I just don't see where it's getting the Intel identity of the device from. Weird. Rick 70-persistent-net.rules Description: Binary data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Phantom wireless device
Rick Jones wrote: > --On Thursday, August 20, 2009 12:20:35 -0400 John Mahoney > wrote: > >> Ubuntu just pushed new kernels. Did you just pick one up. I got the > message two days ago, but have not *rushed* into grabbing them. Maybe a > regression? > > I'm not using those kernels, I run a version of 2.6.29 slightly tweaked > for the Eee. I've been running the same kernel for months so nothing's > changed in that respect. What do you have in /etc/udev/rules.d/70-persistent-net.rules? What does the command iwconfig show? I'm wondering if your rename rules are tripping over the master device. FWI, the master0 wireless device will disappear in 2.6.32. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Phantom wireless device
--On Thursday, August 20, 2009 12:20:35 -0400 John Mahoney wrote: Ubuntu just pushed new kernels. Did you just pick one up. I got the message two days ago, but have not *rushed* into grabbing them. Maybe a regression? I'm not using those kernels, I run a version of 2.6.29 slightly tweaked for the Eee. I've been running the same kernel for months so nothing's changed in that respect. Thanks for the ideas though! Rick On Thu, Aug 20, 2009 at 8:38 AM, 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. 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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Phantom wireless device
Ubuntu just pushed new kernels. Did you just pick one up. I got the message two days ago, but have not *rushed* into grabbing them. Maybe a regression? On Thu, Aug 20, 2009 at 8:38 AM, 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. > > 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 > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Phantom wireless device
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. 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. Aug 20 12:17:44 mineee NetworkManager: starting... Aug 20 12:17:44 mineee NetworkManager: Found radio killswitch /org/freedesktop/Hal/devices/computer_rfkill_eeepc_wlan_wlan Aug 20 12:17:44 mineee NetworkManager: (eth0): new Ethernet device (driver: 'ATL1E') Aug 20 12:17:44 mineee NetworkManager: (eth0): exported as /org/freedesktop/Hal/devices/net_00_23_54_04_a2_7b Aug 20 12:17:44 mineee NetworkManager: (ra0): driver does not support SSID scans (scan_capa 0x00). Aug 20 12:17:44 mineee NetworkManager: (ra0): new 802.11 WiFi device (driver: 'rt2860') Aug 20 12:17:44 mineee NetworkManager: (ra0): exported as /org/freedesktop/Hal/devices/net_pci_1814_781 Aug 20 12:17:44 mineee NetworkManager: (ra0): driver does not support SSID scans (scan_capa 0x00). Aug 20 12:17:44 mineee NetworkManager: (ra0): new 802.11 WiFi device (driver: 'pcieport-driver') Aug 20 12:17:44 mineee NetworkManager: (ra0): exported as /org/freedesktop/Hal/devices/net_pci_8086_27d6 Aug 20 12:17:44 mineee NetworkManager: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Aug 20 12:17:44 mineee last message repeated 2 times Aug 20 12:17:48 mineee NetworkManager: (eth0): device state change: 1 -> 2 (reason 2) Aug 20 12:17:48 mineee NetworkManager: (eth0): preparing device. Aug 20 12:17:48 mineee NetworkManager: (eth0): deactivating device (reason: 2). Aug 20 12:17:48 mineee NetworkManager: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Aug 20 12:17:48 mineee NetworkManager: (ra0): device state change: 1 -> 2 (reason 2) Aug 20 12:17:48 mineee NetworkManager: (ra0): bringing up device. Aug 20 12:17:48 mineee NetworkManager: (ra0): preparing device. Aug 20 12:17:48 mineee NetworkManager: (ra0): deactivating device (reason: 2). Aug 20 12:17:48 mineee NetworkManager: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Aug 20 12:17:48 mineee NetworkManager: (ra0): device state change: 1 -> 2 (reason 2) Aug 20 12:17:48 mineee NetworkManager: (ra0): preparing device. Aug 20 12:17:48 mineee NetworkManager: (ra0): deactivating device (reason: 2). Aug 20 12:17:48 mineee NetworkManager: (ra0): device state change: 2 -> 3 (reason 0) Aug 20 12:17:48 mineee NetworkManager: (ra0): device state change: 2 -> 3 (reason 0) Aug 20 12:17:48 mineee NetworkManager: (ra0): supplicant interface state: starting -> ready Aug 20 12:17:48 mineee NetworkManager: (ra0): supplicant interface state: starting -> ready Aug 20 12:17:49 mineee avahi-daemon[3453]: Registering new address record for fe80::222:43ff:fe24:1b24 on ra0.*. Aug 20 12:17:53 mineee NetworkManager: Activation (ra0) starting connection 'Auto Jones' Aug 20 12:17:53 mineee NetworkManager: (ra0): device state change: 3 -> 4 (reason 0) Aug 20 12:17:53 mineee NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled... Aug 20 12:17:53 mineee NetworkManager: Activation (ra0) starting connection 'Auto Jones' Aug 20 12:17:53 mineee NetworkManager: (ra0): device state change: 3 -> 4 (reason 0) Aug 20 12:17:53 mineee NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled... Aug 20 12:17:53 mineee NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) started... Aug 20 12:17:53 mineee NetworkManager: Activation (ra0) Stage 2 of 5 (Device Configure) scheduled... Aug 20 12:17:53 mineee NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) complete. Aug 20 12:17:53 mineee NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) started... Aug 20 12:17:53 mineee NetworkManager: Activation (ra0) Stage 2 of 5 (Device Configure) scheduled... Aug 20 12:17:53 mineee NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) complete. Aug 20 12:17:53 mineee NetworkManager: Activation (ra0) Stage 2 of 5 (Device Configure) starting... Aug 20 12:17:53 mineee NetworkManager: (ra0): device state change: 4 -> 5 (reason 0) Aug 20 12:17:53 mineee
