From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Wireless is not working after upgrading kernel to 4.2.0-rc5-00183-g3fbdc37
Date: Sun, 9 Aug 2015 11:26:44 -0500 [thread overview]
Message-ID: <55C77F44.1080408@lwfinger.net> (raw)
In-Reply-To: <CAGQKE9sN1bU8YtmLZa2eLyahwjxr3mRAVmsd5ixMiXgAXGKrGQ@mail.gmail.com>
On 08/09/2015 09:35 AM, srinivas k wrote:
> Hi,
>
> I have upgrade my kernel to 4.2.0-rc5-00183-g3fbdc37, after upgrading
> i could not see my wireless is working.
>
>
> Here is the outpt of "lspci -nn -d 14e4:"
>
> penguin at penguin:~$ lspci -nn -d 14e4:
> 07:00.0 Network controller [0280]: Broadcom Corporation BCM43142
> 802.11b/g/n [14e4:4365] (rev 01)
>
> Sorry for my bad english,
According to https://wireless.wiki.kernel.org/en/users/Drivers/b43, that device
is not supported by b43. The only driver for that device is wl, the proprietary
driver by Broadcom. That driver needs to be reinstalled every time the kernel is
changed. That is what you need to do.
Larry
next prev parent reply other threads:[~2015-08-09 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 14:35 Wireless is not working after upgrading kernel to 4.2.0-rc5-00183-g3fbdc37 srinivas k
2015-08-09 16:26 ` Larry Finger [this message]
2015-08-09 17:57 ` Rafał Miłecki
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=55C77F44.1080408@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