Karmic Upgrade Networkmanager No Longer Has Wireless

Bug #482721 reported by Félim Whiteley
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

After the set of updates on Friday (13/11/2009 see attached updates log) Network Manager has stopped seeing the intel 3945 wireless card on my Dell 1520 inspiron. It was working perfectly prior to the update, it's not related to the kill switch issue people appear to be having as I don't touch the hard button. I'm not sure which update broke it.

Revision history for this message
Félim Whiteley (felimwhiteley) wrote :
Revision history for this message
Félim Whiteley (felimwhiteley) wrote :

Should mention it turns up fine in dmesg, iwconfig also shows it as there but not associated. Network Manager doesn't even show it though. I've attached dmesg output, I later after boot switch the kill switch on and off in case any interesting info could be gleaned.

Revision history for this message
Félim Whiteley (felimwhiteley) wrote :

Syslog seems to be reporting NetworkManager stopping the wireless card becasue of "reason 2". Attached log.

(Extra info, it's 64bit Kubuntu Karmic fresh install, full disk encryption from the alternate CD)

Philip Muškovac (yofel)
affects: ubuntu → linux (Ubuntu)
Andy Whitcroft (apw)
tags: added: kernel-series-unknown
Revision history for this message
Félim Whiteley (felimwhiteley) wrote :

I notice it's (or what looks like it) getting logged as a potential bug against the kernel? Just tried the old initial vmlinuz-2.6.31-14-generic and it does not work either.

tags: added: karmic regression-potential
removed: kernel-series-unknown
Revision history for this message
Félim Whiteley (felimwhiteley) wrote :

Just an update on past few kernel updates, none have fixed the issue, I've even tried the Karmic backport wireless modules to no avail. Current Kernel is:

2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64 GNU/Linux

Attached a dmesg again in case of use. again it appears in dmesg but network manager sees no card.

Revision history for this message
Félim Whiteley (felimwhiteley) wrote :

Just checked the NetworkManager log mesages from syslog and unless I'm reading it wrong it's detecting the wlan0, then correctly detecting a killswitch but then incorrectl saying I've activated it... I did not.

Revision history for this message
Félim Whiteley (felimwhiteley) wrote :
Download full text (6.2 KiB)

Ok seems I misunderstood the use of the kernel backports module. so lets ignore that! But I've discoverd what appears to be happening, although it's beyond me why. I had Network Manager open, the "Enable Wireless" checkbox is disabled as it believes there is no Wifi card. I also open syslog. I flicked the hardware kill switch from the on to off position.

For a brief second the "Enable Wireless" became clickable, the syslog reported me sending an enable to the card but then almost immediatly it sent a kill, thereby greyout out the tickbox again and printing the kill commands in the syslog. I did this a couple of times, the last dumping a whole load of debuging info by the looks of it (possibly unrelated). Hope this helps..

To clarify;
 - the switch in the on position does nothing
 - switch to off momentarily activates the card but immediatly kills it again

Dec 15 14:20:28 endeavour NetworkManager: <info> Wireless now enabled by radio killswitch
Dec 15 14:20:28 endeavour NetworkManager: <info> (wlan0): bringing up device.
Dec 15 14:20:28 endeavour kernel: [17291.930773] iwl3945 0000:0c:00.0: firmware: requesting lbm-iwlwifi-3945-2.ucode
Dec 15 14:20:28 endeavour kernel: [17292.003862] iwl3945 0000:0c:00.0: loaded firmware version 15.32.2.9
Dec 15 14:20:28 endeavour kernel: [17292.004037] iwl3945 0000:0c:00.0: Radio disabled by HW RF Kill switch
Dec 15 14:20:28 endeavour NetworkManager: <info> Wireless now disabled by radio killswitch
Dec 15 14:21:15 endeavour NetworkManager: <info> Wireless now enabled by radio killswitch
Dec 15 14:21:15 endeavour NetworkManager: <info> (wlan0): bringing up device.
Dec 15 14:21:15 endeavour kernel: [17339.328654] iwl3945 0000:0c:00.0: Radio disabled by HW RF Kill switch
Dec 15 14:21:16 endeavour NetworkManager: <info> Wireless now disabled by radio killswitch
Dec 15 14:21:25 endeavour NetworkManager: <info> Wireless now enabled by radio killswitch
Dec 15 14:21:25 endeavour kernel: [17349.698805] BUG: scheduling while atomic: swapper/0/0x10010000
Dec 15 14:21:25 endeavour kernel: [17349.698812] Modules linked in: ppdev vboxnetflt vboxnetadp vboxdrv snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss iptable_nat nf_nat iptable_mangle arc4 xt_tcpudp snd_seq_midi snd_rawmidi snd_seq_midi_event nf_conntrack_ipv4 ecb nf_defrag_ipv4 joydev snd_seq dell_wmi xt_state snd_timer iwl3945 nf_conntrack nvidia(P) sdhci_pci sdhci iptable_filter ricoh_mmc ip_tables snd_seq_device dell_laptop iwlcore uvcvideo psmouse mac80211 snd led_class videodev soundcore v4l1_compat v4l2_compat_ioctl32 snd_page_alloc x_tables serio_raw dcdbas lp cfg80211 parport sha256_generic aes_x86_64 aes_generic cbc dm_crypt usbhid video output ohci1394 ieee1394 b44 ssb pcmcia pcmcia_core mii intel_agp
Dec 15 14:21:25 endeavour kernel: [17349.698924] CPU 1: ...

Read more...

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
tags: added: regression-update
removed: regression-potential
Revision history for this message
Hannes Koller (hannes-koller) wrote :

Similar Problem here. Dell Latitude E6400 , Intel Corporation Wireless WiFi Link 5100, Kubuntu 9.10 . Everything worked perfectly until I linux-image-2.6.31-16-generic got installed. Now the wireless option is disabled in knetworkmanager, although the wlan0 interface exists and can be configured with iwconfig. When I boot an older kernel ( linux-image-2.6.31-14-generic ) everything works fine with knetworkmanager.

Revision history for this message
Félim Whiteley (felimwhiteley) wrote :

For some reason and I can't figure out why it doesn't work when I try an older Kernel, that particular one in fact. The time stamp has been modified on the kernel modules directory too which is really odd, almost like something was updated on the older kernel. Unfortunately I really don't know what might have triggered it.

Revision history for this message
Félim Whiteley (felimwhiteley) wrote :

I've jsut had the card start working again this monring. I'm running vmlinuz-2.6.31-18 and it's functioning correctly. Problem is I'm not entirly sure when this started work! I believe it's only this monring, but it doesn't look like anything I installed yesterday could have solved that issue, the Kernel was installed on the 8th of January and I'm pretty sure it was still broken.

Yesterdays Updates (20/01/2009)
[UPGRADE] bind9-host 1:9.6.1.dfsg.P1-3ubuntu0.2 -> 1:9.6.1.dfsg.P1-3ubuntu0.3
[UPGRADE] dnsutils 1:9.6.1.dfsg.P1-3ubuntu0.2 -> 1:9.6.1.dfsg.P1-3ubuntu0.3
[UPGRADE] gzip 1.3.12-8ubuntu1 -> 1.3.12-8ubuntu1.1
[UPGRADE] libbind9-50 1:9.6.1.dfsg.P1-3ubuntu0.2 -> 1:9.6.1.dfsg.P1-3ubuntu0.3
[UPGRADE] libdns53 1:9.6.1.dfsg.P1-3ubuntu0.2 -> 1:9.6.1.dfsg.P1-3ubuntu0.3
[UPGRADE] libexpat1 2.0.1-4ubuntu1 -> 2.0.1-4ubuntu1.1
[UPGRADE] libisc50 1:9.6.1.dfsg.P1-3ubuntu0.2 -> 1:9.6.1.dfsg.P1-3ubuntu0.3
[UPGRADE] libisccc50 1:9.6.1.dfsg.P1-3ubuntu0.2 -> 1:9.6.1.dfsg.P1-3ubuntu0.3
[UPGRADE] libisccfg50 1:9.6.1.dfsg.P1-3ubuntu0.2 -> 1:9.6.1.dfsg.P1-3ubuntu0.3
[UPGRADE] liblwres50 1:9.6.1.dfsg.P1-3ubuntu0.2 -> 1:9.6.1.dfsg.P1-3ubuntu0.3

And day before had bunch of Kerberos update
[UPGRADE] libgssapi-krb5-2 1.7dfsg~beta3-1ubuntu0.3 -> 1.7dfsg~beta3-1ubuntu0.4
[UPGRADE] libk5crypto3 1.7dfsg~beta3-1ubuntu0.3 -> 1.7dfsg~beta3-1ubuntu0.4
[UPGRADE] libkrb5-3 1.7dfsg~beta3-1ubuntu0.3 -> 1.7dfsg~beta3-1ubuntu0.4
[UPGRADE] libkrb5support0 1.7dfsg~beta3-1ubuntu0.3 -> 1.7dfsg~beta3-1ubuntu0.4
[UPGRADE] quassel 0.5.0-0ubuntu1 -> 0.5.0-0ubuntu1.1
[UPGRADE] quassel-data 0.5.0-0ubuntu1 -> 0.5.0-0ubuntu1.1

So I've no idea what has fixed it. Any other debug of use?

Revision history for this message
Félim Whiteley (felimwhiteley) wrote :

Ok something odd is happening, I rebooted into the 17 kernel to see if wireless died again, it did, so I thought problem solved by the 18 kernel. No... I've jsut rebooted into 18 and I'm back to the RF-Killswitch nonsense, I really don't know how it started working yesterday! Any ideas?

Nothing was changed in last 24hrs bar the addition ofthe sun-java6-plugin.

Revision history for this message
Roland Schulz (roland-rschulz) wrote :

I believe I have the same problem. And it is also sometimes OK (wireless works) and sometimes it is not working (disabled enabled in knetworkmanager). Luckily for me it is usually OK and only seldom not OK. Thus if it is not OK I just need to reboot and it is usually working then. Maybe you want to just try booting a few times and see whether without changing anything you also have it sometimes working and sometimes not.

Revision history for this message
David Coles (dcoles) wrote :

I've just started to encounter the issue with my Dell M1530. `lshal` reports four different kill switch states with the Dell ones being possibly in conflict with the other two statues. A quick work around for me was to `rmmod dell_laptop` module after which the kill switch starts functioning as normal.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544217 sounds quite similar. I'll have to have a play around a bit more to see if it's the same issue. I wonder if this modules has been enabled in a recent Kernel update?

Revision history for this message
Félim Whiteley (felimwhiteley) wrote :

David you're a genius, minute I ran rmmod the wifi light turned on and it's sorted! Fantastic!

Revision history for this message
Stan Osborne (stan-ana) wrote :

I have a Dell laptop using 9.10 stable with this problem. I was initially using 9.04 stable. After an update to 9.04 this problem appeared. I then upgraded to 9.10. This problem persists. Once NetworkManger suddenly decided it could manage the wireless interface. So for awhile it worked again. Since then I have rebooted a few times and it has stopped working again. I don't know what I did to get it to work, nor what I did subsequent to make it stop working. The module dell_laptop is not installed so I am not able to try "rmmod dell_laptop". The only module with 'dell' in its name is dell_wmi. Since I can get the interface to work using iwconfig/ifconfig (sometimes ifup works), this is an annoying defect. Hopefully this problem with nm-applet/NetworkManager is soon corrected in an update. If anyone has ideas on how to correct this problem before an update is available I will try them.

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.