* BCM43142 doesn't work
@ 2016-02-05 23:53 Samuel Sieb
2016-02-06 0:41 ` Rafał Miłecki
0 siblings, 1 reply; 3+ messages in thread
From: Samuel Sieb @ 2016-02-05 23:53 UTC (permalink / raw)
To: linux-wireless
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: BCM43142 doesn't work
2016-02-05 23:53 BCM43142 doesn't work Samuel Sieb
@ 2016-02-06 0:41 ` Rafał Miłecki
2016-02-06 0:54 ` Samuel Sieb
0 siblings, 1 reply; 3+ messages in thread
From: Rafał Miłecki @ 2016-02-06 0:41 UTC (permalink / raw)
To: Samuel Sieb; +Cc: linux-wireless@vger.kernel.org
On 6 February 2016 at 00:53, Samuel Sieb <samuel@sieb.net> wrote:
> 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
Which means bcma (bus!) supports BCM43132. It detects bus (!) devices
correctly and registers them. There is no driver supporting wireless
device found on this chipset.
It's a bit like having support for PCI bus. You still need driver for
various devices that can be found/connected to such bus.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: BCM43142 doesn't work
2016-02-06 0:41 ` Rafał Miłecki
@ 2016-02-06 0:54 ` Samuel Sieb
0 siblings, 0 replies; 3+ messages in thread
From: Samuel Sieb @ 2016-02-06 0:54 UTC (permalink / raw)
To: linux-wireless@vger.kernel.org
On 02/05/2016 04:41 PM, Rafał Miłecki wrote:
> On 6 February 2016 at 00:53, Samuel Sieb <samuel@sieb.net> wrote:
>> 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
>
> Which means bcma (bus!) supports BCM43132. It detects bus (!) devices
> correctly and registers them. There is no driver supporting wireless
> device found on this chipset.
>
Thank you, that makes sense. So I will need a 3rd party driver after
all. Unfortunately, the wireless chipset is not one of the specs listed
in most stores.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-02-06 1:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-05 23:53 BCM43142 doesn't work Samuel Sieb
2016-02-06 0:41 ` Rafał Miłecki
2016-02-06 0:54 ` Samuel Sieb
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).