Brodcom 43 Failing of FC8

[Michael D. Berger]

I installed FC8 on my dual boot laptop, and ran "yum update".
when I try to activate Broadcom 43 my wifi, I get:


   SIOCSIFFLAGS: No such file or directory

   Determining IP information for wlan0...SIOCSIFFLAGS: No
   such file or directory
   SIOCSIFFLAGS: No such file or directory

Note lspci:
...
02:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN 
Mini-PCI Card (rev 01)
...

Any suggestions?

Thanks,
Mike.

[Martin Marques]

Mike -- EMAIL IGNORED escribió:
>  I installed FC8 on my dual boot laptop, and ran "yum
> update".
>  when I try to activate Broadcom 43 my wifi, I get:
>  
>  
>     SIOCSIFFLAGS: No such file or directory
>  
>     Determining IP information for wlan0...SIOCSIFFLAGS: No
>     such file or directory
>     SIOCSIFFLAGS: No such file or directory
>  
>  Note lspci:
>  ...
>  02:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN 
>  Mini-PCI Card (rev 01)
>  ...
>  
>  Any suggestions? 
Check dmesg. There must be more info there (especially when b43 is loaded).

[Michael D. Berger]

On Thu, 31 Jan 2008 17:25:57 -0200, Martin Marques wrote:

>  Mike -- EMAIL IGNORED escribió:
> > I installed FC8 on my dual boot laptop, and ran "yum update". when I
> > try to activate Broadcom 43 my wifi, I get:
> > 
> > 
> >    SIOCSIFFLAGS: No such file or directory
> > 
> >    Determining IP information for wlan0...SIOCSIFFLAGS: No such file or
> >    directory
> >    SIOCSIFFLAGS: No such file or directory
> > 
> > Note lspci:
> > ...
> > 02:00.0 Network controller: Broadcom Corporation Dell Wireless 1390
> > WLAN Mini-PCI Card (rev 01)
> > ...
> > 
> > Any suggestions?
>  
>  Check dmesg. There must be more info there (especially when b43 is
>  loaded). 
Yes, indeed, dmesg:

b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/
   Drivers/b43#devicefirmware and download the correct firmware
   (version 4).
input: b43-phy0 as /class/input/input13

Thanks again,
Mike.

[Michael D. Berger]

On Thu, 31 Jan 2008 20:40:09 +0000, Mike -- EMAIL IGNORED wrote:

>  On Thu, 31 Jan 2008 17:25:57 -0200, Martin Marques wrote:
>  
> > Mike -- EMAIL IGNORED escribió:
> >> I installed FC8 on my dual boot laptop, and ran "yum update". when I
> >> try to activate Broadcom 43 my wifi, I get:
> >> 
> >> 
> >>    SIOCSIFFLAGS: No such file or directory
> >> 
> >>    Determining IP information for wlan0...SIOCSIFFLAGS: No such file
> >>    or directory
> >>    SIOCSIFFLAGS: No such file or directory
> >> 
> >> Note lspci:
> >> ...
> >> 02:00.0 Network controller: Broadcom Corporation Dell Wireless 1390
> >> WLAN Mini-PCI Card (rev 01)
> >> ...
> >> 
> >> Any suggestions?
> > 
> > Check dmesg. There must be more info there (especially when b43 is
> > loaded).
>  
>  Yes, indeed, dmesg:
>  
>  b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.
>  b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/
>     Drivers/b43#devicefirmware and download the correct firmware (version
>     4).
>  input: b43-phy0 as /class/input/input13
>  
>  Thanks again,
>  Mike. 
So I did what it says, and:

[root@mbrc15 driver]# which b43-fwcutter
/usr/bin/b43-fwcutter
[root@mbrc15 driver]# b43-fwcutter -v
b43-fwcutter version 009
[root@mbrc15 driver]# b43-fwcutter -w /lib/firmware/ wl_apsta_mimo.o
Sorry, the input file is either wrong or not supported by b43-fwcutter.
This file has an unknown MD5sum cb8d70972b885b1f8883b943c0261a3c.
[root@mbrc15 driver]#
root@mbrc15 driver]# pwd
/root/broadcom/broadcom-wl-4.150.10.5/driver

Any ideas?

Thanks,
Mike.

[Michael D. Berger]

On Thu, 31 Jan 2008 23:23:55 +0000, Mike -- EMAIL IGNORED wrote:

>  On Thu, 31 Jan 2008 20:40:09 +0000, Mike -- EMAIL IGNORED wrote:
>  
> > On Thu, 31 Jan 2008 17:25:57 -0200, Martin Marques wrote:
> > 
> >> Mike -- EMAIL IGNORED escribió:
> >>> I installed FC8 on my dual boot laptop, and ran "yum update". when
> I
> >>> try to activate Broadcom 43 my wifi, I get:
> >>> 
> >>> 
> >>>    SIOCSIFFLAGS: No such file or directory
> >>> 
> >>>    Determining IP information for wlan0...SIOCSIFFLAGS: No such file
> >>>    or directory
> >>>    SIOCSIFFLAGS: No such file or directory
> >>> 
> >>> Note lspci:
> >>> ...
> >>> 02:00.0 Network controller: Broadcom Corporation Dell Wireless 1390
> >>> WLAN Mini-PCI Card (rev 01)
> >>> ...
> >>> 
> >>> Any suggestions?
> >> 
> >> Check dmesg. There must be more info there (especially when b43 is
> >> loaded).
> > 
> > Yes, indeed, dmesg:
> > 
> > b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.
> > b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/
> >    Drivers/b43#devicefirmware and download the correct firmware
> >    (version 4).
> > input: b43-phy0 as /class/input/input13
> > 
> > Thanks again,
> > Mike.
>  
>  So I did what it says, and:
>  
>  [root@mbrc15 driver]# which b43-fwcutter /usr/bin/b43-fwcutter
>  [root@mbrc15 driver]# b43-fwcutter -v b43-fwcutter version 009
>  [root@mbrc15 driver]# b43-fwcutter -w /lib/firmware/ wl_apsta_mimo.o
>  Sorry, the input file is either wrong or not supported by b43-fwcutter.
>  This file has an unknown MD5sum cb8d70972b885b1f8883b943c0261a3c.
>  [root@mbrc15 driver]#
>  root@mbrc15 driver]# pwd
>  /root/broadcom/broadcom-wl-4.150.10.5/driver
>  
>  Any ideas?
>  
>  Thanks,
>  Mike. 
Wait .. I see I used the wrong firmware version for my kernel.

Mike.

[Martin Marques]

Mike -- EMAIL IGNORED escribió:
>  
>  Wait .. I see I used the wrong firmware version for my kernel. 
Use the right driver and tell use how it turned out.

[Jeff Burns]

>  Wait .. I see I used the wrong firmware version for my kernel.
>  
>  Mike.
>   
Hi Mike,

You need to grab this file:

http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2

Extract and then do

[]# b43-fwcutter
-w /lib/firmware/ /path/to/broadcom-wl-4.80.53.0/kmod/wl_apsta.o

This is what brought my BCM4306 to life.

HTH,

Jeff

[Robert P. J. Day]

On Fri, 1 Feb 2008, Jeff Burns wrote:

>  > Wait .. I see I used the wrong firmware version for my kernel.
>  >
>  > Mike.
>  >
>
>  Hi Mike,
>
>  You need to grab this file:
>
>  http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
>
>  Extract and then do
>
>  []# b43-fwcutter
>  -w /lib/firmware/ /path/to/broadcom-wl-4.80.53.0/kmod/wl_apsta.o
>
>  This is what brought my BCM4306 to life. 
not to sound repetitive, but my wiki page has a fairly reliable set of
instructions that have worked for me.

http://www.crashcourse.ca/wiki/index.php/Broadcom_wireless_on_Fedora_8

rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

Home page:                                         http://crashcourse.ca
Fedora Cookbook:    http://crashcourse.ca/wiki/index.php/Fedora_Cookbook
========================================================================

[Jeff Burns]

On Fri, 2008-02-01 at 03:39 -0500, Robert P. J. Day wrote:
>  On Fri, 1 Feb 2008, Jeff Burns wrote: 
[snip]
>  > []# b43-fwcutter
>  > -w /lib/firmware/ /path/to/broadcom-wl-4.80.53.0/kmod/wl_apsta.o
>  >
>  > This is what brought my BCM4306 to life.
>  
>  not to sound repetitive, but my wiki page has a fairly reliable set of
>  instructions that have worked for me.
>  
>  http://www.crashcourse.ca/wiki/index.php/Broadcom_wireless_on_Fedora_8
>  
>  rday 
Well that would have saved me some time! Thanks for the link. Your site
has been bookmarked.

Jeff

[Terry Polzin]

On Friday February 1 2008, Robert P. J. Day wrote:
>  On Fri, 1 Feb 2008, Jeff Burns wrote:
>  > > Wait .. I see I used the wrong firmware version for my kernel.
>  > >
>  > > Mike.
>  >
>  > Hi Mike,
>  >
>  > You need to grab this file:
>  >
>  > http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
>  >
>  > Extract and then do
>  >
>  > []# b43-fwcutter
>  > -w /lib/firmware/ /path/to/broadcom-wl-4.80.53.0/kmod/wl_apsta.o
>  >
>  > This is what brought my BCM4306 to life.
>
>  not to sound repetitive, but my wiki page has a fairly reliable set of
>  instructions that have worked for me.
>
>  http://www.crashcourse.ca/wiki/index.php/Broadcom_wireless_on_Fedora_8 
Robert & list:

I've followed the instructions on your wiki to no avail. (yesterday)
Today booting 1 kernel back everything seems to load.  
Now to jump right in and get wep running.
What does your /etc/sysconfig/wpa_supplicant look like.

THANKS,

Terry

Hardware Platform; Dell latitude D630 (directly out of the crate)
OS; CentOs 5.1 (to date only thing that will run anaconda)

[Robert P. J. Day]

On Sun, 3 Feb 2008, Terry Polzin wrote:

>  On Friday February 1 2008, Robert P. J. Day wrote:
>  > On Fri, 1 Feb 2008, Jeff Burns wrote:
>  > > > Wait .. I see I used the wrong firmware version for my kernel.
>  > > >
>  > > > Mike.
>  > >
>  > > Hi Mike,
>  > >
>  > > You need to grab this file:
>  > >
>  > > http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
>  > >
>  > > Extract and then do
>  > >
>  > > []# b43-fwcutter
>  > > -w /lib/firmware/ /path/to/broadcom-wl-4.80.53.0/kmod/wl_apsta.o
>  > >
>  > > This is what brought my BCM4306 to life.
>  >
>  > not to sound repetitive, but my wiki page has a fairly reliable set of
>  > instructions that have worked for me.
>  >
>  > http://www.crashcourse.ca/wiki/index.php/Broadcom_wireless_on_Fedora_8
>
>  Robert & list:
>
>  I've followed the instructions on your wiki to no avail. (yesterday)
>  Today booting 1 kernel back everything seems to load. 
???.  so your current kernel didn't work, but the previous one did?
curious.  if you followed those instructions in the wiki, and did the
associated debugging commands, at any point did you not get the
expected output?  i'm just curious at what step things went wrong.

>  Now to jump right in and get wep running.
>  What does your /etc/sysconfig/wpa_supplicant look like. 
i didn't do anything with wpa_supplicant.  my goal on that page was
to, absolutely minimally, get wireless working.  once that's verified
to work, any extra customization beyond that is just gravy, so that
why i stop where i did.  but maybe i should write some more, just for
the heck of it.

rday

p.s.  based on really recent developments, i'm willing to believe that
some content on that wiki page is already out of date.  if it is, feel
free to let me know.

--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

Home page:                                         http://crashcourse.ca
Fedora Cookbook:    http://crashcourse.ca/wiki/index.php/Fedora_Cookbook
========================================================================

[Terry Polzin]

On Friday February 1 2008, Robert P. J. Day wrote:
>  On Fri, 1 Feb 2008, Jeff Burns wrote:
>  > > Wait .. I see I used the wrong firmware version for my kernel.
>  > >
>  > > Mike.
>  >
>  > Hi Mike,
>  >
>  > You need to grab this file:
>  >
>  > http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
>  >
>  > Extract and then do
>  >
>  > []# b43-fwcutter
>  > -w /lib/firmware/ /path/to/broadcom-wl-4.80.53.0/kmod/wl_apsta.o
>  >
>  > This is what brought my BCM4306 to life.
>
>  not to sound repetitive, but my wiki page has a fairly reliable set of
>  instructions that have worked for me.
>
>  http://www.crashcourse.ca/wiki/index.php/Broadcom_wireless_on_Fedora_8
>
>  rday
>  --
>  ========================================================================
>  Robert P. J. Day
>  Linux Consulting, Training and Annoying Kernel Pedantry
>  Waterloo, Ontario, CANADA
>
>  Home page:                                         http://crashcourse.ca
>  Fedora Cookbook:    http://crashcourse.ca/wiki/index.php/Fedora_Cookbook
>  ======================================================================== 
I take it all back, according to /var/log/messages it still can't load any 
firmware, specifically it wants /lib/firmware/bcm43xx_microcode5.fw.

fwcutter didn't produce a file by that name.  Am I missing a step?

[Terry Polzin]

>  I take it all back, according to /var/log/messages it still can't
> load any
>  firmware, specifically it wants /lib/firmware/bcm43xx_microcode5.fw.
>
>  fwcutter didn't produce a file by that name.  Am I missing a step? 

I've found a tarball via Google search that had the files I needed.
I'm still curious though on how to get there myself in the event I ever need 
newer firmware.

[Martin Marques]

Mike -- EMAIL IGNORED escribió:
>  
>  So I did what it says, and:
>  
>  [root@mbrc15 driver]# which b43-fwcutter
>  /usr/bin/b43-fwcutter
>  [root@mbrc15 driver]# b43-fwcutter -v
>  b43-fwcutter version 009
>  [root@mbrc15 driver]# b43-fwcutter -w /lib/firmware/ wl_apsta_mimo.o 
Did you copy and paste that? You have an extra space. before 
wl_apsta_mimo.o.

BTW, what's the diference between the wl_apsta_mimo.o and the wl_apsta.o?

>  Sorry, the input file is either wrong or not supported by
> b43-fwcutter.
>  This file has an unknown MD5sum cb8d70972b885b1f8883b943c0261a3c. 
Did that tar give any error?

>  [root@mbrc15 driver]#
>  root@mbrc15 driver]# pwd
>  /root/broadcom/broadcom-wl-4.150.10.5/driver 

I'm using broadcom-wl-4.80.53.0.tar.bz2-

[Michael D. Berger]

On Thu, 31 Jan 2008 22:58:07 -0200, Martin Marques wrote:

>  Mike -- EMAIL IGNORED escribió:
> > 
> > So I did what it says, and:
> > 
> > [root@mbrc15 driver]# which b43-fwcutter /usr/bin/b43-fwcutter
> > [root@mbrc15 driver]# b43-fwcutter -v b43-fwcutter version 009
> > [root@mbrc15 driver]# b43-fwcutter -w /lib/firmware/ wl_apsta_mimo.o
>  
>  Did you copy and paste that? You have an extra space. before
>  wl_apsta_mimo.o. 
I did paste it.  That space belongs there,  The -w is followed
by the target directory.  Then a space and the filename.

>  
>  BTW, what's the diference between the wl_apsta_mimo.o and the
>  wl_apsta.o? 
I don't know; I did what I was told.

>  
> > Sorry, the input file is either wrong or not supported by b43-fwcutter.
> > This file has an unknown MD5sum cb8d70972b885b1f8883b943c0261a3c.
>  
>  Did that tar give any error? 
No tar error.

>  
> > [root@mbrc15 driver]#
> > root@mbrc15 driver]# pwd
> > /root/broadcom/broadcom-wl-4.150.10.5/driver
>  
>  
>  I'm using broadcom-wl-4.80.53.0.tar.bz2- 
Yes, that was my last error.  I switched to the version you are
using and it now works, unencrypted, but with MAC authentication.

I have yet to try WPA encryption.  Have you tried it?  Tomorrow
I leave for a long weekend, so I won't try it until next week.
However with the wifi working, I should be able to look at the
newsgroup.

Thanks again for your help.
Mike.

[Robert P. J. Day]

On Fri, 1 Feb 2008, Mike -- EMAIL IGNORED wrote:

>  On Thu, 31 Jan 2008 22:58:07 -0200, Martin Marques wrote:
>
>  > Mike -- EMAIL IGNORED escribió:
>  >>
>  >> So I did what it says, and:
>  >>
>  >> [root@mbrc15 driver]# which b43-fwcutter /usr/bin/b43-fwcutter
>  >> [root@mbrc15 driver]# b43-fwcutter -v b43-fwcutter version 009 
those first two commands don't seem to make much sense -- why would
you run the "which" command on b43-fwcutter only to have an extra
argument of the fully-qualified file name?  i'm guessing you combined
the which command and its output on a single line, and that's really
not a good idea if you're trying to explain what you did.

rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

Home page:                                         http://crashcourse.ca
Fedora Cookbook:    http://crashcourse.ca/wiki/index.php/Fedora_Cookbook
========================================================================

[Michael D. Berger]

On Fri, 01 Feb 2008 03:30:12 -0500, Robert P. J. Day wrote:

>  On Fri, 1 Feb 2008, Mike -- EMAIL IGNORED wrote:
>  
> > On Thu, 31 Jan 2008 22:58:07 -0200, Martin Marques wrote:
> >
> > > Mike -- EMAIL IGNORED escribió:
> > >>
> > >> So I did what it says, and:
> > >>
> > >> [root@mbrc15 driver]# which b43-fwcutter /usr/bin/b43-fwcutter
> > >> [root@mbrc15 driver]# b43-fwcutter -v b43-fwcutter version 009
>  
>  those first two commands don't seem to make much sense -- why would you
>  run the "which" command on b43-fwcutter only to have an extra argument
>  of the fully-qualified file name?  i'm guessing you combined the which
>  command and its output on a single line, and that's really not a good
>  idea if you're trying to explain what you did.
>  
>  rday
>  -- 
[...]

Yes, I see now that lines were inappropriately merged. I had:

[root@mbrc15 driver]# which b43-fwcutter
/usr/bin/b43-fwcutter
[root@mbrc15 driver]# b43-fwcutter -v
b43-fwcutter version 009
[root@mbrc15 driver]# b43-fwcutter -w /lib/firmware/ wl_apsta_mimo.o
Sorry, the input file is either wrong or not supported by b43-fwcutter.
This file has an unknown MD5sum cb8d70972b885b1f8883b943c0261a3c.
[root@mbrc15 driver]#
[root@mbrc15 driver]# pwd
/root/broadcom/broadcom-wl-4.150.10.5/driver


which I hope appears as 10 lines, as it did when I originally
posted it.  In any case, this is OBE, since I was using the
wrong version.  It is now working, but I am yet to try encryption.

Mike.

[Robert P. J. Day]

On Fri, 1 Feb 2008, Mike -- EMAIL IGNORED wrote:

>  On Fri, 01 Feb 2008 03:30:12 -0500, Robert P. J. Day wrote:
>
>  > On Fri, 1 Feb 2008, Mike -- EMAIL IGNORED wrote:
>  >
>  >> On Thu, 31 Jan 2008 22:58:07 -0200, Martin Marques wrote:
>  >>
>  >> > Mike -- EMAIL IGNORED escribió:
>  >> >>
>  >> >> So I did what it says, and:
>  >> >>
>  >> >> [root@mbrc15 driver]# which b43-fwcutter /usr/bin/b43-fwcutter
>  >> >> [root@mbrc15 driver]# b43-fwcutter -v b43-fwcutter version 009
>  >
>  > those first two commands don't seem to make much sense -- why would you
>  > run the "which" command on b43-fwcutter only to have an extra argument
>  > of the fully-qualified file name?  i'm guessing you combined the which
>  > command and its output on a single line, and that's really not a good
>  > idea if you're trying to explain what you did.
>  >
>  > rday
>  > --
>  [...]
>
>  Yes, I see now that lines were inappropriately merged. I had:
>
>  [root@mbrc15 driver]# which b43-fwcutter
>  /usr/bin/b43-fwcutter
>  [root@mbrc15 driver]# b43-fwcutter -v
>  b43-fwcutter version 009
>  [root@mbrc15 driver]# b43-fwcutter -w /lib/firmware/ wl_apsta_mimo.o
>  Sorry, the input file is either wrong or not supported by b43-fwcutter.
>  This file has an unknown MD5sum cb8d70972b885b1f8883b943c0261a3c.
>  [root@mbrc15 driver]#
>  [root@mbrc15 driver]# pwd
>  /root/broadcom/broadcom-wl-4.150.10.5/driver
>
>
>  which I hope appears as 10 lines, as it did when I originally
>  posted it.  In any case, this is OBE, since I was using the
>  wrong version.  It is now working, but I am yet to try encryption. 
when i first tried the above several weeks ago, i couldn't get even
simple WEP encryption to work.  more recently, though, encryption
seems to work fine.  let me know if you run across anything
interesting, and i can add it to the wiki page.

rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

Home page:                                         http://crashcourse.ca
Fedora Cookbook:    http://crashcourse.ca/wiki/index.php/Fedora_Cookbook
========================================================================

[Martin Marques]

Mike -- EMAIL IGNORED escribió:
>  On Thu, 31 Jan 2008 22:58:07 -0200, Martin Marques wrote:
> > I'm using broadcom-wl-4.80.53.0.tar.bz2-
>  
>  Yes, that was my last error.  I switched to the version you are
>  using and it now works, unencrypted, but with MAC authentication.
>  
>  I have yet to try WPA encryption.  Have you tried it?  Tomorrow
>  I leave for a long weekend, so I won't try it until next week.
>  However with the wifi working, I should be able to look at the
>  newsgroup. 
Yes I using WPA. Try NetworkManager. Works great.