Well, I did test the Mainline Build Kernel 4.16 as suggested. Here are
the results:
$ lspci
00:00.0 Host bridge: Intel Corporation Device 3ec2 (rev 07)
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07)
00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Device a2af
00:16.0 Communication controller: Intel Corporation Device a2ba
00:17.0 SATA controller: Intel Corporation Device a282
00:1b.0 PCI bridge: Intel Corporation Device a2e7 (rev f0)
00:1b.2 PCI bridge: Intel Corporation Device a2e9 (rev f0)
00:1b.4 PCI bridge: Intel Corporation Device a2eb (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a290 (rev f0)
00:1c.1 PCI bridge: Intel Corporation Device a291 (rev f0)
00:1c.2 PCI bridge: Intel Corporation Device a292 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Device a294 (rev f0)
00:1c.6 PCI bridge: Intel Corporation Device a296 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device a298 (rev f0)
00:1d.5 PCI bridge: Intel Corporation Device a29d (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a2c9
00:1f.2 Memory controller: Intel Corporation Device a2a1
00:1f.3 Audio device: Intel Corporation Device a2f0
00:1f.4 SMBus: Intel Corporation Device a2a3
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960]
(rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 0fba (rev a1)
05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02)
07:00.0 Ethernet controller: Qualcomm Atheros Device e0b1 (rev 10)
08:00.0 USB controller: ASMedia Technology Inc. Device 2142
09:00.0 USB controller: ASMedia Technology Inc. Device 2142
0b:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 10)
$
$ lspci -vv
[...]
05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02)
Subsystem: Apple Inc. AirPort Extreme
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at ef500000 (64-bit, non-prefetchable) [disabled]
[size=16K]
Capabilities: <access denied>
Kernel modules: bcma
07:00.0 Ethernet controller: Qualcomm Atheros Device e0b1 (rev 10)
Subsystem: Gigabyte Technology Co., Ltd Device e000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at ef400000 (64-bit, non-prefetchable) [size=256K]
Region 2: I/O ports at d000 [size=128]
Capabilities: <access denied>
Kernel driver in use: alx
Kernel modules: alx
[...]
$
So this time it looks like the network adapter is recognized by the
kernel 4.16 (it was UNCLAIMED by kernel 4.15).
Both the Wi-Fi network adapter and Bluetooth are recognized. However,
Ubuntu System Settings does not see any Wi-Fi ... So it can't connect
through anything Wi-Fi ...
It looks like there is definitely a bug in kernel 4.15.0, although I
don't know why Ubuntu can't see the recognized Wi-Fi network adapter in
kernel 4.16.0.
How can we label this bug then ? Is it considered kernel-fixed-upstream
? though there is no Wi-Fi recognized by Ubuntu Xenial 16.04 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760108
Title:
Broadcom B43 Wireless Driver Not Functional after Update to Linux
Kernel 4.15
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760108/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
