Ok, so yes the driver is installed properly, but I just have no interface. When I run iwconfig I get
lo no wireless extensions.
eth0 no wireless extensions.
So I assume I just need to add in an interface for wireless. I just don’t know how. Also, if anyone knows how to disable the KDE NetworkManager, I would be a fan of that also (I just don’t know how)
In YaST
Hardware Information > Network Card > Wireless 1397 WLAN Mini-Card
Kernel Driver: ssb
Hardware Information > Network Interface only lists two interfaces: eth0 and lo
/lib/firmware has the iwlwifi-5000-2.ucode (which from my readings on the internet is the correct driver)
On 11/22/2009 07:56 PM, rtconner wrote:
>
> Ok, so yes the driver is installed properly, but I just have no
> interface. When I run iwconfig I get
> Code:
> --------------------
>
> lo no wireless extensions.
> eth0 no wireless extensions.
> --------------------
>
>
> So I assume I just need to add in an interface for wireless. I just
> don’t know how. Also, if anyone knows how to disable the KDE
> NetworkManager, I would be a fan of that also (I just don’t know how)
>
> Specs
> Dell Lattitude E5500
> Linux 2.6.31.5-0.1-desktop i686
> OpenSuse 11.2 (i586)
> 4.3.1 (KDE 4.3.1) “release 6”
>
>
> In YaST
> Hardware Information > Network Card > Wireless 1397 WLAN Mini-Card
> Kernel Driver: ssb
> Hardware Information > Network Interface only lists two interfaces:
> eth0 and lo
>
> /lib/firmware has the iwlwifi-5000-2.ucode (which from my readings on
> the internet is the correct driver)
Absolutely not!
If the device uses ssb, then it is a Broadcom driver. You are not getting a
wireless interface BECAUSE the driver is not loading correctly, either because
the device is not supported, or because the firmware is not installed. To find
out which, please post the output from ‘dmesg | grep b43’.
I think the chipset of your card is a Broadcom BCM4312 and the wl module will run this card. the b43 driver will not work for this chipset. just go here to get it
On 11/22/2009 10:26 PM, rtconner wrote:
>
> :\ Goodness. So much to learn when you use a linux OS.
Yes, you are not spoonfed as a user of Window$.
You have two choices: (1) Get the broadcom-wl package for your kernel, or (2)
Get a 3.6.32 kernel for your architecture.
Be aware that (1) will “taint” your kernel so that kernel devs will not look at
any future kernel problems that you may have; however, if you are using a
closed-source graphics driver, then the tainting is already done.
this is where I got the firmware for my card on my laptop and have been using them ever since. I found it fairly easy to install and am by no means a linux guru.
On 11/23/2009 12:06 AM, rtconner wrote:
>
> Haha. Ok. So now I have to learn how to compile kernels? I’m not
> intimidated by this one bit. Wish me luck, I guess.
Not necessarily. There are 2.6.32 kernels in some repos. Use Webpin to find them.
On 11/23/2009 12:16 AM, syampillai wrote:
> @lwfinger Typo: 2.6.32 kernel.
> What are the Broadcom card models supported in this version?
> I have a 4328 card and I am currently using wl driver.
You will still need to use the wl driver. The reverse engineering is not done
yet for any of the 802.11n cards. Only the BCM4312 with PCI IDs 14e4:4315 is now
covered by the 2.6.32 kernel.
On 11/23/2009 12:26 AM, JeremiahMosser wrote:
>
> You could also check out
> http://linuxwireless.org/en/users/Drivers/b43 this is where
> I got the firmware for my card on my laptop and have been using them
> ever since. I found it fairly easy to install and am by no means a linux
> guru.
That driver is built-in. Only the firmware needs installing. This discussion
concerns the BCM models not yet handled.
Ok thanks folks. I just finally got around to installing 2.6.32-rc8 and it did fix my wireless. It was my first time compiling a kernel and it was not as bad as I thought.
