I updated the kernel to 2.6.17.1 no problem...Wireless in dapper...go suck eggs

[bugman]

Well, I heard that 2.6.17.1 supported the Broadcom chipset.  Plus,  I always wanted to compile a kernel just to see if I can do it.  The how-to's are a lot of help and dapper runs much faster with the new kernel.    Yup, configured it to use the Broadcom module (stock (default) with this version), all dependencies too.  Modprobe sees the device.  Moreover, it sees many wireless networks in the area,  it just will not connect.  No security on my local network, it is open, and dapper fails to connect.  Tried the same card and drive in another laptop with windows (both XP and Vista) and it connected without a hitch.  The only thing not working here is linux.

-----Original Message-----
From: ubuntu-users-bounces at lists.ubuntu.com [mailto:ubuntu-users-bounces at lists.ubuntu.com] On Behalf Of Gard Spreemann
Sent: Wednesday, June 21, 2006 6:57 PM
To: Ubuntu Help and User Discussions
Subject: Re: I updated the kernel to 2.6.17.1 no problem...Wireless in dapper...go suck eggs

On 6/22/06, bugman <bugman at optonline.net> wrote:
> Should it be this hard to get wireless working in dapper?  I 
> recompiled dapper to work with the 2.6.17.1 kernel.  My first kernel 
> compile and no problems.  But getting wireless to work, no way.  The 
> Linksys card wpc54g broadcom 43xx was showing the local wireless 
> networks but would just not connect.  So I rebooted and now all I can get is "SIOCGIFFLAGS ERROR:NO SUCH
> DEVICE".   This is probably the most common wireless chipset in the world.
> Why should this be so hard?  It worked in Breezy, and it does not work now.
> This is an upgrade?
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
>
>

When you say you recompiled Dapper to work with Linux 2.6.17.1, you actually mean you compiled Linux 2.6.17.1. First a question: Why did you do this? Ubuntu Dapper's latest stock kernel is 2.6.15-25, and comes with a bcm43xx module.

In case you still want to run a self-compiled 2.6.17.1 instead, did you remember to configure it to include the bcm43xx module, and all the various ieee80211 modules it depends on? If so, try modprobe bcm43xx after you have booted the new kernel, and then see if the NO SUCH DEVICE error message is given.

--
Gard Spreemann

--
ubuntu-users mailing list
ubuntu-users at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-users