System Freezing on Dynabook Laptop (Garuda Linux KDE)

Issues & Assistance Unsupported hardware | Dual boot
, ,
1

Issue Description:
I’m using Garuda Linux (plain KDE) on a Dynabook laptop, and the system frequently freezes. When this happens:

  • I can’t interact with anything on the screen.
  • Audio and other inputs (e.g., keyboard or mic) seem to continue working in the background.

This issue has been ongoing for a long time, and I haven’t found a solution yet.

What I’ve Tried:

  • Searched the web and forums for similar issues.
  • Checked the Garuda Linux wiki and FAQ sections.
  • Updated the system and checked logs for errors (couldn’t identify anything conclusive).

Additional Information:
I used Fedora on the same laptop for about 10 weeks, and this freezing issue did not occur there. Could this be related to differences in how Arch-based systems handle hardware, drivers, or kernel configurations?

garuda-inxi Output:

System:
  Kernel: 6.12.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=f31b6098-c1a4-49c9-9149-91014bae2745 rw rootflags=subvol=@
    quiet loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A info: frameworks v: 6.10.0
    wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Garuda
    base: Arch Linux
Machine:
  Type: Laptop System: Dynabook product: dynabook TECRA A40-G
    v: PMZ20E-05800WAR serial: <superuser required> Chassis: type: 10
    v: Version 1.0 serial: <superuser required>
  Mobo: Dynabook model: A0104/0002 v: Version A0
    serial: <superuser required> part-nu: PMZ20E uuid: <superuser required>
    UEFI: Dynabook v: Version 4.50 date: 02/13/2023
Battery:
  ID-1: BAT1 charge: 17.4 Wh (51.3%) condition: 33.9/42.0 Wh (80.7%)
    power: 15.6 W volts: 0.1 min: 15.4 model: G71C000LY111 type: Li-ion
    serial: <filter> status: discharging
CPU:
  Info: model: Intel Core i7-10710U bits: 64 type: MT MCP arch: Comet Lake
    gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
    model-id: 0xA6 (166) stepping: 0 microcode: 0xFE
  Topology: cpus: 1x dies: 1 clusters: 6 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB
    desc: 6x256 KiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 400 min/max: 400/4700 scaling: driver: intel_pstate
    governor: powersave cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400
    8: 400 9: 400 10: 400 11: 400 12: 400 bogomips: 38399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Comet Lake UHD Graphics vendor: Dynabook driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:9bca
    class-ID: 0300
  Device-2: Chicony TOSHIBA Web Camera - HD driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:7 chip-ID: 04f2:b689
    class-ID: 0e02
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: intel unloaded: modesetting
    alternate: fbdev,vesa dri: i965 gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x14d6 built: 2016 res: 1366x768
    dpi: 112 gamma: 1.2 size: 309x173mm (12.17x6.81") diag: 354mm (13.9")
    ratio: 16:9 modes: 1366x768
  API: Vulkan v: 1.4.303 layers: 4 device: 0 type: integrated-gpu name: Intel
    UHD Graphics (CML GT2) driver: N/A device-ID: 8086:9bca
    surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
    19.1.6 256 bits) driver: N/A device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: vulkaninfo de: kscreen-console,kscreen-doctor x11: xprop
Audio:
  Device-1: Intel Comet Lake PCH-LP cAVS vendor: Dynabook
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl
    bus-ID: 00:1f.3 chip-ID: 8086:02c8 class-ID: 0403
  API: ALSA v: k6.12.9-zen1-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.2.7 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 I219-V vendor: Dynabook driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:0d4f class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Info: services: iwd, NetworkManager, smbd, systemd-timesyncd,
    wpa_supplicant
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: 1-10:8 chip-ID: 8087:0029
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: <filter>
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff
    link-mode: peripheral accept
Drives:
  Local Storage: total: 1.34 TiB used: 52.03 GiB (3.8%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZVLQ512HALU-00000 size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: FXV7101Q temp: 36.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37960G
    size: 894.25 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter>
    fw-rev: 1.02 scheme: GPT
Partition:
  ID-1: / raw-size: 238.16 GiB size: 238.16 GiB (100.00%) used: 52 GiB (21.8%)
    fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 25.8 MiB (26.9%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 238.16 GiB size: 238.16 GiB (100.00%)
    used: 52 GiB (21.8%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-4: /var/log raw-size: 238.16 GiB size: 238.16 GiB (100.00%)
    used: 52 GiB (21.8%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-5: /var/tmp raw-size: 238.16 GiB size: 238.16 GiB (100.00%)
    used: 52 GiB (21.8%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.38 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 12
    dev: /dev/zram0
Sensors:
  Src: /sys System Temperatures: cpu: 50.0 C pch: 48.0 C mobo: N/A
  Fan Speeds (rpm): N/A
  Power: 12v: N/A 5v: 5 3.3v: N/A vbat: N/A
Info:
  Memory: total: 16 GiB available: 15.38 GiB used: 4.35 GiB (28.3%)
  Processes: 331 Power: uptime: 22m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.14 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: 1184 pm: pacman pkgs: 1150 libs: 352 tools: yay pm: flatpak
    pkgs: 34 Compilers: gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1
    running-in: kitty inxi: 3.3.37
Garuda (2.6.26-1.1):
  System install date:     2024-12-29
  Last full system update: 2025-01-16
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)```
2

Hi.
Have you tried the LTS kernel?

2 Likes
3

have not let me look into how to do that let see if that gonna work hope so pls pls

4

sudo pacman -S linux-lts linux-lts-headers
Reboot and select LTS kernel through the Grub menu

3 Likes
5

Search for how to get to a virtual terminal with a frozen system Linux

Try logging into an X session, rather than wayland.

If you can access a TTY you have far more options, such as restarting plasmashell & kwin (on X11}, or killing any process that could be causing the lockup.

3 Likes
6

It would also be interesting to know which edition/spin (DE), also KDE?

2 Likes
7

nope still same but i have seen something tho whenever i am on power it does that less than when i’m on battery idk why

local/linux-lts 6.6.70-1
local/linux-lts-headers 6.6.70-1
local/linux-zen 6.12.9.zen1-1
local/linux-zen-headers 6.12.9.zen1-1
8

Nobara-41-KDE-2025-01-05.iso:

9

let me look into it thanks for help bro

1 Like
10

ya nope didnt work it stuck in that to but do realised something to when am on charing it doesnt do that and only when it’s on battery it does these thing lol

11

@kiyo_dum Please try to write properly and use punctuation. This is an international forum, not everyone speaks/understands English (+ slang) and is therefore dependent on the help of online translators.
Thank you.

Garuda Linux KDE lite? If so, you are on your own, we do not provide any support for KDE lite editions :wink:

It is not a good idea to wait until no one can understand after which event (update/package installation etc.) the issue occurred :wink:

That does not mean that there are clear indications. If you think that other users should not check the logs, then that is not particularly helpful - but it is your decision :wink:

It looks like a cat has walked over your keyboard, but the meaning was just about understandable:
Try a different power manager.

3 Likes
12

LOL dude, I am not a native speaker myself. I learned from anime dubs, games (hmm…COD…), etc. It’s not by choice.

By the way, the long thing, this one is a new KDE install, so I haven’t done much new with it.

LLM helped me write that. I just gave her what’s going on and what I have done to try to fix it. That’s all. I am not good with words. you see

13

I can’t say it’s fixed per se, but when I put it in the power cable, it works without any problem, so I kind of say it’s a fix for now, so, like my life, it’s held together with tape, and it is what it is, lol.

14

What’s not to understand about the fact that you should write sensibly and without slang? Read the forum rules and please stick to them. It’s also not exactly a sign of sensible communication to address members of the Garuda team like @tbg as “bro”.

Then it would probably make more sense if you used a translator yourself.

Maybe you shouldn’t rely on pseudo-AI.

If that’s your solution instead of eliminating the cause of the problem…then good luck.

5 Likes