So crazy thing going on.
I picked up a Dell laptop with some bad pixel issues in the screen, other than that it works great. I installed DietPi 8.9.2 no problem, with the mate desktop, I planned on using rhe laptop with a monitor and keyboard a la a skinny desktop. . The problem I am running into is when I close the laptop and the screen goes out, Dietpi goes to sleep. I know someone is going to say āleave the screen openā but Iād rather not. I know how in windows to make the screen closing do nothing to the power,. But I am lost here. Do I need a different desktop than Mate or am missing something cause I canāt find any power or screen settings.
Well it didnāt seem to make a difference at first, I changed the setting on the gui in mate after the install, closed the screen and it still powered down wirh the āblankā setting. So I changed it to ādo nothingā and rebooted the laptop
Now itās closed and fully functional. Hoping this will also help cool it down, sheās running a bit hot.
Thanks again, I knew I was missing something simple.
Hi, it works OK all night but today when I connect to ethernet and install openssh laptop go to sleep when close the lid. I canāt find any option in dietpi-config > display settings to set headless server.
On DietPi it is not installed OOTB, and usually not required on headless/console systems, but good to know that it can be used for it, respectively handles it (not always wanted) when installed for specific reasons.
As a general recommendation: Try to avoid editing existing config files, but create own ones for overriding settings instead:
That way it is easier to revert, more transparent what changed and APT remains able to update the default config without interactive confirmation or having diverging logind.conf and logind.conf.dpkg-dist files.
Headless mode has only a meaning on RPi, where GPU memory allocation, framebuffer and HDMI signal stack can be completely turned off to save RAM and energy. On x86 systems there is no generic way of doing that which has any benefit, at least not to my knowledge.
I solved the problem on my own by changing the consoleblank at boot.
Verify the value used at the moment with cat /sys/module/kernel/parameters/consoleblank. The value is in seconds. The easiest way to add the parameter at boot is using the kernel command-line.
Open /etc/default/grub
Add consoleblank=600 to the GRUB_CMDLINE_LINUX_DEFAULT= which sets the timeout to 10 minutes (600 seconds).