Mouse not working after 20250613.12fe085f linux-firmware update

Issues & Assistance
1

Hello, I have an AMD 9070XT and I’ve been following discussions about the 20250613.12fe085f firmware split updates.

I have ran the suggested commands on this forum and tried upgrading linux-firmware-amdgpu to the 20250613.12fe085f-8 version and it sure doesn’t end up in a blank screen after boot.

But I have another issue with this update: my mouse doesn’t work at all. I have tried 2 different USB mice, both wired and wireless (with dongle), both are Logitech. I see the cursor on the screen, but it doesn’t move or react to anything. Keyboard works fine, Logitech as well.

I have tried all firmware versions between 20250613.12fe085f-3 and 20250613.12fe085f-8 (except -6 which has the blank screen) and it’s the same issue on all of them.

I have tried searching various forums, this one included, and I haven’t found anyone posting about similar problems. Only other mouse related issues I saw were things like duplicated cursor on the screen or the cursor lagging, but nothing about the mouse not working at all.

I reverted to a previous snapshot for now, but I can update again to gather logs that might help. I would like assistance with what commands should I run to gather logs and a bit of patience as copy-pasting and saving stuff between the terminal and a text editor will be a bit harder with just a keyboard.

Thanks!

Edit 1

For clarification, I have run the update with the following commands:

pacman -Rdd linux-firmware
garuda-update linux-firmware

This resulted in getting the firmware version 0250613.12fe085f-6.
I then upgraded to 0250613.12fe085f-8 by running the command: downgrade linux-firmware-amdgpu.

Here’s my garuda-inxi output before running the update:

System:
  Kernel: 6.14.9-arch1-1-znver3 arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-znver3
    root=UUID=6ff3851c-d5b1-4c08-b237-e19d4e1c67ec rw rootflags=subvol=@
    quiet loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.14.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: X570 AORUS ELITE v: -CF
    serial: <superuser required>
  Mobo: Gigabyte model: X570 AORUS ELITE serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends LLC. v: F39
    date: 03/22/2024
CPU:
  Info: model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 0 microcode: 0xA20102D
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 16 threads: 32 tpc: 2
    smt: enabled cache: L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 8 MiB
    desc: 16x512 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 1746 min/max: 550/5086 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 1746 2: 1746 3: 1746
    4: 1746 5: 1746 6: 1746 7: 1746 8: 1746 9: 1746 10: 1746 11: 1746 12: 1746
    13: 1746 14: 1746 15: 1746 16: 1746 17: 1746 18: 1746 19: 1746 20: 1746
    21: 1746 22: 1746 23: 1746 24: 1746 25: 1746 26: 1746 27: 1746 28: 1746
    29: 1746 30: 1746 31: 1746 32: 1746 bogomips: 217592
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 [RX 9070/9070 XT]
    vendor: XFX driver: amdgpu v: kernel pcie: gen: 5 speed: 32 GT/s lanes: 16
    ports: active: DP-2,DP-3 empty: DP-1,HDMI-A-1,Writeback-1 bus-ID: 0c:00.0
    chip-ID: 1002:7550 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: amdgpu dri: radeonsi gpu: amdgpu
    d-rect: 5120x1440 display-ID: 0
  Monitor-1: DP-2 pos: primary,left model: LG (GoldStar) 27GL850
    serial: <filter> built: 2020 res: mode: 2560x1440 hz: 144 scale: 114% (1.15)
    to: 2226x1252 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23")
    diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440 min: 640x480
  Monitor-2: DP-3 pos: right model: LG (GoldStar) 27GL850 serial: <filter>
    built: 2020 res: mode: 2560x1440 hz: 144 scale: 114% (1.15) to: 2226x1252
    dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
    ratio: 16:9 modes: max: 2560x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.1.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
    gfx1201 ACO DRM 3.61 6.14.9-arch1-1-znver3) device-ID: 1002:7550
    memory: 15.62 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.4.313 layers: 13 device: 0 type: discrete-gpu name: AMD
    Radeon Graphics (RADV GFX1201) driver: mesa radv v: 25.1.1-arch1.2
    device-ID: 1002:7550 surfaces: N/A device: 1 type: cpu name: llvmpipe
    (LLVM 19.1.7 256 bits) driver: mesa llvmpipe v: 25.1.1-arch1.2 (LLVM
    19.1.7) device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: corectrl wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel v: kernel
    pcie: gen: 5 speed: 32 GT/s lanes: 16 bus-ID: 0c:00.1 chip-ID: 1002:ab40
    class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0e:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Focusrite-Novation Scarlett 2i2 3rd Gen driver: snd-usb-audio
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.1.2:8
    chip-ID: 1235:8210 class-ID: 0102 serial: <filter>
  Device-4: Kingston HyperX QuadCast
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-1.1.4:10 chip-ID: 0951:16df class-ID: 0300
    serial: <filter>
  Device-5: Walmart AB13X Headset Adapter
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-1.4:9 chip-ID: 001f:0b21 class-ID: 0300
    serial: <filter>
  API: ALSA v: k6.14.9-arch1-1-znver3 status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: PipeWire v: 1.4.4 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 I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp6s0 state: down mac: <filter>
  Device-3: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
    rev: 3.2 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-1.3:4
    chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  IF: enp7s0f1u1u3 state: down mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-6.4:4 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
  Local Storage: total: 3.64 TiB used: 844.74 GiB (22.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Samsung model: SSD 960 EVO 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: 3B7QCXE7 temp: 36.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Kingston model: SA2000M81000G
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: S5Z42105 temp: 38.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 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: 2B6Q scheme: GPT
Partition:
  ID-1: / raw-size: 102.63 GiB size: 102.63 GiB (100.00%)
    used: 65.84 GiB (64.2%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:5
  ID-2: /boot/efi raw-size: 450 MiB size: 96 MiB (21.33%)
    used: 610 KiB (0.6%) fs: vfat dev: /dev/nvme0n1p2 maj-min: 259:4
  ID-3: /home raw-size: 299.47 GiB size: 299.47 GiB (100.00%)
    used: 13.03 GiB (4.4%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:3
  ID-4: /var/log raw-size: 102.63 GiB size: 102.63 GiB (100.00%)
    used: 65.84 GiB (64.2%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:5
  ID-5: /var/tmp raw-size: 102.63 GiB size: 102.63 GiB (100.00%)
    used: 65.84 GiB (64.2%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:5
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 62.25 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p7 maj-min: 259:7
  ID-2: swap-2 type: zram size: 62.7 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 32
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 51.5 C mobo: 29.0 C gpu: amdgpu temp: 50.0 C
    mem: 65.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 64 GiB note: est. available: 62.7 GiB used: 8.69 GiB (13.9%)
  Processes: 664 Power: uptime: 1h 17m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 25.06 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1959 libs: 570 tools: octopi,paru Compilers:
    clang: 19.1.7 gcc: 15.1.1 Shell: garuda-inxi default: fish v: 4.0.2
    running-in: konsole inxi: 3.3.38
Garuda (2.7.2-1):
  System install date:     2025-03-30
  Last full system update: 2025-06-04
  Is partially upgraded:   Yes
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:

Edit 2

So I’ve ran the following commands both before and after the update:

  • garuda-inxi
  • dmesg-w
  • lsusb
  • libinput list-devices
  • libinput debug-events

Looking at the results of those 2 libinput commands, it seems that my mouse receiver is no longer detected. For libinput debug-events I moved the mouse around and clicked a bit both before and after the update.

I have attached the results of all the commands here: https://www.dropbox.com/scl/fi/otywcpozla24wj00sc7sg/linux-firmware-update.zip?rlkey=9b2ectqvqxu6vbemncx9rnseq&st=755myuqo&dl=0

Edit 3

So I’ve ran some more random experiments and what I saw as new behavior is that if I disconnect my keyboard and reconnect it back, it ends up unresponsive just like the mouse.
Keyboard worked again only after a full reboot, mouse still dead as usual.

So there seems to be quite a few issues with input devices in general.

2

Welcome, first you need to post your garuda-inxi try running garuda-update

1 Like
3

I’ve edited my post to contain the garuda-inxi output before updating and also some info on how I’ve ran the updates in the first place.

Should I run the update the post a new output from garuda-inxi?

4

Welcome on the Forum!

And just a garuda-update (from the beginning before removing anything) as stated here does not allow your mouse to work?

1 Like
5

Hi, thanks for the suggestion, I didn’t see the response there.

The update worked without running any -Rdd stuff as mentioned, but my mouse was still dead.

I still had to do a manual upgrade of linux-firmware-amdgpu to -9 (tried the newest now) to not get a blank screen with the default -6.

So yeah, still not working unfortunately.

6

If it helps, I have ran some commands before and after the update in order to see if there are any differences.

I’ve edited my post with more details.

7

It seems to be missing some devices indeed.
Your mouse and Logitech?

8

I rolled back to pre-update and decided to wait. I get to the login screen, where my mouse doesn’t work, and then it goes to a blakscreen when I login. Seems like this update makes quite a few changes that need some work still.

5800x3d/9070(non-xt) / Garuda Mokka

Tried a few things myself, as per some of the forum posts, and the black screen just won’t go away. Plus, I’d need to solve the mouse issue. Sorry i can’t offer assistance, but sometimes knowing that more than a few people are impacted helps.

1 Like
9

I think this is directly related to

which is (hopefully) solved by

It was previously reverted for that reason.

pkgrel 9 is out in testing now, so you should expect it to be available very soon, please update to it ASAP and confirm it fixes the problem with GPU.

You can refresh this page to see when it’s available to garuda-update to:

EDIT: It was pushed shortly after my message was sent, it should make it to mirrors momentarily: Last Updated: 2025-06-25 02:26 UTC

6 Likes
10

Nice, so the default is now on -9 which removes the need to do the manual upgrade.

Now still waiting for some news about the mouse issues though.

I can’t find anything reported on that Gitlab project about the mouse issues. I see they disabled registrations temporarily, can somebody with an account help me with opening an issue with all the data that I’ve provided?

1 Like
11

Glad to see I’m not the only one.

You’re the only other person with the unresponsive mouse problem that I see posting about it, which makes me think we’re some sort of edge case with this.

1 Like
12

No issues with mouse or me; but I have been seeing errors/delays related to a USB device not responding, but all my devices are working so I’m not entirely sure what it is.

13

Is it using the same wireless receiver? Do you see both devices with lsusb? Maybe interesting related errors to share from jctl and sudo dmesg, especially if you unplug and replug it before running.

Please post the error and command used, supposing it could be related.

1 Like
14

I use the devices with separate wireless receivers. I even tried plugging them directly and there’s no difference.

If I run lsusb it sees both devices:

Bus 001 Device 012: ID 046d:c547 Logitech, Inc. USB Receiver
Bus 001 Device 015: ID 046d:c545 Logitech, Inc. USB Receiver

Those 2 receivers appear in both the good and the bad version of the system (can be seen in the attached logs on the post on Edit 2).

Just to clarify, you want me to try:

  1. updating the system again
  2. unplug and replug the mouse
  3. run jctl and dmesg and record their outputs

Did I understand correctly?

1 Like
15

Regarding your mouse have you done the basic hardware troubleshooting steps required to narrow down the cause?

Assuming this is a wireless Logitech mouse, things to try:

Swap out your wireless mouse for a wired USB or PS/2 mouse.

Test your wireless mouse out on different USB ports on your computer.

Test your current mouse out on a different computer (preferably running Linux not Windows).

Is this a dual band Logitech mouse, that can be switched between Bluetooth or standard 2. 4 GHz wireless? If so, toggle the wireless mode by pressing the button/switch on the bottom of the mouse. The light will turn blue if it’s in Bluetooth mode.

Logitech sometimes issues firmware updates for their wireless mouse/trackball models. With my Logitech devices I install fwupd and do all my FW updates through that handy utility.

If you are using the Bluetooth mode on your Logitech mouse you might want to install/reinstall linux-firmware-intel as you use an Intel Bluetooth device.

Sorry I typed this before your reply a couple of minutes ago, so you covered some of what I asked.

2 Likes
16

Hi, yes I can answer the questions again for clarity, no problem.

The mouse is a Logitech G502 X. It works either via a wireless receiver, or by plugging it in directly to the USB.

I have tried both with the receiver and plugged in. Same result.

I’ve been using this mouse with Ubuntu for 2 years until a couple of months ago when I switched to Garuda. I don’t have any other Linux device that I can test with, only a macbook and a Windows 11 device and it works well on both. I’m pretty sure it’s not the mouse itself the problem.

I have also checked the firmware and it’s up-to-date.

image
image800×275 33.2 KB

I have also tried using an old wired mouse (also Logitech unfortunately) and the result was the same.
I have tried changing ports, no difference. Also it would be preferable to not have to change ports, since it’s connected to a KVM to easily switch between the work laptop and my PC.

1 Like
17

Well that is strange. My remaining suggestion would then be to reset your bios to the factory default. This often helps with strange hardware issues.

I would suggest powering down, then remove all peripheral attachments such as USB hubs, and any extra USB devices. Leave your computer unplugged with no backup power supply. After a few minutes without power, press and hold the power button a couple of times. Then, reattach your power supply and reboot into your bios. Once in your bios, reset the bios to its factory default state. After resetting your bios you will need to change several settings for Linux compatibility again. You should already know those bios settings (secure boot off, ahci on, OS other). After saving the settings boot into Garuda to see if things have improved.

1 Like
18

Okay that is good, it sees the devices as intended.

  1. Yes, since there were some linux-firmware changes between then and now, maybe it could have been resolved.
  2. Yes, because each connection/disconnection causes events that may reproduce and log the error
  3. Yes, since that’s where errors would most likely show
1 Like
19

Also, it wouldn’t hurt to test alternate kernels.

1 Like
20

Ok, it’s late for me now so I’ll try again tomorrow evening.

I’ll try stuff in this order:

  1. Update bios firmware (I’m behind with 4 versions) + garuda-update
  2. Switch back to the default kernel instead of znver3 + garuda-update
  3. Reset bios settings to defaults after doing the update and having the unresponsive mouse

I’ll try to unplug/plug back the mouse each time and record jctl and dmesg outputs.

Thanks for the suggestions so far!

1 Like