Mouse and keyboard delay at login screen

My problem has persisted over 3 installs of Garuda. The problem is when arriving at the login screen there is a 20-30 second delay before my mouse or keyboard will work sometimes longer. Its a wireless logitech keyboard and mouse. I notice on my AMD system zero wait time but on my intel its always the case. Any pointers would be greatly appreciated.

System:
Kernel: 6.3.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=cb6ac071-b69d-4932-8546-3451a34bf023 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: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: Z790 AORUS MASTER v: -CF
serial: <superuser required>
Mobo: Gigabyte model: Z790 AORUS MASTER v: x.x
serial: <superuser required> UEFI: American Megatrends LLC. v: F8c
date: 04/28/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech ⣯@ serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Device PID:406f
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: 13th Gen Intel Core i9-13900K bits: 64 type: MST AMCP
arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
microcode: 0x113
Topology: cpus: 1x cores: 24 mt: 8 tpc: 2 st: 16 threads: 32 smt: enabled
cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32 KiB, 16x64 KiB
L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
Speed (MHz): avg: 2457 high: 3000 min/max: 800/6000:4500 scaling:
driver: intel_pstate governor: powersave cores: 1: 1100 2: 3000 3: 1100
4: 1100 5: 1100 6: 3000 7: 929 8: 3000 9: 1058 10: 3000 11: 1067 12: 3000
13: 1100 14: 3000 15: 1100 16: 3000 17: 3000 18: 3000 19: 3000 20: 3000
21: 3000 22: 3000 23: 3000 24: 3000 25: 3000 26: 3000 27: 3000 28: 3000
29: 3000 30: 3000 31: 3000 32: 3000 bogomips: 191692
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Raptor Lake-S GT1 [UHD Graphics 770] vendor: Gigabyte
driver: i915 v: kernel arch: Gen-13 process: Intel 7 (10nm) built: 2022+
ports: active: none empty: DP-1,HDMI-A-1 bus-ID: 00:02.0
chip-ID: 8086:a780 class-ID: 0300
Device-2: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Gigabyte
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: DP-3
empty: DP-2,HDMI-A-2,HDMI-A-3 bus-ID: 03:00.0 chip-ID: 1002:73bf
class-ID: 0300
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
compositor: kwin_x11 driver: X: loaded: amdgpu,modesetting unloaded: radeon
alternate: fbdev,intel,vesa dri: radeonsi,iris gpu: amdgpu display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 507x285mm (19.96x11.22")
s-diag: 582mm (22.9")
Monitor-1: DP-3 mapped: DisplayPort-2 model: Samsung Odyssey G8
serial: <filter> built: 2022 res: 1920x1080 hz: 120 dpi: 70 gamma: 1.2
size: 697x392mm (27.44x15.43") diag: 806mm (31.7") ratio: 16:9 modes:
max: 3840x2160 min: 640x480
API: OpenGL v: 4.6 Mesa 23.1.1 renderer: AMD Radeon RX 6900 XT (navi21
LLVM 15.0.7 DRM 3.52 6.3.4-zen1-1-zen) direct-render: Yes
Audio:
Device-1: Intel vendor: Gigabyte driver: snd_hda_intel v: kernel
alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:7a50
class-ID: 0403
Device-2: AMD Navi 21/23 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:ab28
class-ID: 0403
API: ALSA v: k6.3.4-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 0.3.71 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: Broadcom BCM4360 802.11ac Wireless Network Adapter vendor: Apple
driver: wl v: kernel modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 09:00.0 chip-ID: 14e4:43a0 class-ID: 0280
IF: wlp9s0 state: dormant mac: <filter>
Device-2: ASIX AX88179 Gigabit Ethernet driver: cdc_ncm type: USB rev: 3.2
speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-5.3:6 chip-ID: 0b95:1790
class-ID: 0a00 serial: <filter>
IF: enp0s20f0u5u3c2 state: up speed: 1000 Mbps duplex: half mac: <filter>
IF-ID-1: surfshark_ipv6 state: unknown speed: N/A duplex: N/A
mac: <filter>
Bluetooth:
Device-1: Broadcom BCM2070 Bluetooth 3.0 + HS driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:10
chip-ID: 0a5c:22be class-ID: fe01 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 1 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: <filter>
Drives:
Local Storage: total: 18.19 TiB used: 24.25 GiB (0.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WD BLACK SN850X 2000GB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 620331WD temp: 49.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:2 vendor: Western Digital
model: WD BLACK SN850X 2000GB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 620331WD temp: 48.9 C scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:1 vendor: Western Digital
model: WD BLACK SN850X 2000GB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 620331WD temp: 48.9 C scheme: GPT
ID-4: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD140EDGZ-11B1PA0 size: 12.73 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: 0A85 scheme: GPT
Partition:
ID-1: / raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 24.25 GiB (1.3%)
fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:10
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 1.7 MiB (0.6%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:9
ID-3: /home raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 24.25 GiB (1.3%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:10
ID-4: /var/log raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 24.25 GiB (1.3%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:10
ID-5: /var/tmp raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 24.25 GiB (1.3%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:10
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 62.56 GiB used: 1.2 MiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 32.0 C mobo: N/A gpu: amdgpu temp: 53.0 C
mem: 52.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:
Processes: 510 Uptime: 12m wakeups: 4 Memory: available: 62.56 GiB
used: 3.9 GiB (6.2%) Init: systemd v: 253 default: graphical tool: systemctl
Compilers: gcc: 13.1.1 Packages: pm: pacman pkgs: 1336 libs: 371
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-05-27
Last full system update: 2023-05-28 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

Is the keyboard working at the Grub menu (before you get to the login screen, where you choose the OS to boot, snapshots, etc)?

Hello, yes working at Grub menu.

Do you have other USB devices plugged in at boot time? Specifically ones drawing power, for example external hard drives or hubs that are powered over the USB bus.

This post is over twelve years old, but still valid and such a simple thing to try: How to fix "device not accepting address" error | Paul Philippov

5 Likes

No the only thing plugged in is my keyboard/mouse dongle into a usb 2.0 front header.

Try plugging the dongle into different USB ports, for example on the back of the computer to see if it makes a difference.

2 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.