From: Chris Vine <vine35792468@gmail.com>
To: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Fw: Regression: bcm4312 lp-phy device not recognized in 4.15 kernel
Date: Sun, 4 Feb 2018 18:58:55 +0000 [thread overview]
Message-ID: <20180204185855.74e6ade5@bother.homenet> (raw)
I probably should have copied this to the relevant kernel wireless
mailing lists. Anyway, here it is.
As a further datum point, the b43 driver works fine with the 4.15.0-rc3
kernel. So something seems to have changed between that and 4.15.0.
Chris
Begin forwarded message:
Date: Mon, 29 Jan 2018 23:37:49 +0000
From: Chris Vine <vine35792468@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Regression: bcm4312 lp-phy device not recognized in 4.15 kernel
I have an old netbook with a Broadcom bcm4312 802.11b/g lp-phy
[14e4:4315] (rev 01) wifi device. It is no longer recognized in kernel
4.15: it works fine with the 4.14 kernel and earlier, with the b43 and
ssb kernel modules.
I cannot give any further information as there are no error messages
logged. The b43 firmware (wl-5.100.138) is not loaded for it, nor are
the ssb/b43/bcma/ mmc_core/mac80211/cfg80211 modules. The modules can
be loaded by hand without error, but nothing happens and no network
interface is presented.
This is a pretty slow and rubbish netbook but is useful when travelling
to a country which might impound your laptop (no names) and you don't
mind too much losing it. It would be nice to continue to be able to
use it for that.
Chris
next reply other threads:[~2018-02-04 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 18:58 Chris Vine [this message]
2018-02-04 20:03 ` Fw: Regression: bcm4312 lp-phy device not recognized in 4.15 kernel Florian Fainelli
2018-02-04 22:00 ` Chris Vine
2018-02-05 10:26 ` Chris Vine
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=20180204185855.74e6ade5@bother.homenet \
--to=vine35792468@gmail.com \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.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