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

[Stanton Finley]

System-config-network correctly picks up my onboard Broadcom Corporation
BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) but
identifies it as eth1.

When I enter the correct WEP information and try to activate it fails.
FC4 running on this same machine with ndiswrapper identified it as wlan0
and worked well.

When I select "Activate device when computer starts" and reboot the boot
message for this device is "SCIOCSIFFLAGS: No such file or directory".

I am running FC5test2 with kernel 2.6.15-1.1878_FC5-i686.

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?

Has anyone had any luck with the Broadcom BCM4318 using ndiswrapper or
other method on FC5T2?

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

[Dave Jones]

On Fri, Jan 27, 2006 at 02:01:01PM -0700, Stanton Finley wrote:
>  System-config-network correctly picks up my onboard Broadcom
> Corporation
>  BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) but
>  identifies it as eth1.
>  
>  When I enter the correct WEP information and try to activate it fails.
>  FC4 running on this same machine with ndiswrapper identified it as wlan0
>  and worked well.
>  
>  When I select "Activate device when computer starts" and reboot the boot
>  message for this device is "SCIOCSIFFLAGS: No such file or directory".
>
>  I am running FC5test2 with kernel 2.6.15-1.1878_FC5-i686.
>  
>  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

[Stanton Finley]

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/

[Stanton Finley]

On Fri, 2006-01-27 at 16:10 -0700, Stanton Finley wrote:
>  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/
>  
>   
This from /var/log/messages may shed some light:

Jan 27 17:10:06 localhost gconfd (root-3182): starting (version 2.13.5),
pid 3182 user 'root'
Jan 27 17:10:06 localhost gconfd (root-3182): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
configuration source at position 0
Jan 27 17:10:06 localhost gconfd (root-3182): Resolved address
"xml:readwrite:/root/.gconf" to a writable configuration source at
position 1
Jan 27 17:10:06 localhost gconfd (root-3182): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 2
Jan 27 17:10:18 localhost kernel: "bcm43xx": set security called
Jan 27 17:10:18 localhost kernel: "bcm43xx":    .active_key = 0
Jan 27 17:10:18 localhost kernel: "bcm43xx":    .level = 1
Jan 27 17:10:18 localhost kernel: "bcm43xx":    .enabled = 1
Jan 27 17:10:18 localhost kernel: "bcm43xx":    .encrypt = 1
Jan 27 17:10:18 localhost kernel: SoftMAC: Associate: Scanning for
networks first.
Jan 27 17:10:18 localhost kernel: SoftMAC: Start scanning with channel:
1
Jan 27 17:10:18 localhost kernel: SoftMAC: Scanning 13 channels
Jan 27 17:10:18 localhost kernel: SoftMAC: Scanning finished
Jan 27 17:10:18 localhost kernel: SoftMAC: Queueing Authentication
Request to 00:13:10:e9:5c:c2
Jan 27 17:10:18 localhost kernel: SoftMAC: cannot associate without
being authenticated, requested authentication
Jan 27 17:10:18 localhost kernel: SoftMAC: Queueing Authentication
Request to 00:13:10:e9:5c:c2
Jan 27 17:10:18 localhost kernel: SoftMAC: cannot associate without
being authenticated, requested authentication
Jan 27 17:10:18 localhost kernel: SoftMAC: Sent Authentication Request
to 00:13:10:e9:5c:c2.
Jan 27 17:10:18 localhost kernel: SoftMAC: Sent Authentication Request
to 00:13:10:e9:5c:c2.
Jan 27 17:10:18 localhost dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 3
Jan 27 17:10:21 localhost dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 3
Jan 27 17:10:24 localhost dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 5
Jan 27 17:10:29 localhost dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 5
Jan 27 17:10:30 localhost kernel: SoftMAC: Sent Authentication Request
to 00:13:10:e9:5c:c2.
Jan 27 17:10:30 localhost kernel: SoftMAC: Sent Authentication Request
to 00:13:10:e9:5c:c2.
Jan 27 17:10:34 localhost dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 12
Jan 27 17:10:42 localhost kernel: SoftMAC: Sent Authentication Request
to 00:13:10:e9:5c:c2.
Jan 27 17:10:42 localhost kernel: SoftMAC: Sent Authentication Request
to 00:13:10:e9:5c:c2.
Jan 27 17:10:46 localhost dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 20
Jan 27 17:10:54 localhost kernel: SoftMAC: Sent Authentication Request
to 00:13:10:e9:5c:c2.
Jan 27 17:10:54 localhost kernel: SoftMAC: Sent Authentication Request
to 00:13:10:e9:5c:c2.
Jan 27 17:11:06 localhost dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 12
Jan 27 17:11:06 localhost kernel: SoftMAC: Sent Authentication Request
to 00:13:10:e9:5c:c2.
Jan 27 17:11:06 localhost kernel: SoftMAC: Sent Authentication Request
to 00:13:10:e9:5c:c2.
Jan 27 17:11:18 localhost dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 1
Jan 27 17:11:18 localhost kernel: SoftMAC: Authentication timed out with
00:13:10:e9:5c:c2
Jan 27 17:11:18 localhost kernel: SoftMAC: cannot associate without
being authenticated, requested authentication
Jan 27 17:11:18 localhost kernel: SoftMAC: cannot associate without
being authenticated, requested authentication
Jan 27 17:11:18 localhost kernel: SoftMAC: Authentication timed out with
00:13:10:e9:5c:c2
Jan 27 17:11:18 localhost kernel: SoftMAC: cannot associate without
being authenticated, requested authentication
Jan 27 17:11:18 localhost kernel: SoftMAC: cannot associate without
being authenticated, requested authentication
Jan 27 17:11:19 localhost dhclient: No DHCPOFFERS received.

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

[Pete Graner]

Stanton Finley wrote:
>  On Fri, 2006-01-27 at 16:10 -0700, Stanton Finley wrote:
> > 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/
> >
> >
>  This from /var/log/messages may shed some light:
>  
>  Jan 27 17:10:06 localhost gconfd (root-3182): starting (version 2.13.5),
>  pid 3182 user 'root'
>  Jan 27 17:10:06 localhost gconfd (root-3182): Resolved address
>  "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
>  configuration source at position 0
>  Jan 27 17:10:06 localhost gconfd (root-3182): Resolved address
>  "xml:readwrite:/root/.gconf" to a writable configuration source at
>  position 1
>  Jan 27 17:10:06 localhost gconfd (root-3182): Resolved address
>  "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
>  configuration source at position 2
>  Jan 27 17:10:18 localhost kernel: "bcm43xx": set security called
>  Jan 27 17:10:18 localhost kernel: "bcm43xx":    .active_key = 0
>  Jan 27 17:10:18 localhost kernel: "bcm43xx":    .level = 1
>  Jan 27 17:10:18 localhost kernel: "bcm43xx":    .enabled = 1
>  Jan 27 17:10:18 localhost kernel: "bcm43xx":    .encrypt = 1
>  Jan 27 17:10:18 localhost kernel: SoftMAC: Associate: Scanning for
>  networks first.
>  Jan 27 17:10:18 localhost kernel: SoftMAC: Start scanning with channel:
>  1
>  Jan 27 17:10:18 localhost kernel: SoftMAC: Scanning 13 channels
>  Jan 27 17:10:18 localhost kernel: SoftMAC: Scanning finished
>  Jan 27 17:10:18 localhost kernel: SoftMAC: Queueing Authentication
>  Request to 00:13:10:e9:5c:c2
>  Jan 27 17:10:18 localhost kernel: SoftMAC: cannot associate without
>  being authenticated, requested authentication
>  Jan 27 17:10:18 localhost kernel: SoftMAC: Queueing Authentication
>  Request to 00:13:10:e9:5c:c2
>  Jan 27 17:10:18 localhost kernel: SoftMAC: cannot associate without
>  being authenticated, requested authentication
>  Jan 27 17:10:18 localhost kernel: SoftMAC: Sent Authentication Request
>  to 00:13:10:e9:5c:c2.
>  Jan 27 17:10:18 localhost kernel: SoftMAC: Sent Authentication Request
>  to 00:13:10:e9:5c:c2.
>  Jan 27 17:10:18 localhost dhclient: DHCPDISCOVER on eth1 to
>  255.255.255.255 port 67 interval 3
>  Jan 27 17:10:21 localhost dhclient: DHCPDISCOVER on eth1 to
>  255.255.255.255 port 67 interval 3
>  Jan 27 17:10:24 localhost dhclient: DHCPDISCOVER on eth1 to
>  255.255.255.255 port 67 interval 5
>  Jan 27 17:10:29 localhost dhclient: DHCPDISCOVER on eth1 to
>  255.255.255.255 port 67 interval 5
>  Jan 27 17:10:30 localhost kernel: SoftMAC: Sent Authentication Request
>  to 00:13:10:e9:5c:c2.
>  Jan 27 17:10:30 localhost kernel: SoftMAC: Sent Authentication Request
>  to 00:13:10:e9:5c:c2.
>  Jan 27 17:10:34 localhost dhclient: DHCPDISCOVER on eth1 to
>  255.255.255.255 port 67 interval 12
>  Jan 27 17:10:42 localhost kernel: SoftMAC: Sent Authentication Request
>  to 00:13:10:e9:5c:c2.
>  Jan 27 17:10:42 localhost kernel: SoftMAC: Sent Authentication Request
>  to 00:13:10:e9:5c:c2.
>  Jan 27 17:10:46 localhost dhclient: DHCPDISCOVER on eth1 to
>  255.255.255.255 port 67 interval 20
>  Jan 27 17:10:54 localhost kernel: SoftMAC: Sent Authentication Request
>  to 00:13:10:e9:5c:c2.
>  Jan 27 17:10:54 localhost kernel: SoftMAC: Sent Authentication Request
>  to 00:13:10:e9:5c:c2.
>  Jan 27 17:11:06 localhost dhclient: DHCPDISCOVER on eth1 to
>  255.255.255.255 port 67 interval 12
>  Jan 27 17:11:06 localhost kernel: SoftMAC: Sent Authentication Request
>  to 00:13:10:e9:5c:c2.
>  Jan 27 17:11:06 localhost kernel: SoftMAC: Sent Authentication Request
>  to 00:13:10:e9:5c:c2.
>  Jan 27 17:11:18 localhost dhclient: DHCPDISCOVER on eth1 to
>  255.255.255.255 port 67 interval 1
>  Jan 27 17:11:18 localhost kernel: SoftMAC: Authentication timed out with
>  00:13:10:e9:5c:c2
>  Jan 27 17:11:18 localhost kernel: SoftMAC: cannot associate without
>  being authenticated, requested authentication
>  Jan 27 17:11:18 localhost kernel: SoftMAC: cannot associate without
>  being authenticated, requested authentication
>  Jan 27 17:11:18 localhost kernel: SoftMAC: Authentication timed out with
>  00:13:10:e9:5c:c2
>  Jan 27 17:11:18 localhost kernel: SoftMAC: cannot associate without
>  being authenticated, requested authentication
>  Jan 27 17:11:18 localhost kernel: SoftMAC: cannot associate without
>  being authenticated, requested authentication
>  Jan 27 17:11:19 localhost dhclient: No DHCPOFFERS received.
>  
>  Stanton Finley
>  http://stanton-finley.net/
>   
You need to lower the rate:

iwconfig eth1 rate 11M

Works for me...

Pete

-- 
Pete Graner                                email: <pgraner(a)redhat.com&gt;

[Stanton Finley]

On Fri, 2006-01-27 at 20:40 -0500, Pete Graner wrote:
>  You need to lower the rate:
>  
>  iwconfig eth1 rate 11M
>  
>  Works for me...
>  
>  Pete
>  
>  -- 
>  Pete Graner                                email: <pgraner(a)redhat.com&gt;
>   
Thanks for the suggestion Pete, but unless I'm doing something stupid,
(which is not uncommon), no joy. I've tried with and without WEP
encryption, different rates, Managed and Auto, DHCP and fixed IP, but
from the kernel logs it seems to be a problem with associating and
authenticating. I've been combing the threads at
http://lists.berlios.de/pipermail/bcm43xx-dev/ looking for a clue.
Perhaps a future kernel with a future softmac or dscape stack will fix
this.

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

[Pete Graner]

Stanton Finley wrote:
>  On Fri, 2006-01-27 at 20:40 -0500, Pete Graner wrote:
> > You need to lower the rate:
> >
> > iwconfig eth1 rate 11M
> >
> > Works for me...
> >
> > Pete
> >
> > -- 
> > Pete Graner                                email: <pgraner(a)redhat.com&gt;
> >
>  Thanks for the suggestion Pete, but unless I'm doing something stupid,
>  (which is not uncommon), no joy. I've tried with and without WEP
>  encryption, different rates, Managed and Auto, DHCP and fixed IP, but
>  from the kernel logs it seems to be a problem with associating and
>  authenticating. I've been combing the threads at
>  http://lists.berlios.de/pipermail/bcm43xx-dev/ looking for a clue.
>  Perhaps a future kernel with a future softmac or dscape stack will fix
>  this.
>  
>  Stanton Finley
>  http://stanton-finley.net/
>   
I've had varying degrees of success with different access points. At 
home I have a Linksys WRT54G and it works with WEP. At work I can't get 
it to work at all, I beleve we use Cisco APs but I'm not sure. I got it 
to work at Phildelphia Airport last week, but not at BWI...

I've also noticed that the Network Manager drop down that lists all of 
the available networks isn't the same between wireless cards.

I have a Cisco 350 PCMCIA card and I'll plug it into the same notebook. 
When I click on Network Manager I see both wireless cards but the Cisco 
card has 2 "other" APs that the BCM driver isn't seeing.

Also Network Manger shows zero (0) signal bars on the applet, but when 
clicking on the applet shows me that the the AP I'm associated to is at 
100%...

I'm going to update to the new Network Manager with WPA today and see if 
  any of these "just go away". If not I guss BZ here I come....

Pete

Hmm... still a young driver...
-- 
Pete Graner                                email: <pgraner(a)redhat.com&gt;

[Dan Williams]

On Sat, 2006-01-28 at 09:53 -0500, Pete Graner wrote:
>  I've also noticed that the Network Manager drop down that lists
> all of 
>  the available networks isn't the same between wireless cards. 
Each card maintains it's own internal (to the driver and the hardware)
list of scan results, which will of course vary based on supported
channels/frequencies, antenna characteristics, etc.  This is the list
that NM pulls from, so technically it shouldn't be surprising that
you've got different APs for different cards.

> From a user-perspective though, it seems odd that you'd have
> differences 
between cards that are even on the same band (ie, both b/g or both a).
But then again, it's probably wierd for lots of users to have two
wireless cards to start with.

Wireless in general is quite a bit more unpredictable.

>  I have a Cisco 350 PCMCIA card and I'll plug it into the same
> notebook. 
>  When I click on Network Manager I see both wireless cards but the Cisco 
>  card has 2 "other" APs that the BCM driver isn't seeing. 
Cisco 340/350 cards have higher transmit power than most other cards (up
to 50mW I think), and may have better antennas as well.  The
hardware/firmware itself also filters out non-broadcasting access points
from scans.

>  Also Network Manger shows zero (0) signal bars on the applet, but
> when 
>  clicking on the applet shows me that the the AP I'm associated to is at 
>  100%... 
Linux drivers notoriously SUCK when it comes to reporting signal
strength.  The open Broadcom driver actually doesn't support signal
strength yet at all, but that's being worked on.

Dan

[Peter Robinson]

>  > Also Network Manger shows zero (0) signal bars on the applet,
> but when
>  > clicking on the applet shows me that the the AP I'm associated to is at
>  > 100%...
>
>  Linux drivers notoriously SUCK when it comes to reporting signal
>  strength.  The open Broadcom driver actually doesn't support signal
>  strength yet at all, but that's being worked on. 
The interesting thing regarding this for me is that for the same card
(ipw2200) the Network Monitor that comes with gnome displays a
different (double or half - I can't remember) signal strength that
NetworkManager does. Quite bizare, but then not unexpected as I think
the WinXP and Intel applet do a similar thing!

Pete