It seems like the default behavior for GNOME should be bluetooth on. For some reason, it fails.
systemctl status bluetooth outputs systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth)
bluetoothctl returns “waiting to connect to bluetoothd”
When I used modprobe & restarted bluetooth, I got bluetoothctl to start, but any command results in “No default controller available” systemctl status bluetooth after modprobe returns: Apr 05 14:14:05 systemd[1]: Started Bluetooth service. Apr 05 14:14:05 bluetoothd[7123]: Starting SDP server Apr 05 14:14:05 bluetoothd[7123]: src/plugin.c:plugin_init() System does not support csip plugin Apr 05 14:14:05 bluetoothd[7123]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled Apr 05 14:14:05 bluetoothd[7123]: src/plugin.c:plugin_init() System does not support micp plugin Apr 05 14:14:05 bluetoothd[7123]: src/plugin.c:plugin_init() System does not support vcp plugin Apr 05 14:14:05 bluetoothd[7123]: src/plugin.c:plugin_init() System does not support mcp plugin Apr 05 14:14:05 bluetoothd[7123]: src/plugin.c:plugin_init() System does not support bass plugin Apr 05 14:14:05 bluetoothd[7123]: src/plugin.c:plugin_init() System does not support bap plugin Apr 05 14:14:05 bluetoothd[7123]: Bluetooth management interface 1.22 initialized
I did see that. I have a laptop so I can’t really unplug the PSU. I tried power button for 30sec, and that didn’t work. Then I waited until it died so it wouldn’t have power, and tried the power button again. Still didn’t work. I’m at a loss, and since those solutions didn’t work I just assumed that there was a different issue.
Do you see similar things on dmesg regarding Bluetooth? Does it show up when running rfkill, is it in lsmod, does it show up in lsusb? I think just powering down should be sufficient. Laptops with internal battery allow you to disconnect the battery virtually until you reconnect a charger again. No Bluetooth must be extremely frustrating so best luck
Maybe try running nixos-rebuild boot --upgrade and reboot, considering you are on Linux kernel 6.7 - it was generally dropped and downgraded to 6.6.25 (edit: or up to 6.8… with non-zfs setups). Not sure if that will help anymore seeing some discussions. Also check if you have any sort of bluetooth function key or switch, sometimes that disables bluetooth and makes it hard to figure out whats going on.
Please check nix shell nixpkgs#usbutils -c lsusb and share what your exact bluetooth controller is (or if it is a pci device nix shell nixpkgs#pciutils -c lspci.
Thank you so much for mentioning kernel version! I was messing around with it, and I finally realized that musnix (a configuration for producing pro audio) was controlling my kernel version. All I had to do was change that configuration to rt_latest and bluetooth is back!