Hello guys
here is my inxi, and thx
System:
Kernel: 6.3.1-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=b3328148-480b-42c9-9425-ff822289ea26 rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.9 wm: kwin_x11 vt: 1 dm:
1: GDM v: 44.1 note: stopped 2: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B650E-E GAMING WIFI v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 1410
date: 03/17/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech G604 Wireless Gaming Mouse
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
Device-2: hidpp_battery_1 model: Logitech Wireless KeyboarWirele
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 9 7900X bits: 64 type: MT MCP arch: Zen 4 gen: 5
level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
model-id: 0x61 (97) stepping: 2 microcode: 0xA601203
Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 12 MiB desc: 12x1024 KiB
L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 4555 high: 4700 min/max: 3000/5733 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 4700 2: 3522
3: 4700 4: 4700 5: 3373 6: 4700 7: 4700 8: 4700 9: 4700 10: 4700 11: 4700
12: 4700 13: 4700 14: 4700 15: 4700 16: 4700 17: 4700 18: 4700 19: 3738
20: 4700 21: 4700 22: 4700 23: 4700 24: 4700 bogomips: 225182
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA102 [GeForce RTX 3080 Lite Hash Rate] vendor: ASUSTeK
driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
status: current (as of 2023-05) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2216 class-ID: 0300
Device-2: AMD Raphael vendor: ASUSTeK driver: amdgpu v: kernel
arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: none empty: DP-1,HDMI-A-1
bus-ID: 0d:00.0 chip-ID: 1002:164e class-ID: 0300 temp: 52.0 C
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
compositor: kwin_x11 driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: nvidia,amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 92 s-size: 707x393mm (27.83x15.47")
s-diag: 809mm (31.85")
Monitor-1: DP-2 res: 2560x1440 hz: 60 dpi: 93
size: 697x392mm (27.44x15.43") diag: 800mm (31.48") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 530.41.03 renderer: NVIDIA GeForce RTX
3080/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: NVIDIA GA102 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:1aef class-ID: 0403
Device-2: AMD Rembrandt Radeon High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0d:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-3: 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: 1-6:4
chip-ID: 0b05:1a52 class-ID: 0300
Device-4: Logitech [G533 Wireless Headset Dongle]
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 5-1.4:5 chip-ID: 046d:0a66 class-ID: 0300
API: ALSA v: k6.3.1-zen2-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.70 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: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 05:00.0 chip-ID: 8086:15f3
class-ID: 0200
IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
vendor: Foxconn driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s
lanes: 1 bus-ID: 06:00.0 chip-ID: 14c3:0616 class-ID: 0280
Device-3: Microsoft Xbox Wireless Adapter for Windows driver: N/A
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-1.3:4
chip-ID: 045e:02fe class-ID: 0000 serial: <filter>
Drives:
Local Storage: total: 8.79 TiB used: 1.69 TiB (19.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Samsung
model: SSD 970 EVO Plus 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 2B2QEXM7 temp: 50.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: OWC model: Aura P12 Pro 2.0TB
size: 1.75 TiB block-size: physical: 4096 B logical: 4096 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: ECFM15.1 temp: 25.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 1000GB
size: 931.52 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 00RL scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD10EZEX-08WN4A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: 1A01 scheme: MBR
ID-5: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 020 scheme: GPT
ID-6: /dev/sdd maj-min: 8:48 vendor: SanDisk model: SD8SBBU240G1122
size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 6000 scheme: MBR
ID-7: /dev/sde maj-min: 8:64 vendor: Western Digital
model: WD40EMRX-82UZ0N0 size: 3.64 TiB block-size: physical: 4096 B
logical: 512 B type: USB rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
tech: HDD rpm: 5400 serial: <filter> fw-rev: 1021 scheme: GPT
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 80.04 GiB (17.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:3
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 80.04 GiB (17.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 80.04 GiB (17.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 80.04 GiB (17.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 30.5 GiB used: 1.2 MiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 62.4 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: nvidia screen: :0.0 temp: 43 C fan: 53% device: amdgpu
temp: 51.0 C
Info:
Processes: 500 Uptime: 31m wakeups: 12 Memory: available: 30.5 GiB
used: 4.35 GiB (14.3%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 13.1.1 Packages: pm: pacman pkgs: 1875
libs: 557 tools: octopi,paru Shell: fish v: 3.6.1 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.27
Garuda (2.6.16-1):
System install date: 2023-04-15
Last full system update: 2023-05-14
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut nvidia-dkms
Windows dual boot: No/Undetected
Failed units:
Check your /etc/fstab, missing/wrong UUIID
/etc/fstab:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=8B9E-885E /boot/efi vfat defaults,noatime 0 2
UUID=b3328148-480b-42c9-9425-ff822289ea26 / btrfs subvol=/@,defaults,noatime,compress=zstd 0 0
UUID=b3328148-480b-42c9-9425-ff822289ea26 /home btrfs subvol=/@home,defaults,noatime,compress=zstd 0 0
UUID=b3328148-480b-42c9-9425-ff822289ea26 /root btrfs subvol=/@root,defaults,noatime,compress=zstd 0 0
UUID=b3328148-480b-42c9-9425-ff822289ea26 /srv btrfs subvol=/@srv,defaults,noatime,compress=zstd 0 0
UUID=b3328148-480b-42c9-9425-ff822289ea26 /var/cache btrfs subvol=/@cache,defaults,noatime,compress=zstd 0 0
UUID=b3328148-480b-42c9-9425-ff822289ea26 /var/log btrfs subvol=/@log,defaults,noatime,compress=zstd 0 0
UUID=b3328148-480b-42c9-9425-ff822289ea26 /var/tmp btrfs subvol=/@tmp,defaults,noatime,compress=zstd 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
Have you tried different kernels? LTS?
1 Like
Check for any services taking longer than expected to start.
systemd analyze-blame
Check the journal for errors.
journalctl -p 3 -xb
Go ahead and add the output to the thread so we can have a look if you'd like. If it is too lengthy to leave as a reply, use the paste bin linked in the top-right corner.
2 Likes
systemd-analyze blame
3.032s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.0-0000:03:07.0-0000:08:00.0-ata3-host2-target2:0:0-2:0:>
3.032s dev-disk-by\x2ddiskseq-3.device
3.032s dev-disk-by\x2did-wwn\x2d0x500a0751e140b606.device
3.032s dev-disk-by\x2dpath-pci\x2d0000:08:00.0\x2data\x2d1.device
3.032s dev-disk-by\x2did-ata\x2dCT1000MX500SSD1_1822E140B606.device
3.032s dev-disk-by\x2dpath-pci\x2d0000:08:00.0\x2data\x2d1.0.device
3.032s dev-sdc.device
2.996s dev-disk-by\x2did-ata\x2dSanDisk_SSD_PLUS_1000GB_2013C5446102.device
2.996s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.0-0000:03:06.0-0000:07:00.0-ata1-host0-target0:0:0-0:0:>
2.996s dev-disk-by\x2did-wwn\x2d0x5001b444a743ddd6.device
2.996s dev-sda.device
2.996s dev-disk-by\x2dpath-pci\x2d0000:07:00.0\x2data\x2d1.0.device
2.996s dev-disk-by\x2dpath-pci\x2d0000:07:00.0\x2data\x2d1.device
2.996s dev-disk-by\x2ddiskseq-1.device
2.995s dev-disk-by\x2did-ata\x2dSanDisk_SD8SBBU240G1122_163268477110.device
2.995s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.0-0000:03:07.0-0000:08:00.0-ata4-host3-target3:0:0-3:0:>
2.995s dev-disk-by\x2ddiskseq-4.device
2.995s dev-sdd.device
2.995s dev-disk-by\x2did-wwn\x2d0x5001b444a420c62f.device
2.995s dev-disk-by\x2dpath-pci\x2d0000:08:00.0\x2data\x2d2.device
2.995s dev-disk-by\x2dpath-pci\x2d0000:08:00.0\x2data\x2d2.0.device
2.985s dev-disk-by\x2dpartuuid-75711f55\x2d0d29\x2d8743\x2d84c8\x2dbcb1a688112f.device
2.985s dev-sdc1.device
2.985s dev-disk-by\x2dpath-pci\x2d0000:08:00.0\x2data\x2d1.0\x2dpart1.device
2.985s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.0-0000:03:07.0-0000:08:00.0-ata3-host2-target2:0:0-2:0:>
2.985s dev-disk-by\x2dlabel-Terraplatt\x2dzwo.device
2.985s dev-disk-by\x2dpath-pci\x2d0000:08:00.0\x2data\x2d1\x2dpart1.device
2.985s dev-disk-by\x2did-wwn\x2d0x500a0751e140b606\x2dpart1.device
2.985s dev-disk-by\x2ddiskseq-3\x2dpart1.device
2.985s dev-disk-by\x2did-ata\x2dCT1000MX500SSD1_1822E140B606\x2dpart1.device
2.985s dev-disk-by\x2duuid-a50a0297\x2d455f\x2d40a8\x2dadf0\x2d2dfc859ab293.device
2.980s dev-disk-by\x2ddiskseq-1\x2dpart1.device
2.980s dev-disk-by\x2did-ata\x2dSanDisk_SSD_PLUS_1000GB_2013C5446102\x2dpart1.device
2.980s dev-disk-by\x2dpath-pci\x2d0000:07:00.0\x2data\x2d1.0\x2dpart1.device
2.980s dev-disk-by\x2did-wwn\x2d0x5001b444a743ddd6\x2dpart1.device
2.980s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.0-0000:03:06.0-0000:07:00.0-ata1-host0-target0:0:0-0:0:>
2.980s dev-disk-by\x2duuid-d2c3a30e\x2df73c\x2d4960\x2dae53\x2dae55600f13fc.device
2.980s dev-sda1.device
2.980s dev-disk-by\x2dpartuuid-26565932\x2d01.device
2.980s dev-disk-by\x2dlabel-Vol\x5cx20V.device
2.980s dev-disk-by\x2dpath-pci\x2d0000:07:00.0\x2data\x2d1\x2dpart1.device
2.978s dev-disk-by\x2ddiskseq-4\x2dpart1.device
2.978s dev-disk-by\x2did-wwn\x2d0x5001b444a420c62f\x2dpart1.device
2.978s dev-disk-by\x2dpath-pci\x2d0000:08:00.0\x2data\x2d2.0\x2dpart1.device
2.978s dev-disk-by\x2duuid-eb5550cb\x2d5123\x2d4b01\x2db59d\x2d4137c50aefe1.device
2.978s dev-disk-by\x2did-ata\x2dSanDisk_SD8SBBU240G1122_163268477110\x2dpart1.device
2.978s dev-disk-by\x2dpath-pci\x2d0000:08:00.0\x2data\x2d2\x2dpart1.device
2.978s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.0-0000:03:07.0-0000:08:00.0-ata4-host3-target3:0:0-3:0:>
2.978s dev-disk-by\x2dlabel-Zeugs.device
2.978s dev-sdd1.device
2.978s dev-disk-by\x2dpartuuid-2985969c\x2d01.device
2.807s dev-disk-by\x2ddiskseq-2.device
2.807s dev-sdb.device
2.807s dev-disk-by\x2did-ata\x2dWDC_WD10EZEX\x2d08WN4A0_WD\x2dWCC6Y4VECYJJ.device
2.807s dev-disk-by\x2did-wwn\x2d0x50014ee20e31800e.device
2.807s dev-disk-by\x2dpath-pci\x2d0000:07:00.0\x2data\x2d2.device
2.807s dev-disk-by\x2dpath-pci\x2d0000:07:00.0\x2data\x2d2.0.device
2.807s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.0-0000:03:06.0-0000:07:00.0-ata2-host1-target1:0:0-1:0:>
2.782s dev-ttyS0.device
2.782s sys-devices-platform-serial8250-tty-ttyS0.device
2.782s sys-devices-platform-serial8250-tty-ttyS11.device
2.782s dev-ttyS11.device
2.782s dev-ttyS10.device
2.782s sys-devices-platform-serial8250-tty-ttyS10.device
2.781s dev-ttyS12.device
2.781s sys-devices-platform-serial8250-tty-ttyS12.device
2.781s sys-devices-platform-serial8250-tty-ttyS1.device
2.781s dev-ttyS1.device
2.781s sys-devices-platform-serial8250-tty-ttyS13.device
2.781s dev-ttyS13.device
2.781s sys-devices-platform-serial8250-tty-ttyS14.device
2.781s dev-ttyS14.device
2.780s dev-ttyS15.device
2.780s sys-devices-platform-serial8250-tty-ttyS15.device
2.780s dev-ttyS16.device
2.780s sys-devices-platform-serial8250-tty-ttyS16.device
2.780s sys-devices-platform-serial8250-tty-ttyS17.device
2.780s dev-ttyS17.device
2.780s dev-ttyS2.device
2.780s sys-devices-platform-serial8250-tty-ttyS2.device
2.780s sys-devices-platform-serial8250-tty-ttyS20.device
2.780s dev-ttyS20.device
2.779s dev-ttyS18.device
2.779s sys-devices-platform-serial8250-tty-ttyS18.device
2.779s sys-devices-platform-serial8250-tty-ttyS22.device
2.779s dev-ttyS22.device
2.779s dev-ttyS21.device
2.779s sys-devices-platform-serial8250-tty-ttyS21.device
2.779s sys-devices-platform-serial8250-tty-ttyS26.device
2.779s dev-ttyS26.device
2.778s dev-ttyS19.device
2.778s sys-devices-platform-serial8250-tty-ttyS19.device
2.778s sys-devices-platform-serial8250-tty-ttyS24.device
2.778s dev-ttyS24.device
2.778s sys-devices-platform-serial8250-tty-ttyS27.device
2.778s dev-ttyS27.device
2.778s sys-devices-platform-serial8250-tty-ttyS23.device
2.778s dev-ttyS23.device
2.778s dev-ttyS25.device
2.778s sys-devices-platform-serial8250-tty-ttyS25.device
2.778s dev-ttyS28.device
2.778s sys-devices-platform-serial8250-tty-ttyS28.device
2.777s sys-devices-platform-serial8250-tty-ttyS3.device
2.777s dev-ttyS3.device
2.777s dev-ttyS30.device
2.777s sys-devices-platform-serial8250-tty-ttyS30.device
2.777s sys-devices-platform-serial8250-tty-ttyS31.device
2.777s dev-ttyS31.device
2.777s dev-ttyS6.device
2.777s sys-devices-platform-serial8250-tty-ttyS6.device
2.777s dev-ttyS29.device
2.777s sys-devices-platform-serial8250-tty-ttyS29.device
2.776s sys-devices-platform-serial8250-tty-ttyS4.device
2.776s dev-ttyS4.device
2.776s dev-ttyS5.device
2.776s sys-devices-platform-serial8250-tty-ttyS5.device
2.776s dev-ttyS7.device
2.776s sys-devices-platform-serial8250-tty-ttyS7.device
2.776s sys-devices-platform-serial8250-tty-ttyS9.device
2.776s dev-ttyS9.device
2.775s dev-ttyS8.device
2.775s sys-devices-platform-serial8250-tty-ttyS8.device
2.744s dev-disk-by\x2dpartuuid-cbe96ce9\x2d01.device
2.744s dev-disk-by\x2duuid-a83a8322\x2d51ec\x2d43ad\x2db13e\x2d78c146da5cce.device
2.744s dev-disk-by\x2dlabel-Terraplatt.device
2.744s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.0-0000:03:06.0-0000:07:00.0-ata2-host1-target1:0:0-1:0:>
2.744s dev-disk-by\x2did-ata\x2dWDC_WD10EZEX\x2d08WN4A0_WD\x2dWCC6Y4VECYJJ\x2dpart1.device
2.744s dev-disk-by\x2dpath-pci\x2d0000:07:00.0\x2data\x2d2.0\x2dpart1.device
2.744s dev-disk-by\x2ddiskseq-2\x2dpart1.device
2.744s dev-sdb1.device
2.744s dev-disk-by\x2did-wwn\x2d0x50014ee20e31800e\x2dpart1.device
2.744s dev-disk-by\x2dpath-pci\x2d0000:07:00.0\x2data\x2d2\x2dpart1.device
2.742s sys-module-configfs.device
2.689s dev-disk-by\x2did-nvme\x2dOWC_Aura_P12_Pro_2.0TB_2204261271188.device
2.689s dev-nvme0n1.device
2.689s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.0-0000:03:00.0-0000:04:00.0-nvme-nvme0-nvme0n1.device
2.689s dev-disk-by\x2ddiskseq-5.device
2.689s dev-disk-by\x2did-nvme\x2dnvme.1987\x2d32323034323631323731313838\x2d4f57432041757261205031322050726f2>
2.689s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1.device
2.689s dev-disk-by\x2did-nvme\x2dOWC_Aura_P12_Pro_2.0TB_2204261271188_1.device
2.686s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNM0TA01884L.device
2.686s dev-disk-by\x2did-nvme\x2deui.0025385a2190495b.device
2.686s sys-devices-pci0000:00-0000:00:02.2-0000:0c:00.0-nvme-nvme1-nvme1n1.device
2.686s dev-disk-by\x2dpath-pci\x2d0000:0c:00.0\x2dnvme\x2d1.device
2.686s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNM0TA01884L_1.device
2.686s dev-nvme1n1.device
2.686s dev-disk-by\x2ddiskseq-6.device
2.686s dev-nvme0n1p1.device
2.686s dev-disk-by\x2duuid-f514370f\x2dfdb7\x2d484b\x2dab61\x2d698712c5d7c8.device
2.686s dev-disk-by\x2did-nvme\x2dOWC_Aura_P12_Pro_2.0TB_2204261271188\x2dpart1.device
2.686s dev-disk-by\x2dpartuuid-6b7b3c27\x2db3ff\x2df548\x2d895b\x2d4bca7c089be7.device
2.686s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart1.device
2.686s sys-devices-pci0000:00-0000:00:02.1-0000:02:00.0-0000:03:00.0-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p>
2.686s dev-disk-by\x2did-nvme\x2dOWC_Aura_P12_Pro_2.0TB_2204261271188_1\x2dpart1.device
2.686s dev-disk-by\x2ddiskseq-5\x2dpart1.device
2.686s dev-disk-by\x2did-nvme\x2dnvme.1987\x2d32323034323631323731313838\x2d4f57432041757261205031322050726f2>
2.685s dev-disk-by\x2dpartuuid-50073911\x2d628a\x2dc84e\x2d9130\x2d5c5e478afeb2.device
2.685s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNM0TA01884L\x2dpart1.device
2.685s dev-disk-by\x2dpath-pci\x2d0000:0c:00.0\x2dnvme\x2d1\x2dpart1.device
2.685s dev-nvme1n1p1.device
2.685s sys-devices-pci0000:00-0000:00:02.2-0000:0c:00.0-nvme-nvme1-nvme1n1-nvme1n1p1.device
2.685s dev-disk-by\x2did-nvme\x2deui.0025385a2190495b\x2dpart1.device
2.685s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNM0TA01884L_1\x2dpart1.device
2.685s dev-disk-by\x2duuid-8B9E\x2d885E.device
2.685s dev-disk-by\x2ddiskseq-6\x2dpart1.device
2.684s dev-disk-by\x2duuid-b3328148\x2d480b\x2d42c9\x2d9425\x2dff822289ea26.device
2.684s dev-disk-by\x2did-nvme\x2deui.0025385a2190495b\x2dpart2.device
2.684s dev-disk-by\x2dpath-pci\x2d0000:0c:00.0\x2dnvme\x2d1\x2dpart2.device
2.684s sys-devices-pci0000:00-0000:00:02.2-0000:0c:00.0-nvme-nvme1-nvme1n1-nvme1n1p2.device
2.684s dev-disk-by\x2dpartlabel-root.device
2.684s dev-disk-by\x2dpartuuid-ffa6f45f\x2de751\x2d834d\x2dbae0\x2d9c105f69e4ac.device
2.684s dev-disk-by\x2ddiskseq-6\x2dpart2.device
2.684s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNM0TA01884L\x2dpart2.device
2.684s dev-nvme1n1p2.device
2.684s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNM0TA01884L_1\x2dpart2.device
1.236s systemd-tmpfiles-setup.service
877ms initrd-switch-root.service
457ms linux-modules-cleanup.service
285ms systemd-udev-trigger.service
255ms systemd-remount-fs.service
226ms systemd-modules-load.service
220ms [email protected]
210ms polkit.service
202ms [email protected]
184ms lm_sensors.service
182ms [email protected]
180ms [email protected]
159ms avahi-daemon.service
153ms systemd-machined.service
146ms systemd-fsck@dev-disk-by\x2duuid-8B9E\x2d885E.service
134ms lvm2-monitor.service
117ms systemd-binfmt.service
111ms kmod-static-nodes.service
101ms plymouth-quit-wait.service
100ms systemd-tmpfiles-setup-dev.service
89ms dev-hugepages.mount
88ms dev-mqueue.mount
88ms sys-kernel-debug.mount
88ms sys-kernel-tracing.mount
86ms dev-zram0.swap
85ms systemd-journal-flush.service
74ms plymouth-read-write.service
74ms systemd-random-seed.service
71ms [email protected]
70ms dracut-pre-udev.service
67ms garuda-pacman-snapshot-reject.service
66ms systemd-oomd.service
66ms dbus.service
66ms systemd-timesyncd.service
65ms systemd-update-utmp.service
63ms systemd-logind.service
60ms plymouth-quit.service
56ms NetworkManager.service
55ms [email protected]
50ms ModemManager.service
50ms [email protected]
49ms libvirtd.service
47ms systemd-user-sessions.service
46ms NetworkManager-wait-online.service
45ms packagekit.service
43ms systemd-sysctl.service
41ms dracut-shutdown.service
38ms plymouth-start.service
33ms upower.service
27ms systemd-udevd.service
26ms systemd-journald.service
22ms udisks2.service
22ms systemd-tmpfiles-clean.service
16ms plymouth-switch-root.service
13ms dracut-cmdline.service
10ms power-profiles-daemon.service
8ms dracut-pre-pivot.service
7ms boot-efi.mount
6ms systemd-fsck-root.service
5ms home.mount
5ms colord.service
5ms initrd-cleanup.service
5ms initrd-parse-etc.service
5ms root.mount
4ms srv.mount
4ms garuda-pacman-lock.service
4ms var-cache.mount
4ms systemd-vconsole-setup.service
4ms sys-fs-fuse-connections.mount
3ms var-log.mount
3ms var-tmp.mount
3ms sys-kernel-config.mount
3ms modprobe@dm_mod.service
2ms initrd-udevadm-cleanup-db.service
2ms proc-sys-fs-binfmt_misc.mount
1ms rtkit-daemon.service
1ms tmp.mount
1ms [email protected]
lines 227-253/253 (END)
Ξ» journalctl -p 3 -xb
Mai 15 15:58:25 wirr-sys kernel: hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)
Mai 15 15:58:25 wirr-sys kernel:
Mai 15 15:58:28 wirr-sys (udev-worker)[718]: host10: /usr/lib/udev/rules.d/50-sata.rules:2 Failed to write AT>
Mai 15 15:58:28 wirr-sys (udev-worker)[755]: event17: Failed to call EVIOCSKEYCODE with scan code 0x7c, and k>
Mai 15 15:58:30 wirr-sys libvirtd[2106]: Interner Fehler: Missing udev property 'ID_VENDOR_ID' on 'usb1'
Mai 15 15:58:30 wirr-sys libvirtd[2106]: Interner Fehler: Missing udev property 'ID_VENDOR_ID' on '1-2'
Mai 15 15:58:30 wirr-sys libvirtd[2106]: Interner Fehler: Missing udev property 'ID_VENDOR_ID' on '1-3'
Mai 15 15:58:30 wirr-sys libvirtd[2106]: Interner Fehler: Missing udev property 'ID_VENDOR_ID' on '1-6'
Mai 15 15:58:31 wirr-sys kernel: mt7921e 0000:06:00.0: Message 0004008a (seq 1) timeout
Mai 15 15:58:34 wirr-sys systemd[2976]: Failed to start BTRFS Assistant Snapper check.
ββ Subject: A start job for unit UNIT has failed
ββ Defined-By: systemd
ββ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
ββ
ββ A start job for unit UNIT has finished with a failure.
ββ
ββ The job identifier is 94 and the job result is failed.
Mai 15 15:58:34 wirr-sys kernel: mt7921e 0000:06:00.0: Message 0004008a (seq 2) timeout
Mai 15 15:58:37 wirr-sys konsole[3936]: kf.xmlgui: Shortcut for action "" "Schnellbefehle anzeigen" set with>
Mai 15 15:58:37 wirr-sys konsole[3936]: kf.xmlgui: Shortcut for action "" "SSH-Verwaltung anzeigen" set with>
Mai 15 15:58:37 wirr-sys kernel: mt7921e 0000:06:00.0: Message 0004008a (seq 3) timeout
Mai 15 15:58:38 wirr-sys sudo[3994]: wirr : a password is required ; TTY=pts/0 ; PWD=/home/wirr ; USER=ro>
Mai 15 15:58:41 wirr-sys kernel: usb 1-11: device descriptor read/64, error -110
Mai 15 15:58:41 wirr-sys kernel: mt7921e 0000:06:00.0: Message 0004008a (seq 4) timeout
Mai 15 15:58:44 wirr-sys kernel: mt7921e 0000:06:00.0: Message 0004008a (seq 5) timeout
Mai 15 15:58:47 wirr-sys kernel: mt7921e 0000:06:00.0: Message 0004008a (seq 6) timeout
Mai 15 15:58:50 wirr-sys kernel: mt7921e 0000:06:00.0: Message 0004008a (seq 7) timeout
Mai 15 15:58:53 wirr-sys kernel: mt7921e 0000:06:00.0: Message 0004008a (seq 8) timeout
Mai 15 15:58:56 wirr-sys kernel: usb 1-11: device descriptor read/64, error -110
Mai 15 15:58:57 wirr-sys kernel: mt7921e 0000:06:00.0: Message 0004008a (seq 9) timeout
Mai 15 15:59:00 wirr-sys kernel: mt7921e 0000:06:00.0: Message 0004008a (seq 10) timeout
Mai 15 15:59:00 wirr-sys kernel: mt7921e 0000:06:00.0: hardware init failed
Mai 15 15:59:02 wirr-sys kernel: usb 1-11: device descriptor read/64, error -110
Mai 15 15:59:17 wirr-sys kernel: usb 1-11: device descriptor read/64, error -110
Mai 15 15:59:28 wirr-sys kernel: usb 1-11: device not accepting address 9, error -71
Mai 15 15:59:38 wirr-sys kernel: usb 1-11: device not accepting address 10, error -71
Mai 15 15:59:38 wirr-sys kernel: usb usb1-port11: unable to enumerate USB device
Mai 15 17:30:12 wirr-sys sudo[207467]: wirr : a password is required ; TTY=pts/0 ; PWD=/home/wirr ; USER=>
lines 12-38/38 (END)
Are your peripherals attached to a hub or docking station? If so, what is the model of it?
1 Like
wirr
15 May 2023 17:03
11
no, i do have a hub for headphones and xone where the headphones are working, but the controller not...
This answer is somewhat unclear. Is the hub with your headphones plugged in to your computer? If so, unplug the hub and test booting without it to see if it has any effect on the availability of the peripherals.
1 Like
wirr
16 May 2023 04:52
13
ah sorry
and no, booting with the hub disconnected has no effect either
Okay, is one of the USB devices an external drive? If so, test with the external drive disconnected.
One of your USB devices is not responding correctly when the USB controller attempts to assign it an address. A common reason for this is the USB device isn't getting enough power, which can happen with hubs and external hard drives during the boot process if they are not externally powered (because the PC is using power for other stuff).
This also seems likely because after the boot process resolves, the devices eventually come up.
If that isn't the problem, then most likely it is either hardware or firmware related (either the PC or the device). Low-hanging fruit troubleshooting-wise would include swapping cables or using another kernel, but outside of those nothing easy comes to mind. You could check the website of the vendor of the USB device to see if a firmware update is available for the device, but that may be a long shot.
For starters, I would try booting without each connected device and re-check the journal to see if you can identify which device is causing a problem.
4 Likes
wirr
16 May 2023 09:41
15
Okay, is one of the USB devices an external drive? If so, test with the external drive disconnected.
One of your USB devices is not responding correctly when the USB controller attempts to assign it an address. A common reason for this is the USB device isnβt getting enough power, which can happen with hubs and external hard drives during the boot process if they are not externally powered (because the PC is using power for other stuff).
ok, disconnecting the hub and using the pc-usb only seems to have worked around the booting issue (but i donβt really understand, since it worked few weeks ago just fine and iβd like to keep using the hub as the pc is build in and iβd have a easy connection outside) though the xone-dongle still donβt work , but i guess, i need to open a new thread for it, donβt i?
system
18 May 2023 09:42
16
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
, i thought you were asking if m+k were connected to the hub...