Hi! I'am very excited with the inclusion of the bcm43xx driver in FC5 , I want to replace the venerable but awkward ndiswrapper driver, unfortunately the driver doesn't work for me and freeze my computer:
I have a laptop DELL Precision M60 with : # lspci -vvv ... 02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
Subsystem: Dell Wireless 1350 WLAN Mini-PCI Card Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 Interrupt: pin A routed to IRQ 5 Region 0: Memory at fafec000 (32-bit, non-prefetchable) [size=8K]
1- I downloaded the newest driver from DELL:R115321.EXE (dated Jan-06-2006) [albertop@amturing driver]$ cat Version.txt Title : Network:Dell _Wireless (US) WLAN Network Adapter Card, TrueMobile 1300 b/g PCMCIA, TrueMobile 1300 Internal b/g MPCI, TrueMobile 1400 Internal Dual-band WLAN Card , Wireless 1350(b/g)WLAN miniPCI Card, Wireless 1370 (b/g)WLAN MiniPCI Card, Wireless 1390 (802.11g) WLAN MiniCard, Wireless 1390 WLAN (802.11g) ExpressCard, Wireless 1450 (a/b/g) Dual-Band WLAN miniPCI Card, Wireless 1470 (a/b/g) Dual-Band WLAN miniPCI card, Wireless 1490 (802.11a/g) Dual-Band WLAN MiniCard, Wireless� 1350 WLAN (b/g) PC Card Driver Version : A09 OEM Name : Dell OEM Ver : 4.10.40.0 / 4.10.47.3 Computers : 1D7, 6400/E1505, ME051, MXC051, MXC061, MXG051; Inspiron - 1000, 1100, 1150, 1200, Inspiron - 2200, 300m, 500m, 5100, 510m, 5150, 5160, 6000, 600m, Inspiron - 700m, 710m, 8500, 8600, 9100, 9200, 9300, 9400/E1705, B120, Inspiron - XPS, XPS Gen 2; Latitude - 100L, 110L, 120L , D400, D410, D420, D500, D505, D510, D520, D600, D610, D620, D800, D810, D820, X1, X300; Precision - M20, M60, M65, M70, M90; XPS - M1710, M2010, Oses : Windows 2000 Professional,Windows XP Home Edition,Windows XP Media Center EditionWindows XP Professional Languages : Brazilian Portuguese,Chinese-S,Chinese-T,English,French,German,Italian,Japanese,Korean,Polish,Russian,Spanish,Swedish Created : Fri Jan 6 11:45:40 CST 2006
2. I run fwcutter: [root@amturing bcm43xx-fwcutter-003]# bcm43xx-fwcutter bcmwl5.sys fwcutter can cut the firmware out of bcmwl5.sys filename : bcmwl5.sys version : 4.10.40.0 MD5 : 30d20fc98bcfd52e1da778cf19b223d4
extracting bcm43xx_microcode2.fw ... extracting bcm43xx_microcode4.fw ... extracting bcm43xx_microcode5.fw ... *****: Sorry, it's not posible to extract "bcm43xx_microcode11.fw". *****: Extracting firmware from an old driver is bad. Choose a more recent one. *****: Luckily bcm43xx driver doesn't include microcode11 uploads at the moment. *****: But this can be added in the future... extracting bcm43xx_pcm4.fw ... extracting bcm43xx_pcm5.fw ... extracting bcm43xx_initval01.fw ... extracting bcm43xx_initval02.fw ... extracting bcm43xx_initval03.fw ... extracting bcm43xx_initval04.fw ... extracting bcm43xx_initval05.fw ... extracting bcm43xx_initval06.fw ... extracting bcm43xx_initval07.fw ... extracting bcm43xx_initval08.fw ... extracting bcm43xx_initval09.fw ... extracting bcm43xx_initval10.fw ...
3- I installed the firwware to /lib/firmware [root@amturing bcm43xx-fwcutter-003]# make installfw if ! [ -d /lib/firmware ]; then mkdir /lib/firmware; fi install -o 0 -g 0 -m 600 bcm43xx_*.fw /lib/firmware
4 Restart my machine. [root@amturing bcm43xx-fwcutter-003]# iwconfig
eth1 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4306" Mode:Managed Access Point: Invalid Bit Rate=1 Mb/s Tx-Power=off RTS thr:off Fragment thr:off Encryption key:off
I run manually: iwconfig eth1 essid .. iwconfig eth1 rate 11Mb iwconfig eth1 mode Managed iwconfig eth1 ap 00:0d:72:7c:24:c9 iwconfig eth1 key restricted 00000000
I run again iwconfig ans I see again: Access Point invalid
The worst thing is when I do a iwlist eth1 scan
My computer freeze and iwlist says something like eth1 no such device!!!!
The last thing logged before the freeze: Feb 28 00:22:03 amturing kernel: bcm43xx: set security called Feb 28 00:22:03 amturing kernel: bcm43xx: .active_key = 0 Feb 28 00:22:03 amturing kernel: bcm43xx: .level = 1 Feb 28 00:22:03 amturing kernel: bcm43xx: .enabled = 1 Feb 28 00:22:03 amturing kernel: bcm43xx: .encrypt = 1 Feb 28 00:22:03 amturing kernel: SoftMAC: Associate: Scanning for networks first. Feb 28 00:22:03 amturing kernel: SoftMAC: Associate: failed to initiate scan. Is device up? Feb 28 00:22:03 amturing kernel: bcm43xx: PHY connected Feb 28 00:22:03 amturing kernel: bcm43xx: Radio turned on Feb 28 00:22:03 amturing kernel: bcm43xx: Chip initialized Feb 28 00:22:03 amturing kernel: bcm43xx: DMA initialized Feb 28 00:22:03 amturing kernel: bcm43xx: 80211 cores initialized Feb 28 00:22:03 amturing kernel: bcm43xx: Keys cleared
This is info from my /var/log/messages at startup:
Feb 27 23:38:25 amturing kernel: ieee80211: 802.11 data/management/control stack, git-1.1.7 Feb 27 23:38:25 amturing kernel: ieee80211: Copyright (C) 2004-2005 Intel Corporation jketreno@linux.intel.com Feb 27 23:38:25 amturing kernel: bcm43xx driver Feb 27 23:38:25 amturing kernel: ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 Feb 27 23:38:25 amturing kernel: bcm43xx: Chip ID 0x4306, rev 0x3 Feb 27 23:38:25 amturing kernel: bcm43xx: Number of cores: 5 Feb 27 23:38:25 amturing kernel: bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled Feb 27 23:38:25 amturing kernel: bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled Feb 27 23:38:25 amturing kernel: bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled Feb 27 23:38:25 amturing kernel: bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled Feb 27 23:38:25 amturing kernel: bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled Feb 27 23:38:25 amturing kernel: bcm43xx: PHY connected Feb 27 23:38:25 amturing kernel: bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2 Feb 27 23:38:25 amturing kernel: bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) Feb 27 23:38:25 amturing kernel: bcm43xx: Radio turned off Feb 27 23:38:25 amturing kernel: bcm43xx: Radio turned off Feb 27 23:38:25 amturing kernel: cs: IO port probe 0x3d4-0x4ff: clean. Feb 27 23:38:25 amturing kernel: cs: IO port probe 0x3c0-0x3d2: clean.
Feb 28 00:10:38 amturing kernel: bcm43xx: Radio turned off Feb 28 00:10:38 amturing kernel: bcm43xx: DMA 0x0200 (RX) max used slots: 0/64 Feb 28 00:10:38 amturing kernel: bcm43xx: DMA 0x0260 (TX) max used slots: 0/512 Feb 28 00:10:38 amturing kernel: bcm43xx: DMA 0x0240 (TX) max used slots: 0/512 Feb 28 00:10:38 amturing kernel: bcm43xx: DMA 0x0220 (TX) max used slots: 0/512 Feb 28 00:10:38 amturing kernel: bcm43xx: DMA 0x0200 (TX) max used slots: 0/512 Feb 28 00:11:32 amturing kernel: bcm43xx: set security called Feb 28 00:11:32 amturing kernel: bcm43xx: .active_key = 0 Feb 28 00:11:32 amturing kernel: bcm43xx: .level = 1 Feb 28 00:11:32 amturing kernel: bcm43xx: .enabled = 1 Feb 28 00:11:32 amturing kernel: bcm43xx: .encrypt = 1
Feb 28 00:22:03 amturing kernel: bcm43xx: set security called Feb 28 00:22:03 amturing kernel: bcm43xx: .active_key = 0 Feb 28 00:22:03 amturing kernel: bcm43xx: .level = 1 Feb 28 00:22:03 amturing kernel: bcm43xx: .enabled = 1 Feb 28 00:22:03 amturing kernel: bcm43xx: .encrypt = 1 Feb 28 00:22:03 amturing kernel: SoftMAC: Associate: Scanning for networks first. Feb 28 00:22:03 amturing kernel: SoftMAC: Associate: failed to initiate scan. Is device up? Feb 28 00:22:03 amturing kernel: bcm43xx: PHY connected Feb 28 00:22:03 amturing kernel: bcm43xx: Radio turned on Feb 28 00:22:03 amturing kernel: bcm43xx: Chip initialized Feb 28 00:22:03 amturing kernel: bcm43xx: DMA initialized Feb 28 00:22:03 amturing kernel: bcm43xx: 80211 cores initialized Feb 28 00:22:03 amturing kernel: bcm43xx: Keys cleared Feb 28 00:22:03 amturing kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
I tried disabling encription in my AP but this didn't work neither. By the way my acces point is a 2Wire Appliance
Other messages that i recover from messages before a freeze:
Freeze n-2: Feb 27 22:56:35 amturing kernel: bcm43xx: ASSERTION FAILED (0) at: drivers/net/wireless/bcm43xx/bcm43xx_main.c:403:bcm43xx_plcp_get_bitrate() Feb 27 23:08:09 amturing kernel: bcm43xx: ASSERTION FAILED (0) at: drivers/net/wireless/bcm43xx/bcm43xx_main.c:403:bcm43xx_plcp_get_bitrate()
Freeze n-1: Feb 27 23:32:35 amturing kernel: bcm43xx: ASSERTION FAILED (0) at: drivers/net/wireless/bcm43xx/bcm43xx_main.c:403:bcm43xx_plcp_get_bitrate()
I'd like to fix the problem, but I don't know what else to do!
Thanks for your help Alberto Patino
Alberto Patino wrote:
Hi! I'am very excited with the inclusion of the bcm43xx driver in FC5 , I want to replace the venerable but awkward ndiswrapper driver, unfortunately the driver doesn't work for me and freeze my computer:
I have a laptop DELL Precision M60 with :
[...]
I'd like to fix the problem, but I don't know what else to do!
You are lucky, my Dell Precision M60 freezes as soon as the module is loaded and so far I failed to get any valuable information in syslog. However, bcm43xx isn't really considered stable, is it? So I just delete the bcm43xx-module after each kernel-update to avoid having it activated by fedora and stick to ndiswrapper. You should probably report your problesm to the bcm43xx-developers https://lists.berlios.de/mailman/listinfo/bcm43xx-dev instead of fedora-testing, because it seems to be unlikely that this issue is fedora-specific.
Alberto Patino wrote:!
I have a laptop DELL Precision M60 with : I'd like to fix the problem, but I don't know what else to do!
You are lucky, my Dell Precision M60 freezes as soon as the module is loaded and so far I failed to get any valuable information in syslog. However, bcm43xx isn't really considered stable, is it?
Is not stable but we must to help to do this driver stable :)
You should probably report your problesm to the bcm43xx-developers https://lists.berlios.de/mailman/listinfo/bcm43xx-dev instead of fedora-testing, because it seems to be unlikely that this issue is fedora-specific.
Yes you are right I'll submit this to the bcm43xx driver' guys.
Alberto Patiño
On 2/28/06, Patrick von der Hagen patrick@wudika.de wrote:
You are lucky, my Dell Precision M60 freezes as soon as the module is loaded and so far I failed to get any valuable information in syslog. However, bcm43xx isn't really considered stable, is it? So I just delete the bcm43xx-module after each kernel-update to avoid having it activated by fedora and stick to ndiswrapper.
Well, I have advances with the FC5 bcm43xx driver for my DELL M60.
In the first try I downloaded from the Dell site the latest broadcom driver. This firmware caused my machine to freeze.
I read the kernel source Documentation/network/bcm43xx.txt and I saw a list of drivers and versions. The first time I didn't understand the version numbers associated with the http link. But know I catch that the number is the version asociated withe the particular drver. The dell newest driver doesn't match this number so I looked up for a driver matching the version. (Fortunately I had several dell drives stored in my lap)
Well I had 3 drivers version from DELL, I remove the newest driver I installed with bcm43xx-fwcutter and I reinstalled a older version matching the one pinpoint out in the bcm43xx.txt file.
Alberto P.
Now I can scan with iwconfig.
However i cannot do network connection yet with the wireless interface, I'll try this later.
On 3/1/06, Alberto Patino pato.lukaz@gmail.com wrote:
On 2/28/06, Patrick von der Hagen patrick@wudika.de wrote:
You are lucky, my Dell Precision M60 freezes as soon as the module is loaded and so far I failed to get any valuable information in syslog. However, bcm43xx isn't really considered stable, is it? So I just delete the bcm43xx-module after each kernel-update to avoid having it activated by fedora and stick to ndiswrapper>
Well, I have advances with the FC5 bcm43xx driver for my DELL M60.
In the first try I downloaded from the Dell site the latest broadcom driver. This firmware caused my machine to freeze.
I read the kernel source Documentation/network/bcm43xx.txt and I saw a list of drivers and versions. The first time I didn't understand the version numbers associated with the http link. But know I catch that the number is the version asociated withe the particular drver. The dell newest driver doesn't match this number so I looked up for a driver matching the version. (Fortunately I had several dell drives stored in my lap)
Well I had 3 drivers version from DELL, I remove the newest driver I installed with bcm43xx-fwcutter and I reinstalled a older version matching the one pinpoint out in the bcm43xx.txt file.
Alberto P.
Now I can scan with iwconfig.
However i cannot do network connection yet with the wireless interface, I'll try this later.
well, 4 nights I have the bcm43xx included in FC5 Test3 working. The weird thing is that I achieved this with an insolit procedure:
I notice that getting the eth1 wireless interface up was only posibble when I was using the alias number, so I run the next list of commands.
iwconfig eth1:1 rate 11Mb iwconfig eth1:1 ap 00:0d:72:7c:24:c9
route add default gw 172.16.0.1 dev eth1:1 route add -net 172.16.0.0 netmask 255.255.0.0 dev eth1:1 route add default gw 172.16.0.1 dev eth1:1
And now the driver is working.
My /etc/sysconfig/network-scripts/ifcfg-eth1:
[root@amturing ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1 # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. USERCTL=yes IPV6INIT=no PEERDNS=yes GATEWAY=172.16.0.1 TYPE=Wireless DEVICE=eth1:1 HWADDR=00:0b:7d:07:75:d0 BOOTPROTO=none NETMASK=255.255.0.0 DHCP_HOSTNAME= IPADDR=172.16.1.34 DOMAIN= ESSID=2WIRE205 CHANNEL=1 MODE=Managed RATE='11 Mb/s' ONPARENT=no
Now its time to test the newest driver from the berlios site!
Thanks this is awesome! :)
-- Don't be evil!!!
-
Alberto Patino -
Patrick von der Hagen