Using Keyboard makes Garuda Crash

Hello,

new to both Linux and Garuda here.

Installed Garuda alongside Win10 (dual boot) on my laptop

had some problems during the install:

had to use systemd.mask=mhwd-live.service to securely boot
and even there I had stability issues ON THE LIVE USB itself

fortunately a Bios/uefi update seemed to have made things better and I was finally able to install Garuda onto the laptop

but one major problem remains : using the keyboard makes the system crash
it seems like it goes into a forced shutdown

to be more precise:
I can still use the keyboard but I have to make sure to stay around 1 or 2 keypresses per second and that there is no overlap between the keypresses ( as you can imagine that isn't something that can be used on the long run as a gamer / aspiring dev )

I also connected a wireless Logitech Keyboard/MousePad to the laptop (logitech K400r) that uses a dongle
using the logitech keyboard DID NOT make garuda crash, this makes me think that this is linked to maybe the driver for the built in keyboard, or maybe the bios/uefi itself

I've tried looking for crash logs, but /var/crashes doesn't exist
my inexperience here shows, since I can't seem to find where I could find those crash reports, or logs.

The built in Keyboard had per key LED lighting, and there are also LEDs on the bottom of the laptop (ambiance lighting). I don't know if there is some kind of interference with this type of keyboard, but seeing that Garuda targets the gaming community I feel like LED keyboards would be supported

thanks for any input, and I am available if you need any extra information

SYSTEM INFO :

System:    Kernel: 5.12.2-zen2-1-zen x86_64 bits: 64 compiler: gcc v: 10.2.0
           parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
           root=UUID=9ced3168-9c0d-403b-a12f-7872de9f227b rw [email protected] quiet splash
           rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1
           loglevel=3
           Desktop: LXQt 0.17.1 tk: Qt 5.15.2 info: cairo-dock, lxqt-panel wm: kwin_x11 vt: 1
           dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:   Type: Laptop System: ASUSTeK product: ROG Strix G713QR_G713QR v: 1.0 serial: <filter>
           Mobo: ASUSTeK model: G713QR v: 1.0 serial: <filter> UEFI: American Megatrends LLC.
           v: G713QR.315 date: 03/11/2021
Battery:   ID-1: BAT0 charge: 87.6 Wh (100.0%) condition: 87.6/90.0 Wh (97.3%) volts: 17.3
           min: 15.9 model: AS3GWAF3KC GA50358 type: Li-ion serial: <filter> status: Full
CPU:       Info: 8-Core model: AMD Ryzen 9 5900HX with Radeon Graphics bits: 64 type: MT MCP
           arch: Zen 3 family: 19 (25) model-id: 50 (80) stepping: 0 microcode: A50000B cache:
           L2: 4 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
           bogomips: 105403
           Speed: 2531 MHz min/max: 1200/3300 MHz boost: enabled Core speeds (MHz): 1: 2531
           2: 1660 3: 2751 4: 1397 5: 1396 6: 1397 7: 1395 8: 1397 9: 3736 10: 2742 11: 3875
           12: 3832 13: 3643 14: 3667 15: 3996 16: 3632
           Vulnerabilities: Type: itlb_multihit status: Not affected
           Type: l1tf status: Not affected
           Type: mds status: Not affected
           Type: meltdown status: Not affected
           Type: spec_store_bypass
           mitigation: Speculative Store Bypass disabled via prctl and seccomp
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, STIBP:
           always-on, RSB filling
           Type: srbds status: Not affected
           Type: tsx_async_abort status: Not affected
Graphics:  Device-1: NVIDIA GA104M [GeForce RTX 3070 Mobile / Max-Q] vendor: ASUSTeK
           driver: nvidia v: 465.27 alternate: nouveau,nvidia_drm bus-ID: 01:00.0
           chip-ID: 10de:249d class-ID: 0300
           Device-2: AMD vendor: ASUSTeK driver: amdgpu v: kernel bus-ID: 06:00.0
           chip-ID: 1002:1638 class-ID: 0300
           Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver:
           loaded: modesetting,nvidia display-ID: :0 screens: 1
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
           s-diag: 582mm (22.9")
           Monitor-1: eDP-1 res: 1920x1080 hz: 300 dpi: 128 size: 382x215mm (15.0x8.5")
           diag: 438mm (17.3")
           OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.12.2-zen2-1-zen LLVM 11.1.0)
           v: 4.6 Mesa 21.1.0 direct render: Yes
Audio:     Device-1: AMD vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 06:00.1
           chip-ID: 1002:1637 class-ID: 0403
           Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: ASUSTeK
           driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x bus-ID: 06:00.5
           chip-ID: 1022:15e2 class-ID: 0480
           Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
           bus-ID: 06:00.6 chip-ID: 1022:15e3 class-ID: 0403
           Sound Server-1: ALSA v: k5.12.2-zen2-1-zen running: yes
           Sound Server-2: JACK v: 0.125.0 running: no
           Sound Server-3: PulseAudio v: 14.2 running: yes
           Sound Server-4: PipeWire v: 0.3.27 running: yes
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK
           driver: r8169 v: kernel port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
           IF: enp2s0 state: down mac: <filter>
           Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: e000 bus-ID: 03:00.0
           chip-ID: 8086:2723 class-ID: 0280
           IF: wlan0 state: up mac: <filter>
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-4:3
           chip-ID: 8087:0029 class-ID: e001
           Report: bt-adapter ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
           rfk-block: hardware: no software: yes address: <filter>
Drives:    Local Storage: total: 1.84 TiB used: 86.56 GiB (4.6%)
           SMART Message: Unable to run smartctl. Root privileges required.
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 1TB
           size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
           rotation: SSD serial: <filter> rev: 2B2QEXE7 scheme: GPT
           ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: SK Hynix model: HFM001TD3JX013N
           size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
           rotation: SSD serial: <filter> rev: 41000C20 scheme: GPT
Partition: ID-1: / raw-size: 249.65 GiB size: 249.65 GiB (100.00%) used: 19.71 GiB (7.9%)
           fs: btrfs dev: /dev/nvme1n1p7 maj-min: 259:10
           ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 25.9 MiB (10.1%)
           fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:4
           ID-3: /home raw-size: 249.65 GiB size: 249.65 GiB (100.00%) used: 19.71 GiB (7.9%)
           fs: btrfs dev: /dev/nvme1n1p7 maj-min: 259:10
           ID-4: /var/log raw-size: 249.65 GiB size: 249.65 GiB (100.00%) used: 19.71 GiB (7.9%)
           fs: btrfs dev: /dev/nvme1n1p7 maj-min: 259:10
           ID-5: /var/tmp raw-size: 249.65 GiB size: 249.65 GiB (100.00%) used: 19.71 GiB (7.9%)
           fs: btrfs dev: /dev/nvme1n1p7 maj-min: 259:10
Swap:      Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100)
           ID-1: swap-1 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram0
           ID-2: swap-2 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram1
           ID-3: swap-3 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram2
           ID-4: swap-4 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram3
           ID-5: swap-5 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram4
           ID-6: swap-6 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram5
           ID-7: swap-7 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram6
           ID-8: swap-8 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram7
           ID-9: swap-9 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram8
           ID-10: swap-10 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram9
           ID-11: swap-11 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram10
           ID-12: swap-12 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram11
           ID-13: swap-13 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram12
           ID-14: swap-14 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram13
           ID-15: swap-15 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram14
           ID-16: swap-16 type: zram size: 967.6 MiB used: 0 KiB (0.0%) priority: 32767
           dev: /dev/zram15
Sensors:   System Temperatures: cpu: 59.0 C mobo: N/A gpu: amdgpu temp: 54.0 C
           Fan Speeds (RPM): cpu: 2500
Info:      Processes: 420 Uptime: 1m wakeups: 4 Memory: 15.12 GiB used: 2.76 GiB (18.3%)
           Init: systemd v: 248 tool: systemctl Compilers: gcc: 10.2.0 clang: 11.1.0 Packages:
           pacman: 1474 lib: 420 Shell: fish v: 3.2.2 running-in: alacritty inxi: 3.3.04

Hi there.

It would make troubleshooting the source of the issue much easier if you could report on if you experience the same problem on other live boot disks Garuda or otherwise.

Try some ISO's with KDE or Gnome.

2 Likes

had the live boot media issue with all garuda live boot disks (tried 5 of them) as well as with the manjaro distro's and ubuntu

Have you seen this:

https://liamfrappell.medium.com/fixing-black-screen-and-keyboard-shutdown-issues-on-an-asus-rog-strix-scar-2021-laptop-in-ubuntu-20-9ce964bf34d0

First hit returned.

Further:

An alternate driver is listed on the second linked post.

I would also test the linux-next-git kernel.

3 Likes

thx, a lot
mainly checked here on garuda forum

i'll look into these options

thx for the quick response

1 Like

Also, if your hardware does not play well with any Linux distribution then we're not going to be able to fix it. Complain to the hardware manufacturer, or return it to the retailer in exchange for hardware that works.

3 Likes

Hello my dear freind i am here to help to

1.open konsole type for checking errors sudo systemctl --failed
2.Check for errors in logfiles sudo journalctl -p 3 -xb

then you can try to fix it

might want to check dates there....

1 Like

to check errors in logs and files

Please do not necrobump old technical threads.