Description of problem: The Asus Z87-Delux motherboard has an onboard wifi/bluetooth radio. The wifi works using the akmod-wi Broadcom driver but the Bluetooth card does not even show up with lspci nor lsusb. lspi shows the wifi card as: Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03) But nothing for the bluetooth... This is a brand new system with an intel i7-4770 CPU. Everything else seems to work flawlessly and well with F20. I have verified the BT is enabled in the bios. Version-Release number of selected component (if applicable): How reproducible: Constantly Steps to Reproduce: 1.Install fedora20 with Gnome desktop on a system with an Asus Z87-Delux motherboard 2.try to find the bluetooth device from system settings->Bluetooth or lspci, lsusb, etc. Actual results: No bluetooth device detected. Expected results: Bluetooth detected and working. Additional info: Please help me complete my new hot system and get the BT working. :) Cheers, Jon
Hello, Just checking in, its been about a month now and I had not heard anything back about this. Will this be investigated? Is there anything I can do to help sort this out? Best regards, Jon
This is a kernel or a hardware problem. Either the Bluetooth device isn't available anymore, or the kernel doesn't see it or cannot enable it.
Its not a hardware problem and its a brand new motherboard and combo card. Obviously its a kernel driver problem. Your response is cryptic. Are you saying you will not be investigating it, or what? This same board works out of the box in ubuntu as can be seen with a search so it seems obvious to me that its a Fedora kernel issue... Will you be investigating the issue or not? Jon
Same problem as above, New MOBO/BT/WIFI BCM4352 is not recognized. [root@teraquad ~]# lspci -vnn -d 14e4: 09:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:855c] Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at fb400000 (64-bit, non-prefetchable) [size=32K] Memory at fb200000 (64-bit, non-prefetchable) [size=2M] Capabilities: [48] Power Management version 3 Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [68] Vendor Specific Information: Len=44 <?> Capabilities: [ac] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Device Serial Number 54-27-00-ff-ff-00-00-01 Capabilities: [150] Power Budgeting <?> Capabilities: [160] Virtual Channel Capabilities: [1b0] Latency Tolerance Reporting Capabilities: [220] #15 Kernel driver in use: wl Kernel modules: wl [root@teraquad ~]#
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is 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 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. 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 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
The bug still exists, no bluetooth. [jon@localhost-localdomain ~]$ uname -a Linux localhost-localdomain 3.17.2-200.fc20.x86_64 #1 SMP Tue Nov 4 18:04:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [jon@localhost-localdomain ~]$ sudo lspci -vnn -d 14e4: [sudo] password for jon: 0a:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:855c] Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at f7600000 (64-bit, non-prefetchable) [size=32K] Memory at f7400000 (64-bit, non-prefetchable) [size=2M] Capabilities: [48] Power Management version 3 Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [68] Vendor Specific Information: Len=44 <?> Capabilities: [ac] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Device Serial Number 24-0a-00-ff-ff-00-00-01 Capabilities: [150] Power Budgeting <?> Capabilities: [160] Virtual Channel Capabilities: [1b0] Latency Tolerance Reporting Capabilities: [220] #15 Kernel driver in use: wl Kernel modules: wl Cheers, Jon
I now am developing an application using BT and would really love to be able to use this radio for testing. Has there been any progress in looking at this bug? Perhaps someone knows of a workaround for now? Thanks! Jon
I think, this is the same: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1382302 Maybe someone should send this upstream, but I can’t find a bluez-bugtracker …
I have the same problem Dell inspiron 3521 with BCM43142 Wifi is working well I have fedora 21 with latest updates kernel: 3.17.7-300.fc21.x86_64
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is 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 20 kernel bugs. Fedora 20 has now been rebased to 3.18.7-100.fc20. 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 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
Sorry I guess I missed the last note. This bug is still present with no change, please reopen the bug. Kernel: 3.19.5-100.fc20.x86_64 Cheers, Jon
Based on the Ubuntu thread, the support is now in the kernel driver to load the necessary firmware but the firmware itself isn't packaged. The firmware would need to come from an official source so we could jump through all the legal hoops (see https://fedoraproject.org/wiki/Licensing:Main#Binary_Firmware and https://fedoraproject.org/wiki/Firmware) if we wanted to actually package the firmware. Without the firmware, I don't think there is much that can be done here. Closing this bug. A separate discussion can be had about bringing in the firmware if an approved source is found.