Wondering if anyone could help me with my problem? I’ve been successfully using my wireless lan with other distros, but since installing suse I’ve hit a wall. The ndiswrapper isntalls bcmwl5.inf ok, but it doesn’t seem to associate it with any hardware.
I’ve tried going through the Yast GUI but there must be a conflict somewhere as it never fires up the wireless and after reboot the kernel module name field is blank again.
I’ve followed the guidelines here (Ndiswrapper - openSUSE) and set the modprobe ndiswrapper in /etc/init.d/network. I’ve also blacklisted ssb which was apparently overwriting ndiswrapper priority at some point. I’m sure I have the correct bcmwl5 file as I’ve had it working yesterday on ubuntu…
I’m now at a loss of things to try, any help much appreciated.
waggonwheel wrote:
> Hi,
>
> Wondering if anyone could help me with my problem? I’ve been
> successfully using my wireless lan with other distros, but since
> installing suse I’ve hit a wall. The ndiswrapper isntalls bcmwl5.inf ok,
> but it doesn’t seem to associate it with any hardware.
>
> I’ve tried going through the Yast GUI but there must be a conflict
> somewhere as it never fires up the wireless and after reboot the kernel
> module name field is blank again.
>
> I’ve followed the guidelines here (‘Ndiswrapper - openSUSE’
> (http://en.opensuse.org/Ndiswrapper#Ndiswrapper)) and set the modprobe
> ndiswrapper in /etc/init.d/network. I’ve also blacklisted ssb which was
> apparently overwriting ndiswrapper priority at some point. I’m sure I
> have the correct bcmwl5 file as I’ve had it working yesterday on
> ubuntu…
>
> I’m now at a loss of things to try, any help much appreciated.
>
> Here some more info:
>
> linux-zodp:/home/gary # lspci | grep road
> 08:04.0 Network controller: Broadcom Corporation BCM4318 [AirForce One
> 54g] 802.11g Wireless LAN Controller (rev 02)
> linux-zodp:/home/gary # lspci -n | grep ‘08:04’
> 08:04.0 0280: 14e4:4318 (rev 02)
> linux-zodp:/home/gary # ndiswrapper -l
> bcmwl5 : driver installed
Are you blacklisting ssb which is the first-level driver used by the BCM4318?
Why are you trying to use the Windows driver when b43 works with the BCM4318,
and will avoid a lot of problems?
I blacklisted ssbbecause it was overwriting the priority I was setting for the module driver. In more detail what I was doing was setting ndiswrapper as ‘module name’ in the hardware setup in Yast. However, everytime I reboot the ndiswrapper is overwritten by ssb.
waggonwheel wrote:
> Thanks for the reply lwfinger…
>
> I blacklisted ssbbecause it was overwriting the priority I was setting
> for the module driver. In more detail what I was doing was setting
> ndiswrapper as ‘module name’ in the hardware setup in Yast. However,
> everytime I reboot the ndiswrapper is overwritten by ssb.
>
> I don’t know what is the b43 driver?
B43 is the native Linux driver for a number of BCM43XX cards, including the
BCM4318. Using it instead of the Windows driver with ndiswrapper will avoid
tainting the kernel, as well as a number of crashes associated with the Windows
driver.
and rebooted but should I expect that to have done anything because it hasn’t. How do I associate the drivers with the hardware card? Yast appears completely useless to me, every time I specify the driver module, nothing happens and after reboot the driver module I specified is no longer saved, just an empty box…
The wlan has no driver, how can I assign it and get it to stick? Any help appreciated, thanks…
waggonwheel wrote:
> I ran,
> sudo /usr/sbin/install_bcm43xx_firmware
>
> and rebooted but should I expect that to have done anything because it
> hasn’t. How do I associate the drivers with the hardware card? Yast
> appears completely useless to me, every time I specify the driver
> module, nothing happens and after reboot the driver module I specified
> is no longer saved, just an empty box…
>
> The wlan has no driver, how can I assign it and get it to stick? Any
> help appreciated, thanks…
You need to get ssb and b43 out of the blacklist file. Ssb is the buss driver
for b43 and b43legacy. Once ssb is loaded, it can read a deeply buried register
for the device to see which of the two drivers (b43 or b43legacy) should be loaded.
I had some time to get back to this and now the card is up and running OK. Thanks for your help. In the end after installing the b43 drivers and de-blacklisting the ssb the ndiswrapper eventually ‘stuck’ to the wireless card.
Larry,
What do you do if you need to use the ndiswrapper for an adapter that only works with the Windows driver? I blacklisted ssb just a few minutes ago to see if I can get my Linksys Wireless N Notebook adapter to work. Although it hasn’t as of yet I want to make sure I don’t mess up what’s already working.
