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 <era+launchpad....@iki.fi> 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 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 > -- 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
