Re: Broadcom BCM43xx appears in system-config-network as eth1 in FC5T2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2006-01-27 at 16:04 -0500, Dave Jones wrote:
>  > I understand that there is an open source Broadcom driver being
>  > developed at bcm43xx.berlios.de. Are there plans to incorporate this
>  > driver into the FC5 kernel?
> 
> That's what's showing up as your 'eth1'.
> My guess is that as you were unaware of what was going on,
> you don't have the firmware installed.  You'll need to get fwcutter
> from the bcm43xx website, and feed it a windows driver to suck
> out the necessary firmware blobs, and drop them into /lib/firmware
> 
> 		Dave

Thanks for the heads-up Dave.

This is what I did:

[stan@localhost ~]$ svn checkout
svn://svn.berlios.de/bcm43xx/trunk/fwcutter
A    fwcutter/fwcutter.c
A    fwcutter/fwcutter_list.h
A    fwcutter/md5.c
A    fwcutter/md5.h
A    fwcutter/Makefile
A    fwcutter/README
 U   fwcutter
Checked out revision 1106.
[stan@localhost ~]$ ls
Desktop  fwcutter
[stan@localhost ~]$ cd fwcutter
[stan@localhost fwcutter]$ ls
fwcutter.c  fwcutter_list.h  Makefile  md5.c  md5.h  README
[stan@localhost fwcutter]$ make
cc -std=c99 -O2 -fomit-frame-pointer -Wall -pedantic -D_BSD_SOURCE
-DFWCUTTER_VERSION_=0.0.1   -c -o fwcutter.o fwcutter.c
cc -std=c99 -O2 -fomit-frame-pointer -Wall -pedantic -D_BSD_SOURCE
-DFWCUTTER_VERSION_=0.0.1   -c -o md5.o md5.c
cc -std=c99 -O2 -fomit-frame-pointer -Wall -pedantic -D_BSD_SOURCE
-DFWCUTTER_VERSION_=0.0.1 -o fwcutter fwcutter.o md5.o
[stan@localhost fwcutter]$ su
Password:
[root@localhost fwcutter]# make install
install -o 0 -g 0 -m 755 fwcutter /usr/local/bin/
[root@localhost fwcutter]#

At this point I copied bcmwl5.sys to ~/ from the WLAN folder of the HP
driver disk that came with the laptop and chmoded it to 777.

[root@localhost stan]# ls
bcmwl5.sys Desktop fwcutter
[root@localhost stan]# mv bcmwl5.sys ./fwcutter
[root@localhost stan]# cd fwcutter
[root@localhost fwcutter]# ls
bcmwl5.sys  fwcutter  fwcutter.c  fwcutter_list.h  fwcutter.o  Makefile
md5.c  md5.h  md5.o  README
[root@localhost fwcutter]# fwcutter bcmwl5.sys
fwcutter can cut the firmware out of bcmwl5.sys
  filename :  bcmwl5.sys
  version  :  3.100.64.0
  MD5      :  e7debb46b9ef1f28932e533be4a3d1a9

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 ...
[root@localhost fwcutter]# make installfw
if ! [ -d /lib/firmware ]; then mkdir /lib/firmware; fi
install -o 0 -g 0 -m 600 bcm43xx_*.fw /lib/firmware
[root@localhost fwcutter]# ls /lib/firmware
bcm43xx_initval01.fw  bcm43xx_initval04.fw  bcm43xx_initval07.fw
bcm43xx_initval10.fw   bcm43xx_microcode5.fw
bcm43xx_initval02.fw  bcm43xx_initval05.fw  bcm43xx_initval08.fw
bcm43xx_microcode2.fw  bcm43xx_pcm4.fw
bcm43xx_initval03.fw  bcm43xx_initval06.fw  bcm43xx_initval09.fw
bcm43xx_microcode4.fw  bcm43xx_pcm5.fw
[root@localhost fwcutter]#

At this point the firmware seems to be installed.

[root@localhost fwcutter]#  system-config-network

Hit "Edit" on "eth1" and made sure that "Activate device when computer
starts" was checked on the "General" tab and that dhcp is selected. On
the "Wireless Settings" tab entered all of the WEP parameters that used
to work with ndiswrappper: Mode: Auto, Network name (SSID) specified,
xxx, Channel: 6, Transmit rate: Auto, Key (use 0x for hex):
0xxxxxxxxxxx, clicked "OK". Clicked "Activate" on highlighted "eth1".
Clicked "Yes". Clicked "OK". Dialog box came up "Determining IP
information for eth1... failed. Cannot activate network device eth1".

At this point amazingly the WLAN led on my HP laptop is lit. Apparently
it just can't get an IP address from DHCP.

Rebooted. Same thing.

BTW this is how I did it on the same machine with FC4 and ndiswrapper: 
http://stanton-finley.net/HP_Pavilion_ZE2108WM.html

Any further ideas?

Stanton Finley
http://stanton-finley.net/


-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]