I have searched and have not found anything specific to my issue. I am currently using NDISWrapper to load the bcmwl15 driver and when it’s active it works beautifully.
Problem is sometimes at boot, the card doesn’t “turn on” and I don’t know how else to describe it. The OS does not even detect that the hardware is present. I have disabled wireless hotkey in BIOS. The only way to make the wireless card “active” is to reboot with the wired connection to the router. After doing that the wireless card “wakes up” and works awesome.
Is there anything I can do to make sure the driver load at boot? Sometimes I get the error that NDISWrapper is not modprobbed when I go to network configuration and if I wish to do i now? I don’t know if that has anything to do with the boot sequence. Using the <modprobe ndiswrapper> command as root does nothing permanant.
When you say “logged as root” are we talking sudo, su, or actually root?
I think using NDISwrapper might be half your problem. A quick google didn’t give me an insight on whether compat-wireless has a bcmwl15 equivalent, but I would try and install compat-wireless. You will in all likely hood have to do this from the command line and be prepared to sit and watch the driver compile.
If that does not work, there is a file to add things to be automatically modprobbed.
On 02/02/2011 08:36 PM, Fathawk wrote:
>
> I’m logged in as root at the command prompt, I guess I am ignorant to
> any other permissions?
>
> I will research the other package you suggested tomorrow.
>
> Thanks for the kick start.
You should use Ndiswrapper only if it is absolutely necessary, and it is not for
any Broadcom device.
Pleae post the output of ‘/sbin/lspci -nnk’ for the Broadcom wireless device.
On 02/03/2011 07:06 AM, Fathawk wrote:
>
> Here is the output
>
>
> Code:
> --------------------
>
> 05:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11a/b/g [14e4:4312] (rev 01)
> Subsystem: Dell Wireless 1490 Dual Band WLAN Mini-Card [1028:0007]
> Kernel driver in use: ndiswrapper
The device with IDs 14e4:4312 is handled by b43. Get rid of ndisrapper and the
Windows driver. If you blacklisted ssb or b43, remove that as well. Then with a
network connection, run the commands
The last of those commands should show your AP in the list of scanned data. If
it says that the network is down, then your wireless disable switch is likely in
the disabled state.
I have to say thanks lwfinger, I am learning a lot about the terminal and it’s usage.
O.K. I have removed everything I can find relating to ndiswrapper and blacklist.conf lists nothing about the drivers. The only place I found blacklist commands was in ndiswrapper itself, which is gone.
I have re-installed the driver and when I run “/sbin/lspci -nnk” it shows “Kernel driver in use: b43-pci-bridge”
I have run “sudo /usr/sbin/iwlist scan” and there are no wlan entries and all I get is “does not support scanning” for eth0 and lo.
Rebooted numerous times and still get no activity on the wireless, I think that’s why I gave up originally and went with the wrapper, but I would rather make it right and use the right software.
So just to restate there are no entries on “iwlist scan” for wlan0.
On 02/03/2011 06:36 PM, Fathawk wrote:
>
> To add:
>
> When I ran the
>
>
> Code:
> --------------------
> sudo /sbin/modprobe -rv b43
> --------------------
>
>
> I get:
>
>
> Code:
> --------------------
> WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
> --------------------
>
>
> Which is puzzling, since I was sure I got all of the ndiswrapper files
> off the system?
It would seem that you have not. You need to use the ‘sudo ndiswrapper –e
<drivername>’ to unload the ndiswrapper driver. To fix any blacklist problem,
you will need to edit (as root) the file /etc/modprobe.d/50-blacklist.conf and
remove any entries that mention ssb or b43.
Once you have done the above, run the command
dmesg | egrep "ssb|b43"
and post the result.
Sorry that you have to use the command line to do some of these things; however,
remember that there is a 50 year history of development of command-line tools in
Unix. Most of these were cloned in Linux. They are so developed and so powerful.
How much work would it take in an editor to eliminate all the lines except those
with “ssb” or “b43” in them?
I’m old school, but my KDE desktop comes up running 11 tabs on the console, and
most of my work is done there. Yes, there are GUIs for some of the things that I
do; however, they execute in a fraction of the time that it takes the bloated
GUI to load.
No need to be sorry as I was aware I would need to learn to work on command line when I installed Linux, there’s just a bit of a learning curve coming from DOS. I will try the above suggestions when I get back to the machine.
Scroll through the post until you find the first red “DO NOT USE THESE INSTRUCTIONS” Those are the instructions you want. It talks about installing compat drivers for your card. (Lots more terminal The hardest transition for me was dir to ls and /option to -option)
However, since there is apparently a ndis driver hanging around, the compat may not work until it’s gone.
Actually, Trouble connecting to AP via wireless. openSUSE 11.3 was just a few forum posts down from yours and he has the same card. That post talks about using the Broadcom driver, not compat. But once again, I have a feeling the ndiswrapper problem needs resolved.
On 02/04/2011 06:36 PM, bsilvereagle wrote:
>
> Since ndiswrapper is not found, you may have uninstalled ndiswrapper the
> executable and not the wrapped driver.
>
> ‘HOWTO: Use b43 driver with 14e4:4315 (Broadcom bcm4312 rev 01) -
> Ubuntu Forums’ (http://ubuntuforums.org/showthread.php?t=1266620)
This is the WRONG card. The BCM4312 != BCM4312. There are two devices, one with
14e4:4312 and the other with 14e4:4315. Actually, both work with b43.
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
insmod /lib/modules/2.6.34.7-0.7-desktop/kernel/net/wireless/cfg80211.ko
insmod /lib/modules/2.6.34.7-0.7-desktop/kernel/net/mac80211/mac80211.ko
insmod /lib/modules/2.6.34.7-0.7-desktop/kernel/drivers/net/wireless/b43/b43.ko
On 02/05/2011 06:06 AM, Fathawk wrote:
>
> I see an active card, strange.
>
>
> Code:
> --------------------
> sudo /sbin/modprobe -v b43
> --------------------
>
>
> Code:
> --------------------
> WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
> insmod /lib/modules/2.6.34.7-0.7-desktop/kernel/net/wireless/cfg80211.ko
> insmod /lib/modules/2.6.34.7-0.7-desktop/kernel/net/mac80211/mac80211.ko
> insmod /lib/modules/2.6.34.7-0.7-desktop/kernel/drivers/net/wireless/b43/b43.ko
>
> --------------------
>
>
>
> Code:
> --------------------
> dmesg | egrep “ssb|b43”
> --------------------
>
>
> Code:
> --------------------
> 8.376751] b43-pci-bridge 0000:05:00.0: PCI INT A → GSI 18 (level, low) → IRQ 18
> 8.376765] b43-pci-bridge 0000:05:00.0: setting latency timer to 64
> 8.386079] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x11, vendor 0x4243)
> 8.386091] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0A, vendor 0x4243)
> 8.386100] ssb: Core 2 found: USB 1.1 Host (cc 0x817, rev 0x03, vendor 0x4243)
> 8.386108] ssb: Core 3 found: PCI-E (cc 0x820, rev 0x01, vendor 0x4243)
> 8.406179] ssb: Sonics Silicon Backplane found on PCI device 0000:05:00.0
> 8.458078] ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x4243)
> 8.458087] ssb: Core 1 found: V90 (cc 0x807, rev 0x03, vendor 0x4243)
> 8.458095] ssb: Core 2 found: PCI (cc 0x804, rev 0x0A, vendor 0x4243)
> 8.479138] ssb: Sonics Silicon Backplane found on PCI device 0000:08:00.0
> 8.488569] b44 ssb1:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:19:b9:6f:1e:f9
> 281.996359] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
> 282.544261] Registered led device: b43-phy0::tx
> 282.544338] Registered led device: b43-phy0::rx
> 282.544390] Registered led device: b43-phy0::radio
> 283.943092] b43 ssb0:0: firmware: requesting b43/ucode5.fw
> 284.106390] b43 ssb0:0: firmware: requesting b43/pcm5.fw
> 284.120338] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
> 284.195838] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
> 284.371057] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
>
> --------------------
>
>
>
> When I shut down and power up, I have to issue the modprobe command for
> the driver to load before the card will become active.
>
> Is there a way to get the driver to load at boot?
Get rid of what is left of ndiswrapper. You may have to reinstall it with YaST
and/or zypper, use the -e command, then uninstall ndiswrapper. You will likely
then need to delete /etc/modprobe.d/ndiswrapper.
Probably didn’t have to, but I reinstalled the firmware after hunting down and killing what was left of ndisrapper and now everything is on the up and up.
Many thanks, lwfinger.
On 02/05/2011 10:06 PM, Fathawk wrote:
>
> Done and done.
>
> Probably didn’t have to, but I reinstalled the firmware after hunting
> down and killing what was left of ndisrapper and now everything is on
> the up and up.
> Many thanks, lwfinger.
You are quite welcome. We like happy “customers” and to get rid of ndiswrapper.
It has a place, but not for devices with native drivers.
Firmware is independent of the kernel and will persist until you install a new
release of openSUSE; however, it will persist through an upgrade. I recommend
backing up the contents of /lib/firmware/b43 so that it will be locally
available when you do a new install.
The hardest transition for me was dir to ls and /option to -option)