System get's dark on videos randomly

Hi everyone,

today i am seeking for some ideas how i solve an intermittent problem.

Device is an HP ZBook G5 15" with an Intel Core i7-9850H
The system is equipped with 32 GB RAM and a second decidated NVIDIA Quadro graphics adapter, but this one i never use (i haven’t even installed the driver) because for my tasks the internal Intel (Intel CoffeeLake-H GT2 [UHD Graphics 630] ) is sufficient.

Every now and then while watching a video, the system crashes. The screen turns dark, keyboard is not reacting at all.
I have to long press the power button, then the little LED in the Shift-Lock is flashing for a second.
Once this is done, i can restart the device and it works as if nothing happened.

The problem can occur totally random once or twice a day, sometimes the device runs for days.
It is also not impacted
There is nothing in the logs as far as i can see.
Installed is Manjaro latest stable and properly updated with KDE on Wayland.
But it also crashes after a fresh install and/or on X. It also does not depend if it’s browser based (e.g. Youtube) or a locally installed Video via VLC Player

Any ideas where i can start troubleshooting are much appreciated.
Thanks

Here’s something potentially helpful: inxi -zv8 :wink:

Whatever helps :wink:

System:
  Kernel: 6.12.73-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=b734715b-4f93-4672-ada3-2f059e4f5957 rw quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.5.5 tk: Qt v: N/A info: frameworks v: 6.23.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: HP product: HP ZBook 15 G6 v: SBKPF
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 860F v: KBC Version 65.39.00 serial: <superuser required>
    part-nu: 6CJ09AV uuid: <superuser required> Firmware: UEFI vendor: HP
    v: R92 Ver. 01.32.00 date: 03/04/2025
Battery:
  ID-1: BAT0 charge: 43.2 Wh (72%) condition: 60/75 Wh (80%) volts: 15.31
    min: 15.4 model: Hewlett-Packard Primary type: Li-ion serial: <filter>
    charging: status: discharging cycles: 92
Memory:
  System RAM: total: 32 GiB available: 30.95 GiB used: 3.8 GiB (12.3%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: Top-Slot 1(left) type: DDR4 detail: synchronous size: 16 GiB
    speed: spec: 3200 MT/s actual: 2667 MT/s volts: curr: 1 width (bits):
    data: 64 total: 64 manufacturer: Micron part-no: 16ATF2G64HZ-3G2J1
    serial: <filter>
  Device-2: Top-Slot 2(right) type: DDR4 detail: synchronous size: 16 GiB
    speed: spec: 3200 MT/s actual: 2667 MT/s volts: curr: 1 width (bits):
    data: 64 total: 64 manufacturer: Micron part-no: 16ATF2G64HZ-3G2J1
    serial: <filter>
  Device-3: Bottom-Slot 1(left) type: no module installed
  Device-4: Bottom-Slot 2(right) type: no module installed
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i7-9850H bits: 64 type: MT MCP arch: Coffee Lake
    gen: core 9 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 0xD (13) microcode: 0x104
  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: 800 min/max: 800/4600 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 9: 800 10: 800 11: 800 12: 800 bogomips: 62431
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs
    ibrs_enhanced ida intel_pt invpcid lahf_lm lm mca mce md_clear mmx
    monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq
    pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pts rdrand rdseed rdtscp
    rep_good sdbg sep smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3
    stibp syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx
    vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: indirect_target_selection mitigation: Aligned branch/return thunks
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_rstack_overflow status: Not affected
  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: Enhanced / Automatic IBRS; IBPB:
    conditional; PBRSB-eIBRS: SW sequence; BHI: SW loop, KVM: SW loop
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort mitigation: TSX disabled
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, HDMI-A-3
    bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
  Device-2: NVIDIA TU117GLM [Quadro T2000 Mobile / Max-Q]
    vendor: Hewlett-Packard driver: nvidia v: 590.48.01
    alternate: nouveau,nvidia_drm non-free: 550-580.xx+ status: current (as
    of 2025-11; EOL~2026-12-xx) arch: Turing code: TUxxx process: TSMC 12nm FF
    built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s ports: active: none empty: DP-3,DP-4,HDMI-A-4
    bus-ID: 01:00.0 chip-ID: 10de:1fb8 class-ID: 0300
  Device-3: Chicony HP HD Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:3 chip-ID: 04f2:b669
    class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
    unloaded: nouveau alternate: fbdev,nv,vesa dri: iris gpu: i915
    display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0852 built: 2018 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2 chroma: red:
    x: 0.592 y: 0.349 green: x: 0.329 y: 0.557 blue: x: 0.153 y: 0.118 white:
    x: 0.314 y: 0.329 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
    ratio: 16:9 modes: 1920x1080
  EDID-Warnings: 1: parse_edid: unknown flag 2
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
    inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.3.5-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL
    GT2) device-ID: 8086:3e9b memory: 30.22 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.341 layers: 4 device: 0 type: integrated-gpu name: Intel
    UHD Graphics 630 (CFL GT2) driver: mesa intel v: 25.3.5-arch1.1
    device-ID: 8086:3e9b surfaces: N/A device: 1 type: discrete-gpu
    name: Quadro T2000 driver: nvidia v: 590.48.01 device-ID: 10de:1fb8
    surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard
    driver: sof-audio-pci-intel-cnl alternate: snd_hda_intel, snd_soc_avs,
    snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0401
  Device-2: NVIDIA vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
    bus-ID: 01:00.1 chip-ID: 10de:10fa class-ID: 0403
  API: ALSA v: k6.12.73-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-LM vendor: Hewlett-Packard driver: e1000e
    v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bb class-ID: 0200
  IF: enp0s31f6 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: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
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-14:4 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 2 state: up address: N/A
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 476.94 GiB used: 423.38 GiB (88.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN720
    SDAQNTW-512G-1006 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: 10123106 temp: 44.9 C scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 476.64 GiB size: 468.09 GiB (98.21%)
    used: 423.16 GiB (90.4%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: b734715b-4f93-4672-ada3-2f059e4f5957
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 42.6 MiB (14.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
    label: N/A uuid: 0556-0437
  ID-3: /tmp/.mount_NextclpacEKJ raw-size: N/A size: 184 MiB
    used: 184 MiB (100.0%) fs: fuse.nextcloud-4.0.4-x86_64.appimage
    source: ERR-102
Swap:
  Alert: No swap data was found.
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-1:2 info: Shenzhen Rapoo 2.4G Wireless Device
    type: keyboard,mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 24ae:2015 class-ID: 0301
  Device-2: 1-7:3 info: Chicony HP HD Camera type: video driver: uvcvideo
    interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 500mA chip-ID: 04f2:b669 class-ID: 0e02 serial: <filter>
  Device-3: 1-14:4 info: Intel AX200 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0029 class-ID: e001
  Hub-2: 2-0:1 info: super-speed hub ports: 10 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 33.0 C pch: 37.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1911 libs: 437 tools: pamac,yay pm: flatpak
    pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    2: https://mirror.23m.com/manjaro/stable/$repo/$arch
    3: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
    4: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    5: https://manjaro.kurdy.org/stable/$repo/$arch
    6: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    7: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 399
  1: cpu: 8.6% command: brave pid: 5759 mem: 304.3 MiB (0.9%)
  2: cpu: 5.5% command: brave pid: 1950 mem: 430.3 MiB (1.3%)
  3: cpu: 5.1% command: brave pid: 2012 mem: 270.9 MiB (0.8%)
  4: cpu: 3.7% command: kwin_wayland pid: 1070 mem: 221.4 MiB (0.6%)
  5: cpu: 1.1% command: brave pid: 4552 mem: 305.7 MiB (0.9%)
  Memory top: 5 of 399
  1: mem: 441.9 MiB (1.3%) command: plasmashell pid: 1283 cpu: 0.3%
  2: mem: 430.3 MiB (1.3%) command: brave pid: 1950 cpu: 5.5%
  3: mem: 382.9 MiB (1.2%) command: brave pid: 5950 cpu: 1.0%
  4: mem: 325.3 MiB (1.0%) command: konsole pid: 6151 cpu: 0.2%
  5: mem: 305.7 MiB (0.9%) command: brave pid: 4552 cpu: 1.1%
Info:
  Processes: 399 Power: uptime: 1h 41m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 1 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.35 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 259 default: graphical
    tool: systemctl
  Compilers: clang: 21.1.8 gcc: 15.2.1 Shell: Bash v: 5.3.9
    running-in: konsole inxi: 3.3.40

Are you running out of RAM after some hours? Uptime only 1h41 and 12.3% in use, presumably being used mainly by the browser.

I assume of course you are watching the videos using a web browser? :wink:

Worth keeping an eye on it with a Terminal window running e.g.:

watch -n30 free -h
1 Like

Hi,

never had RAM problems. It’s completely independent how long the system is running.
There are 32 GB RAM installed, most of the time it runs with less than 20% of it.
Currently two browser instances open with seven tabs in total.

              gesamt       benutzt     frei      gemns.  Puffer/Cache verfügbar
Speicher:       30Gi       4,5Gi        23Gi       781Mi       4,0Gi        26Gi
Swap:             0B          0B          0B

I watch most videos via browser. But even locally copied files from a different source are having the issue intermittently playing it via VLC.
As i am not doing that often, it happens less than in a browser session.
Oh, and it doesn’t matter which browser i am using. Chromium, Firefox, Brave, Opera…

EDIT: I sometimes edit 4K videos or larger pictures where RAM is required. Never had a single issue there so far.

Thanks
Uwe

1 Like

How about the log

journalctl --no-pager -b-1

That gives the full log of the last boot.

Maybe use -e to get to the end directly.

1 Like

Yes, but the problem occurs before that boot which is required after the system got stuck. I don’t think there is much helpful in it.

EDIT: scrolled back and found this, followed by the dump itself:

Mär 13 15:33:48 ZBook kernel: traps: QThread[1679] general protection fault ip:7f9811a2cdfa sp:7f978b7fcfb0 error:0 in libQt6Core.so.6.10.2[22cdfa,7f9811891000+3e9000]
Mär 13 15:33:48 ZBook systemd-coredump[39465]: Process 1256 (plasmashell) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Mär 13 15:33:48 ZBook systemd[1]: Created slice Slice /system/systemd-coredump.
Mär 13 15:33:48 ZBook systemd[1]: Started Process Core Dump (PID 39465/UID 0).
Mär 13 15:33:50 ZBook systemd-coredump[39466]: [🡕] Process 1256 (plasmashell) of user 1000 dumped core.

It then came back with that:

Mär 13 15:33:50 ZBook systemd[1]: systemd-coredump@0-12289-39465_39765-0.service: Deactivated successfully.
Mär 13 15:33:50 ZBook systemd[1]: systemd-coredump@0-12289-39465_39765-0.service: Consumed 2.002s CPU time over 2.179s wall clock time, 1.2G memory peak.
Mär 13 15:33:50 ZBook systemd[973]: plasma-plasmashell.service: Main process exited, code=dumped, status=11/SEGV
Mär 13 15:33:50 ZBook systemd[973]: plasma-plasmashell.service: Failed with result 'core-dump'.
Mär 13 15:33:50 ZBook systemd[973]: plasma-plasmashell.service: Consumed 55.001s CPU time over 3h 22min 55.598s wall clock time, 790.4M memory peak.
Mär 13 15:33:51 ZBook systemd[973]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 1.
Mär 13 15:33:51 ZBook systemd[973]: Starting KDE Plasma Workspace...
Mär 13 15:33:51 ZBook systemd[973]: Started KDE Plasma Workspace.

But i am not sure if this was caused by the issue i am talking about, because the time in between was too short for a full reboot with power down.

You could try different VLC outputs to see if that makes a difference.

Tools > PreferencesOutput

Some are better than others, depending on your system, but be warned – some of these may actually cause a crash while you’re experimenting.


I use SMPlayer, which always seems lighter than VLC – The default theme looks rather ugly, but can be changed if desired.

sudo pacman -S smplayer smplayer-skins smplayer-themes

There is also KDE’s Dragon Player which is lighter still.

sudo pacman -S dragon

Dragon is a very simple player, without many settings to bother with.

If neither of these players demonstrate any improvement, it could be that the UHD Graphics 630 isn’t quite as sufficient for your needs.

I’ve tried different players. As i do not play local videos often, i think there is no evidence which works best.
However the majority of my videos are either Youtube or a different online source via browser where none of the locally installed players would help.

The graphics adapter shouldn’t be the problem playing random HD videos.
As said, it is working fine sometimes for days, even if the device was running for many hours. And the next days it occurs 2-3 times within hours.

EDIT:
Forgotten to mention something, maybe it’s important:
When the crash occurs, it happens everytime when a video tries to start. It never happened so far while the video is already running.

One more idea:

As i am not able to find anything useful in the logs, could it be that the system didn’t crash but simply darken the screen and disable the keyboard but keeps running in the background?

Sounds stupid, but i have no idea otherwise…

UNIX systems are quite convoluted in that regard. There is a pecking order when it comes to keyboard input, but most people don’t realize that.

A keyboard is a hardware device. Therefore, keyboard input is handled first and foremost by the kernel, albeit that the kernel can’t really do anything with it unless they are effectively kernel commands, i.e. the one-key System Requests — the “REISUB” thing, even though there are more System Requests than just those seven. For the kernel to interpret these one-character commands, the keyboard needs to be put in unraw mode first by way of the AltSysRqR System Request.

As such, with the above in mind, the kernel forwards the keyboard output to the console — in practice, this means the tty (terminal), even though they are actually not the same thing. The terminal understands a number of keyboard inputs of its own, but those are usually inputs by way of a control character — commonly by pressing Ctrl or Alt (or both) in combination with another key.

If the keyboard input is neither a System Request nor a terminal command, then the terminal will forward the input to the active process in the terminal. If you’re in a GUI environment, then that active process will be X11 or your Wayland compositor.

If the input still does not match the X11 server or Wayland compositor, then it gets forwarded to the active application on the desktop.

The bottom line is that if the system does not appear to respond to keyboard input, then there are several layers where the input fails to reach the system. A locked up application can effectively freeze your keyboard while your desktop environment is still running, or while the kernel is still running.

The System Requests are therefore the only way to test whether your system is still alive, because even though the keyboard may appear to be frozen, each of the System Requests will at least provide some feedback if you give it a few seconds, even if it’s only through the drive activity light.

1 Like

Thanks for your input. based on that i will try different things.

1 Like

Let’s assume for a moment the plasmashell process actually crashed (as mentioned in your log). Then a black screen will be the logical result.

In this case you can still switch/login to another tty (for example Ctrl+Alt+F4). From there you should be able to restart the plasma session.

systemctl restart --user plasma-plasmashell.service

Please note this is just a workaround for the actual bug - not a solution.

That is not the preferred method. KDE recommends… :backhand_index_pointing_down:

kquitapp6 plasmashell && kstart plasmashell

Thanks for the suggestions, will give it a try once it crashes again

As far as i see, the keyboard is not responsive, in the past i was only able to push the power button (long) to get a full system reset and then restart again (wrote it in the initial post).
Even the Shift-Lock/Num-Lock buttons (with LEDs in it) aren’t responding.

However, i will try all of the given options.

Uwe

This means that the kernel is dead. In that case, a hard reset is indeed the only option. :man_shrugging:

:sob:

Thanks for your reply.

1 Like

Have you tried updating the kernel?

1 Like

Is this going to my problem? I am using this one on stable release. Seem to be the latest one there:

6.12.73-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon, 16 Feb 2026 21:36:06 +0000

Which one should i use?
EDIT: Currently updating to 6.18.12-1 because it is shown to me as “LTS” Kernel

2 Likes

Yes, 6.18 is the latest LTS kernel, and will be supported until at least December 2027. :wink:

2 Likes