Bug 1599138
| Summary: | kernel 4.17 does not recognize hardware AMDGPU or load Broadcom wifi module | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul Lambert <eb30750> | ||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 27 | CC: | airlied, bskeggs, dtvjhoE10, dujingshan, dwagelaar, ewk, giuseppe.catastini, hdegoede, ichavero, itamar, jarodwilson, jcline, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, mchehab, mjg59, red, steved | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2018-09-26 18:58:07 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 1457339 [details]
dmesg output
Can you reproduce this without the out-of-tree drivers (i.e. virtualbox) Sorry, I gave that comment on the wrong bug. Upgraded to kernel 4.17.5. Little help. Appears that Bluetooth now works still no wifi and amdgpu still broke broadcom BCM4312 working with kernel 4.16.xx; in dmesg you find wl: module license 'MIXED/Proprietary' taints kernel. Disabling lock debugging due to kernel taint wl: module verification failed: signature and/or required key missing - tainting kernel eth0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) broadcom BCM4312 NOT working with kernel 4.16.xx; in dmesg you find wl: loading out-of-tree module taints kernel. wl: module license 'MIXED/Proprietary' taints kernel. Disabling lock debugging due to kernel taint wl: module verification failed: signature and/or required key missing - tainting kernel So, messages are the same regarding kernel tainting, but kernel 4.6.xx properly loads at the end the module and provides eth0. What is not clear for me is "loading out-of-tree module kernel taints": why out-of-tree module? It is built from akmods from FC28 broadcom-wl-6.30.223.271-6.fc28.noarch rpm. This rpm comes through dnf and RPMfusion repository: perhaps this is the reason of troubles (not full open source code). First there are no issues with Linux 4.16 kernel. All networking was working with 4.16 kernel. Last I was using was 4.16.15 When I upgraded to 4.17.3 Bluetooth, WiFi and probably usb was broke. In addition there is no amdgpu driver nor a driver for an acer-like device. Kernel 4.17.6 did recognize the WiFi device but it would not work. With kernel 4.17.7 the WiFi device is not even recognized. Maybe more security has been added to the module loader and the kernel device drivers are simply not loading. I have attempted to uncover if this is the case by grepping the log files. Not found any consistent error messages. I would like to believe theiris only one root cause for the driver omissions. And, once the cause is identified it is a quick fix. I did not answer the out of tree question. I have assimilated the Broadcom source code for the 4365 version (and more recent). This is well beyond the previous bm driver. I have identified all the crashes and patched the code to where there are no kernel crashes from this driver. However, there are some crashes due to bugs in sme.c code which is based in Linux. I reported it to that org. When a new kernel comes out I reboot without networking and the run my own script that compiles the 4365 driver with the new kernel. The script then copies the wl.ko file to the new kernel module directory. Then reboot. So yes the kernel Broadcom WiFi driver is external to the compiled Fedora tree. The hardware device drivers exist in binary code and do not need modifying. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.17.7-100.fc27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28. If you experience different issues, please open a new bug report for those. Verified on Fedora 28 that: 1) broadcom BCM4312 is properly working with kernel 4.16.xx. 2) broadcom BCM4312 NOT working with kernel 4.17.xx (tested up to version 4.17.7-200.fc28.x86_64 lspci -l provide same output booting with kernel 4.16.xx and 4.17.xx wl module properly compiled and loaded, also if dmesg provides (for both 4.16 and 4.17): wl: loading out-of-tree module taints kernel. wl: module license 'MIXED/Proprietary' taints kernel. Disabling lock debugging due to kernel taint wl: module verification failed: signature and/or required key missing - tainting kernel When booting with kernel 4.16.xx dmesg output has additional line after the above last reported one: eth0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) lspci -k provides the same output booting with kernel 4.16.xx or kernel 4.17.xx Sorry for the above misprinting lspci -k 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03) Subsystem: Dell Device 0256 00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 03) Kernel driver in use: pcieport Kernel modules: shpchp 00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) Subsystem: Dell Device 0256 Kernel driver in use: uhci_hcd 00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) Subsystem: Dell Device 0256 Kernel driver in use: uhci_hcd 00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) Subsystem: Dell Device 0256 Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) Subsystem: Dell Studio 1735 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 03) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) Subsystem: Dell Device 0256 Kernel driver in use: uhci_hcd 00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) Subsystem: Dell Device 0256 Kernel driver in use: uhci_hcd 00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) Subsystem: Dell Device 0256 Kernel driver in use: uhci_hcd 00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) Subsystem: Dell Device 0256 Kernel driver in use: ehci-pci 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HM (ICH8M) LPC Interface Controller (rev 03) Subsystem: Dell Device 0256 Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 03) Subsystem: Dell Device 0256 Kernel driver in use: ahci 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03) Subsystem: Dell Device 0256 Kernel driver in use: i801_smbus Kernel modules: i2c_i801 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] Subsystem: Dell Device 0256 Kernel driver in use: radeon Kernel modules: radeon 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV635 HDMI Audio [Radeon HD 3650/3730/3750] Subsystem: Dell Device 0256 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) Subsystem: Dell Device 0256 Kernel driver in use: firewire_ohci Kernel modules: firewire_ohci 03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) Subsystem: Dell Device 0256 Kernel driver in use: sdhci-pci Kernel modules: sdhci_pci 03:01.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) Subsystem: Dell Device 0256 Kernel driver in use: r592 Kernel modules: r592 03:01.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12) Subsystem: Dell Device 0256 09:00.0 Ethernet controller: Broadcom Limited NetLink BCM5784M Gigabit Ethernet PCIe (rev 10) Subsystem: Dell Device 0256 Kernel driver in use: tg3 Kernel modules: tg3 0c:00.0 Network controller: Broadcom Limited BCM4312 802.11b/g LP-PHY (rev 01) Subsystem: Dell Wireless 1397 WLAN Mini-Card Kernel driver in use: wl Kernel modules: ssb, wl Concur with comment 9 and comment 10. The kernel is broken in 4.17.xx whether it be Fedora 27 or 28. This is my wifi hardware running kernel 4.16.12 lspci -vnn -d 14e4: 02:00.0 Network controller [0280]: Broadcom Limited BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:804a] Flags: bus master, fast devsel, latency 0, IRQ 42 Memory at f0b00000 (64-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: wl Kernel modules: wl Same with a Broadcom BCM4321. Running fedora 28 x86-64. broadcom-wl works in kernel 4.16.xx, but does not work in any 4.17.xx released as of today. I have also tested the dkms version but it did not help. Created attachment 1471911 [details]
dmsg output for kernel 4.17.10
Issues in dmesg showed the following
no wifi
no amdgpu
Acer_WMI unsupported (Laptop is sold as an HP)
DRAM ECC_Disabled
Same problem for an AMD RX560 GPU (https://www.msi.com/Graphics-card/Radeon-RX-560-AERO-ITX-4G-OC.html). Works on kernel-4.16.16-200.fc27.x86_64, broken on kernel-4.17.11-100.fc27.x86_64, kernel-4.17.12-100.fc27.x86_64. I can confirm the new kernel breaks Broadcom Wifi drivers on Macbooks4,1 which work up until 4.16.18 and break with 4.17+ (up to current 4.19-pre builds). fpaste --sysinfo (of said macbook) https://paste.fedoraproject.org/paste/AmtogS2g-ou9TWd1ci9sog There are other bugs open for the same problem: Bug 1572349 , https://bugzilla.rpmfusion.org/show_bug.cgi?id=4978. I also submitted the problem to Broadcom via some commercial email contacts, but I suppose someone with better contacts than mines should pitch in and help bring broadcom in on the problem. I may be onto something here. Comparing the output of lspci on the two different kernels I notice the following differences:
4.17 Kernel driver in use: b43-pci-bridge
Kernel modules: wl
vs
4.16 Kernel driver in use: wl
Kernel modules: ssb, wl
In the logs (only of kernel 4.17+):
====================================
ago 23 18:13:25 pc-clara.localdomain kernel: b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
ago 23 18:24:38 pc-clara.localdomain kernel: b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
ago 23 18:27:59 pc-clara.localdomain kernel: b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
ago 23 18:39:59 pc-clara.localdomain kernel: b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
ago 23 18:54:15 pc-clara.localdomain kernel: b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
I would like to try and get rid of that "b43-pci-bridge". But apparently I cannot. Not even physically removing b43.ko from disk and rebuilding the initial ram disk.
No amount of blacklisting seem to work either.
Is by any chance this driver integrated directly into the kernel and not compiled separately as a module?
Could I disable it momentarily, without rebuilding the kernel?
Full output of lspci:
=====================
Kernel 4.17+
============
[root@macbook ~]# lspci -vnn -d 14e4:
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4321 802.11a/b/g/n [14e4:4328] (rev 03)
[omissis] Subsystem: Apple Inc. AirPort Extreme [106b:0088]
Physical Slot: 4
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at d0500000 (64-bit, non-prefetchable) [size=16K]
Memory at d0000000 (64-bit, prefetchable) [size=1M]
Capabilities: [40] Power Management version 2
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [e8] 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 2b-68-e9-ff-ff-dc-00-21
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: b43-pci-bridge
Kernel modules: wl
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4321 802.11a/b/g/n [14e4:4328] (rev 03)
Subsystem: Apple Inc. AirPort Extreme [106b:0088]
Physical Slot: 4
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at d0500000 (64-bit, non-prefetchable) [size=16K]
Memory at d0000000 (64-bit, prefetchable) [size=1M]
Capabilities: [40] Power Management version 2
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [e8] 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 2b-68-e9-ff-ff-dc-00-21
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: wl
Kernel modules: ssb, wl
I may be onto something here. Comparing the output of lspci on the two different kernels I notice the following differences:
4.17 Kernel driver in use: b43-pci-bridge
Kernel modules: wl
vs
4.16 Kernel driver in use: wl
Kernel modules: ssb, wl
In the logs (only of kernel 4.17+):
====================================
ago 23 18:13:25 pc-clara.localdomain kernel: b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
ago 23 18:24:38 pc-clara.localdomain kernel: b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
ago 23 18:27:59 pc-clara.localdomain kernel: b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
ago 23 18:39:59 pc-clara.localdomain kernel: b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
ago 23 18:54:15 pc-clara.localdomain kernel: b43-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002)
I would like to try and get rid of that "b43-pci-bridge". But apparently I cannot. Not even physically removing b43.ko from disk and rebuilding the initial ram disk.
No amount of blacklisting seem to work either.
Is by any chance this driver integrated directly into the kernel and not compiled separately as a module?
Could I disable it momentarily, without rebuilding the kernel?
Full output of lspci:
=====================
Kernel 4.17+
============
[root@macbook ~]# lspci -vnn -d 14e4:
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4321 802.11a/b/g/n [14e4:4328] (rev 03)
[omissis] Subsystem: Apple Inc. AirPort Extreme [106b:0088]
Physical Slot: 4
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at d0500000 (64-bit, non-prefetchable) [size=16K]
Memory at d0000000 (64-bit, prefetchable) [size=1M]
Capabilities: [40] Power Management version 2
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [e8] 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 2b-68-e9-ff-ff-dc-00-21
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: b43-pci-bridge
Kernel modules: wl
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4321 802.11a/b/g/n [14e4:4328] (rev 03)
Subsystem: Apple Inc. AirPort Extreme [106b:0088]
Physical Slot: 4
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at d0500000 (64-bit, non-prefetchable) [size=16K]
Memory at d0000000 (64-bit, prefetchable) [size=1M]
Capabilities: [40] Power Management version 2
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [e8] 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 2b-68-e9-ff-ff-dc-00-21
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: wl
Kernel modules: ssb, wl
sorry for the double comment... Justin, Can we get an update on this issue. Kernel 4.17.19 does not work which the most recent fc27 kernel release. Not using the proper kernel driver (b43 instead of wl) as reported in comment #16 looks like a possible root cause. If fc28 fixes this bug then I am willing to upgrade. However, I can't except upgrading to fc28 and not being able to still boot from fc27 4.16.12 should fc28 still fail. Fc28 works with kernels from fc27, but you can always install 4.16.16 for fc28 from koji. https://koji.fedoraproject.org/koji/buildinfo?buildID=1092581 I confirm Davide's comment 18 above. I run FC27 on a Dell D630 laptop, noticed no WiFi for the past few months. Now I'm on the road and the lack of WiFi is hurting. This laptop has 2 WiFi cards, Broadcom BCM4321 and the older BCM4312. PCI ID was 4328 for the 4321 chip. Did a bit of digging, the b43 isn't the best choice, RH's choice of wl is right. Here's what I get: [root@vista ~]# lspci -vnn -d 14e4: <snip> 0b:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4321 802.11a/b/g/n [14e4:4328] (rev 01) Subsystem: AMBIT Microsystem Corp. Device [1468:0319] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f6cfc000 (64-bit, non-prefetchable) [size=16K] Memory at f0000000 (64-bit, prefetchable) [size=1M] Capabilities: [40] Power Management version 2 Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [15c] Power Budgeting <?> Kernel driver in use: b43-pci-bridge Kernel modules: wl 0c:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01) Subsystem: Dell Wireless 1395 WLAN Mini-Card [1028:000b] Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at f6bfc000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [58] Vendor Specific Information: Len=78 <?> Capabilities: [e8] 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 7c-aa-5f-ff-ff-68-00-22 Capabilities: [16c] Power Budgeting <?> Kernel driver in use: b43-pci-bridge Kernel modules: wl I can test fixes. Created attachment 1486561 [details]
dmesg output
Kernel 4.18.9-100.fc27.x86_64 still missing Broadcom wl and amdgpu Hi Paul, Let's track the Broadcom issue in https://bugzilla.redhat.com/show_bug.cgi?id=1572349. Since this bug is nearly all about that issue I'm going to mark it as a duplicate of that one. If you're still experiencing a problem with amdgpu, please open a separate bug report about just that. Thanks! *** This bug has been marked as a duplicate of bug 1572349 *** Opened bug #1634389 for amdgpu issue. |
Created attachment 1457338 [details] lspci -nn outpur Description of problem: kernel 4.17 has broken the drivers for AMDGPU and Broadcom Wifi Version-Release number of selected component (if applicable): 4.17.4 How reproducible: every bootup Steps to Reproduce: 1. 2. 3. Actual results: Expected results: These device drivers have worked at least back to fc24 Additional info: Attached lspci --nn for 4.16.12 and 4.17.4 Attached dmesg for 4.17.4 boot