Using latest fedora 41 with Plasma Mobile, I can’t get Bluetooth to work. Nothing shows up running bluetoothctl list. It’s an intel wireless 7265, which shows up as a network controller under lspci, but the bluetooth part doesnt. hciconfig returns nothing.

Steps I’ve taken:

sudo modprobe bluetooth

sudo dnf install bluez bluez-utils

sudo systemctl start bluetooth

I’m having deja vu where I followed all these steps before, but somehow I’m stuck here. Thank you for any help.

  • potentiallynotfelix@lemmy.fishOP
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    17 hours ago

    dmesg | grep -i bluetooth says this after loading bluetooth with modprobe:

    Bluetooth: Core ver 2.22
    
    NET: Registered PF_BLUETOOTH protocol family
    
    Bluetooth: HCI device and connection manager initialized
    
    Bluetooth: HCI socket layer initialized
    
    Bluetooth: L2CAP socket layer initialized
    
    Bluetooth: SC0 socket later initialized
    

    Rfkill only lists my wlan device which is unlocked.

    • anon5621@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      17 hours ago

      Usual plasma using bluedevil as frontend for Bluetooth does it installed? And what log saying in Bluetooth service sudo systemctl status bluetooth?

      • potentiallynotfelix@lemmy.fishOP
        link
        fedilink
        arrow-up
        1
        ·
        7 hours ago

        Plasma mobile is probably different, I only see bluetoothctl and bluemoon from bluez-utils. When I run bluetoothctl power on it says No default controller available. systemctl status bluetooth initially returns inactive (dead) with no logs, and when I start it it gives the log:

        Jan 20 16:24:38 solstice systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
        

        This error is fixed by running modprobe bluetooth as root. I can start bluetoothctl, and it runs successfully. The systemd logs return:

        Jan 20 16:25:29 solstice bluetoothd[2481]: src/plugin.c:init_plugin() System does not support bap plugin
        Jan 20 16:25:29 solstice bluetoothd[2481]: src/plugin.c:init_plugin() System does not support bass plugin
        Jan 20 16:25:29 solstice bluetoothd[2481]: src/plugin.c:init_plugin() System does not support mcp plugin
        Jan 20 16:25:29 solstice bluetoothd[2481]: src/plugin.c:init_plugin() System does not support vcp plugin
        

        Another lemmier suggested that my system just doesn’t have the right kernel. This is unfortunate but may be true at this point.