So I got a triple (!) install on two Nmve ssd’s. One windows on separate ssd and Debian Bookworm KDE and GNOME flavours on the other on each separate partition. windows for gaming only with a separate display to a Nvidia RTX GPU. Both the Debian partitions running on separate display from internal Intel GPU. All controlled by GRUB Bootloader. BUT: I had to install “Nvidia-Driver” to both KDE and GNOME to control the other screen to keep it asleep during Linux sessions.
I am not sure whether this may be the cause or something else that lead to my problem, which is as follows: When leaving a session, ordering either flavour to “suspend”, computer will go into sleep but then wake right up again, computer stays awake with fans and pump running. I have tried to change behaviour in system settings and updated uefi/bios in the faint hope it would help but this is persistent - only full shutdown will keep the thing down. I would like to leave the computer knowing it eventually goes to sleep and not come back to a fully awake system and LogIn screen alive. I have been searching the interweb and inquired with chatgpt without solution. Anyone have an idea about where I should start digging, maybe a nudge in the right direction?
Some event is waking it up… possibly
- a cron job
- the mouse if usb or wifi
- try unplugging that extra screen
- try shutting the lid or hold the button down
If you can find the wakeup culprit there will be a way to break the link with software settings.
and
Look at the logfiles
Look at Settings → Power
Yup. Mouse, Logitech wireless with USB with dongle. Pulled the thing out and no more sleep problems :). Damn! I didn’t even think aboot that. Problem is; I now have to unplug mouse until I find out how I can avoid that… Research goes on. Still open for advice…
Have a look at the file login.conf
There may be suspend settings that you can fiddle.
Here goes: “grep . /sys/bus/usb/devices/*/power/wakeup” which had me identify “/sys/bus/usb/devices/1-6.4/power/wakeup:enabled” as the culprit. Then: "cat /sys/bus/usb/devices/1-6.4/idVendor
“cat /sys/bus/usb/devices/1-6.4/idProduct”
Then !“echo “disabled” | sudo tee /sys/bus/usb/devices/1-6.4/power/wakeup
echo “disabled” | sudo tee /sys/bus/usb/devices/1-6.4/power/wakeup”. Then "suspend"and systen went to sleep without more wake triggering.Now have to wake computer with keyboard.
@audun_s ,
Brilliant, but I thought /sys was not permanent
Have got tried a reboot yet?
Yes, tried reboot on both and it works consistently. Then, before claiming any brilliance here, even if that comment was taken to heart :). I must confess to have being a bit of a cheat; I have been using ChatGpt to help with Linux matter, questions and solutions to problems I mostly created all by myself. ChatGpt is not the oracle and well of wisdom many claim, but I have found it helpful. With careful questioning and a bit of fumble (on my part), most of the time it has eventually led me onto the right path. I do not claim to be a “techie” but still very much a newbie except I now understand a bit more of the Linux architecture and haven’t caused all these frequent and self made disasters I once were prone to fumble my way into. There is a World Wide Well of information about Linux out there and some is well worth relying on (like here) and some to stay well clear of. ChatGpt suggest bash script and clues for what to look for and always reveal source when prompted to. Otherwise I come running to this here pages when incomprehension fully takes hold.
I use it sometimes. That is not cheating. GPT works like reading the man pages only with some search ability.
Have you tried tgpt a terminal gpt program … It is good for a quick question… ChatGPT is better for a conversation.
It surprises me that your changes are permanent… things I read suggest otherwise. But it works for you so well done.