Where can I find this firmware file?
Gene Heskett
gene.heskett at verizon.net
Sun Jul 9 04:44:03 UTC 2006
Michael H. Warfield wrote:
> On Sat, 2006-07-08 at 22:02 -0500, Gene Heskett wrote:
>> Patrick wrote:
>>> On Sat, 2006-07-08 at 11:11 -0500, Gene Heskett wrote:
>>> [snip]
>>>> Am I upset?, yes. Apparently support for ndiswrapper has been removed,
>>> Removed from what? I have ndiswrapper running fine on my FC5 laptop with
>>> that crappy Broadcom radio. Came straight from the rpm.livna.org
>>> with "yum install ndiswrapper". If it is not available for
>>> FC4 I guess you could download the latest SRPM from that site and
>>> rebuild it yourself.
>>>
>>> Regards,
>>> Patrick
>> In FC5, they've a new version of the driver in the latest kernels now,
>> and we are supposed to be able to make it work with the help of this
>> bcm43xx-fwcutter utility, so there are apparently no new
>> kmod-ndiswrapper modules for the newer kernels being made. Hasn't been
>> one since 2133 TBE.
>
> Nonsense... Pure and utter nonsense.
>
> [root at canyon ~]# yum list | grep ndiswrapper
> kmod-ndiswrapper.i686 1.18-2.2.6.17_1.2145_F installed
> kmod-ndiswrapper.i686 1.18-2.2.6.17_1.2139_F installed
> ndiswrapper.i386 1.18-1.lvn5 installed
> kmod-ndiswrapper.i586 1.18-2.2.6.17_1.2145_F livna
> kmod-ndiswrapper-kdump.i686 1.18-2.2.6.17_1.2145_F livna
> kmod-ndiswrapper-smp.i586 1.13-4.2.6.16_1.2133_F livna
> kmod-ndiswrapper-smp.i686 1.18-2.2.6.17_1.2145_F livna
> kmod-ndiswrapper-xen0.i686 1.13-4.2.6.16_1.2133_F livna
Humm, according to that, I must not be that bad, but it sure isn't doing
anything but locking my machine up in mid-boot.
Here is what that command says about mine:
[root at diablo /]# yum list|grep ndiswrapper
kmod-ndiswrapper.i686 1.18-2.2.6.17_1.2145_F installed
kmod-ndiswrapper.i686 1.18-2.2.6.17_1.2139_F installed
ndiswrapper.i386 1.18-1.lvn5 installed
snipped to just the installed versions.
So lets refresh what I'm supposed to have in my /etc/modprobe.conf:
Currently its:
#options ndiswrapper if_name=wlan0
alias wlan0 bcm43xx
alias eth1 tg3
#alias wlan0 bcm43xx
which is obviously wrong as thats from when I was trying to make the
kernel driver work.
Also, the contents of /etc/ndiswrapper/bcmwl5a:
total 560
-rw-r--r-- 1 root root 583 Apr 18 12:56 14E4:4301:103C:12F3.5.conf
lrwxrwxrwx 1 root root 51 Apr 18 12:56 14E4:4301.5.conf ->
/etc/ndiswrapper/bcmwl5a/14E4:4301:103C:12F3.5.conf
-rw-r--r-- 1 root root 643 Apr 18 12:56 14E4:4318:103C:1355.5.conf
-rw-r--r-- 1 root root 643 Apr 18 12:56 14E4:4318:103C:1356.5.conf
-rw-r--r-- 1 root root 643 Apr 18 12:56 14E4:4318:103C:1357.5.conf
lrwxrwxrwx 1 root root 51 Apr 18 12:56 14E4:4318.5.conf ->
/etc/ndiswrapper/bcmwl5a/14E4:4318:103C:1355.5.conf
-rw-r--r-- 1 root root 699 Apr 18 12:56 14E4:4319:103C:1358.5.conf
-rw-r--r-- 1 root root 699 Apr 18 12:56 14E4:4319:103C:1359.5.conf
-rw-r--r-- 1 root root 699 Apr 18 12:56 14E4:4319:103C:135A.5.conf
lrwxrwxrwx 1 root root 51 Apr 18 12:56 14E4:4319.5.conf ->
/etc/ndiswrapper/bcmwl5a/14E4:4319:103C:1358.5.conf
-rw-r--r-- 1 root root 643 Apr 18 12:56 14E4:4320:0E11:00E7.5.conf
-rw-r--r-- 1 root root 651 Apr 18 12:56 14E4:4320:103C:12F4.5.conf
-rw-r--r-- 1 root root 643 Apr 18 12:56 14E4:4320:103C:12F8.5.conf
-rw-r--r-- 1 root root 643 Apr 18 12:56 14E4:4320:103C:12FA.5.conf
-rw-r--r-- 1 root root 643 Apr 18 12:56 14E4:4320:103C:12FB.5.conf
lrwxrwxrwx 1 root root 51 Apr 18 12:56 14E4:4320.5.conf ->
/etc/ndiswrapper/bcmwl5a/14E4:4320:0E11:00E7.5.conf
-rw-r--r-- 1 root root 699 Apr 18 12:56 14E4:4324:103C:12F9.5.conf
-rw-r--r-- 1 root root 699 Apr 18 12:56 14E4:4324:103C:12FC.5.conf
-rw-r--r-- 1 root root 699 Apr 18 12:56 14E4:4324:103C:12FD.5.conf
lrwxrwxrwx 1 root root 51 Apr 18 12:56 14E4:4324.5.conf ->
/etc/ndiswrapper/bcmwl5a/14E4:4324:103C:12F9.5.conf
-rw-r--r-- 1 root root 41622 Apr 18 12:56 bcmwl5a.inf
-rw-r--r-- 1 root root 371712 Apr 18 12:56 bcmwl5.sys
Then, for an ls -l /lib/firmware:
-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
And finally, a cat of /etc/sysconfig/network-scripts/ifcfg-wlan0:
DEVICE=wlan0
ONBOOT=no
BOOTPROTO=dhcp
TYPE=Wireless
MODE=Managed
ESSID=MountainHost
CHANNEL=6
IPADDR=192.168.1.1
DOMAIN=coyote.den
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
USERCTL=no
PEERDNS=no
IPV6INIT=no
RATE=Auto
DHCP_HOSTNAME=diablo.coyote.den
HWADDR=00:14:A5:75:32:C9
Currently disabled for obvious reasons.
> Looks like there are 2133 and 2145 out there right now, and have been.
> Half the damn mirrors don't even have the 2154 kernel yet, so I don't
> expect Livna to be caught up yet.
I haven't seen it here either.
> Also... The ndiswrapper driver is NOT just for the fscking Broadcom
> drivers. It's a generic driver wrapper so, even when the bcm34xx driver
> is half way stable, it will still be available for other NDIS based
> Winblows drivers.
Note that the below was when I tried to make the kernel bcm43xx work
instead of ndiswrapper..
>> I followed the procedure thats supposed to make it work, but all I got
>> for my trouble was a lockup, complete and total, and it cost me several
>> hours and a boot to the ubuntu live cd to effect a transfer back to an
>> external radio via an ethernet cable. I keep waiting, and running
>> yumex 2-3x a day, hoping we'll get a new kmod-ntfs for the last 2
>
> kmod-ntfs has jack to do with this thread. It had no relationship with
> ndiswrapper. Why bring that up? (Besides which, all of my kmod-ntfs is
> up to date - what's YOUR problem?)
Sure it does, without it, I'd have no way to access the winblows driver
and get the next thing that bcm43xx thinks it needs. But lets see what
I have:
[root at diablo /]# yum list|grep ntfs
kmod-ntfs.i686 2.1.27-1.2.6.17_1.2139 installed
kmod-ntfs.i686 2.1.27-1.2.6.17_1.2145 installed
ntfs-kmod-common.noarch 2.1.27-1.lvn5 installed
But it doesn't work with the 2145 kernel, I've tried several times. 2139
is the only one that works for that. That was one of the reasons I
asked about yum, which seems hell bent on removing the older versions
even if the kernel is still present and maybe even running ATM.
>
>> kernels, but as of this morning, zip, nada, nothing.
>
> I've been less than happy with the built-in bcm43xx drivers, so far.
> They work in many simple cases with limited access points (APs). In
> some cases, I've been flooded with "associated requests" and "associate
> timeouts" and various random acts of terrorism, especially where there
> are multiplex APs with various parameters. The damn driver spams the
> shit out of syslog with multiple messages. In those cases, I've been
> able to unload the bcm43xx drivers and associated drivers and then load
> the ndiswrapper with the appropriate firmware just fine.
>
> When that driver doesn't work, I've run this...
>
> for i in bcm43xx ieee80211softmac ieee80211 ieee80211_crypt ; do
> rmmod $i
> done
> modprobe ndiswrapper
>
> And away we go... All works cool...
>
> Ndiswrapper is NOT going away even if we have a PERFECT bcm43xx driver
> and 80211 protocol stack. There's just always going to be some drivers
> we need that shim for. Even as a backup.
>
>> --
>> Cheers, Gene
>
> Mike
>
If in the above, you can see why its all gone to hell in a little red
wagon, I'd appreciate a url or pointers on howto fix the current 100%
crashomatic setup.
--
Cheers, Gene
More information about the users
mailing list