MX Linux Forum

Posted: **Thu Jan 16, 2025 5:20 am**

Just noticed after the last 2 system update that my screen after turn off automatically failed to turn on again. I've setup my F7 to turn off the screen, it seems this is not the cause, because if I move my mouse few minutes after turning off the screen by activating F7 key, it works, but if the time is longer (probably between 10-15min, not sure, hasn't timed it), moving the mouse won't turn on the screen (it seems the OS stopped sending signal to monitor, I haven't noticed this behavior before the last 2 updates). The command I'm using for F7 key is

Code: Select all

xset dpms force off

. What am I missing? Is there another way to "wake up" Linux? Currently the only way I found is "hard shut down" (press ON button for few seconds, then the pc shuts down), which I'm pretty sure is not recommended.

Code: Select all

System:
  Kernel: 6.1.0-30-amd64 [6.1.124-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-30-amd64 root=UUID=<filter> ro quiet splash
    init=/lib/systemd/systemd
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.5_x64 Libretto January 21  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: BESSTAR TECH model: UM250 v: V1.0 serial: <superuser required>
    UEFI: American Megatrends v: 5.13 date: 01/07/2021
CPU:
  Info: model: AMD Ryzen 5 PRO 2500U w/ Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen
    level: v3 note: check built: 2017-19 process: GF 14nm family: 0x17 (23) model-id: 0x11 (17)
    stepping: 0 microcode: 0x810100B
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 384 KiB
    desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 1552 high: 1600 min/max: 1600/2000 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1418 2: 1600 3: 1600 4: 1510 5: 1600 6: 1600
    7: 1490 8: 1600 bogomips: 31937
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  Type: spec_rstack_overflow mitigation: safe RET
  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: Retpolines; IBPB: conditional; STIBP: disabled; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel
    arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 04:00.0 chip-ID: 1002:15dd class-ID: 0300
    temp: 32.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99")
  Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: Samsung C24F390 serial: <filter> built: 2021
    res: 1920x1080 hz: 60 dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5")
    ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Vega 8 Graphics (raven LLVM 15.0.6 DRM
    3.49 6.1.0-30-amd64) direct-render: Yes
Audio:
  Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 04:00.1 chip-ID: 1002:15de class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp3x v: kernel
    alternate: snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 04:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.1.0-30-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel modules: wl pcie: gen: 2 speed: 5 GT/s
    lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-2:2 chip-ID: 8087:0029
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 200f hci-v: 5.2 rev: 200f
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, audio, telephony
Drives:
  Local Storage: total: 1.38 TiB used: 636.44 GiB (45.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM048-2E7172 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 0001 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Kingston model: OM8P0S3512F-00 size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: N2.3
    scheme: GPT
Partition:
  ID-1: / raw-size: 424.2 GiB size: 416.48 GiB (98.18%) used: 49.54 GiB (11.9%) fs: ext4
    dev: /dev/sdb6 maj-min: 8:22
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 26.1 MiB (27.2%) fs: vfat
    dev: /dev/sdb2 maj-min: 8:18
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 3.91 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb5
    maj-min: 8:21
Sensors:
  System Temperatures: cpu: 31.9 C mobo: N/A gpu: amdgpu temp: 31.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2503 pm: dpkg pkgs: 2489 libs: 1284 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 6 pm: snap pkgs: 8
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://nl.mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list
    1: deb [signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
Info:
  Processes: 310 Uptime: 36m wakeups: 0 Memory: 15.32 GiB used: 3.89 GiB (25.4%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Posted: **Thu Jan 16, 2025 7:36 am**

@michaelbr ,

You may find, as I did after recent updates, that some of your Power Manager settings have been changed without any action from you. Probably worth checking: Menu > Settings > Settings Manager > Power Manager then look at both System and Display. CharlesV alerted me to this possibility and I was able to resolve my problem. Mine was not exactly like yours but it depends which settings got changed.

Cheers and good luck.

Posted: **Thu Jan 16, 2025 8:45 am**

Kester wrote: Thu Jan 16, 2025 7:36 am @michaelbr ,
Menu > Settings > Settings Manager > Power Manager then look at both System and Display. CharlesV alerted me to this possibility and I was able to resolve my

Thanks for your reply, unfortunately I don't remember my previous settings in System & Display, my current settings are in System tab Suspend, Hybernate, Hybrid Sleep all set to never, and in Display tab, Display power management is enabled, and Put to sleep and Switch off is set to 60min.

Posted: **Thu Jan 16, 2025 11:01 am**

Hi,

Display power management is enabled, and Put to sleep and Switch off is set to 60min.

Out of interest, what happens if you temporarily change those two settings to 'never', test your system and then reset them to your required settings? I'm no export and you may require assistance from someone rather more knowledgeable than I and who understands your quick system info more thoroughly but that test would do no harm and may give an interesting result.

Posted: **Sat Jan 18, 2025 2:33 am**

Kester wrote: Thu Jan 16, 2025 11:01 am Out of interest, what happens if you temporarily change those two settings to 'never', test your system and then reset them to your required settings? I'm no export and you may require assistance from someone rather more knowledgeable than I and who understands your quick system info more thoroughly but that test would do no harm and may give an interesting result.

Thanks, I'll give it a try, it may take few days to get back to you.
update: Sorry did not work, still has no signal after some time.

Posted: **Sat Jan 18, 2025 6:10 am**

Hi Michael,

I hope someone more expert than I will respond to your thread. However I have noticed one particular difference in your quick system info compared with mine which may be significant but don't change anything until you get an expert response. The final part of my qsi is:

Code: Select all

Info:
  Processes: 238 Uptime: 18m wakeups: 1 Memory: 7.62 GiB used: 1.72 GiB (22.6%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

whereas yours is:

Code: Select all

Info:
  Processes: 310 Uptime: 36m wakeups: 0 Memory: 15.32 GiB used: 3.89 GiB (25.4%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

The item I've noticed is 'Init: SysVinit' shown in my qsi and 'Init: systemd' shown in yours. This may or may not be significant but 'SysVinit' / 'systemd' issues come up quite often in this forum so may be worth investigating.

Other differences in our qsis tend to relate to system component differences.

Cheers - I hope someone comes to your aid quickly, it must be very frustrating.

Posted: **Sat Jan 18, 2025 6:38 am**

I noticed this too and have been using my mouse to wake it up. And that with display power mngmnt turned off. I just turned it on for hips and wiggles but will probably turn it off again. Coreboot sans intelme is a different beast.

Posted: **Sun Jan 19, 2025 3:56 am**

Kester wrote: Sat Jan 18, 2025 6:10 am The item I've noticed is 'Init: SysVinit' shown in my qsi and 'Init: systemd' shown in yours. This may or may not be significant but 'SysVinit' / 'systemd' issues come up quite often in this forum so may be worth investigating.

Hi Kester:
I have

Code: Select all

systemd

installed due to ZoneMinder app requires it to work.

Posted: **Sun Jan 19, 2025 11:06 am**

Hi Michael,

installed due to ZoneMinder app requires it to work.

Sorry but my expertise does not go beyond points already raised so I hope you get assistance from a real expert quickly. Good luck.

Cheers.

Posted: **Sun Jan 26, 2025 3:34 am**

It seems the solution proposed by CharlesV solved this problem

Code: Select all

https://forum.mxlinux.org/viewtopic.php?t=83530

MX Linux Forum

screen can't turn on after turned off

screen can't turn on after turned off

Re: screen can't turn on after turned off

Re: screen can't turn on after turned off

Re: screen can't turn on after turned off

Re: screen can't turn on after turned off

Re: screen can't turn on after turned off

Re: screen can't turn on after turned off

Re: screen can't turn on after turned off

Re: screen can't turn on after turned off

Re: screen can't turn on after turned off [Solved]