...

You need to install the Broadcom firmware in order to get this card to work. This can be achived by running /usr/sbin/install_bcm43xx_firmware

Did that. Nothing seemed any different. What next? -- Fr David Ousley davidousley@verizon.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 2009-12-17 at 15:23 -0500, James Bland wrote:

Make sure your LAN connection is up when running the command. The install_bcm43xx_firmware command needs to download the firmware from the internet. After it has downloaded and installed the files you should be able to add your network in networkmanager.

On 12/17/09, Fr David Ousley wrote:

...

...

...

You need to install the Broadcom firmware in order to get this card to work. This can be achived by running /usr/sbin/install_bcm43xx_firmware

Did that. Nothing seemed any different. What next? -- Fr David Ousley davidousley@verizon.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- Sent from my mobile device

Hi, You need to install the package b43-fwcutter via yast too. Then, ~cd /usr/sbin #su #install_bcm43xx_firmware The information on how to do this can be found at http://en.opensuse.org/HCL/Network_Adaptors_(Wireless)Broadcom_BCM43xx and the whole line above is a hyperlink, but when I type it in here it doesn't come out that way, so you will have to type the whole thing in your address window in your browser. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Dear Tejas -- Thanks -- I installed the broadcom-wl from packman with Yast. After reboot the card still does not seem to be recognized (iwconfig, e.g., says there is no wireless). What do I do next? I think I must be missing something here.

Until then your best option is to install the proprietary driver provided by by Broadcom (it's available in packman) called broadcom-wl. Works fine for me.

Regards,

Tejas

-- Fr David Ousley davidousley@verizon.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Check that the wl kernel module loaded and make sure that the blacklist file installed with the package /etc/modprobe.d/broadcom-wl-blacklist is working (the modules listed in it should not be loaded). (Use lsmod)

I don't know how to check whether the wl kernel module is loaded (sorry). /etc/modprobe.d/broadcom-wl-blacklist lists bcm43xx, ssb, b43 adn ndsiwrapper -- which I guess is what it should be. lsmod does not list any of these -- nor does it list broadcom-wl for that matter. Should it? I'm beyond my ken here, so I'd be grateful for step by step instructions and to what to do next. Thanks -- Fr David Ousley davidousley@verizon.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, Dec 18, 2009 at 2:20 PM, John Andersen wrote:

On 12/18/2009 7:39 AM, Fr David Ousley wrote:

...

...

Check that the wl kernel module loaded and make sure that the blacklist file installed with the package /etc/modprobe.d/broadcom-wl-blacklist is working (the modules listed in it should not be loaded). (Use lsmod)

I don't know how to check whether the wl kernel module is loaded (sorry).

/etc/modprobe.d/broadcom-wl-blacklist lists bcm43xx, ssb, b43 adn ndsiwrapper -- which I guess is what it should be.

lsmod does not list any of these -- nor does it list broadcom-wl for that matter.  Should it?  I'm beyond my ken here, so I'd be grateful for step by step instructions and to what to do next.

Thanks

Have you tried at the command line: modprobe broadcom-wl

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Has anyone pointed you at http://en.opensuse.org/HCL/Network_Adapters_%28Wireless%29/Broadcom_BCM43xx#... In particular after installing the 2 packages from packman, you need to either reboot or do some manual work like: rmmod ndiswrapper b43 ssb bcm43xx b43legacy modprobe ieee80211_crypt_tkip insmod wl.ko And in turn lsmod should not be showing any of the b43 modules if you're using the STA driver. (ie. the driver from packman) Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 12/18/2009 09:01 PM, Fr David Ousley pecked at the keyboard and wrote:

...

Has anyone pointed you at

http://en.opensuse.org/HCL/Network_Adapters_%28Wireless%29/Broadcom_BCM43xx#...

In particular after installing the 2 packages from packman, you need to either reboot or do some manual work like:

rmmod ndiswrapper b43 ssb bcm43xx b43legacy modprobe ieee80211_crypt_tkip insmod wl.ko

And in turn lsmod should not be showing any of the b43 modules if you're using the STA driver. (ie. the driver from packman)

Greg

Well, I got it working -- once, setting wl as module name from the drop-down in the hardware section for editing the network card in Yast. After reboot, we're back to where we were before: broadcom-wl is not loaded, and modprobe broadcom-wl gives "not found". No wireless connection shows up in iwconfig. Now in Yast, there are no modules in the drop-down.

lsmod shows that none of the other modules are loaded.

modprobe ieee80211_crypt_tkip executes without error

insmod wl.ko says "no such file or directory"

Any ideas? We now know that it will work; we just need to figure out how to get it to work all the time.

The actual module name is wl _not_ broadcom-wl. I just loaded this same software for my BCM4321, which the driver identifies as a BCM4328 and now I am able to use the on-board wireless. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 12/18/2009 09:33 PM, Fr David Ousley pecked at the keyboard and wrote:

...

The actual module name is wl _not_ broadcom-wl. I just loaded this same software for my BCM4321, which the driver identifies as a BCM4328 and now I am able to use the on-board wireless.

modprobe wl likewise gives FATAL: ... not found

When you go into Yast > Network devices > network settings and edit BCM4312 (mine is 4312 and not 4321), on the hardware tab, do you have wl in the drop-down? I did when it worked, but no longer. Thanks

Yes i do. You did install broadcom-wl from packman didn't you. You'll need to also install the kmp version that matches your kernel flavor. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 12/19/2009 02:54 AM, kanenas@hawaii.rr.com pecked at the keyboard and wrote:

On Friday 18 December 2009 06:49:27 pm Ken Schneider - openSUSE wrote:

...

On 12/18/2009 09:33 PM, Fr David Ousley pecked at the keyboard and wrote:

...

...

The actual module name is wl _not_ broadcom-wl. I just loaded this same software for my BCM4321, which the driver identifies as a BCM4328 and now I am able to use the on-board wireless.

modprobe wl likewise gives FATAL: ... not found

When you go into Yast > Network devices > network settings and edit BCM4312 (mine is 4312 and not 4321), on the hardware tab, do you have wl in the drop-down? I did when it worked, but no longer. Thanks

Yes i do. You did install broadcom-wl from packman didn't you. You'll need to also install the kmp version that matches your kernel flavor.

-- Ken Schneider SuSe since Version 5.2, June 1998

my dell vostro still runs 11.1, 64 bit, but this should work for you as well. i had a whole bunch of on /off problems with the drivers from packmanand knetworkmanager and the fw-cutter shtuff that suse installs. until a kernel comes with built in support, i will use what seems to always work for me now, which goes as follows: 1. using yast, remove everything related to bcm. don't forget something like fw-cutter or fw43-cutter don't quite remember exactly. just search for bcm 2. install ndiswrapper. 3. if you still have the windoze partition, copy the .inf files for the broadcom to some place in your linucs partition. if not, google for the windoze xp driver and get it and expand it. 4. install the driver with ndiswrapper. (just a minimum of rtfm:))if you get error messages about files not found, copy the additional files from your doze partition. 5. open up yast, you should see the wireless card now, configure it and don't forget to put "ndiswrapper" in the driver entry. finish up network config and click on "conventional" mode , *NOT* managed by (k)network manager. 6. find and install wicd. 7. run wicd. 8. you now have wireless. You also have a major security problem, as wicd seems tio be incapable of encrypting the access pwd, and, anyone using your laptop can go to the wicd setup screen and see the pword in plain text. since i don't give my lasptop to others and since the pwords are not stored between sessions, i don't worry about it, until they fix it. yea, wicd is *not* kde anything, but it gave me peace of mind since i installed it. my wireless connections now are / seem more reliable than windoze wireless connections!!!!

You do realize that you only need to *reply* *to* *the* *list*. Why are people unable to understand this! I and everyone else on this list don't need two copies of your replies. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ken --

...

When you go into Yast > Network devices > network settings and edit BCM4312 (mine is 4312 and not 4321), on the hardware tab, do you have wl in the drop-down? I did when it worked, but no longer. Thanks

Yes i do. You did install broadcom-wl from packman didn't you. You'll need to also install the kmp version that matches your kernel flavor.

Aha -- "kernel flavor" turns out to be the reason it worked sometimes and not always after a reboot. Somewhere along the line the "Desktop" kernel was added to the grub menu -- and made the default. Wireless worked with the regular kernel (which has broadcom-wl installed) but not with Desktop (which I assume does not). Changing the default in grub to boot with the regular kernel means that wireless works all the time (at least for the present, says the optimist). Thanks to one and all for the help! Couldn't have done it without you. -- Fr David Ousley davidousley@verizon.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org