From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Using b43 with broadcom 4312 on hp2133 yields "device not ready"
Date: Sat, 15 Apr 2017 11:28:46 -0500 [thread overview]
Message-ID: <a9ead8f0-d135-d84a-9a68-9f08294315c3@lwfinger.net> (raw)
In-Reply-To: <c92149c95e371f5d4dc914210a8f46b8@out-of-bounds.de>
On 04/14/2017 03:13 PM, registration at out-of-bounds.de wrote:
> Hi again,
>
> when using google on the "channel switch error", I came across the commands
> "iwlist" and "iw" so find their output enclosed in the hopes it helps.
>
> Trying "iw phy0 set channel x" did not work, though: device busy
>
> I also found a reference to a kernel patch regarding the issue/error message:
> https://patchwork.kernel.org/patch/4276461/
That patch was applied to kernel code on May 31, 2014.
> hope that helps you help me ;-)
I'm not sure how much help I can give you. I have now built a modern kernel for
my netbook. On it the BCM4312 works fine. That system had older firmware on it
so I downloaded the newest file and installed it. The device still works, thus I
think we can rule out some unexpected changes in either the driver or the
firmware. I was using kernel 4.11.0-rc5.
My conclusion is that your hardware is defective. Unfortunately, although a
replacement part can be obtained on E-Bay for less that $4, replacing the WLAN
module on that particular laptop requires complete disassembly. I would not
recommend that unless you have considerable experience.
My suggestion is that you purchase a USB adapter for this laptop. If you are
willing to purchase from E-Bay, the small, dual-band 802.11ac devices are under
$20 US. I'm not sure what they will cost in Germany.
Larry
prev parent reply other threads:[~2017-04-15 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 11:28 Using b43 with broadcom 4312 on hp2133 yields "device not ready" registration at out-of-bounds.de
2017-04-14 15:28 ` Larry Finger
[not found] ` <c92149c95e371f5d4dc914210a8f46b8@out-of-bounds.de>
2017-04-15 16:28 ` Larry Finger [this message]
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=a9ead8f0-d135-d84a-9a68-9f08294315c3@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).