Dear all
I recently upgraded from Dapper (which is excellent) to Feisty, via Edgy. When I got Feisty working, I found that the KDE screen would be locked every eight seconds or so. Thinking there must have been problems with the upgrade (it wasn't trouble-free) I obtained a Feisty disc and did a clean install. Unfortunately this was worse: the boot process is repeatedly interrupted by the machine going to sleep for no reason, and powering back up lets the machine accomplish a bit more of the process, before going to sleep again!
A colleague of mine (more knowledgable than I) found that a sleep event was being recorded in /var/log/acpid. He renamed /etc/acpi/sleep.sh which at least allowed the boot process to complete properly. However I am back to the KDE screen locking every so many seconds. A sample snippet of acpid is thus:
First, this didn't ever happen in Windows, nor in Dapper - it just happens in Feisty. Also I should point out that my colleague has tried giving me a boot-mode featuring a keyword of "noacpi", which did not make a difference. Lastly, if I boot into a recovery (single-user) mode, the problem does not happen (even if I boot KDE, from where I type, via kdm). I have tried to turn off everything in the BIOS to do with power management to no avail.
I have a much-loved Dell Latitude L400 laptop, 256Mb RAM, 800MHz PIII processor. It has a power button, and a lid closed detection button. Any ideas?
halfer
I recently upgraded from Dapper (which is excellent) to Feisty, via Edgy. When I got Feisty working, I found that the KDE screen would be locked every eight seconds or so. Thinking there must have been problems with the upgrade (it wasn't trouble-free) I obtained a Feisty disc and did a clean install. Unfortunately this was worse: the boot process is repeatedly interrupted by the machine going to sleep for no reason, and powering back up lets the machine accomplish a bit more of the process, before going to sleep again!
A colleague of mine (more knowledgable than I) found that a sleep event was being recorded in /var/log/acpid. He renamed /etc/acpi/sleep.sh which at least allowed the boot process to complete properly. However I am back to the KDE screen locking every so many seconds. A sample snippet of acpid is thus:
Code:
[Wed Jun 20 21:58:50 2007] BEGIN HANDLER MESSAGES /bin/sh: /etc/acpi/sleep.sh: not found [Wed Jun 20 21:58:50 2007] END HANDLER MESSAGES [Wed Jun 20 21:58:50 2007] action exited with status 127 [Wed Jun 20 21:58:50 2007] completed event "button/sleep SBTN 00000080 00000032" [Wed Jun 20 21:58:50 2007] received event "button/sleep SBTN 00000080 00000033" [Wed Jun 20 21:58:50 2007] notifying client 4296[107:114] [Wed Jun 20 21:58:50 2007] notifying client 4774[0:0] [Wed Jun 20 21:58:50 2007] executing action "/etc/acpi/sleep.sh" [Wed Jun 20 21:58:50 2007] BEGIN HANDLER MESSAGES /bin/sh: /etc/acpi/sleep.sh: not found [Wed Jun 20 21:58:50 2007] END HANDLER MESSAGES [Wed Jun 20 21:58:50 2007] action exited with status 127 [Wed Jun 20 21:58:50 2007] completed event "button/sleep SBTN 00000080 00000033" [Wed Jun 20 21:58:50 2007] received event "button/sleep SBTN 00000080 00000034" [Wed Jun 20 21:58:50 2007] notifying client 4296[107:114] [Wed Jun 20 21:58:50 2007] notifying client 4774[0:0] [Wed Jun 20 21:58:50 2007] executing action "/etc/acpi/sleep.sh" [Wed Jun 20 21:58:50 2007] BEGIN HANDLER MESSAGES /bin/sh: /etc/acpi/sleep.sh: not found [Wed Jun 20 21:58:50 2007] END HANDLER MESSAGES [Wed Jun 20 21:58:50 2007] action exited with status 127 [Wed Jun 20 21:58:50 2007] completed event "button/sleep SBTN 00000080 00000034" [Wed Jun 20 21:59:08 2007] client connected from 4774[0:0] [Wed Jun 20 21:59:08 2007] 1 client rule loaded [Wed Jun 20 21:59:18 2007] exiting
I have a much-loved Dell Latitude L400 laptop, 256Mb RAM, 800MHz PIII processor. It has a power button, and a lid closed detection button. Any ideas?
halfer
Comment