Re: broadcom-sta-source driver problem

[Guillaume Lécroart <ggmail@goug.ath.cx>]

Hi there

I'm experiencing the same issue, so I'll try to recap

Squeeze's b43 module does not support bcm4312

The alternative is to use the 'hybrid' wl module provided by broadcom-sta-source and compiled locally using module-assistant.


latest update broke things since the wl module loads without creating the ethX interface.

Upgrading to unstable is not an option either since DMA errors re-set the b43 driver on my platform (red somewhere thatn may be related to ATOM proc).

To make a darker picture, the tg3 (wired ethernet) driver is also broken on this platform (Lenovo ideapad s10) since it randomly freezes with no reason.. 

In other term this netbook now becomes a NoNetBook... ;-)

Anybody else experienced this? Shall I fill a bug report?

2010/1/20 Florian Reitmeir <florian@reitmeir.org>

Hi,

in my simple understanding:
http://linuxwireless.org/en/users/Drivers/b43#firmware_installation

under debian, installing:
  sudo apt-get install b43-fwcutter

should be enough.

On Tue, 19 Jan 2010, Deryk Barker wrote:

John Kapnogiannis wrote:

On Tuesday 19 January 2010 22:53:47 Thierry Chatelet wrote:
 

Well I checked with both and there isn't any interface for wireless. Only
 lo and eth0 for the ethernet.

J
     

I am not really good with broadcom wireless, but as far as I remember, you
have to have a firmware to install, using bcm43xx-fwcutter.
Hum... dont get mad at me if I am wrong
Thierry

   

I suppose I don't a firmware cause the card is currently working just fine with the previous version of the driver which I kept in a backup. I think I should email the maintainer and then file a bug or something. I just hoped someone had a clue about this cause I am out of ideas.
 

If you are upgrading from and earlier kernel then you should indeed  already have the firmware.

One thing I ran into several times (although I think some distros have  stopped doing this) was that each new kernel version came with its own  /lib/firmware directory, so the firmware may simply be in the wrong  location.

Check your logs: if the bcm43xx module has loaded but complains about  missing firware, you might try pointing a find at /lib and looking for it.

good luck

deryk


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

--
Florian Reitmeir

--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org