Hi all,
I’ve been running Bazzite for the past few weeks on my system and I think it could be great, but I have some issues I can’t seem to solve that hinder my day-to-day use. I was hoping someone would be able to help me troubleshoot.
It’s a new machine (which could be part of the problem), an X870E motherboard with a Ryzen 7 9800X3D and 32Gb RAM, with a Radeon RX 7800 XT card.
I have intermittent USB issues where my keyboard and mouse refuse to connect. Unplugging and re-plugging sometimes works, sometimes not.
The onboard WiFi and Bluetooth don’t work yet either. I’m using a Bluetooth dongle to use my HORI pad Steam. Similarly, sometimes it works, sometimes it doesn’t.
The system is also taking a very long time to get past the firmware stage and the initrd stage on bootup. I’ll copy-and-paste some system info in my responses below. Hoping anyone can help, since I really like using Bazzite (I was using Manjaro before, but the low-maintenance aspect and gaming-focused approach is what I would prefer). Thanks in advance!
My Inxi info:
System:
Kernel: 6.12.12-203.bazzite.fc41.x86_64 arch: x86_64 bits: 64
compiler: gcc v: 14.2.1 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=(hd0,gpt2)/ostree/default-96fed9f104e6d731e765ec3f54d22b0d8edb9dce4c1c8f9dfc8e8485ce096fca/vmlinuz-6.12.12-203.bazzite.fc41.x86_64
rhgb quiet root=UUID=929e5c41-e276-4b17-a8c6-01c8eec71bce
rootflags=subvol=root rw
ostree=/ostree/boot.1/default/96fed9f104e6d731e765ec3f54d22b0d8edb9dce4c1c8f9dfc8e8485ce096fca/0
bluetooth.disable_ertm=1 preempt=full
Desktop: GNOME v: 47.3 tk: GTK v: 3.24.43 wm: gnome-shell
tools: gsd-screensaver-proxy dm: 1: GDM v: 47.0 note: stopped 2: SDDM
Distro: Bazzite 41.20250206.0 (Silverblue) Holographic
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
Mobo: ASUSTeK model: ROG STRIX X870E-E GAMING WIFI v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 0606 date: 10/28/2024
CPU:
Info: model: AMD Ryzen 7 9800X3D bits: 64 type: MT MCP arch: N/A level: v4
note: check family: 0x1A (26) model-id: 0x44 (68) stepping: 0
microcode: <I hid this - not sure if this is a unique ID>
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 8 MiB
desc: 8x1024 KiB L3: 96 MiB desc: 1x96 MiB
Speed (MHz): avg: 600 min/max: 600/5269 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 600 2: 600 3: 600
4: 600 5: 600 6: 600 7: 600 8: 600 9: 600 10: 600 11: 600 12: 600
13: 600 14: 600 15: 600 16: 600 bogomips: 150108
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled
via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user
pointer sanitization
Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
conditional; STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected;
BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 32 [Radeon RX 7700 XT /
7800 XT] vendor: Tul / PowerColor driver: amdgpu v: kernel arch: RDNA-3
code: Navi-3x process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2,
DP-3, Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:747e class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon
Graphics] vendor: ASUSTeK driver: amdgpu v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: none empty: DP-4, DP-5,
HDMI-A-2, Writeback-2 bus-ID: 7c:00.0 chip-ID: 1002:13c0 class-ID: 0300
temp: 39.0 C
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.3
compositor: gnome-shell driver: gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 model: Dell P3222QE serial: <filter> built: 2021
res: 3840x2160 dpi: 140 gamma: 1.2 size: 697x392mm (27.44x15.43")
diag: 800mm (31.5") ratio: 16:9 modes: max: 3840x2160 min: 720x400
API: OpenGL v: 4.6 vendor: amd mesa v: 24.3.3 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: AMD Radeon RX 7800 XT (radeonsi navi32 LLVM
19.1.5 DRM 3.59 6.12.12-203.bazzite.fc41.x86_64) device-ID: 1002:747e
memory: 15.62 GiB unified: no display-ID: :0.0
API: Vulkan v: 1.4.304 layers: 15 device: 0 type: discrete-gpu name: AMD
Radeon RX 7800 XT (RADV NAVI32) driver: N/A device-ID: 1002:747e
surfaces: xcb,xlib,wayland device: 1 type: integrated-gpu name: AMD
Radeon Graphics (RADV RAPHAEL_MENDOCINO) driver: N/A
device-ID: 1002:13c0 surfaces: xcb,xlib,wayland
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo,vulkaninfo de: gnome-randr wl: wlr-randr
x11: xdriinfo, xprop, xrandr
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:ab30 class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High
Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 7c:00.1 chip-ID: 1002:1640
class-ID: 0403
Device-3: Jieli UACDemoV1.0 driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:2
chip-ID: 4c4a:4155 class-ID: 0300 serial: <filter>
Device-4: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6:9
chip-ID: 0b05:1b9b class-ID: 0300
API: ALSA v: k6.12.12-203.bazzite.fc41.x86_64 status: kernel-api
tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: MEDIATEK vendor: Foxconn driver: N/A modules: wl pcie: gen: 3
speed: 8 GT/s lanes: 1 port: N/A bus-ID: 0c:00.0 chip-ID: <I hid this - not sure if this is a unique ID>
class-ID: 0280
Device-2: Realtek vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 1 port: e000 bus-ID: 0d:00.0 chip-ID: <I hid this - not sure if this is a unique ID>
class-ID: 0200
IF: enp13s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,wpa_supplicant
Bluetooth:
Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9:3
chip-ID: 0489:e13a class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
Device-2: Cambridge Silicon Radio Bluetooth Dongle (HCI mode)
driver: btusb v: 0.8 type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1
bus-ID: 3-4.1:13 chip-ID: 0a12:0001 class-ID: e001
Report: ID: hci1 rfk-id: 1 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 4c0104
Drives:
Local Storage: total: 3.68 TiB used: 1.33 TiB (36.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Samsung
model: MZVLB1T0HBLR-00000 size: 953.87 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: EXF7201Q temp: 35.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung
model: MZVLB1T0HBLR-00000 size: 953.87 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: EXF7201Q temp: 32.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
Partition:
ID-1: /boot raw-size: 1024 MiB size: 973.4 MiB (95.06%)
used: 315.7 MiB (32.4%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:4
ID-2: /boot/efi raw-size: 600 MiB size: 598.8 MiB (99.80%)
used: 12.6 MiB (2.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:3
ID-3: /var raw-size: 952.28 GiB size: 952.28 GiB (100.00%)
used: 302.24 GiB (31.7%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:5
Swap:
Kernel: swappiness: 180 (default 60) cache-pressure: 100 (default)
zswap: no
ID-1: swap-1 type: zram size: 7.62 GiB used: 0 KiB (0.0%) priority: 100
comp: lz4 avail: lzo-rle,lzo,lz4hc,zstd,deflate,842 max-streams: 16
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 57.0 C mobo: 25.8 C
Fan Speeds (rpm): N/A
GPU: device: amdgpu temp: 43.0 C mem: 60.0 C fan: 0 watts: 13.00
device: amdgpu temp: 40.0 C
Info:
Memory: total: 32 GiB note: est. available: 30.46 GiB
used: 6.97 GiB (22.9%)
Processes: 550 Power: uptime: 7m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.13 GiB services: gsd-power,upowerd
Init: systemd v: 256 target: graphical (5) default: graphical
tool: systemctl
Packages: pm: rpm pkgs: N/A note: see --rpm
tools: dnf,gnome-software,yum pm: flatpak pkgs: 70 Compilers: clang: 18
gcc: 14.2.1 Shell: fish v: 3.7.0 default: Bash v: 5.2.32
running-in: ptyxis-agent inxi: 3.3.37
Systemd-Analyse gives:
Startup finished in 20.275s (firmware) + 1.757s (loader) + 2.623s (kernel) + 1min 37.189s (initrd) + 8.439s (userspace) = 2min 10.286s
graphical.target reached after 8.417s in userspace.
systemd-blame shows:
1min 37.757s dev-disk-by\x2dpartuuid-1712dc38\x2d7d82\x2d42aa\x2d887b\x2d1e25e54a2237.device
1min 37.757s dev-disk-by\x2duuid-7eadfc04\x2df523\x2d441d\x2d9e64\x2da9c0544608fc.device
1min 37.757s dev-disk-by\x2dpath-pci\x2d0000:13:00.0\x2data\x2d1.0\x2dpart-by\x2duuid-7eadfc04\x2df523\x2d441d\x2d9e64\x2da9c0544608fc.device
1min 37.757s dev-disk-by\x2dpath-pci\x2d0000:13:00.0\x2data\x2d1\x2dpart1.device
1min 37.757s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1min 37.757s dev-disk-by\x2dlabel-LinuxHD2.device
1min 37.757s sys-devices-pci0000:00-0000:00:02.1-0000:06:00.0-0000:07:0d.0-0000:13:00.0-ata7-host6-target6:0:0-6:0:0:0-block-sda-sda1.device
1min 37.757s dev-disk-by\x2did-ata\x2dSamsung_SSD_870_QVO_2TB_S5SUNF0R310775X\x2dpart1.device
1min 37.756s dev-disk-by\x2dpath-pci\x2d0000:13:00.0\x2data\x2d1.0\x2dpart-by\x2dpartnum-1.device
1min 37.756s dev-disk-by\x2dpath-pci\x2d0000:13:00.0\x2data\x2d1.0\x2dpart1.device
1min 37.756s dev-sda1.device
1min 37.756s dev-disk-by\x2did-wwn\x2d0x5002538f4132b7db\x2dpart1.device
1min 37.756s dev-disk-by\x2dpath-pci\x2d0000:13:00.0\x2data\x2d1.0\x2dpart-by\x2dpartuuid-1712dc38\x2d7d82\x2d42aa\x2d887b\x2d1e25e54a2237.device
1min 37.756s dev-disk-by\x2dpath-pci\x2d0000:13:00.0\x2data\x2d1.0\x2dpart-by\x2dlabel-LinuxHD2.device
1min 37.706s dev-sda.device
1min 37.706s dev-disk-by\x2dpath-pci\x2d0000:13:00.0\x2data\x2d1.device
1min 37.706s dev-disk-by\x2dpath-pci\x2d0000:13:00.0\x2data\x2d1.0.device
1min 37.706s dev-disk-by\x2did-ata\x2dSamsung_SSD_870_QVO_2TB_S5SUNF0R310775X.device
1min 37.706s sys-devices-pci0000:00-0000:00:02.1-0000:06:00.0-0000:07:0d.0-0000:13:00.0-ata7-host6-target6:0:0-6:0:0:0-block-sda.device
1min 37.706s dev-disk-by\x2did-wwn\x2d0x5002538f4132b7db.device
1min 37.706s dev-disk-by\x2ddiskseq-1.device
1min 37.700s sys-module-fuse.device
1min 37.651s dev-ttyS1.device
1min 37.651s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
1min 37.651s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
1min 37.651s dev-ttyS0.device
1min 37.650s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
1min 37.650s dev-ttyS2.device
1min 37.639s dev-ttyS3.device
1min 37.639s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
1min 37.637s sys-module-configfs.device
1min 37.619s dev-nvme0n1p1.device
1min 37.619s dev-disk-by\x2dpartuuid-16cd812c\x2d6a6f\x2d4d9f\x2d9bae\x2d421f9777b472.device
1min 37.619s dev-disk-by\x2ddiskseq-3\x2dpart1.device
1min 37.619s dev-disk-by\x2duuid-73CD\x2d06FC.device
1min 37.619s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
1min 37.619s sys-devices-pci0000:00-0000:00:01.3-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
1min 37.619s dev-disk-by\x2did-nvme\x2deui.0025388201b71c0a\x2dpart1.device
1min 37.619s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart1.device
1min 37.619s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
1min 37.619s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-16cd812c\x2d6a6f\x2d4d9f\x2d9bae\x2d421f9777b472.device
1min 37.619s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N210450\x2dpart1.device
1min 37.619s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
1min 37.619s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N210450_1\x2dpart1.device
1min 37.619s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-73CD\x2d06FC.device
1min 37.606s dev-nvme0n1p2.device
1min 37.606s sys-devices-pci0000:00-0000:00:01.3-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
1min 37.606s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-9cde11b1\x2da01f\x2d4bba\x2da7be\x2d55c519b2ac80.device
1min 37.606s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
1min 37.606s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N210450\x2dpart2.device
1min 37.606s dev-disk-by\x2dpartuuid-9cde11b1\x2da01f\x2d4bba\x2da7be\x2d55c519b2ac80.device
1min 37.606s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-45d5b8e3\x2d11cb\x2d4fc6\x2d8ca7\x2de5f7adbada48.device
1min 37.606s dev-disk-by\x2duuid-45d5b8e3\x2d11cb\x2d4fc6\x2d8ca7\x2de5f7adbada48.device
1min 37.606s dev-disk-by\x2ddiskseq-3\x2dpart2.device
1min 37.606s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart2.device
1min 37.606s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N210450_1\x2dpart2.device
1min 37.606s dev-disk-by\x2did-nvme\x2deui.0025388201b71c0a\x2dpart2.device
1min 37.602s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-929e5c41\x2de276\x2d4b17\x2da8c6\x2d01c8eec71bce.device
1min 37.602s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-af72abcf\x2decba\x2d46af\x2db5f1\x2daa56b6b36527.device
1min 37.602s dev-nvme0n1p3.device
1min 37.602s dev-disk-by\x2dpartuuid-af72abcf\x2decba\x2d46af\x2db5f1\x2daa56b6b36527.device
1min 37.602s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-bazzite\x2ddeck\x2dgnome_fedora.device
1min 37.602s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N210450\x2dpart3.device
1min 37.602s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart3.device
1min 37.602s sys-devices-pci0000:00-0000:00:01.3-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
1min 37.602s dev-disk-by\x2did-nvme\x2deui.0025388201b71c0a\x2dpart3.device
1min 37.602s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
1min 37.602s dev-disk-by\x2duuid-929e5c41\x2de276\x2d4b17\x2da8c6\x2d01c8eec71bce.device
1min 37.602s dev-disk-by\x2dlabel-bazzite\x2ddeck\x2dgnome_fedora.device
1min 37.602s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N210450_1\x2dpart3.device
1min 37.602s dev-disk-by\x2ddiskseq-3\x2dpart3.device
1min 37.598s sys-devices-pci0000:00-0000:00:01.3-0000:04:00.0-nvme-nvme0-nvme0n1.device
1min 37.598s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1.device
1min 37.598s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N210450.device
1min 37.598s dev-disk-by\x2ddiskseq-3.device
1min 37.598s dev-disk-by\x2did-nvme\x2deui.0025388201b71c0a.device
1min 37.598s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N210450_1.device
1min 37.598s dev-nvme0n1.device
1min 37.597s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-b722bb2b\x2d2a44\x2d4d0e\x2d9057\x2de3b8d940bdb4.device
1min 37.597s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N214676\x2dpart1.device
1min 37.597s dev-disk-by\x2ddiskseq-2\x2dpart1.device
1min 37.597s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N214676_1\x2dpart1.device
1min 37.597s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
1min 37.597s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-LinuxHD1.device
1min 37.597s dev-disk-by\x2did-nvme\x2deui.0025388201b75a73\x2dpart1.device
1min 37.597s dev-disk-by\x2dlabel-LinuxHD1.device
1min 37.597s dev-nvme1n1p1.device
1min 37.597s dev-disk-by\x2dpartuuid-77e2134a\x2dad7b\x2d49dc\x2d9fbc\x2d5f76e417d62c.device
1min 37.597s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-77e2134a\x2dad7b\x2d49dc\x2d9fbc\x2d5f76e417d62c.device
1min 37.597s dev-disk-by\x2duuid-b722bb2b\x2d2a44\x2d4d0e\x2d9057\x2de3b8d940bdb4.device
1min 37.597s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1\x2dpart1.device
1min 37.597s sys-devices-pci0000:00-0000:00:01.4-0000:05:00.0-nvme-nvme1-nvme1n1-nvme1n1p1.device
1min 37.597s dev-nvme1n1.device
1min 37.597s dev-disk-by\x2did-nvme\x2deui.0025388201b75a73.device
1min 37.597s dev-disk-by\x2ddiskseq-2.device
1min 37.597s sys-devices-pci0000:00-0000:00:01.4-0000:05:00.0-nvme-nvme1-nvme1n1.device
1min 37.597s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N214676.device
1min 37.597s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1.device
1min 37.597s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB1T0HBLR\x2d00000_S4GJNF0N214676_1.device
1min 36.764s dracut-initqueue.service
5.066s NetworkManager-wait-online.service
3.885s upower.service
3.045s tuned-ppd.service
1.604s fwupd.service
1.227s bazzite-hardware-setup.service
1.121s cec-onboot.service
1.015s systemd-rfkill.service
978ms systemd-binfmt.service
836ms systemd-resolved.service
829ms systemd-oomd.service
594ms initrd-switch-root.service
465ms NetworkManager.service
154ms firewalld.service
134ms tuned.service
125ms user@1000.service
119ms user@0.service
109ms systemd-tmpfiles-setup.service
93ms udisks2.service
79ms systemd-udev-trigger.service
70ms accounts-daemon.service
59ms systemd-tmpfiles-setup-dev-early.service
57ms systemd-journal-flush.service
55ms systemd-udevd.service
52ms var-lib-nfs-rpc_pipefs.mount
51ms polkit.service
49ms ModemManager.service
49ms dconf-update.service
45ms smartd.service
45ms passim.service
44ms avahi-daemon.service
42ms dbus-broker.service
38ms bluetooth.service
38ms systemd-journald.service
36ms lvm2-monitor.service
36ms systemd-zram-setup@zram0.service
36ms rpm-ostreed.service
35ms gssproxy.service
35ms chronyd.service
33ms boot.mount
33ms dev-zram0.swap
32ms bazzite-autologin.service
32ms systemd-nsresourced.service
31ms bolt.service
31ms cups.service
31ms systemd-logind.service
29ms var-mnt-b722bb2b\x2d2a44\x2d4d0e\x2d9057\x2de3b8d940bdb4.mount
28ms proc-sys-fs-binfmt_misc.mount
26ms unbound-anchor.service
26ms systemd-vconsole-setup.service
25ms user-runtime-dir@0.service
25ms lm_sensors.service
25ms sssd-kcm.service
25ms systemd-tmpfiles-setup-dev.service
24ms dev-hugepages.mount
23ms dev-mqueue.mount
23ms sys-kernel-debug.mount
23ms sys-kernel-tracing.mount
23ms bazzite-tdpfix.service
23ms plymouth-quit-wait.service
22ms bazzite-flatpak-manager.service
22ms plymouth-quit.service
22ms modprobe@dm_mod.service
21ms dracut-cmdline.service
21ms modprobe@efi_pstore.service
21ms modprobe@loop.service
20ms systemd-hostnamed.service
20ms tmp.mount
20ms dracut-pre-udev.service
19ms rpc-statd-notify.service
19ms systemd-user-sessions.service
19ms virtlxcd.service
19ms virtqemud.service
18ms wpa_supplicant.service
17ms plymouth-switch-root.service
17ms uresourced.service
17ms rtkit-daemon.service
17ms bootloader-update.service
16ms colord.service
16ms virtvboxd.service
16ms auditd.service
16ms pipewire-workaround.service
16ms user-runtime-dir@1000.service
16ms switcheroo-control.service
15ms plymouth-start.service
15ms systemd-fsck@dev-disk-by\x2duuid-73CD\x2d06FC.service
15ms systemd-fsck@dev-disk-by\x2duuid-45d5b8e3\x2d11cb\x2d4fc6\x2d8ca7\x2de5f7adbada48.service
15ms dracut-shutdown.service
14ms systemd-random-seed.service
14ms systemd-homed.service
13ms plymouth-read-write.service
13ms modprobe@configfs.service
13ms systemd-fsck-root.service
12ms systemd-sysctl.service
12ms systemd-modules-load.service
11ms systemd-machined.service
11ms dracut-pre-trigger.service
10ms boot-efi.mount
10ms systemd-userdbd.service
10ms audit-rules.service
10ms var.mount
8ms kmod-static-nodes.service
8ms systemd-remount-fs.service
8ms modprobe@amdgpu.service
8ms dracut-pre-pivot.service
7ms modprobe@drm.service
6ms thermald.service
6ms alsa-restore.service
6ms initrd-cleanup.service
5ms initrd-parse-etc.service
5ms wireplumber-workaround.service
5ms systemd-udev-load-credentials.service
5ms systemd-network-generator.service
4ms wireplumber-sysconf.service
4ms systemd-update-utmp-runlevel.service
4ms dracut-pre-mount.service
3ms pipewire-sysconf.service
3ms systemd-update-utmp.service
3ms var-home.mount
3ms ostree-remount.service
3ms initrd-udevadm-cleanup-db.service
2ms modprobe@fuse.service
2ms systemd-sysusers.service
1ms sys-fs-fuse-connections.mount
25us systemd-homed-activate.service
The systemd-chain shows:
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @8.417s
└─multi-user.target @8.415s
└─plymouth-quit.service @8.392s +22ms
└─systemd-user-sessions.service @8.370s +19ms
└─remote-fs.target @8.369s
└─remote-fs-pre.target @3.338s
└─nfs-client.target @3.338s
└─gssproxy.service @3.302s +35ms
└─network.target @3.300s
└─NetworkManager.service @2.834s +465ms
└─network-pre.target @2.833s
└─firewalld.service @2.678s +154ms
└─polkit.service @2.605s +51ms
└─basic.target @2.584s
└─dbus-broker.service @2.541s +42ms
└─dbus.socket @2.535s
└─sysinit.target @2.533s
└─systemd-resolved.service @1.697s +836ms
└─run-credentials-systemd\x2dresolved.service.mount @2.476s
Signed up just to bump this thread; I’m having the exact same issues. I’ve been using Bazzite for months now, and probably around two weeks ago, the system boot time is longer, and Bluetooth is no longer functional. My readouts look pretty close to OPs… hoping there’s a fix for this.
Sad to say it’s not really gone away for me yet. It was a bit better the past few weeks, got an ASUS Bluetooth USB dongle, and things seemed to be working. Then the last few days (since an update I did on Thursday or Friday?) it’s gone wonky again. Long load times, bluetooth works sometimes, no matter what port I plug it into. A system restart may fix it (or not).
There’s no rhyme or reason, since it sometimes works, sometimes not, without me doing/changing anything. It’s weird!
So I had what sounds like a very similar issue a couple of moths ago. Boot times of 3 mins + which seemed to coincide with Bluetooth problems. In my case, BT wouldn’t detect any devices at all 9 times out of 10.
I used systemd-analyze and systemd-analyze blame and saw that in addition to the firmware taking ages (60+ seconds), blame was showing that the OS was waiting on network services to spin up. In systemd-anaylze, this took the form of initrd taking over a minute to finish, whereas it’s normally < 5 seconds.
In the end, I ended up replacing my motherboard’s built in Mediatek Wi-Fi chip with an Intel AX210 chip for roughly £20, which seems to have sorted things out.
I suspect what had happened is the Mediatek chip had failed - they’re fairly notorious for it, reading online - but was still recognised by the operating system. Booting was delayed because the OS was detecting the chip and waiting for it to come online, which it never did, so eventually the wait would timeout and booting would proceed.
It might be worth taking your motherboard’s wifi chip out and seeing if your boot times improve. I didn’t actually try this, as I went straight to replacing it, but it stands to reason that the hardware can’t slow down a boot if it isn’t there.
Thanks for checking in about this. The problem is on-off for me still. I think my issue is different, as the WiFi/Bluetooth chip was working without fault in Windows, before I switched over to Bazzite. It’s never worked there, so I’m guessing it’s a driver issue.
I’ve disabled the onboard chip in my BIOS a while back. The USB dongle was working fine for Bluetooth. I’m on cabled Ethernet anyway, so don’t care about WiFi.
Even now, it’s always a 50-50 gamble when I turn my PC on: will bluetooth work yes or no? Sometimes a simple unplug-plug-in fixes it, sometimes a restart, sometimes going into desktop mode. It’s incredibly odd. Sometimes I get the delayed booting time, sometimes not.