You are not logged in.
After installing acpid I am experiencing some weird behavior when closing/opening the lid on my Thinkpad R61 8918. Before installing the daemon, the screen turned off, when the lid was almost fully closed and it turned on again when I opened the lid.
Wth acppid installed It still turns off as expected, but after turning on, it goes off again for a second or two, and then it mostly turns on, but sometimes it keeps black. If the screen keeps turned off I have to turn the pc off with the power button, as it does not seem to be able to wake back up.
How can I fix this?
I still want the acpid daemon so I can use the special keyboard keys and change cpufreq guvernor when going from battery to ac and vice versa.
If that can be achived in some other way, I can just remove the acpid package again.
Here is my /etc/rc.conf
MOD_AUTOLOAD="yes"
MODULES=(e1000e iwl4965 acpi-cpufreq cpufreq_ondemand cpufreq_powersave snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore thermal thinkpad_acpi)
DAEMONS=(syslog-ng !network hal cpufreq @networkmanager @netfs @crond @alsa slim)
Offline
We also need to see /etc/acpi/handler.sh and any event located in /etc/acpi/events.
Arch - It's something refreshing
Offline
I have not edited handler.sh or anything in the events folder, so the files are plain vanilla.
The only file in the events folder is 'anything':
# Pass all events to our one handler script
event=.*
action=/etc/acpi/handler.sh %e
And the default handler.sh:
#!/bin/sh
# Default acpi script that takes an entry for all actions
# NOTE: This is a 2.6-centric script. If you use 2.4.x, you'll have to
# modify it to not use /sys
minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
set $*
case "$1" in
button/power)
#echo "PowerButton pressed!">/dev/tty5
case "$2" in
PWRF) logger "PowerButton pressed: $2" ;;
*) logger "ACPI action undefined: $2" ;;
esac
;;
button/sleep)
case "$2" in
SLPB) echo -n mem >/sys/power/state ;;
*) logger "ACPI action undefined: $2" ;;
esac
;;
ac_adapter)
case "$2" in
AC)
case "$4" in
00000000)
echo -n $minspeed >$setspeed
#/etc/laptop-mode/laptop-mode start
;;
00000001)
echo -n $maxspeed >$setspeed
#/etc/laptop-mode/laptop-mode stop
;;
esac
;;
*) logger "ACPI action undefined: $2" ;;
esac
;;
battery)
case "$2" in
BAT0)
case "$4" in
00000000) #echo "offline" >/dev/tty5
;;
00000001) #echo "online" >/dev/tty5
;;
esac
;;
CPU0)
;;
*) logger "ACPI action undefined: $2" ;;
esac
;;
button/lid)
#echo "LID switched!">/dev/tty5
;;
*)
logger "ACPI group/action undefined: $1 / $2"
;;
esac
And this is the output of acpi_listen, after closing and then opening the lid:
button/lid LID 00000080 00000001
video VID1 00000080 00000000
button/lid LID 00000080 00000002
Shouldn't it trigger the video event twice; one for switcing off, and one for switching on?
Last edited by fifafrazer (2008-08-25 20:47:31)
Offline
Could the problem be related to the hald daemon, that does something stupid with the screen instead of letting the bios do the job?
How can I check that?
Offline