Keyboard does not always recognoized at boot

General system Kernel, boot, graphics & hardware
1

When my PC boots up, it does not always recognize the keyboard.
The same USB port always works. As soon as the mouse is connected it is recognized.
As soon as I switch to USB 3.0, the keyboard is also recognized.
A very strange behavior.
How can I localize the source of the error and perhaps rectify i

inxi -J 
➜  inxi -J  
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
  Hub-2: 1-6:2 info: Genesys Logic Hub ports: 4 rev: 2.0
  Device-1: 1-7:3 info: Integrated Express RGB LED Controller type: HID
    rev: 2.0
  Device-2: 1-8:4 info: Logitech Keyboard K120 type: keyboard,HID rev: 1.1
  Device-3: 1-9:5 info: CHERRY Mouse type: mouse rev: 2.0
  Hub-3: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
  Hub-4: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
  Device-1: 3-1:2 info: Logitech V10 Notebook Speakers type: audio,HID
    rev: 1.1
  Hub-5: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
  Hub-6: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
  Hub-7: 6-0:1 info: super-speed hub ports: 2 rev: 3.1
inxi -Faz 
➜  inxi -Faz
System:
  Kernel: 6.8.9-arch1-2 arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: initrd=\f329784de44446948b3869b7b1d20a31\6.8.9-arch1-2\initrd
    nvme_load=YES nowatchdog rw
    root=UUID=de0eeb1f-095d-408b-b6c3-ebda58df6d41
    systemd.machine_id=f329784de44446948b3869b7b1d20a31
  Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.1.0
    wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: EndeavourOS
    base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: B550 AORUS ELITE V2
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: F17 date: 03/22/2024
CPU:
  Info: model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
    process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA50000F
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 562 high: 2997 min/max: 400/4673 scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 400 2: 400 3: 2997
    4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400
    14: 400 15: 400 16: 400 bogomips: 121419
  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 mitigation: Safe RET
  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: Retpolines; IBPB: conditional; IBRS_FW;
    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: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] 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-2,HDMI-A-2 empty: DP-1,HDMI-A-1,Writeback-1 bus-ID: 03:00.0
    chip-ID: 1002:73ff class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.6
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu d-rect: 3840x1080 display-ID: 0
  Monitor-1: DP-2 pos: right res: 1920x1080 size: N/A modes: N/A
  Monitor-2: HDMI-A-2 pos: primary,left res: 1920x1080 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
    drv: radeonsi inactive: gbm
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.6-arch1.2
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6600 (radeonsi navi23
    LLVM 17.0.6 DRM 3.57 6.8.9-arch1-2) device-ID: 1002:73ff memory: 7.81 GiB
    unified: no display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 3 device: 0 type: discrete-gpu name: AMD
    Radeon RX 6600 (RADV NAVI23) driver: mesa radv v: 24.0.6-arch1.2
    device-ID: 1002:73ff surfaces: xcb,xlib,wayland
Audio:
  Device-1: 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
  Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 09:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-3: AMD Family 17h/19h HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 09:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Device-4: Logitech V10 Notebook Speakers
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-1:2 chip-ID: 046d:0a10 class-ID: 0300
  API: ALSA v: k6.8.9-arch1-2 status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.0.6 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: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 07:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager, nfsd, systemd-timesyncd
Drives:
  Local Storage: total: 3.17 TiB used: 2.18 TiB (68.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Samsung model: SSD 980 PRO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QGXA7 temp: 36.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 32.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Toshiba model: HDWD110
    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: A8R0 scheme: MBR
  ID-4: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWD110
    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: A8R0
  ID-5: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT240BX500SSD1
    size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 052 scheme: GPT
Partition:
  ID-1: / raw-size: 232.39 GiB size: 227.69 GiB (97.97%)
    used: 68.39 GiB (30.0%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:4
  ID-2: /home raw-size: 931.51 GiB size: 915.82 GiB (98.31%)
    used: 480.33 GiB (52.4%) fs: ext4 dev: /dev/nvme1n1p1 maj-min: 259:2
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 16 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 43.2 C mobo: 31.0 C gpu: amdgpu temp: 38.0 C
    mem: 38.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 16 GiB available: 15.47 GiB used: 3.64 GiB (23.5%)
  Processes: 349 Power: uptime: 36m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.17 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1866 libs: 414 tools: pacseek,yay pm: flatpak
    pkgs: 0 Compilers: clang: 17.0.6 gcc: 14.1.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.26 running-in: konsole inxi: 3.3.34

EDIT: This error only occurs every 250th boot or so

2 Likes
2

I’ve had a look around and I think I’m close to the solution. What i’ve found is:

Some Gigabyte motherboards have a specific setting for USB keyboard support. In the BIOS settings, navigate to the Advanced tab and look for the USB settings. Ensure that the USB keyboard support is enabled and set to the correct mode (e.g., USB keyboard or Legacy USB keyboard).

So I looked at the USB settings in the BIOS again and activated legacy support. Let’s see if the problem is solved

EDIT: Booting 2 - 3 times a day, which means I will know in about 90 days :sweat_smile:

1 Like
3

I should definitely save my settings. I always forget something setting back after every BIOS update :rofl:

1 Like
4

Too many boots. :rofl:

2 Likes
5

Definately. But it happens :joy: It’s really annoying

6

What kind of keyboard is it?

7

It’s a Logitech K120. Just a simple one

1 Like
8

I just want you to know … i probably boot my system more times than you 10 fold! :rofl:

2 Likes
9

I usually boot up in the morning, in the evening when I get back from work, every now and then after an update. That’s all I do.

My system runs without any issues except the keyboard, so no need to boot up several times a day :rofl:

1 Like
10

I also had some problems with keyboards and my Gigabyte board. Some required several seconds before accepting input, which was very noticeable entering the LUKS password. In my situation it would work eventually though. No fluke but always reproducible.

But I don’t remember what I did to fix it. Might have been a BIOS setting. Just checked, USB legacy support in On here (now?). :person_shrugging:

2 Likes
11

I had fixed the problem until the last BIOS update. I also didn’t remember which setting I had made in the BIOS.
As I described above, I should definitely save my settings so that I can find the right settings again after the next BIOS update

1 Like
12

Oh yeah, BIOS updates erasing all previous user settings is a nice surprise:tm:.

I was a Mac user for twenty years, and this was my first PC board - it getting old now. Is that a standard behavior for all manufacturers or a Gigabyte “feature”? Because sweet Jebus, at least throw up a warning for the user.

1 Like
13

I suspect this “feature” applies to all brands…

1 Like
14

I had a similar problem. I moved my mouse/keyboard over to a USB 3.0 port and the issue went away.

In the past I’ve used a script to reset naughty USB controllers. Pretty sure I got it from here.