#bluetooth wont work even tho i have it toggled on
1 messages · Page 1 of 1 (latest)
you mean you ran ujust toggle-bluetooth-modules already and restarted?
what's the output of lsmod | grep btusb?
and systemctl status bluetooth.service?
Yes
this is both commands
and the settings panel showing no bluetooth
systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Fri 2025-08-15 21:45:55 +03; 1min 17s ago
Invocation: c7b1583351ee417eb24b5ed0ae8ca104
Docs: man:bluetoothd(8)
Main PID: 1132 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 37413)
Memory: 5.2M (peak: 10M)
CPU: 141ms
CGroup: /system.slice/bluetooth.service
└─1132 /usr/libexec/bluetooth/bluetoothd
Aug 15 21:45:55 fedora systemd[1]: Starting bluetooth.service - Bluetooth service...
Aug 15 21:45:55 fedora (uetoothd)[1132]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: >
Aug 15 21:45:55 fedora bluetoothd[1132]: Bluetooth daemon 5.83
Aug 15 21:45:55 fedora systemd[1]: Started bluetooth.service - Bluetooth service.
Aug 15 21:45:55 fedora bluetoothd[1132]: Starting SDP server
Aug 15 21:45:55 fedora bluetoothd[1132]: Bluetooth management interface 1.23 initialized
Aug 15 21:45:55 fedora bluetoothd[1132]: Battery Provider Manager created
Aug 15 21:45:55 fedora bluetoothd[1132]: Battery Provider Manager destroyed
@raw flame you've been able to use bluetooth on other distros?
also @raw flame can you rfkill list all and paste the output
yes
i was able to use bkuetooth on secureblue yesterday
today i woke up and its gone
very strange
what actions were taken between yesterday and today
and are you able to boot into yesterday's deployment?
also
shut down my laptop
weird
the device isn't even showing up
can you give all of this
rpm-ostree kargs
rpm-ostree status
and cat /etc/modprobe.d/99-bluetooth.conf
is there anything i could do to fix this?
that's what im collecting information on
lsusb | grep blue pls
also dmesg | grep -i blue (as root)
also lspci | grep -i blue
i cant do sudo anymore
how do i switch to root
do i also do this on root?
also did this no output tho
same as lsusb | grep blue
huh.
also as root, can you
modprobe btusb
modprobe bluetooth
both had no output
cool that's a success case
what next?
🦸 bash-5.2# bluetoothctl list
🦸 bash-5.2# hciconfig
bash: hciconfig: command not found
im at a loss
this is either failing hardware or something transient
this is going to sound dumb but
have you tried rebooting already
😅
i rebooted no change
😐
it was working fine just yesterday night
hm let's try something
im up for anything tbh
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/secureblue/silverblue-main-hardened:20250810
@raw flame this will time travel you back 5 days 😛
alright
i rebased still no bluetooth
or do i have to toggle it on again
rpm-ostree db diff ?
perhaps
probably not though
check if 99-bluetooth.conf is there
yonan@fedora:~$ rpm-ostree db diff
ostree diff commit from: rollback deployment (bc6d9742778d87945a0020a5863bfd88cfddb9f1a68552ee31d584206a6a5ea4)
ostree diff commit to: booted deployment (64fea805050f0037faddf07e696d419c1804b4fb56bb03f7057105a1905ed5ed)
Downgraded:
amd-gpu-firmware 20250808-1.fc42 -> 20250708-1.fc42
amd-ucode-firmware 20250808-1.fc42 -> 20250708-1.fc42
atheros-firmware 20250808-1.fc42 -> 20250708-1.fc42
brcmfmac-firmware 20250808-1.fc42 -> 20250708-1.fc42
cirrus-audio-firmware 20250808-1.fc42 -> 20250708-1.fc42
cpp 15.2.1-1.fc42 -> 15.1.1-2.fc42
gcc 15.2.1-1.fc42 -> 15.1.1-2.fc42
glib2 2.84.4-1.fc42 -> 2.84.3-1.fc42
gst-editing-services 1.26.5-1.fc42 -> 1.26.3-1.fc42
gstreamer1 1.26.5-2.fc42 -> 1.26.3-1.fc42
gstreamer1-plugins-bad-free 1.26.5-1.fc42 -> 1.26.3-1.fc42
gstreamer1-plugins-bad-free-libs 1.26.5-1.fc42 -> 1.26.3-1.fc42
gstreamer1-plugins-base 1.26.5-1.fc42 -> 1.26.3-1.fc42
gstreamer1-plugins-good 1.26.5-1.fc42 -> 1.26.3-1.fc42
gstreamer1-plugins-good-qt 1.26.5-1.fc42 -> 1.26.3-1.fc42
gstreamer1-plugins-good-qt6 1.26.5-1.fc42 -> 1.26.3-1.fc42
iio-sensor-proxy 3.8-1.fc42 -> 3.5-6.fc42
intel-audio-firmware 20250808-1.fc42 -> 20250708-1.fc42
intel-gpu-firmware 20250808-1.fc42 -> 20250708-1.fc42
intel-vsc-firmware 20250808-1.fc42 -> 20250708-1.fc42
iwlegacy-firmware 20250808-1.fc42 -> 20250708-1.fc42
iwlwifi-dvm-firmware 20250808-1.fc42 -> 20250708-1.fc42
iwlwifi-mvm-firmware 20250808-1.fc42 -> 20250708-1.fc42
libatomic 15.2.1-1.fc42 -> 15.1.1-2.fc42
libertas-firmware 20250808-1.fc42 -> 20250708-1.fc42
libgcc 15.2.1-1.fc42 -> 15.1.1-2.fc42
libgomp 15.2.1-1.fc42 -> 15.1.1-2.fc42
libstdc++ 15.2.1-1.fc42 -> 15.1.1-2.fc42
linux-firmware 20250808-1.fc42 -> 20250708-1.fc42
linux-firmware-whence 20250808-1.fc42 -> 20250708-1.fc42
mt7xxx-firmware 20250808-1.fc42 -> 20250708-1.fc42
nvidia-gpu-firmware 20250808-1.fc42 -> 20250708-1.fc42
nxpwireless-firmware 20250808-1.fc42 -> 20250708-1.fc42
openjpeg 2.5.3-8.fc42 -> 2.5.3-6.fc42
python-unversioned-command 3.13.6-1.fc42 -> 3.13.5-1.fc42
python3 3.13.6-1.fc42 -> 3.13.5-1.fc42
python3-boto3 1.40.7-1.fc42 -> 1.40.4-1.fc42
python3-botocore 1.40.7-1.fc42 -> 1.40.4-1.fc42
python3-libs 3.13.6-1.fc42 -> 3.13.5-1.fc42
realtek-firmware 20250808-1.fc42 -> 20250708-1.fc42
rest 0.10.2-1.fc42 -> 0.9.1-12.fc42
selinux-policy 42.5-1.fc42 -> 42.4-1.fc42
selinux-policy-devel 42.5-1.fc42 -> 42.4-1.fc42
selinux-policy-targeted 42.5-1.fc42 -> 42.4-1.fc42
tiwilink-firmware 20250808-1.fc42 -> 20250708-1.fc42
toolbox 0.2-1.fc42 -> 0.1.2-1.fc42
trivalent 139.0.7258.127-438758 -> 139.0.7258.66-438607
trivalent-subresource-filter 139.0.7258.127-1755055 -> 139.0.7258.66-1754797
vim-common 2:9.1.1623-1.fc42 -> 2:9.1.1591-1.fc42
vim-data 2:9.1.1623-1.fc42 -> 2:9.1.1591-1.fc42
vim-enhanced 2:9.1.1623-1.fc42 -> 2:9.1.1591-1.fc42
vim-filesystem 2:9.1.1623-1.fc42 -> 2:9.1.1591-1.fc42
vim-minimal 2:9.1.1623-1.fc42 -> 2:9.1.1591-1.fc42
xxd 2:9.1.1623-1.fc42 -> 2:9.1.1591-1.fc42
Removed:
qcom-wwan-firmware-20250808-1.fc42.noarch
how?
the same command i sent above
i dont see it here
i dont think so then
this command
is there no fix?
I'm not sure what the root cause is, let alone a fix
could be anything, including a hardware issue
as another check
you could try booting an endeavouros live usb or something
and seeing if bluetooth works on the live usb
if it doesn't, then this is a hardware or bios config issue
if it does, then it's a secureblue issue
that would at least narrow it down
issue is i basically dont have aflash right now
should i try reverting back to silverblue?
you could rebase yeah
thsnks
letme know what happens
alright
np
maybe try UEFI/power-saving/power management settings?
sometimes things persist across reboots with Linux that Windows would reset
disabling Quick Boot/Fast Boot in favour of Diagnostic/Standard Boot fixed a vaguely similar issue for me with wifi i think years ago
Now I'm experiencing the same issue....
I do dual boot windows. Let me try that
Turned out to be a glitch (possibly in HW) and Bluetooth icon came back again after shutting the computer down for minutes and booting it back up