salsa
1 August 2023 17:30
1
Hello,
Recently installed this build and really like it so far.
Having a persistent issue with the screen blanking (or going into hibernation, turning off my monitor) at about 15 minutes. I went to Power Management and turned off all of those so I am unsure where else this could be originating.
System:
Kernel: 6.4.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=649300bf-7319-4910-9544-11aa06409d07 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=ff0962c3-da46-4358-a8d0-dd0f51283504 loglevel=3 ibt=off
Desktop: LXQt v: 1.3.0 tk: Qt v: 5.15.10 info: cairo-dock, lxqt-panel
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Mini-pc System: LENOVO product: 11AMS0BX00 v: ThinkCentre M90n-1
serial: <superuser required> Chassis: type: 35 serial: <superuser required>
Mobo: LENOVO model: 314D v: NOK serial: <superuser required> UEFI: LENOVO
v: M2AKT2EA date: 09/17/2021
CPU:
Info: model: Intel Celeron 4205U bits: 64 type: MCP arch: Comet/Whiskey Lake
note: check level: v2 built: 2018 process: Intel 14nm family: 6
model-id: 0x8E (142) stepping: 0xC (12) microcode: 0xF6
Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 2 MiB
desc: 1x2 MiB
Speed (MHz): avg: 900 min/max: 400/1800 scaling: driver: intel_pstate
governor: powersave cores: 1: 900 2: 900 bogomips: 7200
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Whiskey Lake-U GT1 [UHD Graphics 610] vendor: Lenovo
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: DP-2 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0
chip-ID: 8086:3ea1 class-ID: 0300
Device-2: USB C Video Adaptor driver: N/A type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:4 chip-ID: 25a4:9311
class-ID: 1100 serial: <filter>
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: DP-2 model: Samsung serial: <filter> built: 2020 res: 1920x1080
hz: 60 dpi: 40 gamma: 1.2 size: 1210x680mm (47.64x26.77")
diag: 801mm (31.5") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL Message: Unable to show GL data. Required tool glxinfo
missing.
Audio:
Device-1: Intel Cannon Point-LP High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl
bus-ID: 00:1f.3 chip-ID: 8086:9dc8 class-ID: 0403
API: ALSA v: k6.4.7-zen1-1-zen status: kernel-api tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 0.3.76 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 Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:9df0 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10:5
chip-ID: 8087:0aaa class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
Local Storage: total: 119.24 GiB used: 9.61 GiB (8.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZALQ128HCHQ-00BL1 size: 119.24 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 6L1QFXM7 temp: 21.9 C scheme: GPT
Partition:
ID-1: / raw-size: 110.81 GiB size: 110.81 GiB (100.00%)
used: 9.61 GiB (8.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 110.81 GiB size: 110.81 GiB (100.00%)
used: 9.61 GiB (8.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 110.81 GiB size: 110.81 GiB (100.00%)
used: 9.61 GiB (8.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 110.81 GiB size: 110.81 GiB (100.00%)
used: 9.61 GiB (8.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 3.7 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 8.13 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 29.0 C pch: 28.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 201 Uptime: 1m wakeups: 0 Memory: total: 4 GiB available: 3.7 GiB
used: 2.04 GiB (55.2%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 13.1.1 Packages: pm: pacman pkgs: 1319
libs: 365 tools: octopi,paru Shell: Bash v: 5.1.16 running-in: qterminal
inxi: 3.3.28
Garuda (2.6.16-1):
System install date: 2023-07-31
Last full system update: 2023-07-31
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: No/Undetected
Failed units:
I appreciate any assistance. Thank you.
SGS
1 August 2023 17:48
2
Welcome
Check with htop your memory use,
and temperature.
journalctl -b -1 | grep -i hibernation
All in all, I’m glad it runs on such a machine at all.
2 Likes
salsa
1 August 2023 18:02
3
It runs pretty well aside from this although I don't do much heavier than DOSBox emulation.
Here is the output from the log, I also checked if other Hibernation/Sleeps were running. htop showed 1.2gb ram consumption.
journalctl -b -1 | grep -i hibernation
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000fffff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x7bc1e000-0x7bc1efff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x7bc2c000-0x7bc2cfff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x84a54000-0x84a9cfff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x86dcb000-0x86dcbfff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x8935b000-0x8b33dfff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x8b33e000-0x8b3f6fff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x8b3f7000-0x8b491fff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x8b492000-0x8bd0efff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x8bd10000-0x8f7fffff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0x8f800000-0xfdffffff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0xfe000000-0xfe010fff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0xfe011000-0xfebfffff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0xfed04000-0xfedfffff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Jul 31 21:41:02 lu-11ams0bx00 kernel: PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xffffffff]
> ╭─lu@lu in ~ took 17s
╰─λ sudo systemctl status sleep.target suspend.target hibernate.target hybrid-sleep.target
○ sleep.target - Sleep
Loaded: loaded (/usr/lib/systemd/system/sleep.target; static)
Active: inactive (dead)
Docs: man:systemd.special(7)
○ suspend.target - Suspend
Loaded: loaded (/usr/lib/systemd/system/suspend.target; static)
Active: inactive (dead)
Docs: man:systemd.special(7)
○ hibernate.target - System Hibernation
Loaded: loaded (/usr/lib/systemd/system/hibernate.target; static)
Active: inactive (dead)
Docs: man:systemd.special(7)
○ hybrid-sleep.target - Hybrid Suspend+Hibernate
Loaded: loaded (/usr/lib/systemd/system/hybrid-sleep.target; static)
Active: inactive (dead)
Docs: man:systemd.special(7)
salsa
1 August 2023 20:47
4
Here's the output as it happens if that offers any insight:
Aug 01 16:28:56 lu-11ams0bx00 dbus-daemon[481]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Aug 01 16:28:56 lu-11ams0bx00 sudo[4643]: lu : TTY=pts/0 ; PWD=/home/lu ; USER=root ; COMMAND=/usr/bin/true
Aug 01 16:28:56 lu-11ams0bx00 sudo[4643]: pam_unix(sudo:session): session opened for user root(uid=0) by lu(uid=1000)
Aug 01 16:28:56 lu-11ams0bx00 sudo[4643]: pam_unix(sudo:session): session closed for user root
Aug 01 16:29:26 lu-11ams0bx00 dbus-daemon[481]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.105' (uid=0 pid=4690 comm="sudo journalctl -f")
Aug 01 16:29:26 lu-11ams0bx00 dbus-daemon[481]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Aug 01 16:29:26 lu-11ams0bx00 sudo[4690]: lu : TTY=pts/0 ; PWD=/home/lu ; USER=root ; COMMAND=/usr/bin/journalctl -f
Aug 01 16:29:26 lu-11ams0bx00 sudo[4690]: pam_unix(sudo:session): session opened for user root(uid=0) by lu(uid=1000)
Aug 01 16:41:06 lu-11ams0bx00 systemd[1]: Starting Update locate database...
Aug 01 16:41:06 lu-11ams0bx00 systemd[1]: updatedb.service: Deactivated successfully.
Aug 01 16:41:06 lu-11ams0bx00 systemd[1]: Finished Update locate database.
Please post always your terminal in- and output as text like
I have edited your post.
It appears LXQt is currently allowing DPMS to override the user-specified settings in LXQt Power Management, the reason given being "lxqt-powermanagement should not silently touch other components settings". See the discussion here:
opened 03:28AM - 19 Jul 23 UTC
Default DPMS timeouts are in conflict with `lxqt-powermanagement`.
Users migh… t have found various ways of avoiding this problem (like I did), and once the issue was avoided, it might have been forgotten. But, IMHO, it's a serious issue under X11.
Its fix may be as simple as this (inside `IdlenessWatcher::setup()`):
```c++
// override DPMS settings
if (QGuiApplication::platformName() == QStringLiteral("xcb")) {
xcb_dpms_set_timeouts(QX11Info::connection(), 0, 0, 0);
}
```
This solution worked here. Now `xset q` shows
```
DPMS (Display Power Management Signaling):
Standby: 0 Suspend: 0 Off: 0
DPMS is Enabled
Monitor is On
```
However, not being an expert in cmake, I had a hard time to find XCB's DPMS module with it. In the end, I edited what I found in screengrab.
@luis-pereira, @palinek, @yan12125
Am I missing something when I think that this issue is serious? And do you know of a simpler way of finding DPMS? I mean simpler than what's done in screengrab?
It looks like they are fixing this behavior so DPMS will be overridden when the "idleness watcher" is enabled, which seems reasonable to me. The issue is still open at the moment however, so in the meanwhile you may wish to employ the workaround mentioned in the issue (disable DPMS in a startup script).
A simple way to do this would be to make an .xprofile file, which SDDM will source when starting X11.
micro ~/.xprofile
Add to the file:
xset s off -dpms
Save and exit.
I hope that helps, welcome to the community @salsa .
4 Likes
salsa
2 August 2023 04:14
8
Yep, looks like that got it. Thank you!
Gavin
2 August 2023 09:31
9
if by any chance it all starts blanking again after a reboot, what i did was just add caffeiine-ng and add a couple of apps to preferences. No more blanking. Its in aur, so can be downloaded and installed locally if need be.
Just a brief correction: ~/.xprofile does not need to be executable, I took that part out of the post above. I'm not sure why I added that; it was late and must have been typing on auto-pilot.
2 Likes
system
4 August 2023 10:44
11
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
