On Wednesday 10 January 2007 22:00, David Hollis wrote: >On Wed, 2007-01-10 at 19:55 -0500, Gene Heskett wrote: >> On Wednesday 10 January 2007 18:13, David Hollis wrote: >> >On Wed, 2007-01-10 at 16:48 -0500, Gene Heskett wrote: >> >> Jan 10 16:04:38 diablo kernel: bcm43xx: Firmware: no support for >> >> microcode >> >> rev > 0x128 >> > >> >I don't know anything about the bcm43xx driver, but this line does >> > seem interesting. Do you have the extracted firmware available? >> >> The 'extracted firmware' would be what is wrapped up in ndiswrapper. >> There is also an alpha quality driver in the kernel tree, and that is >> the one that is the src of that particular message. The extracted >> windows driver doesn't report that. > >Check out http://bcm43xx.berlios.de/ > Hmm, it would appear we've /.'d them. However, I believe I did that last spring, using the driver directly from the windows partition, and that all the files are now resident in /lib/firmware. Here is a listing of that directory: total 7352 -rwxrw-rw- 1 root root 757760 Nov 28 2005 bcm1xsup.dll -rwxrw-rw- 1 root root 9948 Nov 28 2005 bcm43xx.cat -rw-r--r-- 1 root root 3696 Jul 7 2006 bcm43xx_initval01.fw -rw-r--r-- 1 root root 16 Jul 7 2006 bcm43xx_initval02.fw -rw-r--r-- 1 root root 3696 Jul 7 2006 bcm43xx_initval03.fw -rw-r--r-- 1 root root 16 Jul 7 2006 bcm43xx_initval04.fw -rw-r--r-- 1 root root 2568 Jul 7 2006 bcm43xx_initval05.fw -rw-r--r-- 1 root root 248 Jul 7 2006 bcm43xx_initval06.fw -rw-r--r-- 1 root root 2568 Jul 7 2006 bcm43xx_initval07.fw -rw-r--r-- 1 root root 2568 Jul 7 2006 bcm43xx_initval08.fw -rw-r--r-- 1 root root 248 Jul 7 2006 bcm43xx_initval09.fw -rw-r--r-- 1 root root 248 Jul 7 2006 bcm43xx_initval10.fw -rw-r--r-- 1 root root 20200 Jul 7 2006 bcm43xx_microcode2.fw -rw-r--r-- 1 root root 22352 Jul 7 2006 bcm43xx_microcode4.fw -rw-r--r-- 1 root root 23184 Jul 7 2006 bcm43xx_microcode5.fw -rw-r--r-- 1 root root 1312 Jul 7 2006 bcm43xx_pcm4.fw -rw-r--r-- 1 root root 1312 Jul 7 2006 bcm43xx_pcm5.fw -rwxrw-rw- 1 root root 658896 Nov 28 2005 bcmwl5.inf -rwxrw-rw- 1 root root 379840 Feb 14 2006 bcmwl5.PNF -rwxrw-rw- 1 root root 424320 Nov 28 2005 bcmwl5.sys -rwxrw-rw- 1 root root 81920 Nov 28 2005 bcmwliss.dll -rwxrw-rw- 1 root root 33664 Nov 28 2005 bcmwlnpf.sys -rwxrw-rw- 1 root root 69632 Nov 28 2005 bcmwlpkt.dll -rwxrw-rw- 1 root root 122880 Nov 28 2005 bcmwls32.exe -rwxrw-rw- 1 root root 22672 Nov 28 2005 bcmwls.ini -rwxrw-rw- 1 root root 176128 Nov 28 2005 bcmwlu00.exe -rwxrw-rw- 1 root root 2313329 Nov 28 2005 data1.cab -rwxrw-rw- 1 root root 36304 Nov 28 2005 data1.hdr -rwxrw-rw- 1 root root 512 Nov 28 2005 data2.cab -rw-r--r-- 1 root root 658896 Apr 17 2006 gene.inf -rwxrw-rw- 1 root root 346602 Nov 28 2005 ikernel.ex_ -rwxrw-rw- 1 root root 6200 Feb 14 2006 INFCACHE.1 -rwxrw-rw- 1 root root 168448 Nov 28 2005 is.exe -rwxrw-rw- 1 root root 658896 Nov 28 2005 jene -rwxrw-rw- 1 root root 28 Nov 28 2005 launcher.ini -rwxrw-rw- 1 root root 417 Nov 28 2005 layout.bin -rw-r--r-- 1 root root 0 Jan 10 22:29 ~lib-firm-dir-contents -rwxrw-rw- 1 root root 45056 Nov 28 2005 setup.exe -rwxrw-rw- 1 root root 595 Nov 28 2005 Setup.ini -rwxrw-rw- 1 root root 162610 Nov 28 2005 setup.inx -rwxrw-rw- 1 root root 628 Nov 28 2005 setup.iss -rwxrw-rw- 1 root root 3485 Nov 28 2005 sp29842.cva >You should find a bcm43xx-fwcutter utility (actually, it looks like its >in Extras so you can yum it too). Run that against the .SYS file you >have from Windows to extract the firmware. Then the bcm43xx driver >should be able to operate and you can toss ndiswrapper out the window. Does not the above satisfy the bcm43xx drivers firmware requirements? Recall from the earlier post, that a "modprobe bcm43xx" returns no error on the cli, and that this is the log from that action: Jan 10 16:04:21 diablo kernel: ieee80211: 802.11 data/management/control stack, git-1.1.13 Jan 10 16:04:21 diablo kernel: ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@xxxxxxxxxxxxxxx> Jan 10 16:04:21 diablo kernel: bcm43xx driver Jan 10 16:04:21 diablo kernel: ACPI: PCI Interrupt 0000:03:02.0[A] -> Link [LNKF] -> GSI 10 (level, low) -> IRQ 10 Jan 10 16:04:21 diablo kernel: bcm43xx: Chip ID 0x4318, rev 0x2 Jan 10 16:04:21 diablo kernel: bcm43xx: Number of cores: 4 Jan 10 16:04:21 diablo kernel: bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled Jan 10 16:04:21 diablo kernel: bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled Jan 10 16:04:21 diablo kernel: bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled Jan 10 16:04:21 diablo kernel: bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled Jan 10 16:04:21 diablo kernel: bcm43xx: PHY connected Jan 10 16:04:21 diablo kernel: bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7 Jan 10 16:04:21 diablo kernel: bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8) Jan 10 16:04:21 diablo kernel: bcm43xx: Radio turned off Jan 10 16:04:21 diablo kernel: bcm43xx: Radio turned off Jan 10 16:04:21 diablo kernel: SoftMAC: ASSERTION FAILED (0) at: net/ieee80211/softmac/ieee80211softmac_wx.c:306:ieee80211softmac_wx_get_rate() Jan 10 16:04:21 diablo kernel: SoftMAC: empty ratesinfo? Jan 10 16:04:21 diablo kernel: SoftMAC: empty ratesinfo? Jan 10 16:04:21 diablo kernel: bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0 Jan 10 16:04:21 diablo kernel: SoftMAC: Associate: Scanning for networks first. Jan 10 16:04:21 diablo kernel: SoftMAC: Associate: failed to initiate scan. Is device up? Jan 10 16:04:21 diablo kernel: bcm43xx: PHY connected Jan 10 16:04:21 diablo kernel: bcm43xx: Microcode rev 0x13f, pl 0x66 (2005-10-15 22:46:19) Jan 10 16:04:21 diablo kernel: bcm43xx: Firmware: no support for microcode rev > 0x128 Jan 10 16:04:21 diablo kernel: bcm43xx: core_up for active 802.11 core failed (-1) Jan 10 16:04:38 diablo kernel: SoftMAC: empty ratesinfo? Jan 10 16:04:38 diablo kernel: SoftMAC: empty ratesinfo? Jan 10 16:04:38 diablo kernel: bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0 Jan 10 16:04:38 diablo kernel: SoftMAC: Canceling existing associate request! Jan 10 16:04:38 diablo kernel: SoftMAC: Associate: Scanning for networks first. Jan 10 16:04:38 diablo kernel: SoftMAC: Associate: failed to initiate scan. Is device up? Jan 10 16:04:38 diablo kernel: bcm43xx: Microcode rev 0x13f, pl 0x66 (2005-10-15 22:46:19) Jan 10 16:04:38 diablo kernel: bcm43xx: Firmware: no support for microcode rev > 0x128 Jan 10 16:04:38 diablo kernel: bcm43xx: core_up for active 802.11 core failed (-1) It was the 004-1.fc5 version of that utility I used at the time. I have NDI where I got it at the time, but obviously from the 'fc5' in its name, it is probably the one from extras. So what do I do next? Thanks. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2007 by Maurice Eugene Heskett, all rights reserved.
