broadcom-wl [4312] - have to run install_bcm43xx_firmware everytime

I combed through as many posts as I could and I apologize if this has been posted before.
I have used openSuse for years and have gotten this to work in the past. After upgrading openSuse 11 multiple times, I decided to go fresh with this version.
I am running openSuse 12.1 x64 KDE on a Dell XPS M1530 (Dual Core) and using a Broadcom BCM4312 802.11 a/b/g. Everything else works great as expected.
I ran through the zypper installation as stated on the forum and sure enough, it worked beautifully. I was able to connect to the WiFi router without issue. Life was good. However, every time I restart, the system does not see my Broadcom BCM4312 802.11 a/b/g and I have to connect my CAT6 cable. I have to sudo in and run ‘install_bcm43xx_firmware’ and it comes back and connects to my router. I can disconnect my CAT6…and everything works as designed. I created some restore points so I could get back to this configuration (if needed) and started going through blacklisting stuff (as suggested in some places) with mixed and tragic results. Needless to say, I had to restore back to my last restore point which is where I stand. Is there any way to get openSuse 12.1 x64 KDE to recognize the Broadcom BCM4312 802.11 a/b/g when I login? A Perl script at startup still requires CAT6 to get the bcm43xx_firmware and is not really a solution in my eyes. Any better ideas?

Linux NEWSLED12.site 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3 14:45:45 UTC 2011 (187dde0) x86_64 x86_64 x86_64 GNU/Linux
Broadcom BCM4312 802.11 a/b/g
Dell XPS M1530

Thanks - TD

Make sure you choose system connection here
http://dl.dropbox.com/u/10573557/SUSE%20Misc/kde-wireless-new.png

Once the firmware is there, you don’t need to keep installing it

On 12/11/2011 02:46 AM, caf4926 wrote:
>
> Make sure you choose system connection here
> http://dl.dropbox.com/u/10573557/SUSE%20Misc/kde-wireless-new.png
>
> Once the firmware is there, you don’t need to keep installing it

The reason why reinstalling the firmware brings up the network is because the
install_bcm43xx_firmware script loads the driver. It appears that something is
keeping b43 from loading. Check /etc/modprobe.d/50-blacklist.conf for references
to ssb and/or b43. If you ever used wl, they will be in that file.

Thanks for both replies. I have always had “Connect Automatically” checked so that is not the issue. The second response re: b43, or ssb being blacklisted is very close to the “feel” of what I’m experiencing. Unfortunately, neither ssb, or b43 are blacklisted in “/etc/modprobe.d/50-blacklist.conf”, but this is what I notice right after I login:
Neither are loaded.
NEWSLED12:/home/tadahla # lsmod | grep “ssb|wl|b43|bcma”
NEWSLED12:/home/tadahla #

After install_bcm43xx_firmware runs… this is what I get…
NEWSLED12:/home/tadahla # lsmod | grep “ssb|wl|b43|bcma”
b43legacy 137421 0
b43 363772 0
mac80211 332546 2 b43legacy,b43
cfg80211 210325 3 b43legacy,b43,mac80211
bcma 29583 1 b43
ssb 67780 2 b43legacy,b43
pcmcia 70281 2 b43,ssb
mmc_core 108074 4 b43,ssb,mmc_block,sdhci

I vaguely remember something about b43-fwcutter being involved in openSuse 10/11 and I was able to fix at LinuxWorld 2008, or one of the Brainshares, but those notes are long gone. I tried being creative with other postings, but it didn’t fix my issue.

Maybe something that is not blacklisted is causing a conflict and should be? Any help is welcome.

Thanks - TD

I have always had “Connect Automatically” checked
I was actually pointing you to a different check box called ‘System Connection’.

Sorry about that… Both “Connect Automatically” and “System Connection” were always checked. I’m starting to think conflict with ssb, or b43.

Have you tried blacklisting ssb

On 12/11/2011 10:46 PM, tadahla wrote:
>
> Sorry about that… Both “Connect Automatically” and “System
> Connection” were always checked. I’m starting to think conflict with
> ssb, or b43.

I agree. You need to find what is causing the conflict. In the meantime, stop
reinstalling the firmware. As I explained earlier, it is the


sudo /sbin/modprobe -v b43

that is making the driver load and work. You can use that by itself.

To see what might be happening, Run the following command and post the output:


sudo egrep -r "ssb|b43" /etc/modprobe.d/*

On 12/11/2011 11:06 PM, caf4926 wrote:
>
> Have you tried blacklisting ssb

Don’t do that if you expect to be able to use b43.

@lwfinger - Thank You!!! They weren’t blacklisted in ‘/etc/modprobe.d/50-blacklist.conf’, but I looked at ‘/etc/modprobe.d/50-broadcom-wl.blacklist.conf’ and sure enough: both ssb and b43 were blacklisted. I vi’ed in a dd’ed the lines out…restarted and… open for business. Thanks again for your help. This has been resolved - TD

/etc/modprobe.d/50-broadcom-wl.blacklist.conf

Is normally removed when you remove ‘wl’