linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Sieb <samuel@sieb.net>
To: linux-wireless@vger.kernel.org
Subject: BCM43142 doesn't work
Date: Fri, 5 Feb 2016 15:53:39 -0800	[thread overview]
Message-ID: <56B53603.4080905@sieb.net> (raw)

I found a message to this list from 2013 that indicates the BCM43142 
chipset should work:
https://marc.info/?l=linux-wireless&m=137223374523831&w=2

However, what happens is:
Feb 04 11:55:50 localhost kernel: bcma: bus0: Found chip with id 43142, 
rev 0x01 and package 0x08
Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 0 found: ChipCommon 
(manuf 0x4BF, id 0x800, rev 0x28, class 0x0)
Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 1 found: IEEE 802.11 
(manuf 0x4BF, id 0x812, rev 0x21, class 0x0)
Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 2 found: PCIe (manuf 
0x4BF, id 0x820, rev 0x16, class 0x0)
Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 3 found: UNKNOWN 
(manuf 0x43B, id 0x368, rev 0x00, class 0x0)
Feb 04 11:55:50 localhost kernel: bcma: bus0: Bus registered

Nothing else in the logs, no devices created.  Am I missing something 
like firmware?  I would prefer to not have to use a 3rd party driver or 
worse, ndiswrapper.  This is in an HP laptop.

lscpi:
03:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n 
(rev 01)
         DeviceName: Harrier
         Subsystem: Hewlett-Packard Company Device 2230
         Flags: bus master, fast devsel, latency 0, IRQ 38
         Memory at f0c00000 (64-bit, non-prefetchable) [size=32K]
         Capabilities: [40] Power Management version 3
         Capabilities: [58] Vendor Specific Information: Len=78 <?>
         Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
         Capabilities: [d0] Express Endpoint, MSI 00
         Capabilities: [100] Advanced Error Reporting
         Capabilities: [13c] Virtual Channel
         Capabilities: [160] Device Serial Number <removed>
         Capabilities: [16c] Power Budgeting <?>
         Kernel driver in use: bcma-pci-bridge
         Kernel modules: bcma

03:00.0 0280: 14e4:4365 (rev 01)
         DeviceName: Harrier
         Subsystem: 103c:2230

             reply	other threads:[~2016-02-06  0:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 23:53 Samuel Sieb [this message]
2016-02-06  0:41 ` BCM43142 doesn't work Rafał Miłecki
2016-02-06  0:54   ` Samuel Sieb

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=56B53603.4080905@sieb.net \
    --to=samuel@sieb.net \
    --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;
as well as URLs for NNTP newsgroup(s).