Hello everyone , i would like some advice here so that i can properly report this issue.
I have installed the latest Fedora Silverblue and instantly rebased it with the UBlue nvidia flavor . I noticed that every odd or so boot that hardware drivers do not load properly , most often its bluetooth which causes my bluetooth switch to instantly flick back off , and i have also had it where nvidia-smi did not work and i could not use cuda , and then there once was an issue where my audio sounded terrible. This issue persisted after reinstalling and rebasing twice .
And to quickly mention , im using an nvidia gaming laptop specifically an Ideapad Gaming 3
3050ti 95w
R5 5600H
24GB Mem
i also did the other recomended tweaks for nvidia hardware like optimus and setting the kernal parameters or something like that via the official guide to rebase for Ublue.
Here are some of the commands i ran and a snippet of the boot logs where i believe the issue to be.
===Standard Boot Log Snip===
Feb 08 13:13:49 fedora kernel: mt7921e 0000:03:00.0: Message 00020007 (seq 11) timeout
Feb 08 13:13:49 fedora kernel: mt7921e 0000:03:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110
Feb 08 13:13:49 fedora kernel: mt7921e 0000:03:00.0: PM: failed to resume async: error -110
Feb 08 13:13:54 fedora kernel: Bluetooth: hci0: Failed to write uhw reg(-110)
Feb 08 13:14:03 fedora kernel: usb 1-4: Failed to suspend device, error -110
Feb 08 13:14:13 fedora kernel: Bluetooth: hci0: Execution of wmt command timed out
Feb 08 13:14:13 fedora kernel: Bluetooth: hci0: Failed to send wmt patch dwnld (-110)
Feb 08 13:14:13 fedora kernel: Bluetooth: hci0: Failed to set up firmware (-110)
Feb 08 13:14:16 fedora kernel: usb 1-4: Failed to suspend device, error -110
Feb 08 13:15:01 fedora gdm-password][9754]: gkr-pam: unable to locate daemon control file
Feb 08 13:15:01 fedora systemd-logind[1206]: Failed to open '/boot//loader/entries': Remote address changed
Feb 08 13:15:01 fedora systemd[1412]: Failed to start app-gnome-xdg\x2duser\x2ddirs-9911.scope - Application launched by gnome-session-binary.
Feb 08 13:15:03 fedora systemd-logind[1206]: Failed to open '/boot//loader/entries': Remote address changed
- Here something to note is that im pretty syre mt7921e is the name of my wireless mediatek card
===journalctl -b 0 -u bluetooth===
Feb 08 11:25:56 fedora systemd[1]: Starting bluetooth.service - Bluetooth service...
Feb 08 11:25:56 fedora (uetoothd)[1189]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Feb 08 11:25:56 fedora bluetoothd[1189]: Bluetooth daemon 5.79
Feb 08 11:25:56 fedora systemd[1]: Started bluetooth.service - Bluetooth service.
Feb 08 11:25:56 fedora bluetoothd[1189]: Starting SDP server
Feb 08 11:25:56 fedora bluetoothd[1189]: src/plugin.c:init_plugin() System does not support bap plugin
Feb 08 11:25:56 fedora bluetoothd[1189]: src/plugin.c:init_plugin() System does not support bass plugin
Feb 08 11:25:56 fedora bluetoothd[1189]: src/plugin.c:init_plugin() System does not support mcp plugin
Feb 08 11:25:56 fedora bluetoothd[1189]: src/plugin.c:init_plugin() System does not support vcp plugin
Feb 08 11:25:56 fedora bluetoothd[1189]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Feb 08 11:25:56 fedora bluetoothd[1189]: src/plugin.c:init_plugin() System does not support micp plugin
Feb 08 11:25:56 fedora bluetoothd[1189]: src/plugin.c:init_plugin() System does not support ccp plugin
Feb 08 11:25:56 fedora bluetoothd[1189]: src/plugin.c:init_plugin() System does not support csip plugin
Feb 08 11:25:56 fedora bluetoothd[1189]: src/plugin.c:init_plugin() System does not support asha plugin
Feb 08 11:25:56 fedora bluetoothd[1189]: Bluetooth management interface 1.23 initialized
Feb 08 11:25:58 fedora bluetoothd[1189]: Battery Provider Manager created
Feb 08 11:25:58 fedora bluetoothd[1189]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Feb 08 11:25:59 fedora bluetoothd[1189]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/ldac
- Not sure what to make out here , seems like the service started correctly
– At the very bottom –
`Feb 08 13:13:49 fedora bluetoothd[1189]: Battery Provider Manager destroyed`
- Notable as i read somewhere that power management can cause issues , not sure if this has anything to do with it.
===systemctl --failed===
work@fedora:~$ systemctl --failed
UNIT LOAD ACTIVE SUB >
● flatpak-system-update.service loaded failed fail>
Legend: LOAD → Reflects whether the unit definit>
ACTIVE → The high-level unit activation st>
SUB → The low-level unit activation sta>
1 loaded units listed.
lines 1-8/8 (END)...skipping...
UNIT LOAD ACTIVE SUB DESCRIPTION
● flatpak-system-update.service loaded failed failed Flatpak Automatic Update
=== lspci -k | grep -i bluetooth , lsusb | grep -i bluetooth , lsmod | grep btusb ===
work@fedora:~$ lspci -k | grep -i bluetooth
work@fedora:~$ lsusb | grep -i bluetooth
work@fedora:~$ lsmod | grep btusb
btusb 77824 0
btrtl 36864 1 btusb
btintel 69632 1 btusb
btbcm 24576 1 btusb
btmtk 32768 1 btusb
bluetooth 1052672 17 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
- A few commands were run here , bluetooth isn’t listed as a failed service.
- The following two lspci and lsusb commands were supposed to return the bluetooth devices i believe but returned nothing.
Any advice would be appreciated.