public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: BRM <bm_witness@yahoo.com>
To: Users Gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] b43-legacy and newer linux kernels?
Date: Thu, 12 Aug 2010 22:10:02 -0700 (PDT)	[thread overview]
Message-ID: <726837.95093.qm@web51904.mail.re2.yahoo.com> (raw)

I have a laptop that has been running Linux Kernel 2.6.30 Gentoo-R8 (gentoo 
sources, don't remember which version) for a while. It has a Broadcom 4306 Rev 2 
wireless card that has been working well with that kernel. I extracted the 
firmware from the broadcom-wl-4.150.10.5 blob a while ago using b43-fwcutter 
011. I have to hard-code the network settings in /etc/conf.d/net for my home 
network, but am able to use wpa_supplicant whenever I go elsewhere. (I think 
it's my home wireless router that causes the issue; probably needs a firmware 
upgrade.)

Any how, I recently upgraded to Linux Kernel 2.6.34 Gentoo-R7 (gentoo-sources 
2.6.34-r1); again using the b43-legacy driver for the wireless. However, now I 
can't keep a network connection up. I keep getting errors from the 
/etc/init.d/net.wlan0 startup - namely: SIOCSIFFLAGS Unknown Error 132. I had to 
reboot onto the older kernel to write this message and try to research the issue 
a little.

From on-line, some sites suggest the following as a solution:

rmmod ath9k
rfkill block all
rfkill unblock all
modprobe ath9k
rfkill unblock all
however, rfkill seems to only be in testing for gentoo 
(http://packages.gentoo.org/package/net-wireless/rfkill), and I'm using the 
b43-legacy instead of the ath9k driver - okay, no problem there, just switch out 
which driver is unloaded and reloaded. Haven't tried it yet as I have to reboot; 
but even so - they are saying this has to be done on every reboot, and that's 
not much of a solution.

Further, I can't seem to find a version of b43-fwcutter that will extract any of 
the b43-legacy firmware - even the one I had successfully extracted (011, 012, 
13).

Has anyone else seen this? Does anyone know if this gets resolved (or made 
worse) by a newer kernel?

Ben




             reply	other threads:[~2010-08-13  6:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13  5:10 BRM [this message]
2010-08-13  8:08 ` [gentoo-user] b43-legacy and newer linux kernels? Neil Bothwick
2010-08-13 16:08   ` Mick
2010-08-13 17:58     ` BRM
2010-08-13 18:24       ` Bill Longman
2010-08-14 10:18         ` Mick
2010-08-14 10:27           ` Mick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=726837.95093.qm@web51904.mail.re2.yahoo.com \
    --to=bm_witness@yahoo.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox