I’ve been through all the posts and I still can’t get my wireless network card to work. When I pull up Yast->Network Devices->Network Settings I don’t see my wireless network card. I’ve tried installing the b43 firmware (/usr/sbin/install_bcm43xx_firmware) but that doesn’t seem to work. Any help would be appreciated.
I tried /sbin/install_bcm43xx_firmware and that didn’t work. It said that the b43 and b43legacy firmware were successfully installed. I should say that I had it working before but I had to recompile the kernel and it stopped working. I don’t remember exactly how I got it to work though. Any help would be appreciated.
I desperately need help! I’ve tried everything but it doesn’t seem to work. It worked for me before but I don’t remember what I did. Any help is greatly appreciated.
I suspect that since you’re using a custom recompiled kernel and since the bcm43xxx drivers are actually kernel modules, the problem might be just a tad overwhelming for me. You’d need a real linux guru to troubleshoot that. I don’t think that bulk kernel modules will work with custom kernels, though; you should probably recompile the modules too. At least that’s how I see it, but I’ve never compiled a kernel myself, so…
Anyway, there should be no problem for you taking the ndiswrapper route. Ndiswrapper gets installed with a default SuSE install if I’m not mistaken (or else you can install it via YAST). All you have to do then is modprobe ndiswrapper and after a reboot you just set up your new wireless connection in YAST (under Network Devices/Network Settings). If YAST asks you to modprobe the detected ndiswrapper configuration, answer yes. Then you select Add connection, select wireless as the connection type and type in “ndiswrapper” as driver. On the next page(s) fill-in your ESSID name and the type of encryption you use, reboot, and voila’, your connection should be up. A word of warning: I’ve never succeded in making the option “use ifup at boot” work - only “use network manager at boot” ever worked for me.
On the other hand, seeing that you’re quite a savvy user, you might opt to “go native”, i.e. recompile the bcm43xx module, which would be a wiser choice in my opinion. You’d have a more consistent, sturdy system in the end. Don’t get me wrong, ndiswrapper is OK and Windows drivers are OK too, it’s just the combination of the two that doesn’t inspire confidence. Not even on the ideological level;)
Update. I did some research and the bcm4328 is definitely not supported (yet) by the bcm43xx project. If you succeded in making it work, you obviously must have compiled the kernel module yourself - just as this guy did: BCM4328 latest GIT driver. Or perhaps you had it working with ndiswrapper - as happened to me yesterday. After a sleepless night spent trying to make the bcm43xx driver work, I was finally convinced I succeeded (the wireless connection was eventually up) and went to bed. This morning I began to have some Sherlockian doubts and checked with YAST: sure enough, my old ndiswrapper config had somehow crept in - there was no trace of the bcm43xx module whatsoever. That made me do a more thorough search of the Internet, until I found (several) categorical confirmations that the bcm43xx module definitely doesn’t support our chip as of this time.
Will there be any luck with the newest openSuSE 11.1?
I’d like to get my
Broadcom BCM4328 802.11a/b/g/n (rev 03) going and replace my USB myessentials WiFi device.
I’ve been using SuSE from around 8.0 so this has become sort of a burning question, and effort. I think that we have been all there and done that with our notebooks. LOL!
jjmacey wrote:
> Hi All,
>
> Will there be any luck with the newest openSuSE 11.1?
The driver is still not modified for this card. The guy that was working on the
N PHY reverse engineering seems to have disappeared - there is no timetable.
The driver is still not modified for this card. The guy that was working on the
N PHY reverse engineering seems to have disappeared - there is no timetable.
Larry, no wonder ROFLOL! This is truly a big challenge.
Any recommendations? I’ve tried ndiswrapper, wadcutter, etc. I’d like to get this straightened out.
jjmacey wrote:
>> The driver is still not modified for this card. The guy that was working
>> on the
>> N PHY reverse engineering seems to have disappeared - there is no
>> timetable.
>
> Larry, no wonder ROFLOL! This is truly a big challenge.
>
> Any recommendations? I’ve tried ndiswrapper, wadcutter, etc. I’d like
> to get this straightened out.
I don’t know what wadcutter is, but others have had some success using
ndiswrapper with the Windows XP driver. The Vista one has not worked. Your other
option is the Broadcom hybrid wl driver. It works for some, not for others -
just like ndiswrapper.
