Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Bluetooth in HP laptop doesn't work, because the driver isn't in the kernel or packaged. There are some guides in the internet, but they aren't integrated in kernel and aren't guaranteed to work. Actual results: I can't use bluetooth. Expected results: I can use bluetooth. Additional info: Laptop: HP Pavilion g6. Ralink wifi works, but the wifi button is always red (It's supposed to be white, while wifi is enabled). Distribution: Fedora 29 KDE Spin (64 bit). All packages are updated. The problem isn't fixed in Ubuntu, OpenSUSE and Arch also.
Created attachment 1517073 [details] From Info Center
Created attachment 1517074 [details] From Info Center
Created attachment 1517075 [details] From Info Center
For completeness, could you post the output from these commands: $ uname -r $ lspci -nnk -d 1814: # include the colon From the attached screenshot, the vendor:device id is 1814:3298, which is mentioned in this bug report from 2013: Bug 907594 - Bluetooth adapter not found in 3.7 kernel but OK in 3.6
(In reply to Steve from comment #4) > For completeness, could you post the output from these commands: > > $ uname -r > $ lspci -nnk -d 1814: # include the colon > > From the attached screenshot, the vendor:device id is 1814:3298, which is > mentioned in this bug report from 2013: > > Bug 907594 - Bluetooth adapter not found in 3.7 kernel but OK in 3.6 ```uname -r: 4.19.10-300.fc29.x86_64``` ```lspci -nnk -d 1814: 07:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] DeviceName: Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Ad Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Adapter [103c:18ec] Kernel driver in use: rt2800pci Kernel modules: rt2800pci 07:00.1 Bluetooth [0d11]: Ralink corp. RT3290 Bluetooth [1814:3298] Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Adapter [103c:18ec]```
I tried to format text by adding "```". :)
bluetoothctl lags, until I close it by CTRL+c. # dmesg | grep -i bluetooth # Only gave output after su. [85022.921931] Bluetooth: Core ver 2.22 [85022.922011] Bluetooth: HCI device and connection manager initialized [85022.922015] Bluetooth: HCI socket layer initialized [85022.922017] Bluetooth: L2CAP socket layer initialized [85022.922024] Bluetooth: SCO socket layer initialized
Now, it worked as non-root.
> I tried to format text by adding "```". :) Thanks for posting the uname and lspci output. You don't need to format anything -- maintainers are used to looking at that stuff ... :-) > Now, it worked as non-root. If you are in group "wheel", you can run many administrative commands without being "root": $ groups joeuser wheel
(In reply to ali.sherif10 from comment #7) > bluetoothctl lags, until I close it by CTRL+c. Thanks for reporting that. I opened a bug for the "bluez" package: Bug 1662536 - bluetoothctl hangs when there are no bluetooth devices
(In reply to ali.sherif10 from comment #0) ... > Ralink wifi works, but the wifi button is always red (It's supposed to be > white, while wifi is enabled). ... Getting the LEDs to work is a separate problem. I suggest opening a new bug for that.
BTW, it might be faster and easier to buy a USB bluetooth adapter at a well-known online retailer. This one has Linux support: Plugable USB Bluetooth 4.0 Low Energy Micro Adapter (Windows 10, 8.1, 8, 7, Raspberry Pi, Linux Compatible; Classic Bluetooth, and Stereo Headset Compatible)
*********** 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 29 kernel bugs. Fedora 29 has now been rebased to 4.20.5-200.fc29. 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 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 3 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.