Greetings;
This is a resend as the first one never came back.
I did the kde-base updates tonight, assuming that would fix my missing
kde menu's. It did not, kde, see bug 197778, is still crippled... I'd
been running kernel 2133 because that was the last one that had support
for both ntfs and ndiswrapper. And I hadn't tried any of the newer
ones because livna is out of synch, the kmod-ntfs and kmod-ndiswrappers
stuff reporting dependencies on an older version of ndiswrappers than
what I had installed. 2133 was the last kernel where all this matched up.
Thinking maybe it took a reboot to fix the missing kde menu's, I did,
back to 2133. Imagine my surprise when the on-screen boot trace
reported ntfs AND wlan0 both on the injured and disabled list. It
appears that somewhere along the line, both kmod-ntfs and ndiswrappers
was removed. Thats a bit like waking up and finding I'm in solitary
confinement...
So I piddle with /etc/modprobe.conf to see if I can make the bcm43xx
driver load and run, I mean that was the general idea of all these
changes wasn't it?
It now looks like this:
#options ndiswrapper if_name=wlan0
alias wlan0 bcm43xx
Anything missing there?
But when I reboot to 2139 where ntfs still works, this comes out of the
network startup. From dmesg:
bcm43xx: Chip ID 0x4318, rev 0x2
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
and later when the interface is brought up:
bcm43xx: set security called
bcm43xx: .level = 0
bcm43xx: .enabled = 0
bcm43xx: .encrypt = 0
SoftMAC: Associate: Scanning for networks first.
SoftMAC: Associate: failed to initiate scan. Is device up?
bcm43xx: PHY connected
bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load
failed.
Now, atm I am booted to kernel-2.6.17-1.2139_FC5 because apparently
thats the only one left with a working kmod-ntfs, and I've borrowed a
radio from the motel, and brought up the eth0 interface in order to get
on the net.
How is this "bcm43xx_microcode5.fw" file to be obtained and installed?
And, equally important to me, when do we get a kmod-ntfs that stays in
synch with the current kernels? Out of 5 kernels I currently have in my
/boot partition, 2139 is the only one that will allow access to
/mnt/hda1, (an ntfs partition with XP I don't run on it) the probable
source of this missing firmware file. I've tried them all in the last
hour and was very disappointed that ntfs access that worked perfectly
when booted to 2133 or any earlier kernel a week ago suddenly didn't work.
Note also that this is NOT NM driven, but the usual "service network
restart", NM still being broken for the broadcom 43xx radios I assume.
PS appended at resend time:
I lost about 4 hours last night as I'd found the fwcutter instructions
and ran it to repopulate the /lib/firmware directory. Following its own
help screen, I now have this in that directory, obtained from the actual
/mnt/hda1/SWSETUP/WLAN/bcmwl5.sys (my XP partition) file:
-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 05:46 bcm43xx_initval01.fw
-rw-r--r-- 1 root root 16 Jul 7 05:46 bcm43xx_initval02.fw
-rw-r--r-- 1 root root 3696 Jul 7 05:46 bcm43xx_initval03.fw
-rw-r--r-- 1 root root 16 Jul 7 05:46 bcm43xx_initval04.fw
-rw-r--r-- 1 root root 2568 Jul 7 05:46 bcm43xx_initval05.fw
-rw-r--r-- 1 root root 248 Jul 7 05:46 bcm43xx_initval06.fw
-rw-r--r-- 1 root root 2568 Jul 7 05:46 bcm43xx_initval07.fw
-rw-r--r-- 1 root root 2568 Jul 7 05:46 bcm43xx_initval08.fw
-rw-r--r-- 1 root root 248 Jul 7 05:46 bcm43xx_initval09.fw
-rw-r--r-- 1 root root 248 Jul 7 05:46 bcm43xx_initval10.fw
-rw-r--r-- 1 root root 20200 Jul 7 05:46 bcm43xx_microcode2.fw
-rw-r--r-- 1 root root 22352 Jul 7 05:46 bcm43xx_microcode4.fw
-rw-r--r-- 1 root root 23184 Jul 7 05:46 bcm43xx_microcode5.fw
-rw-r--r-- 1 root root 1312 Jul 7 05:46 bcm43xx_pcm4.fw
-rw-r--r-- 1 root root 1312 Jul 7 05:46 bcm43xx_pcm5.fw
-rwxrw-rw- 1 root root 658896 Nov 28 2005 bcmwl5.inf
-rwxrw-rw- 1 root root 379840 Feb 14 21:34 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 20:13 gene.inf
-rwxrw-rw- 1 root root 346602 Nov 28 2005 ikernel.ex_
-rwxrw-rw- 1 root root 6200 Feb 14 21:34 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
-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
Some of the above is no doubt from the previous ndiswrapper install.
However, now that the missing bcm43xx_microcode5.fw file has been found,
any attempt to bring up wlan0 now results in a machine lockup with a
well over 1 screenfull oops report frozen onscreen from the dhcp
invocation till the power button is used. I tried all 5 available
kernels with the same results and finally had to use a ubuntu 606 live
cd to mount my partition and effect the edits of
/etc/sysconfig/network-scripts ifcfg-eth0 to enable it, and ifcfg-wlan0
to disable it, at which point I was finally able reboot to 2139, the
only one with ntfs support available now. Obviously I'm not a happy
camper over this turn of events.
Can anyone tell me where I got off the beaten track with my version of
bcm43xx-fwcutter such that it made obviously bogus driver files?
And after all that, my kde menu's are still missing after updateing
kde-base & devel last night, so bug 197778 has not been addressed just yet.
--
Cheers, Gene
