Bluetooth connects but doesn't show any device

It’s a CSR 4.0 Dongle. Everything normal excepts bluetooth. It keeps searching for devices but doesn’t show anything. Its a phone from Samsung and a logitech keyboard.

udo systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2022-06-26 01:52:44 -03; 8min ago
Docs: man:bluetoothd(8)
Main PID: 2472 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 4560)
Memory: 1.9M
CPU: 27ms
CGroup: /system.slice/bluetooth.service
└─2472 /usr/lib/bluetooth/bluetoothd

lsmod | grep btusb
btusb 65536 0
btrtl 28672 1 btusb
btbcm 20480 1 btusb
btintel 45056 1 btusb
bluetooth 737280 5 btrtl,btintel,btbcm,btusb

rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

Something related to this :

https://wiki.archlinux.org/title/Bluetooth#Device_does_not_show_up_in_scan

1 Like

Or is it related to the new linux-firmware package which gives an error when loading the bluetooth firmware - at least on some PCs.

1 Like

journalctl -b -0 | grep Bluetooth
would tell …

2 Likes

journalctl -b -0 | grep Bluetooth
jun 26 13:25:31 pedro-h81mh systemd[529]: Starting Bluetooth OBEX Agent…
jun 26 13:25:31 pedro-h81mh systemd[529]: Condition check resulted in Bluetooth OBEX Agent being skipped.
jun 26 13:25:33 pedro-h81mh systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
jun 26 13:27:48 pedro-h81mh systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
jun 26 13:30:26 pedro-h81mh systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

When I go to sys/class I found no folder called bluetooth and seems that I can not edit this to create a bluetooth one. Any ideia?

Create the directory:

sudo mkdir /sys/class/bluetooth

Then reboot and look again.

mkdir: could not create directory “/sys/class/bluetooth”: Operation not permitted.

tf is that? Sorry bothering, pal.

have you used sudo?

Yes, unfortunately, it isn’t working.

[root@pedro-h81mh devices]# sudo mkdir /sys/class/bluetooth
mkdir: could not create directory “/sys/class/bluetooth”: Operation not permitted.
[root@pedro-h81mh devices]# mkdir /sys/class/bluetooth
mkdir: não foi possível criar o diretório “/sys/class/bluetooth”: Operação não permitida
[root@pedro-h81mh devices]#

Are you using root as standard user for logging into you system?

1 Like

Can you show the output of

ls -al /sys/class/bluetooth

Yes I am using root for logging sir.

ls -al /sys/class/bluetooth
ls: não foi possível acessar ‘/sys/class/bluetooth’: Arquivo ou diretório inexistente (couldn’t access /sys/class/bluetooth. File or directory doesn’t exist.

This probably means your system is messed up then. I wouldn’t know how to get out of this problem, as your root user seems restricted (it cannot create a directory in /sys/ wich it should normally be able to do.)

Sorry…

You can not create folders in /sys. Not even as root. /sys is a kernel filesystem like /proc. Only the kernel can make changes to it.

Thanks for the heads-up. I wasn’t aware of this. Just tried & found out myself that you are right!

:blush: