Hello,
I applied the LMDE Pack four two days ago.
Since I found the computer wake up in the morning (it normally suspend after one hour), I wondered about the suspend.
So I try to force the computer to suspend (via menu shutdown). It do the process. I even hear the fan and the hard disk stop. But as soon as it has stopped it wake up again.
in the log, I can't see what has requested the computer to wake up, but maybe I don't know the proper log to look in.
Anyway, that is not very convenient…
I tried the same with the Hibernate option and face exactly the same problem. It is hibernating, but resume immediately (full boot of the hard).
Can anybody help me?
Thanks
suspend restart immediatly…
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
LMDE 2 has reached end of support as of 1-1-2019
suspend restart immediatly…
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: suspend restart immediatly…
Hi,
I have checked and made test.
When I select the kernel 2.6.39 in grub, instead of 3.0.2, suspend and hibernate works well. Thus I guess Kernel or module incompatibility with hardware, but I don't know how to solve that.
By the way, one questions is… is it really important to follow the "latest" kernel? what can really be expected by changing kernel? better hardware performance for very new things, or other important point?
Thanks and regards
I have checked and made test.
When I select the kernel 2.6.39 in grub, instead of 3.0.2, suspend and hibernate works well. Thus I guess Kernel or module incompatibility with hardware, but I don't know how to solve that.
By the way, one questions is… is it really important to follow the "latest" kernel? what can really be expected by changing kernel? better hardware performance for very new things, or other important point?
Thanks and regards
Re: suspend restart immediatly…
You could compare the output of lsmod if you think it's a module.FDF wrote:When I select the kernel 2.6.39 in grub, instead of 3.0.2, suspend and hibernate works well. Thus I guess Kernel or module incompatibility with hardware, but I don't know how to solve that.
http://wiki.debian.org/KernelFAQBy the way, one questions is… is it really important to follow the "latest" kernel? what can really be expected by changing kernel? better hardware performance for very new things, or other important point?
Re: suspend restart immediatly…
Same problem here. Immediatly restarting after suspend or hibernate.
Any advice, how to collect more info about this behaviour?
Any advice, how to collect more info about this behaviour?
Re: suspend restart immediatly…
Hi, I have never been further, and stick with the old kernel…
Re: suspend restart immediatly…
maybe a USB device, in my case it was my mouse that made suspend restart. do a:
you will have maybe USB0 USB1 USB2 and USB3 in enabled state. Do a:
to disable USB0, then suspend to see if it restarts immediately. if yes, disable another USB.
when you find the right USB, put the echo command in /etc/rc.local
To know what was the device, I had to check the pci string from wakeup in the dmesg log, for instance
Hope this helps!
Code: Select all
cat /proc/acpi/wakeup
Code: Select all
echo USB0 > /proc/acpi/wakeup
when you find the right USB, put the echo command in /etc/rc.local
To know what was the device, I had to check the pci string from wakeup in the dmesg log, for instance
Code: Select all
dmesg | grep 0000:00:04.0
Re: suspend restart immediatly…
Before I do anything I get
I don't have the user rights to do a
and that doesn't work either:
But that works:
and leads to a disabled USB0 wakeup trigger (line six from top):
The good news is: That works. I can use hibernate and it will but the system to sleep.
The bad news is: new problem. It online works once. If I did a hibernate before and if I do it a second time, it will not really suspend. Going down yes,
but the blower continue running and I can't reactivate from the power button.
Code: Select all
cat /proc/acpi/wakeup
HUB0 S5 *disabled pci:0000:00:09.0
XVR0 S5 *disabled pci:0000:00:0e.0
XVR1 S5 *disabled pci:0000:00:0d.0
XVR2 S5 *disabled pci:0000:00:0c.0
XVR3 S5 *disabled pci:0000:00:0b.0
USB0 S4 *enabled pci:0000:00:02.0
USB2 S4 *enabled pci:0000:00:02.1
MMAC S5 *disabled pci:0000:00:0a.0
MMCI S5 *disabled
UAR1 S5 *disabled pnp:00:07
PS2K S4 *enabled pnp:00:09
Code: Select all
echo USB0 > /proc/acpi/wakeup
Code: Select all
sudo echo USB0 > /proc/acpi/wakeup
Code: Select all
echo USB0 > wakeup
sudo cp wakeup /proc/acpi/wakeup
Code: Select all
HUB0 S5 *disabled pci:0000:00:09.0
XVR0 S5 *disabled pci:0000:00:0e.0
XVR1 S5 *disabled pci:0000:00:0d.0
XVR2 S5 *disabled pci:0000:00:0c.0
XVR3 S5 *disabled pci:0000:00:0b.0
USB0 S4 *disabled pci:0000:00:02.0
USB2 S4 *enabled pci:0000:00:02.1
MMAC S5 *disabled pci:0000:00:0a.0
MMCI S5 *disabled
UAR1 S5 *disabled pnp:00:07
PS2K S4 *enabled pnp:00:09
The bad news is: new problem. It online works once. If I did a hibernate before and if I do it a second time, it will not really suspend. Going down yes,
but the blower continue running and I can't reactivate from the power button.