Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: The bluetooth adapter is not working (the icon is not preset in the system tray and also it says that no bluetooth adapters were found in the gnome system settings) on the 3.7 kernel. However, booting into 3.6 kernel everything is fine.
I am not seeing this problem; I suspect it is hardware-specific. What type and model of machine are you using? I think you should be able to get the version of the Bluetooth hardware with the working kernel and running "hciconfig hci0 version", assuming you do see hci0 in the list from "hciconfig" with no arguments.
I think it is hardware-specific too. I have a HP Pavilion g6 laptop with Ralink rt3290 wifi card. When I press the wifi button on my laptop, which is the same if I want to disable bluetooth, it does nothing. I know that experimental support for this wifi card was introduced in 3.6 kernel which worked fine, and I do not know if it is the 3.7 version fault. Anyways this bug it is annoying. Hciconfig returns nothing.
Is this working with 3.8 kernels?
I do not know what is happening with these new kernels because now I do not have internet connection with 3.8. And if I would have, it quickly disconnect. I use just 3.6 that works perfecctly. I tried openSUSE 12.3 and the same problem with 3.7, so its related to the kernel, not Fedora.
I have same symptoms with a HP 4340s with Ralink RT3290 under F18. With kernel 3.8.3-201.fc18.x86_64 the bluetooth adaptor is not detected and the hardware switch does nothing. The light on the hardware switch is orange, not white as it in under Windows. Works fine under windows. There is no 3.6 kernel for F18 on koji so can't try that.
FWIW same problem with 3.9rc3
I can provide logs etc - just let me know which...
lspci -v 03:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth Subsystem: Hewlett-Packard Company Device 18ec Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at d0600000 (32-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-00-d8-5c-b1-31-17-a4
lspci -nn 03:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] 03:00.1 Bluetooth [0d11]: Ralink corp. RT3290 Bluetooth [1814:3298]
There seem to be several threads about this on the web. There is a driver available for this model: http://www.zotac.com/components/gpd_download/Download/count.php?var=2396&driverlink=http://downloads.zotac.com/mediadrivers/mb/download/NB087_Ubuntu.zip but I haven't yet got it to compile (F18). My laptop has a SLED 11 sticker so a bit disappointed not to be able to get this working.
I am facing the same problem. Laptop: HP Sleekbook 15 *** Kernel: 3.6.10-4.fc18.x86_64 (Fedora 18 DVD Install) - Wireless enable/disable button works (light doesn't work, stays orange, should turn white when wifi is enabled) - Bluetooth doesn't work. bluedevil says no adapter found, how ever rfkill lists the bluetooth lspci -nn 07:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] 07:00.1 Bluetooth [0d11]: Ralink corp. RT3290 Bluetooth [1814:3298] rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: no 2: hp-bluetooth: Bluetooth Soft blocked: no Hard blocked: no *** Kernel: 3.8.4-202.fc18.x86_64 - Wireless enable/disable button doesn't work, stays permanently on (lucky!) and the light as ususal stays permanently orange. - Bluetooth doesn't work. bluedevil says no adapter found AND rfkill sees nothing! lspci 07:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] 07:00.1 Bluetooth [0d11]: Ralink corp. RT3290 Bluetooth [1814:3298] rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no lspci -nn 07:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] 07:00.1 Bluetooth [0d11]: Ralink corp. RT3290 Bluetooth [1814:3298]
Similar problem here, with newer kernel. It looks as if the usb-bluetooth-dongle is not working. It works in Fedora 17 and in Windows 7. The Bluetooth settings in KDE says no adaptors found. Here is the system information that I could find: uname -a Linux localhost.localdomain 3.10.3-300.fc19.x86_64 #1 SMP Fri Jul 26 00:00:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux lsusb ... Bus 001 Device 005: ID 0a5c:2100 Broadcom Corp. Bluetooth 2.0+eDR dongle dmesg | grep -i blue [ 8.285325] Bluetooth: Core ver 2.16 [ 8.285364] Bluetooth: HCI device and connection manager initialized [ 8.285380] Bluetooth: HCI socket layer initialized [ 8.285383] Bluetooth: L2CAP socket layer initialized [ 8.285391] Bluetooth: SCO socket layer initialized [ 33.076981] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 33.076985] Bluetooth: BNEP filters: protocol multicast [ 33.076998] Bluetooth: BNEP socket layer initialized [ 834.206412] Bluetooth: RFCOMM TTY layer initialized [ 834.206430] Bluetooth: RFCOMM socket layer initialized [ 834.206431] Bluetooth: RFCOMM ver 1.11 [ 1752.307480] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 1752.307496] Bluetooth: HIDP socket layer initialized rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:19:86:00:21:8F ACL MTU: 1017:8 SCO MTU: 64:0 DOWN RX bytes:1852 acl:0 sco:0 events:68 errors:0 TX bytes:284 acl:0 sco:0 commands:68 errors:0 hcitool dev Devices:
*********** 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 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. 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 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
All kernels on this hardware doesn't recognize the bluetooth adapter... I thought it is a Fedora bug, but all distros have the same issue, so it is a kernel bug...
I just used fedup to upgrade from ver. 19 to 20, hoping it would solve the bluetooth issue because it hasn't been working for awhile now and I saw that Fedora 20 had a new Bluez version. The bluetooth adapter on my Dell E6400 is not recognized and it appears that no device is created for it. I upgraded because I saw a previous bug report ( https://ask.fedoraproject.org/question/34791/no-bluetooth-adapters-found-broadcom-bcm2046b1-or-dell-wireless-365-bluetooth/ ) which suggests an upgrade would fix it. It also suggests that at least one person using Ubuntu showed an additional device with lsusb and bluetooth worked there. I've included many of the displays I'm getting, which are the same as I was getting under f19. [root@localhost dhoch]# uname -a Linux localhost.localdomain 3.12.7-300.fc20.x86_64 #1 SMP Fri Jan 10 15:35:31 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [root@localhost dhoch]# rpm -qa | grep bluez bluez-libs-5.13-1.fc20.x86_64 bluez-cups-5.13-1.fc20.x86_64 pybluez-0.18-7.fc20.x86_64 bluez-5.13-1.fc20.x86_64 bluez-hid2hci-5.13-1.fc20.x86_64 [root@localhost dhoch]# systemctl -l status bluetooth.service bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled) Active: active (running) since Thu 2014-01-16 07:47:58 MST; 2h 30min ago Docs: man:bluetoothd(8) Main PID: 7334 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─7334 /usr/libexec/bluetooth/bluetoothd Jan 16 07:47:58 localhost.localdomain bluetoothd[7334]: Bluetooth daemon 5.13 Jan 16 07:47:58 localhost.localdomain systemd[1]: Started Bluetooth service. Jan 16 07:47:58 localhost.localdomain bluetoothd[7334]: Starting SDP server Jan 16 07:47:58 localhost.localdomain bluetoothd[7334]: Bluetooth management interface 1.3 initialized [root@localhost dhoch]# dmesg | grep -i blue [ 501.478526] Bluetooth: Core ver 2.16 [ 501.478603] Bluetooth: HCI device and connection manager initialized [ 501.478613] Bluetooth: HCI socket layer initialized [ 501.478615] Bluetooth: L2CAP socket layer initialized [ 501.478621] Bluetooth: SCO socket layer initialized [ 501.485028] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 501.485032] Bluetooth: BNEP filters: protocol multicast [ 501.485041] Bluetooth: BNEP socket layer initialized [root@localhost dhoch]# dmesg | grep -i 0a5c [ 2.059931] usb 3-1: New USB device found, idVendor=0a5c, idProduct=4500 [ 2.440994] usb 5-1: New USB device found, idVendor=0a5c, idProduct=5800 [root@localhost dhoch]# dmesg | grep -i 413c [ 3.389920] usb 3-1.1: New USB device found, idVendor=413c, idProduct=8157 [ 3.396331] input: HID 413c:8157 as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.1/3-1.1:1.0/input/input9 [ 3.396422] hid-generic 0003:413C:8157.0003: input,hidraw2: USB HID v1.11 Keyboard [HID 413c:8157] on usb-0000:00:1a.0-1.1/input0 [ 3.574932] usb 3-1.2: New USB device found, idVendor=413c, idProduct=8158 [ 3.582532] input: HID 413c:8158 as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0/input/input10 [ 3.582635] hid-generic 0003:413C:8158.0004: input,hidraw3: USB HID v1.11 Mouse [HID 413c:8158] on usb-0000:00:1a.0-1.2/input0 These returned nothing: [root@localhost dhoch]# dmesg | grep -i hci0 [root@localhost dhoch]# dmesg | grep -i rfkill [root@localhost dhoch]# dmesg | grep -i rfcomm [root@localhost dhoch]# lsusb Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 002: ID 046d:c51b Logitech, Inc. V220 Cordless Optical Mouse for Notebooks Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 0c45:63f8 Microdia Sonix Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 004: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick Bus 003 Device 003: ID 413c:8157 Dell Computer Corp. Integrated Keyboard Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub [root@localhost dhoch]# hciconfig list Can't get device info: No such device [root@localhost dhoch]# bluetoothctl [bluetooth]# power on No default controller available [root@localhost dhoch]# hcitool dev Devices: [root@localhost dhoch]# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 2: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no [root@localhost dhoch]# lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07) 00:03.2 IDE interface: Intel Corporation Mobile 4 Series Chipset PT IDER Controller (rev 07) 00:03.3 Serial controller: Intel Corporation Mobile 4 Series Chipset AMT SOL Redirection (rev 07) 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03) 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation G98M [Quadro NVS 160M] (rev a1) 03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21) 03:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 11) 0c:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01) There used to be main.conf, rfcomm.conf, & another one under /etc/bluetooth, they aren't there anymore since the upgrade. Don't know what the problem is, but I've found many bugs surrounding the bluetooth service going back to pre-15 releases. I found one closed bug report #1023720 which claims the problem was fixed with an upgrade to older versions of kernel and bluez then what I'm currently running. Thanks for any help!
Mine is all working now on Dell e6400 ~]$ uname -r 3.13.3-201.fc20.x86_64 ~]$ yum list bluez* Loaded plugins: langpacks, refresh-packagekit Installed Packages bluez.x86_64 5.14-1.fc20 @updates bluez-cups.x86_64 5.14-1.fc20 @updates bluez-hcidump.x86_64 2.5-3.fc20 @fedora bluez-hid2hci.x86_64 5.14-1.fc20 @updates bluez-libs.x86_64 5.14-1.fc20 @updates ~]$ lsusb Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 002: ID 046d:c51b Logitech, Inc. V220 Cordless Optical Mouse for Notebooks Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 0c45:63f8 Microdia Sonix Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 005: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card Bus 003 Device 004: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick Bus 003 Device 003: ID 413c:8157 Dell Computer Corp. Integrated Keyboard Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bluetooth not working in fedora20 [welcome@localhost ~]$ uname -a Linux localhost.localdomain 3.14.0-0.rc6.git2.2.fc21.x86_64 #1 SMP Wed Mar 12 15:01:36 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lspci -v 06:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Adapter Flags: bus master, fast devsel, latency 0, IRQ 36 Memory at f0210000 (32-bit, non-prefetchable) [size=64K] Capabilities: <access denied> Kernel driver in use: rt2800pci 06:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Adapter Flags: bus master, fast devsel, latency 0 Memory at f0200000 (32-bit, non-prefetchable) [size=64K] Capabilities: <access denied> [welcome@localhost ~]$ [welcome@localhost ~]$ bluetoothctl [bluetooth]# list [bluetooth]# power on No default controller available [bluetooth]# [welcome@localhost ~]$ dmesg | grep -i bluetooth [ 41.536256] Bluetooth: Core ver 2.18 [ 41.536489] Bluetooth: HCI device and connection manager initialized [ 41.536505] Bluetooth: HCI socket layer initialized [ 41.536511] Bluetooth: L2CAP socket layer initialized [ 41.536535] Bluetooth: SCO socket layer initialized [ 41.545645] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 41.545654] Bluetooth: BNEP filters: protocol multicast [ 41.545673] Bluetooth: BNEP socket layer initialized [welcome@localhost ~]$ [welcome@localhost ~]$ lsusb Bus 002 Device 002: ID 05c8:0361 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [welcome@localhost ~]$
[welcome@localhost ~]$ rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no [welcome@localhost ~]$
This bug is open since 2013-02-04. Is there a chance that it will be resolved ? Bluetooth with RT3290LE still not working in fedora20...
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.