Bluetooth adapter not found on Pavillion g6

Ask Fedora
1

Hi, i am new to linux and i tried install fedora 40 on my old laptop but bluetooth doesn’t work. It says no adapter found. Can anyone help with solution?

2

Welcome to fedora @arman1990

Please have a look here > Start Here to see what is necessary, so that we can help you.

Many times the Bluetooth device is paired with the WIFI adapter, so we would need to know more about your hardware specifications.

3

i use system fedora 40 workstation. I searched internet and i found that i need to reveal my bluetooth hardware. I tried lspcie -nnk on terminal and on wi fi and bluetooth adapter it shows:

02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290]
	DeviceName: Ralink RT3290LE 802.11bgn 1x1 Wi-Fi Adapter
	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
02: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]

P.S. Sorry that i don’t know how properly paste terminal text in forums and advice in that would be helpful.

4

That part is easy.
Simply either use the </> button on the toolbar to mark the text you have already pasted as ‘preformatted text’ or put the triple backquotes ( ``` ) on the line before the text and on the line following the text so it appears as you can see in your post above. (I edited that post for you). You can see the way it appears by editing your own post and looking at the way I marked it.

The bluetooth chipset does not show a separate driver with your output above. Since bluetooth is managed as a usb channel try using lsusb to identify the bus and device ID for that chipset then use lsusb -s BUS:DEVICE -v to get the full details for that device. Replace BUS and DEVICE with the 3 digit bus and device numbers given with the first use of lsusb.

You can also use bluetoothctl to see if the device is manageable by the system.

5

Thank you very much for help. Now i understand and use this.

6

i used lsusb and didn’t found any mention of bluetooth this what it shows

Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 18f8:0f99 [Maxxter] Optical gaming mouse
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 04f2:b34f Chicony Electronics Co., Ltd HP Truevision HD
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 04d9:1602 Holtek Semiconductor, Inc. USB Keyboard
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

i tried bluetoothctl and it hanging on this

Waiting to connect to bluetoothd...

.

7

topic up

8

What output gives the following command:

sudo rfkill list It should show all no nothing blocked.

If something is hard blocked you have to unblock with (see my example below, in my case it is device 1):

sudo rfkill list
0: phy0: Wireless LAN
	Soft blocked: yes
	Hard blocked: no
1: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no
[ilikelinux@host ~] $ sudo rfkill unblock 1
9

sudo rfkill list shows wirelss LAN and does’t show bluetooth

0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
10

The adapter is obviously seen by the system. Apparently the driver is not loading for it or does not properly support it.

Please reboot then run sudo dmesg | grep -i blu and let us know the result. It should show the device being configured or possibly failing to properly configure.

11

i tried sudo dmesg | grep -i blu and its nothing happens as though i should type new command

armanabikenov@fedora:~$ sudo dmesg | grep -i blu
armanabikenov@fedora:~$ sudo dmesg | grep -i blu
12

This then seems an issue with the rt2800pci driver for that adapter.
Search on the internet about others having issues with the RT3290LE device and you may find a driver solution. You can also add the chipset ID [ 1814:3290 ] and [1814:3298]