openSUSE Forums > Archives > SF Archives > ARCHIVES - Network/Internet > ARCHIVES - Wireless Networking » Bcm43xx Problems Not A Nube (updated But Not Solved)

Go Back   openSUSE Forums > Archives > SF Archives > ARCHIVES - Network/Internet > ARCHIVES - Wireless Networking
Forums FAQ Members List Search Today's Posts Mark Forums Read


ARCHIVES - Wireless Networking Questions specific to wireless networking using SUSE Linux

 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 07-May-2008, 16:10
Trogdor91
Guest
 
Posts: n/a
Smile

I have an HP dv6000 with a broadcom wireless card that needs the bcm43xx dirver to work
my card more specificaly is BCM94311MCG
i am using opensuse 10.3 x64
lspci shows 03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 02)
there is a light and a switch on the outside of the computer when wireless is on and firware is uploaded the light is blue. when firmware is not uploaded or wireless is off or both. the light is redish orange. The switch togles wireless on or off.
card shows up as eth1

i did modprobe after each try

I have tried

1. Ndiswrapper
every single tutorial i could find and ifconfig and iwconfig never showed anything. Light color never changed.
I even compiled ndiswrapper from source and got the same result

2. Extracting the firmware from the hp, and broadcom sites using the fw cutter suplied with suse 10.3
The light changed to blue, and every command i try shows the card is up and runing find but when i scan it says device does not support scanning: device does not exist. If i let it sit the light evetualy goes back to redish orange and then every command doesn't even show eth1. A minute or two later the light goes blue again for a couple minutes then red. It keeps changing between blue and red but the time between the change almost double each time.

3. Installing the bcm43xx package from opensuse.org build service (it is the firmware in a package)
see above

4. running install_bcm43xx_firmware, a tool that downloads and cuts the firmware and places it in /lib/firmware
Hey guess what same thing see above

i made sure each firmware was placed in /lib/firmware
i made sure the firmware dir was /lib/firmware

Nothing i try works it make me want to scream
If anyone has this working or has the same problems please tell me

oh and i tri boot suse 10.3, vista, and kubuntu gusty
i have it working on kubuntu gusty from the tutorial here https://help.ubuntu.com/community/Wi...eisty_No-Fluff

that tutorial didn't work on suse.
My step 2 is step 2a on this tutorial

UPDATE
I have come to find that when i set up my card in yast and set module as ndiswrapper. it didn't save the module entry remains blank after i save the setting no matter what i enter
I have checked and ndiswrapper.ko exists and is listed in the modules file
  #2 (permalink)  
Old 08-May-2008, 21:08
andrewd18
Guest
 
Posts: n/a
Default

Regarding bcm43xx, you should upgrade to kernel 2.6.25 or higher; they released a patch that fixed all of the problems for my 94311MCG card. The new kernel module is called b43.

See http://linuxwireless.org/ for the latest firmware.

~~ Andrew D.
  #3 (permalink)  
Old 08-May-2008, 23:14
Spreadsheet
Guest
 
Posts: n/a
Default

I had the same problem a while ago, with a similar computer. However, isn't kernel 2.6.25 a testing release? And, when I tried to install openSUSE on that computer it froze up during the part in installation when it looked for hardware. So I had to use the safe mode, which had the fan not working. Any help with that?
  #4 (permalink)  
Old 09-May-2008, 09:42
andrewd18
Guest
 
Posts: n/a
Default

Quote:
I had the same problem a while ago, with a similar computer. However, isn't kernel 2.6.25 a testing release? And, when I tried to install openSUSE on that computer it froze up during the part in installation when it looked for hardware. So I had to use the safe mode, which had the fan not working. Any help with that?
[/b]
2.6.25 is not testing, it's an officially released kernel. http://www.kernel.org

If it froze up, you're having ACPI problems, which are likely unrelated to the wireless problem the OP mentioned. I also recommend updating your kernel as ACPI fixes are included in kernel updates.
  #5 (permalink)  
Old 09-May-2008, 18:28
Spreadsheet
Guest
 
Posts: n/a
Default

Thanks, but I thought odd numbers were testing. Oh well.
  #6 (permalink)  
Old 10-May-2008, 12:24
andrewd18
Guest
 
Posts: n/a
Default

Quote:
Thanks, but I thought odd numbers were testing. Oh well.[/b]
That's how it was in 2.4. They changed the system in 2.6.x.
  #7 (permalink)  
Old 10-May-2008, 14:27
The Ravenous Llama
Guest
 
Posts: n/a
Default

this may seem like an idiot thing to mention, but have you checked your firewall? i had problems with my bcm 4318 for the longest time. i also tried ndiswrapper and bcm43xx with firmware. in the end, i discovered that my wireless card was not set to a zone in suse's firewall, and thus was unusable. i changed it to external zone and now my card runs fine with firmware files. just a suggestion.

EDIT: actually, for other reasons i had to install the b43 drivers and the updated kernel myself. i'd recommend it, my wireless card is much zippier and less volatile to errors than it was before.
 

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2