Wlan using b43 on Mandriva

Dear Members

I've just installed Mandriva on my notebook. Everything works fine except the wlan card. That is a BCM4318 chip in my HP nx6125.

The system uses the bcm43xx module and with my Asus wl-500gx router there is absolutely no problem.
Also I would like to use my machine in the school, but it seems the bcm43xx module doesn't work perfectly witch the AP's there.

Sometimes it can work but most of the cases it can't. It can see the AP's but it can't connect.

That's why I would like to use the b43 module instead.
The first problem I've found is I couldn't unload the bcm43xx driver. When I try to remove it, the system reloads just after it. (Does anyone know why, and where can I modify that?)

I've found a solution (in an other forum) to remove the driver by delete the module completely, then depmod -a.

After that I can load the b43 driver by modprobe b43.

The messages log cantained the following lines anfter I did it:

May 14 20:25:34 localhost kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 22 (level, low) -> IRQ 22
May 14 20:25:34 localhost kernel: ssb: Sonics Silicon Backplane found on PCI device 0000:02:02.0
May 14 20:25:34 localhost kernel: b43-phy0: Broadcom 4318 WLAN found
May 14 20:25:34 localhost kernel: udev: renamed network interface wmaster0 to eth0
May 14 20:25:34 localhost ifplugd(eth0)[6708]: ifplugd 0.28 initializing.
May 14 20:25:34 localhost ifplugd(eth0)[6708]: Using interface eth0/00:14:A5:18:36:B1
May 14 20:25:34 localhost ifplugd(eth0)[6708]: Using detection mode: IFF_RUNNING
May 14 20:25:34 localhost ifplugd(eth0)[6708]: Initialization complete, link beat not detected.
May 14 20:25:44 localhost ntpd[4788]: sendto(193.225.218.44) (fd=21): Invalid argument
May 14 20:26:44 localhost ntpd[4788]: Deleting interface #3 eth0, fe80::214:a5ff:fe18:36b1#123, interface stats: received=0, sent=0, dropped=0, active_time=901 secs
May 14 20:26:44 localhost ntpd[4788]: Deleting interface #5 eth0, 192.168.10.8#123, interface stats: received=12, sent=12, dropped=2, active_time=901 secs
May 14 20:26:45 localhost acpid: client connected from 4777[0:0]

The wlan indicator LED didn't light on and I also didn't see any wlan networks.

I've searched over the net and I could not find any solutions, only questions and some topic of ndiswrapper. I've also asked in a local forum in my country but it seems they can't help me on Mandriva.

I hope there is anyone here who knows Mandriva or have any ideas how to get b43 work on my notebook.

Edit: I've extracted the firmware by b43-fwcutter.

Thanks for any reply.

I also have an HP with 43xx card For me, the best way to go was NDiswrapper. Fwcutter worked but was slow. Ran around 11bps.

As for the previous (automatic) loaded driver, I had to black list the Slackware supported driver and went with the NDiswrapper. There are several threads under my name that has good advise from the forum members. Just search for Ace Blackwell

i have the same problem with you before but i manage to make my wlan work for a couple of months...

if your problem is the modprobing of bcm43xx, then you should edit "/etc/modprobe.conf.local". type "blacklist bcm43xx" w/o quotes.
in order to load the b43 driver, just open your network manager and edit the wlan card and go to "hardware details" and change/insert the module name to "b43".

i solve my problem before by ndiswrapper. but when i learn how to update the kernel, i stop using ndiswrapper. updating the kernel is my better choice to make broadcom wlan work.

If you want to use the b43 you should blacklist the bcm43xx driver if that's the one that loads automatically. I have a Dell Inspiron 1501 laptop (1390 Broadcom mini PCI wireless card,bcmwl5 driver) and used ndiswrapper to get my wireless with Mandriva. Very easy to install and works like a charm. On the same laptop I have Ubuntu 7.10,Opensuse 10.2 and Slax all having wireless with ndiswrapper.
When will those wireless card manufacturers finally consent to provide linux drivers for their cards?!

Same here : don't bother and go directly with ndiswrapper.
It's unfortunate but it has always worked much better. I've not tested what is present in recent kernels but ndiswrapper has never caused me any problem so I stay with it.

Also, you can find the drivers here : http://driverpacks.net/DriverPacks/DriverPack.php?pag=w (*big* 7-zip file)
(or on your windows partition)

Thanks for your answers.

I wouldn't like to use ndiswrapper, but I've tried it with two x64 XP drivers, without success.
The wlan indicator LED came up, but it didn't work yet.
Log:

May 15 23:50:46 localhost kernel: ndiswrapper version 1.52 loaded (smp=yes, preempt=no) May 15 23:50:46 localhost kernel: ndiswrapper (link_pe_images:576): fixing KI_USER_SHARED_DATA address in the driver May 15 23:50:46 localhost kernel: ndiswrapper: driver bcmwl5 (Broadcom,02/11/2005, 3.100.64.0) loaded May 15 23:50:46 localhost kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 22 (level, low) -> IRQ 22 May 15 23:50:46 localhost kernel: ndiswrapper: using IRQ 22 May 15 23:50:46 localhost kernel: wlan0: ethernet device 00:14:a5:18:36:b1 using NDIS driver: bcmwl5, version: 0x364400a, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4318.5.conf May 15 23:50:46 localhost kernel: wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK May 15 23:50:46 localhost kernel: usbcore: registered new interface driver ndiswrapper May 15 23:50:46 localhost kernel: ndiswrapper: changing interface name from 'wlan0' to 'eth0' May 15 23:50:46 localhost kernel: udev: renamed network interface wlan0 to eth0 May 15 23:50:46 localhost ifplugd(eth0)[3819]: Using detection mode: SIOCETHTOOL May 15 23:50:46 localhost ifplugd(eth0)[3819]: Exiting. May 15 23:50:46 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready May 15 23:50:46 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready May 15 23:50:46 localhost kernel: ndiswrapper (add_wep_key:827): invalid key length (63) May 15 23:50:46 localhost ifplugd(eth0)[6231]: ifplugd 0.28 initializing. May 15 23:50:46 localhost ifplugd(eth0)[6231]: Using interface eth0/00:14:A5:18:36:B1 with driver <ndiswrapper+bcmwl5> (version: 1.52+Broadcom,02/11/2005, 3.100.) May 15 23:50:46 localhost ifplugd(eth0)[6231]: Using detection mode: SIOCETHTOOL May 15 23:50:46 localhost ifplugd(eth0)[6231]: Initialization complete, link beat not detected.

...but I really don't would like to use ndiswrapper when also there is a native driver.

Xeroblast:
I've found a /etc/modprobe.conf file.
I've modify the alias eth0 ndiswrapper line (because last time I've tried ndiswrapper) to alias eth0 b43
and an other line at the end of the file to
alias pci:v000014E4......... b43

Now it doesn't load bcm43xx nor ndiswrapper but b43.

The lsmod |grep b43 is:

b43 157360 0 ssb 37636 1 b43 rfkill 11152 1 b43 pcmcia 40856 2 b43,ssb rng_core 8968 1 b43 mac80211 135308 1 b43 led_class 8456 1 b43 input_polldev 8208 1 b43 pcmcia_core 40868 4 b43,pcmcia,yenta_socket,rsrc_nonstatic

and the messages log contains:

b43-phy1: Broadcom 4318 WLAN found b43-phy1 debug: Found PHY: Analog 3, Type 2, Revision 7 b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8 phy1: Selected rate control algorithm 'simple' udev: renamed network interface wmaster0 to eth0

I've started the Mandriva Linux Control Center, under the Network & Internet I've launched 'Set up a new interface'...
I've selected wireless [next], then the Broadcom Corporation BCM4318 [Airforce 1 54g] 802.11g Wireless LAN Controller [next].
It says: Unable to find network interface for selected device (using b43 driver).

The messages log also contains the following lines:

May 16 19:37:58 localhost drakconnect[6320]: ### Program is starting ### May 16 19:38:02 localhost drakconnect[6320]: running: /bin/rpm -q --qf %{name} wireless-tools May 16 19:38:06 localhost drakconnect[6320]: running: dmidecode May 16 19:38:06 localhost drakconnect[6320]: No settings found for driver "b43" in category "network::connection::wireless" May 16 19:38:18 localhost drakconnect[6320]: No settings found for driver "b43" in category "network::connection::wireless"

The ipconfig only has eth1 (the wired LAN) and lo sections now.

"then just open your network manager and edit the wlan card and go to "hardware details" and change/insert the module name to "b43"."

I didn't find where is that place where I can edit the wlan card or it's hardware details.
Can you describe that place more exactly?

I think the solution is not too far.

Thanks for the replies again.

I am not sure but did you try to install ndiswrapper and the driver right away with a wireless encryption key(wep)? I wouldn't do that. Install without any encryption first and if that works you can go for encryption after that.

Exsencon:
No, I've just tried to install it from the Mandriva's configuration panel.

Also if I try simply WEP, I have to modify my router's configuration and I don't really want to do that especially on weekend, because my brother would like to use the net and also there are other machines that would like to use the wlan connection, so they wouldn't be able to work while I test it.

Anyway, I didn't worked too much for the solution with ndiswrapper because I would like to use a native driver.

Thanks you for your answer, maybe last I will have to use ndiswrapper.
...but I would be sad if it would be the only working solution.

---------------------------

I still don't know what to do with b43.

I've searched a bit for b43 and I've found logs on the net similar to this:

b43-phy0 debug: Loading firmware version 410.2160 (2007-06-01 11:21:13) b43-phy0 debug: Chip initialized b43-phy0 debug: 30-bit DMA initialized Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx Registered led device: b43-phy0:radio b43-phy0 debug: Wireless interface started b43-phy0 debug: Adding Interface type 2

In my log, similar lines are missing.
First of all, it seems it wouldn't like to load the firmware.

Also, I've tried to delete all the files from the /lib/firmwares/ directory and after reboot in the log it didn't came up a message to say the firmware couldn't be loaded by b43. The necessary firmware files were originally copied to /lib/firmwares/b43/ directory by b43-fwcutter while the bcm43xx-fwcutter were copied its files directly to /lib/firmware/ directory.

Where can I say where is my firmware to b43? Also, where can I say it to at least try to load the firmware?
...or is there another log that shows me more info about the problem of b43?

Now in the Network Center, there are three devices...

First is the wired LAN,
second is the original "Broadcom Corporation BCM4318 [Airforce 1 54g] 802.11g Wireless LAN Controller"
third is simply eth0.

The second one has the wireless window, but everything is grey except configure. When I click on it, it says 'Unable to find network interface for selected device (using b43 driver)'.

The eth0 looks like a normal wired LAN, but I think it would be the wireless connection.

Any suggestions?

If I modify the /etc/modprobe.conf appropriate lines to bcm43xx and copy its files back, that is work after reboot. (...but it still don't work in the school.)

So, what do you think, what I have to do now?
It drives me crazy...


Edit:

iwconfig shows:

lo no wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. wlan0_rename IEEE 802.11g ESSID:"" Mode:Managed Channel:0 Access Point: Not-Associated Tx-Power=0 dBm Retry min limit:7 RTS thrff Fragment thr=2346 B Encryption keyff Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Regarding your iwconfig output did you try(as root):

iwconfig wlan0 essid <your essid>

I still would advise you go for ndiswrapper,I did 14 linux distros on my laptop with ndiswrapper and only FedoraF8 gave me a hard time (had to use b43)All the others worked perfectly.
Also(at least in my case)ndiswrapper always gives the better connection.

By iwconfig wlan0_rename ssid <id> I can give my ssid but it still can't connect, also it seems it doesn't load the firmware at all.

---

I've installed ndiswrapper and now I have the following lines in the log:

ndiswrapper version 1.52 loaded (smp=yes, preempt=no) ndiswrapper (link_pe_images:576): fixing KI_USER_SHARED_DATA address in the driver ndiswrapper: driver bcmwl5 (Broadcom,02/11/2005, 3.100.64.0) loaded ndiswrapper: using IRQ 22 usbcore: registered new interface driver ndiswrapper ndiswrapper: changing interface name from 'wlan0' to 'eth0' ndiswrapper (add_wep_key:827): invalid key length (63)

It seems the only real problem I have with ndiswrapper is the length of the wpa2 key.
Also, in the network control center, if I give it my details and write an extra character to the key (so if I complete it to 64 bytes) it says:
'The pre-shared key should have between 8 and 63 ASCII characters, or 64 hexadecimal characters.'

My key is exactly 63 characters long (of ASCII characters). That was correct in all devices, but it seems ndiswrapper is in trouble with it.

Maybe someone knows what to do to let it handle the 63 characters of key because it isn't too easy to modify it in all of the other equipments (and also I think it isn't the safest thing...).

(Any other things seems to be ok. No more errors, the wlan LED lights up and the device is in the network center correctly.)

Do I need to compile a newer version of ndiswrapper?

----------

b43:
I've found a place here.

On that page there is a quote of dmesg |grep b43:

b43-phy0 ERROR: Firmware file "b43/ucode5.fw" no found or load failed. b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Dr...devicefirmware and download the latest firmware (version 4).

Why didn't I have similar errors in my log? I really don't understand it.

When I read about it it's very clear how to load b43 module and how to download the firmware... but what can I do if there aren't error messages from the module? Also without any firmwares installed.
It's absolutely not ok.

Do I have to compile a new kernel or what can I do?

I think my b43 module is wrong.
... or how can I recompile just the module?

OK, it seems that with ndiswrapper your wireless interface is eth0 instead of wlan0,no big deal really.In order to make it work you will have to blacklist b43,bcm43xx or whatever is in there or at least modprobe them out (modprobe -r b43 or whatever) then you will have to let go of your wpa2 or wep key at least temporarily. I suppose when you do ndiswrapper -l you get something like: driver present,hardware present
Then you just do: modprobe ndiswrapper
When you do iwconfig and eth0 is your wireless interface you should do:

iwconfig eth0 essid your essid

it should work that way

sowe... got buzy!!!

i believe why your ndiswrapper didnt work coz youre using the ndiswrapper in you installer(DO NOT USE THE INSTALLER CD!)... download the newest ndiswrapper at this site "http://sourceforge.net/projects/ndiswrapper/" and install it...
bash#>wget http://nchc.dl.sourceforge.net/sourc...er-1.52.tar.gz
bash#>tar -xvf ndiswrapper-X.XX.tar.gz
bash#>cd ndiswrapper
bash#>./configure /*use option if necessary*/
bash#>make
bash#>sudo make install

then setup ndiswrapper to load your windows driver...

---

if you want to use the native driver then you have to update your kernel... 2.6.24.X and higher kernel... coz 2.6.22.X - 2.6.23.X still need patches...
bash#>su /*then enter your password*/
bash#>cd /usr/src/
bash#>wget http://www.kernel.org/pub/linux/kern...X.XX.X.tar.bz2
bash#>tar -xvf linux-X.X.XX.X.tar.bz2
bash#>make mrproper
bash#>zcat /proc/config.gz > .config
bash#>make ; make modules ; make modules_install
bash#>cp arch/`uname -i`/boot/bzImage /boot/vmlinuz-X.X.XX.X
bash#>cp System.map /boot/System.map-X.X.X.X
bash#>cp System.map /boot/System.map
bash#>mkinitrd -k vmlinuz-X.X.XX.X -i initrd-X.X.XX.X

then setup your boot loader to load this kernel...

Exsencon:
Yes, my wlan interface is eth0 with the system's ndiswrapper and also with the bcm43xx driver.
If I choose to use ndiswrapper, bcm43xx and b43 don't load by the system, so there is only ndiswrapper.
I think ndiswrapper should work if I modify the WPA2 key I have. I will try it later if nothing helps because almost always somebody would like to use the LAN.
(It would be better if I have another WLAN router/AP to try with it.)

Xeroblast:
I've used my installer only to install the system, then I've modified the sources list to an ftp, so I have most of the files from the Internet. I'm also using the updater to keep the system up-to-date.

It is a good idea to download the ndiswrapper directly and compile (then install) it myself.

---

I'm using kernel image named 2.6.24.4-laptop-1mnb, so I don't know why didn't it work.

I've tried to compile the kernel as you described it.
Everything was ok but I don't understand how can I use mkinitrd.

It's output to mkinitrd -k vmlinuz-2.6.25.4 -i initrd-2.6.25.4 is:

usage: mkinitrd [--version] [--help] [-v] [-f] [--preload <module>] [--force-scsi-probe | --omit-scsi-modules] [--force-ide-probe | --omit-ide-modules] [--image-version] [--force-raid-probe | --omit-raid-modules] [--with=<module>] [--force-lvm-probe | --omit-lvm-modules] [--builtin=<module>] [--omit-dmraid] [--net-dev=<interface>] [--fstab=<fstab>] [--nocompress] <initrd-image> <kernel-version> [--dsdt[=<dsdt.aml>]] (ex: mkinitrd /boot/initrd-2.6.24.4-laptop-1mnb.img 2.6.24.4-laptop-1mnb)

If I try mkinitrd /boot/initrd-2.6.25.4.img /boot/vmlinuz-2.6.25.4
It answers: No modules available for kernel "/boot/vmlinuz-2.6.25.4".

What did I wrong?
Anyway, the original b43.ko (unzipped) is 252958 bytes and the newly compiled one is 268866 bytes.

I hope this difference gives me the solution.

So, how can I generate the initrd file to work?

-------------------------------------------------------------------------------

OK, I still don't know what was it's problem but I did a make install and now the kernel is on.

After I modprobe b43, dmesg writes:

ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 22 (level, low) -> IRQ 22 ssb: Sonics Silicon Backplane found on PCI device 0000:02:02.0 b43-phy0: Broadcom 4318 WLAN found b43-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7 b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8 phy0: Selected rate control algorithm 'pid' Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ] udev: renamed network interface wmaster0 to eth0

I don't know how is it with the firmware, also my wlan LED doesn't lights up.

It writes the same without the whole firmware files.

-----------------------------------------------------------

I've tried the downloaded and compiled ndiswrapper (from http://nchc.dl.sourceforge.net/sourc...er-1.52.tar.gz)

Its log is:

ndiswrapper version 1.52 loaded (smp=yes, preempt=no) ndiswrapper (link_pe_images:576): fixing KI_USER_SHARED_DATA address in the driver ndiswrapper: driver bcmwl5 (Broadcom,02/11/2005, 3.100.64.0) loaded ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 22 (level, low) -> IRQ 22 ndiswrapper: using IRQ 22 wlan0: ethernet device 00:14:a5:18:36:b1 using NDIS driver: bcmwl5, version: 0x364400a, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4318.5.conf wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK usbcore: registered new interface driver ndiswrapper ndiswrapper: changing interface name from 'wlan0' to 'eth0' udev: renamed network interface wlan0 to eth0 ADDRCONF(NETDEV_UP): eth0: link is not ready ndiswrapper (add_wep_key:827): invalid key length (63)

ndiswrapper -l:

bcmwl5 : driver installed device (14E4:4318) present (alternate driver: bcm43xx)

Now bcm43xx or b43 are not present.

It seems this ndiswrapper also has problems with longer wpa keys.

Maybe I'll try b43 with another distribution later.

If someone has any idea, please post it.

-------------------------------

!!!
Anyway, ndiswrapper works without encryption.
So, I'm sure it's problem is the WPA2 key. (Maybe the length of it...)
!!!

-------------------------------

Interesting. I've booted up from an Ubuntu live DVD (the latest).
It uses b43 as default wlan module and it missed the b43 firmware in the log (and took me an advice to download it from linuxwireless). - so it seems to be ok.

Its b43 module's size is 193992 bytes (so it is different in size).

It's kernel version is something like 2.6.24.xx.

I think I will install it to another HDD and write out it's kernel coniguration.
...then I will compile the kernel for Mandriva with that config.

Is it an usable idea?

If I try mkinitrd /boot/initrd-2.6.25.4.img /boot/vmlinuz-2.6.25.4 It answers: No modules available for kernel "/boot/vmlinuz-2.6.25.4".

i think when you run "bash#>make ; make modules ; make modules_install" there is no modules... try running "make menuconfig" after "zcat...." and make sure there are modules loaded...

-------

i think its about the key... im also using a long encryption key but i dont use whitespace, i only use dash(-)

Now, my Mandriva works with b43 (since ~10 minutes)

I've browsed the /etc/sysconfig/ directory file by file, then I've continued it on /etc/udev/ directory.

I've found a file called 61-net_config.rules in /etc/udev/rules.d/ directory. Here, I've just commented out the line belongs to eth0.
After reboot, the WLAN LED was light up and now it's work correctly.

I've only a little difference in it's name, now it's only eth0 instead of it's original, longer name in network center [Broadcom Corporation BCM4318 [Airforce 1 54g] 802.11g Wireless LAN Controller] (may I modify it to the original? ).

Anyway, now in the 61-net_config.rules file there is an other line refers to eth0, and it's only differs in ATTRS{type}=="1" option, before the NAME field. (Maybe it has been modified an other file also.)

Thank you all your helps.
Now, I'm very happy.

I hope this thread will be useful for others who also want to use b43 on Mandriva.

Thank you again.