I just want to thank Larry for helping me sort out my broadcom wireless issues as well. I followed the thread and finally got my wireless connection to work. Cheers Leo
Sorry to revive an old thread but, i recently installed the latest version of openSuse 11.1. Everything is working great. The wired connection is a bit slow so if anyone can give me some input, that would be great. But really i want the wireless to work.
i ran
sudo /usr/sbin/install_bcm43xx_firmware through my wired connection.
I then executed modprobe bcm43xx to add the module to the linux kernel but i get
FATAL: Module bcm43xx not found.
it seems that it’s not installing the driver?
Whats the best solution to this problem?
Thanks.
check in /lib/firmware for folder/s named b43 & b43legacy. If these are populated, you may need a re-boot to sort things out
Andy
donricouga wrote:
> Sorry to revive an old thread but, i recently installed the latest
> version of openSuse 11.1. Everything is working great. The wired
> connection is a bit slow so if anyone can give me some input, that would
> be great. But really i want the wireless to work.
>
> i ran
> SUDO /USR/SBIN/INSTALL_BCM43XX_FIRMWARE THROUGH MY WIRED
> CONNECTION.
>
> I THEN EXECUTED MODPROBE BCM43XX TO ADD THE MODULE TO THE LINUX
> KERNEL BUT I GET
> **FATAL: MODULE BCM43XX NOT FOUND.
> it seems that it’s not installing the driver?
The driver bcm43xx was removed from the kernel as of 2.6.25. The
correct drivers now are b43 or b43legacy, depending on what hardware
you have - the system figures that out for you. It depends on the
revision level of the 802.11 core in your BCM43XX device. Note: The
caps version is still used to indicate your device.
A reboot and or a rmmod/insmod should bring your wireless device up.
Larry
**
thanks for all the help but still i’m out of luck. DeltaFlyer44 i do have those folders in my /lib/hardware folders. I’m trying to add the hardware through Yast and no luck. It can find wireless networks and seems like it doesn’t even recognize my hardware.
here is my hardware configuration
34: PCI 300.0: 0280 Network controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_14e4_4328
Unique ID: svHJ.cVoHMOE8QgD
Parent ID: z8Q3.biJ9F01qKoE
SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:03:00.0
SysFS BusID: 0000:03:00.0
Hardware Class: network
Model: “Dell Wireless 1500 Draft 802.11n WLAN Mini-card”
Vendor: pci 0x14e4 “Broadcom”
Device: pci 0x4328 “BCM4328 802.11a/b/g/n”
SubVendor: pci 0x1028 “Dell”
SubDevice: pci 0x000a “Wireless 1500 Draft 802.11n WLAN Mini-card”
Revision: 0x03
Driver: “b43-pci-bridge”
Driver Modules: “ssb”
Memory Range: 0xfe8fc000-0xfe8fffff (rw,non-prefetchable)
Memory Range: 0xd0000000-0xd00fffff (rw,prefetchable)
IRQ: 16 (536 events)
Module Alias: “pci:v000014E4d00004328sv00001028sd0000000Abc02sc80i00”
Driver Info #0:
Driver Status: ssb is active
Driver Activation Cmd: “modprobe ssb”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #23 (PCI bridge)
donricouga wrote:
> thanks for all the help but still i’m out of luck. DeltaFlyer44 i do
> have those folders in my /lib/hardware folders. I’m trying to add the
> hardware through Yast and no luck. It can find wireless networks and
> seems like it doesn’t even recognize my hardware.
>
> here is my hardware configuration
>
> 34: PCI 300.0: 0280 Network controller
> [Created at pci.318]
> UDI: /org/freedesktop/Hal/devices/pci_14e4_4328
> Unique ID: svHJ.cVoHMOE8QgD
> Parent ID: z8Q3.biJ9F01qKoE
> SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:03:00.0
> SysFS BusID: 0000:03:00.0
> Hardware Class: network
> Model: “Dell Wireless 1500 Draft 802.11n WLAN Mini-card”
> Vendor: pci 0x14e4 “Broadcom”
> Device: pci 0x4328 “BCM4328 802.11a/b/g/n”
> SubVendor: pci 0x1028 “Dell”
> SubDevice: pci 0x000a “Wireless 1500 Draft 802.11n WLAN Mini-card”
> Revision: 0x03
> Driver: “b43-pci-bridge”
> Driver Modules: “ssb”
> Memory Range: 0xfe8fc000-0xfe8fffff (rw,non-prefetchable)
> Memory Range: 0xd0000000-0xd00fffff (rw,prefetchable)
> IRQ: 16 (536 events)
> Module Alias: “pci:v000014E4d00004328sv00001028sd0000000Abc02sc80i00”
> Driver Info #0:
> Driver Status: ssb is active
> Driver Activation Cmd: “modprobe ssb”
> Config Status: cfg=no, avail=yes, need=no, active=unknown
> Attached to: #23 (PCI bridge)
The Broadcom device with PCI ID 0x4328 does not work with b43 (yet).
You will need to use either ndiswrapper, or the hybrid Broadcom wl
driver, which may be found in the Packman repo. You will need to
blacklist ssb.
oh ok thanks. So i tried the ndiswrapper route.
i followed these instructions, which included blacklisting the appropriate drivers. But to no avail.
Setting up wireless with ndiswrapper « openSUSE (and others) on an Inspiron 1501
this is the output of ndiswrapper -l
bcmwl6 : driver installed
device (14E4:4328) present (alternate driver: ssb)
Looks like there is some driver conflict.
In the hardware configuration under network card setup, should I not see ndiswrapper as one of the available kernel modules?
Im getting to a point where i just want to drill a bunch of holes and run a really long ethernet cable 
Thank you guys for any help
donricouga wrote:
>
> oh ok thanks. So i tried the ndiswrapper route.
>
> i followed these instructions, which included blacklisting the
> appropriate drivers. But to no avail.
>
> ‘Setting up wireless with ndiswrapper « openSUSE (and others) on an
> Inspiron 1501’ (http://tinyurl.com/a5unvl)
>
> this is the output of ndiswrapper -l
>
> bcmwl6 : driver installed
> device (14E4:4328) present (alternate driver: ssb)
>
> Looks like there is some driver conflict.
> In the hardware configuration under network card setup, should I not
> see ndiswrapper as one of the available kernel modules?
>
> Im getting to a point where i just want to drill a bunch of holes and
> run a really long ethernet cable
There is not necessarily a conflict. Just like Windows, Linux uses the
PCI ID to determine what driver to use. For your device, that is ssb.
For those systems that can use the native driver, ssb is loaded,
interrogates an internal register in the device, and uses that info to
determine whether to load b43 or b43legacy. The PCI ID is why the
alternate driver is listed as ssb.
You need to check the output of lsmod and look to see if ssb is
loaded. If so, your blacklisting didn’t work. Once ssb is no longer
loaded, you will need to check to make sure that ndiswrapper is
loaded. If not, load it with the command ‘sudo /sbin/modprobe -v
ndiswrapper’.
Two final points: You are using a 32-bit Windows driver. Does that
match your Linux system? Finally, is that driver for Vista, or XP?
There are reports that the Vista drivers do not work with ndiswrapper.
Larry
Hi,
A 32bit driver will works perfectly well on a 64bit system (the emulation in in ndiswrapper is based on wine and does not yet support 64bit natively). Also some vista drivers might not work with ndiswrapper but this really depends on the driver. You do need to ensure that both ssb and b43 are blacklisted to use ndiswrapper.
I now have the windows xp drivers directly from broadcom. It says it supports bcm4328 which is exactly what i have. Now i’m going the ndiswrapper route. but i have some problems. Firstly i did black list both b43 and ssb by adding them to the /etc/modprobe.d/blacklist file. bcm43xx is already blacklisted. I restarted comp. Doing
linux-xlq2:/usr/sbin # ndiswrapper -l
bcmwl6 : driver installed
device (14E4:4328) present (alternate driver: ssb)
Shouldn’t the ssb driver be blacklisted??? Why is it showing up as an alternate driver?
Lastly, I’m following the instructions on how to install the drivers(http://www.swerdna.net.au/linhowtowireless.html) using ndiswrapper and look at what i get doing the following. How to resolve??
**
linux-xlq2:/usr/sbin # ndiswrapper -m**
module configuration contains directive install pci:v000014E4d00004311sv00000007sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 390.
module configuration contains directive install pci:v000014E4d00004311sv00000008sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 391.
module configuration contains directive install pci:v000014E4d00004311svsdbcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 392.
module configuration contains directive install pci:v000014E4d00004312sv00000007sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 393.
module configuration contains directive install pci:v000014E4d00004312sv00000008sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 394.
module configuration contains directive install pci:v000014E4d00004312svsdbcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 395.
module configuration contains directive install pci:v000014E4d00004315sv0000000Bsd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 396.
module configuration contains directive install pci:v000014E4d00004315svsdbcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 397.
module configuration contains directive install pci:v000014E4d00004318sv00000005sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 398.
module configuration contains directive install pci:v000014E4d00004318sv00000006sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 399.
module configuration contains directive install pci:v000014E4d00004318svsdbcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 400.
module configuration contains directive install pci:v000014E4d00004319sv00000005sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 401.
module configuration contains directive install pci:v000014E4d00004319sv00000006sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 402.
module configuration contains directive install pci:v000014E4d00004319svsdbcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 403.
module configuration contains directive install pci:v000014E4d00004320sv00000001sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 404.
module configuration contains directive install pci:v000014E4d00004320sv00000002sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 405.
module configuration contains directive install pci:v000014E4d00004320sv00000003sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 406.
module configuration contains directive install pci:v000014E4d00004320sv00000004sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 407.
module configuration contains directive install pci:v000014E4d00004320svsdbcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 408.
module configuration contains directive install pci:v000014E4d00004324sv00000001sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 409.
module configuration contains directive install pci:v000014E4d00004324sv00000002sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 410.
module configuration contains directive install pci:v000014E4d00004324sv00000003sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 411.
module configuration contains directive install pci:v000014E4d00004324sv00000004sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 412.
module configuration contains directive install pci:v000014E4d00004324svsdbcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 413.
module configuration contains directive install pci:v000014E4d00004328sv00000009sd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 414.
module configuration contains directive install pci:v000014E4d00004328sv0000000Asd00001028bcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 415.
module configuration contains directive install pci:v000014E4d00004328svsdbcsci* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 416.
module configuration already contains alias directive
I guess it is easy when we ask the experts. I remember my teacher sent me a brochure so that I can see it well. But I believe I still need an expert.I thank her for the tips so I sent a card through www.marketmailing.com
Hi there,
I just installed OpenSuSe 11.1 on my HP Pavilion dv5035nr. I had been using Ubuntu 8.10 (intrepid ibex), but I wanted to try another distro to see if I liked it better.
I’ve been having so much trouble with my broadcom 4318 wireless card. I have no other way of getting on the internet save using the available wireless network.
I downloaded broadcom’s drivers, and using b43-fwcutter I installed it on my computer the way several of you outlined before (and the b43 linux website).
Last nitht after rebooting the blue wifi light turned on which was a good sign. But then I could see no network to connect to for a brief moment!, then I run nm-tool on a terminal and my card detected everything. I connected to one of the networks and I was online fine.
This morning however, my card is behaving abnormally and I don’t know what to do. If I reboot, I am able to connect to my wireless network, but with very low strength. After a few minutes I get disconnected and I can’t log back in!. Moreover the signal strength goes up suddenly, but then all the wireless networks simply die down and my card is not able to detect anything. Even if I run nm-tool again, I get nothing, even though it states my card is working well.
Do I need a special package? All these networks are WEP, so there shouldn’t be any trouble…
It’s not my wireless card, because it worked flawlessly in ubuntu 8.10 and 8.04 (though for both of them a package called wpa_supplicant was installed).
hi acimmarusti; welcome to the opensuse forums; not sure if you used the Ubuntu forums when you used ubuntu, but there is a sort of etiquette that you don’t jump into some else’s threads, with your problems;
you would be best to post your concerns as a new post;
before doing that, make sure you read what are called “the stickies”; they are the two postings at the top of the wireless forums; have a really good read, and follow the instructions there;
all best wishes,