Broadcom wireless card no longer detected after upgrade from Jaunty release candidate

[David Ring]

I have a Lenovo 3000 N500 laptop. Prior to today when I ran update-manager, my wireless card was detected. Today my laptop does not detect the Intel Wireless card. This worked in all the Jaunty alpha's, all the beta's and the release candidate, and the final version - but something updated today and because of that - I cannot connect to wireless. My laptop is dual boot so I'm running Windows XP at the moment - and it detects my card and connects - so that rules out my hardware being broken and not working.

I tried to run nm-applet directly and I get an error that it already is running - I'm guessing that nm-applet has been updated recently or something else has been.

I am running Jaunty 64 bit.

Thanks,

David

[David Ring (n1ea)]

nm-applet still does not again recognize my Intel WiFi card - this WAS working in the Jaunty 64 release - but due to an update it does not work.

I've just updated my machine via ethernet - and I still don't have WiFi - something was broken by an update.

Best to all,

David

[David Ring (n1ea)]

Is there anything I can do to get this very serious bug fixed?

I had working wifi before update-manager updated a week ago - now even when
updating over ethernet, my wifi card is no longer detected. My wifi card is
detected by running a life CD but not on a updated Jaunty system on my hard
drive.

I've received NO messages on this bug except from this one from AZ.

Thanks

David

On Sun, Apr 26, 2009 at 4:45 PM, Aleksander Zlatanchev <<email address hidden>
> wrote:

> ** Package changed: ubuntu => linux (Ubuntu)
>
> --
> wireless networkin
> https://bugs.launchpad.net/bugs/367552
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: New
>
> Bug description:
> I have a Lenovo 3000 N500 laptop. Prior to today when I ran
> update-manager, my wireless card was detected. Today my laptop does not
> detect the Intel Wireless card. This worked in all the Jaunty alpha's, all
> the beta's and the release candidate, and the final version - but something
> updated today and because of that - I cannot connect to wireless. My laptop
> is dual boot so I'm running Windows XP at the moment - and it detects my
> card and connects - so that rules out my hardware being broken and not
> working.
>
> I tried to run nm-applet directly and I get an error that it already is
> running - I'm guessing that nm-applet has been updated recently or something
> else has been.
>
> I am running Jaunty 64 bit.
>
> Thanks,
>
> David
>

[era (era)]

If this is still a problem, could you attach to the bug report the output of the command "sudo lspci -vvnn" or, if this is a USB device, "lsusb -v"

See furthermore https://help.ubuntu.com/community/WifiDocs/WirelessTroubleShootingGuide for detailed troubleshooting instructions. You may find that the guideline suggests adding other information to this bug report as well.

Apologies for the very late response. Your bug report should have been rerouted to the proper package, but apparently never was.

[era (era)]

The bug status "Incomplete" indicates that this bug needs further information from you in order to be processed.

The bug status "Invalid" for the package wifi-radar simply means that the bug does not have with that particular piece of software to do (wifi-radar is a monitoring application for finding wifi access points).

[David Ring (n1ea)]

I understand the very late response, and I'd be glad to help you, but I've
reverted to an earlier kernel.

I'm running the same hardware now. I went back to the earlier kernels - the
later ones don't support the broadcom wireless.

Attached is lspci.txt

Best regards and thanks for all of your work!

David

On Tue, Aug 11, 2009 at 2:45 PM, era <email address hidden> wrote:

> If this is still a problem, could you attach to the bug report the
> output of the command "sudo lspci -vvnn" or, if this is a USB device,
> "lsusb -v"
>
> See furthermore
> https://help.ubuntu.com/community/WifiDocs/WirelessTroubleShootingGuide
> for detailed troubleshooting instructions. You may find that the
> guideline suggests adding other information to this bug report as well.
>
> Apologies for the very late response. Your bug report should have been
> rerouted to the proper package, but apparently never was.
>
> ** Changed in: wifi-radar (Ubuntu)
> Status: New => Invalid
>
> --
> wireless networking
> https://bugs.launchpad.net/bugs/367552
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: New
> Status in “wifi-radar” package in Ubuntu: Invalid
>
> Bug description:
> I have a Lenovo 3000 N500 laptop. Prior to today when I ran
> update-manager, my wireless card was detected. Today my laptop does not
> detect the Intel Wireless card. This worked in all the Jaunty alpha's, all
> the beta's and the release candidate, and the final version - but something
> updated today and because of that - I cannot connect to wireless. My laptop
> is dual boot so I'm running Windows XP at the moment - and it detects my
> card and connects - so that rules out my hardware being broken and not
> working.
>
> I tried to run nm-applet directly and I get an error that it already is
> running - I'm guessing that nm-applet has been updated recently or something
> else has been.
>
> I am running Jaunty 64 bit.
>
> Thanks,
>
> David
>

[era (era)]

Sorry for spamming, but there's a different command you could use to attach the required log files to this bug report.

Open a terminal and copy/paste the following command line there:

apport-collect -p linux-image-`uname -r` 367552

Thanks in advance, and sorry for posting imprecise instructions earlier.

[era (era)]

> I'm running the same hardware now. I went back to the earlier kernels - the
> later ones don't support the broadcom wireless.

Also, can you indicate which kernel versions you have tried, and which work and which don't? Thanks!

[era (era)]

Oh, and one more last thing: the apport command line should be run while running a kernel which exhibits the problem you are describing.

[David Ring (n1ea)]

Hello again,

The latest kernel that runs my wifi is

~$ uname -r
2.6.28-14-generic

I have problems (caps lock doesn't work, and sometimes shifted keys don't
show on the screen in X server but they do work in CLI) - but that's another
story

Here is the kernel list:

title Ubuntu karmic (development branch), kernel 2.6.31-5-generic
uuid 7a888141-3f17-4c92-b3a1-dcd7a7002e37
kernel /boot/vmlinuz-2.6.31-5-generic
root=UUID=7a888141-3f17-4c92-b3a1-dcd7a7002e37 ro quiet splash
initrd /boot/initrd.img-2.6.31-5-generic
quiet

title Ubuntu karmic (development branch), kernel 2.6.31-5-generic
(recovery mode)
uuid 7a888141-3f17-4c92-b3a1-dcd7a7002e37
kernel /boot/vmlinuz-2.6.31-5-generic
root=UUID=7a888141-3f17-4c92-b3a1-dcd7a7002e37 ro single
initrd /boot/initrd.img-2.6.31-5-generic

title Ubuntu karmic (development branch), kernel 2.6.31-1-rt
uuid 7a888141-3f17-4c92-b3a1-dcd7a7002e37
kernel /boot/vmlinuz-2.6.31-1-rt
root=UUID=7a888141-3f17-4c92-b3a1-dcd7a7002e37 ro quiet splash
initrd /boot/initrd.img-2.6.31-1-rt
quiet

title Ubuntu karmic (development branch), kernel 2.6.31-1-rt
(recovery mode)
uuid 7a888141-3f17-4c92-b3a1-dcd7a7002e37
kernel /boot/vmlinuz-2.6.31-1-rt
root=UUID=7a888141-3f17-4c92-b3a1-dcd7a7002e37 ro single
initrd /boot/initrd.img-2.6.31-1-rt

ALL OF THE KERNELS BELOW WORK - Even WITHOUT the Broadcom STA module loaded!
(The keyboard doesn't work with "CAPS LOCK" in kernel 2.6.28-14-generic, but
that's another matter!

title Ubuntu karmic (development branch), kernel 2.6.28-14-generic
uuid 7a888141-3f17-4c92-b3a1-dcd7a7002e37
kernel /boot/vmlinuz-2.6.28-14-generic
root=UUID=7a888141-3f17-4c92-b3a1-dcd7a7002e37 ro quiet splash
initrd /boot/initrd.img-2.6.28-14-generic
quiet

title Ubuntu karmic (development branch), kernel 2.6.28-14-generic
(recovery mode)
uuid 7a888141-3f17-4c92-b3a1-dcd7a7002e37
kernel /boot/vmlinuz-2.6.28-14-generic
root=UUID=7a888141-3f17-4c92-b3a1-dcd7a7002e37 ro single
initrd /boot/initrd.img-2.6.28-14-generic

title Ubuntu karmic (development branch), kernel 2.6.28-3-rt
uuid 7a888141-3f17-4c92-b3a1-dcd7a7002e37
kernel /boot/vmlinuz-2.6.28-3-rt
root=UUID=7a888141-3f17-4c92-b3a1-dcd7a7002e37 ro quiet splash
initrd /boot/initrd.img-2.6.28-3-rt
quiet

title Ubuntu karmic (development branch), kernel 2.6.28-3-rt
(recovery mode)
uuid 7a888141-3f17-4c92-b3a1-dcd7a7002e37
kernel /boot/vmlinuz-2.6.28-3-rt
root=UUID=7a888141-3f17-4c92-b3a1-dcd7a7002e37 ro single
initrd /boot/initrd.img-2.6.28-3-rt

title Ubuntu karmic (development branch), kernel 2.6.27-7-generic
uuid 7a888141-3f17-4c92-b3a1-dcd7a7002e37
kernel /boot/vmlinuz-2.6.27-7-generic
root=UUID=7a888141-3f17-4c92-b3a1-dcd7a7002e37 ro quiet splash
initrd /boot/initrd.img-2.6.27-7-generic
quiet

title Ubuntu karmic (development branch), kernel 2.6.27-7-generic
(recovery mode)
uuid 7a888141-3f17-4c92-b3a1-dcd7a7002e37
kernel /boot/vmlinuz-2.6.27-7-generic
root=UUID=7a888141-3f17-4c92-b3a1-dcd...

[era (era)]

Thanks for the additional information. If you could still at some point boot into one of the newer kernels and run the apport command, that would allow a developer to look into this report.

If you are on Karmic, the command to run is slightly different:

apport-collect -p linux 367552

Thanks in advance!

[David Ring (n1ea)]

Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf4a00000 irq 22'
   Mixer name : 'Conexant CX20561 (Hermosa)'
   Components : 'HDA:80862802 HDA:14f15051'
   Controls : 14
   Simple ctrls : 7
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=ad3ff9a6-8e54-4873-83fa-3e4865f9e890
MachineType: LENOVO 423352U
NonfreeKernelModules: wl
Package: linux (not installed)
ProcCmdLine: root=UUID=7a888141-3f17-4c92-b3a1-dcd7a7002e37 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.27-7.14-generic
RelatedPackageVersions:
 linux-restricted-modules-2.6.27-7-generic 2.6.27-7.12
 linux-firmware 1.15
RfKill: Can't open RFKILL control device: No such file or directory
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/22/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6GET18WW(V1.09)
dmi.board.name: KIWDX
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr6GET18WW(V1.09):bd05/22/2009:svnLENOVO:pn423352U:pvrLenovo3000N500:rvnLENOVO:rnKIWDX:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: 423352U
dmi.product.version: Lenovo 3000 N500
dmi.sys.vendor: LENOVO

[era (era)]

Just to be perfectly clear on this, was this run on a kernel which does NOT support your Broadcom card? You said earlier:

> The latest kernel that runs my wifi is
> ~$ uname -r
> 2.6.28-14-generic

... and these dumps seem to be produced on a kernel which is older than that (viz. 2.6.27-7.14)

[David Ring (n1ea)]

Hello EInterra,

I would not be able to submit the data to launchpad without Internet
access. I might have sent it while running an older kernel - I can select
which kernel I want to run at the startup menu - I probably was checking
that ALL the older kernels worked also. I tried each kernel in my boot
menu, and the newest kernel that runs both my wifi and ethernet is 2.6.28.14

I just downloaded the Alternative CD installer for Jaunty. When I went
through the kernel selection - I just selected "linux" - it seeming to be
the most "unflavored" choice.

Then I did a "upgrade" by using "update-manager -d" CLI command.

What is interesting is that I am using 2.6.31-5 - after I upgraded!
*~$ uname -a
Linux david-laptop 2.6.31-5-generic #24-Ubuntu SMP Sat Aug 1 12:47:58 UTC
2009 x86_64 GNU/Linux
*
I don't know if the upgrade-manager -d script actually checks to see what
the Internet connection is - and what module is used - and compiles the
kernel to include it.

Prior to installing Jaunty with the Alternate Install CD, I had tried the
Ubuntu Koala Alpha 2 "Live CD" - and I couldn't connect.

I installed the 64 AMD Jaunty "Live CD" then did a update-manager -d upgrade
to Koala. Now it works fine. As I said perhaps the script to upgrade has
been made smarter and looked at which modules I needed to connect to
Internet.

I found this on launchpad shows a similar problem:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/385961

The bug submitter had his upgrade crash because the kernel didn't include
his wifi and/or ethernet module. I've had this happen MANY times!!!

The last time I did it - around the time I submitted this bug, I finally got
an "upgrade" which removed the old kernels and thus I had no Internet
connectivity - so I got a copy of the Jaunty Alternative Install 64 bit CD
(I had been running the 32 bit version of Ubuntu Jaunty/Koala) and then did
a CLI upgrade to Koala - it works fine now -

Hope this helps!

David

On Sun, Aug 16, 2009 at 4:10 PM, era <email address hidden> wrote:

> Just to be perfectly clear on this, was this run on a kernel which does
> NOT support your Broadcom card? You said earlier:
>
> > The latest kernel that runs my wifi is
> > ~$ uname -r
> > 2.6.28-14-generic
>
> ... and these dumps seem to be produced on a kernel which is older than
> that (viz. 2.6.27-7.14)
>
> --
> Broadcom wireless card no longer detected after upgrade from Jaunty release
> candidate
> https://bugs.launchpad.net/bugs/367552
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: New
> Status in “wifi-radar” package in Ubuntu: Invalid
>
> Bug description:
> I have a Lenovo 3000 N500 laptop. Prior to today when I ran
> update-manager, my wireless card was detected. Today my laptop does not
> detect the Intel Wireless card. This worked in all the Jaunty alpha's, all
> the beta's and the release candidate, and the final version - but something
> updated today and because of that - I cannot connect to wireless. My laptop
> is dual boot so I'm running Windows XP at the moment - and it detects my
> card and connects - so that rules out my hardware...

[era (era)]

So if I understand you correctly, the problem is not necessarily straightforward to reproduce, and you have no realistic means to send the diagnostic data? Additionally, you have an acceptable workaround in place. So there are basically two options:

1. Close this bug report as Invalid. This is in theory not at all permanent, but not many people will have any incentive to look into it ever again.

2. Mark this as Incomplete in case you eventually get a wired connection or some other means to submit the required information

I would go for option #2 but if you think it's not likely that we will ever be able to proceed, I would be tempted to move to #1.

[David Ring (n1ea)]

Hello Era,

It seems that a kernel upgrade solved the problem. I received this from
Micah:

*The Intel Drivers in Karmic require a newer kernel. Please check out*

*Bug #395630 for your wireless issue. *

* *

*
*
Maybe merging this bug with bug #397552 is in order.

Everything is fine now.

Best

David

On Mon, Aug 17, 2009 at 1:00 PM, era <email address hidden> wrote:
>
> So if I understand you correctly, the problem is not necessarilystraightforward to reproduce, and you have no realistic means to sendthe diagnostic data? Additionally, you have an acceptable workaround inplace. So there are basically two options: 1. Close this bug report as Invalid. This is in theory not at allpermanent, but not many people will have any incentive to look into itever again. 2. Mark this as Incomplete in case you eventually get a wired connectionor some other means to submit the required information I would go for option #2 but if you think it's not likely that we willever be able to proceed, I would be tempted to move to #1.
> -- Broadcom wireless card no longer detected after upgrade from Jaunty
> release candidate https://bugs.launchpad.net/bugs/367552 You received this
> bug notification because you are a direct subscriber of the bug. Status
> in “linux” package in Ubuntu: New Status in “wifi-radar” package in
> Ubuntu: Invalid Bug description: I have a Lenovo 3000 N500 laptop.
> Prior to today when I ran update-manager, my wireless card was detected.
> Today my laptop does not detect the Intel Wireless card. This worked in
> all the Jaunty alpha's, all the beta's and the release candidate, and the
> final version - but something updated today and because of that - I cannot
> connect to wireless. My laptop is dual boot so I'm running Windows XP at
> the moment - and it detects my card and connects - so that rules out my
> hardware being broken and not working. I tried to run nm-applet directly
> and I get an error that it already is running - I'm guessing that nm-applet
> has been updated recently or something else has been. I am running
> Jaunty 64 bit. Thanks, David
>