Talk:How to configure acpid - Revision history

Kevmitch at 08:53, 21 January 2008

2008-01-21T08:53:08Z

Kevmitch: /* Which event is which */

2008-01-21T08:25:34Z

‎Which event is which

Kevmitch: /* Which event is which */

2008-01-21T08:24:41Z

‎Which event is which

Zubro: /* Lock screen on wake */ test fix

2006-05-25T18:40:11Z

‎Lock screen on wake: test fix

Zubro: Set ATI driver to run on economy mode when running on battery

2006-05-21T15:29:29Z

Set ATI driver to run on economy mode when running on battery

Zubro: Lock screen on wake

2006-05-21T15:25:08Z

Lock screen on wake

Papi at 17:29, 20 March 2006

2006-03-20T17:29:15Z

Papi at 17:28, 20 March 2006

2006-03-20T17:28:31Z

Papi at 17:24, 20 March 2006

2006-03-20T17:24:46Z

Wyrfel at 00:57, 10 March 2006

2006-03-10T00:57:55Z

@@ Line 148: / Line 148: @@
 However, let's try discovering it in a more reasonable approach: do a
-{{cmdroot|tail -f /var/log/acpid}} ({{cmdroot|tail -f /var/log/messages}} with newer versions of acpid). Then press the {{key|Fn}}{{key|F4}}
+{{cmdroot|tar -f /var/log/acpid}}. Then press the {{key|Fn}}{{key|F4}}
 combination and see what happens in the terminal. Look for lines that
 say "recieved event" and then look at the event strings there. Do they

@@ Line 148: / Line 148: @@
 However, let's try discovering it in a more reasonable approach: do a
-{{cmdroot|tail -f /var/log/acpid}}({{cmdroot|tail -f /var/log/messages}} with newer versions of acpid). Then press the {{key|Fn}}{{key|F4}}
+{{cmdroot|tail -f /var/log/acpid}} ({{cmdroot|tail -f /var/log/messages}} with newer versions of acpid). Then press the {{key|Fn}}{{key|F4}}
 combination and see what happens in the terminal. Look for lines that
 say "recieved event" and then look at the event strings there. Do they

@@ Line 148: / Line 148: @@
 However, let's try discovering it in a more reasonable approach: do a
-{{cmdroot|tar -f /var/log/acpid}}. Then press the {{key|Fn}}{{key|F4}}
+{{cmdroot|tail -f /var/log/acpid}}({{cmdroot|tail -f /var/log/messages}} with newer versions of acpid). Then press the {{key|Fn}}{{key|F4}}
 combination and see what happens in the terminal. Look for lines that
 say "recieved event" and then look at the event strings there. Do they

@@ Line 238: / Line 238: @@
   if [ ! -z "$XUSER" ] ; then
-          if ! xscreensaver-command -time|grep "screen locked" ; then
+          if ! su -c "DISPLAY=:0 /usr/bin/xscreensaver-command -time|grep 'screen locked'" - XUSER ; then
                   su -c "DISPLAY=:0 /usr/bin/xscreensaver-command -lock" - $XUSER >/tmp/lid.log 2>&1
           fi
@@ Line 276: / Line 276: @@
   if [ ! -z "$XUSER" ] ; then
-          if ! xscreensaver-command -time|grep "screen locked" ; then
+          if ! su -c "DISPLAY=:0 /usr/bin/xscreensaver-command -time|grep 'screen locked'" - XUSER ; then
                   su -c "DISPLAY=:0 /usr/bin/xscreensaver-command -lock" - $XUSER >/tmp/lid.log 2>&1
           fi

← Older revision		Revision as of 15:29, 21 May 2006
Line 290:		Line 290:

	[[User:Zubro\|Zubro]] 17:25, 21 May 2006 (CEST)		[[User:Zubro\|Zubro]] 17:25, 21 May 2006 (CEST)
		+
		+	== Set ATI driver to run on economy mode when running on battery ==
		+
		+	Here is the /etc/acpi/actions/lm_ac_adapter.sh I use on a Debian to lower the frequency of the ATI chip when my AC adapter is unplugged :
		+
		+	#!/bin/bash
		+
		+	# ac on/offline event handler
		+
		+	test -f /usr/sbin/laptop_mode && /usr/sbin/laptop_mode auto
		+
		+	# if not launched through a ac_adapter event do nothing
		+	echo "$1" \| grep -qv "ac_adapter" && exit 0
		+
		+	# get user running X
		+	XUSER=`ps aux\|grep -w x\\-session-manager\|cut -d' ' -f 1\|head -n1`
		+
		+	# if X not found, quit
		+	test -z "$XUSER" && exit 0
		+
		+	# set GPU speed
		+	if [ "$4" -eq 0 ] ; then
		+	# AC adapter is off-line
		+
		+	su -c "DISPLAY=:0 /usr/X11R6/bin/aticonfig --set-powerstate=1 --effective=now" - $XUSER
		+
		+	elif [ "$4" -eq 1 ] ; then
		+	# AC adapter is on-line
		+
		+	su -c "DISPLAY=:0 /usr/X11R6/bin/aticonfig --set-powerstate=3 --effective=now" - $XUSER
		+	fi
		+	[[User:Zubro\|Zubro]] 17:29, 21 May 2006 (CEST)

← Older revision		Revision as of 15:25, 21 May 2006
Line 231:		Line 231:
	Steve		Steve
	--[[User:Papi\|Papi]] 18:29, 20 March 2006 (CET)		--[[User:Papi\|Papi]] 18:29, 20 March 2006 (CET)
		+
		+	== Lock screen on wake ==
		+
		+	To lock the screen (in Gnome) when I open the lid, I've added these lines in my /etc/acpi/actions/lm_lid.sh script :
		+	XUSER=`ps aux\|grep -w x\\-session-manager\|cut -d' ' -f 1\|head -n1`
		+
		+	if [ ! -z "$XUSER" ] ; then
		+	if ! xscreensaver-command -time\|grep "screen locked" ; then
		+	su -c "DISPLAY=:0 /usr/bin/xscreensaver-command -lock" - $XUSER >/tmp/lid.log 2>&1
		+	fi
		+	fi
		+
		+	For information, here is my complete /etc/acpi/actions/lm_lid.sh file, on a Debian, with laptop mode :
		+	#!/bin/bash
		+
		+	# lid button pressed/released event handler
		+
		+	# if launched through a lid event and lid is open, do nothing
		+	echo "$1" \| grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0
		+
		+	# remove USB 1.1 driver
		+	rmmod uhci_hcd
		+
		+	# sync filesystem and clock
		+	sync
		+	/sbin/hwclock --systohc
		+
		+	# switch to console
		+	FGCONSOLE=`fgconsole`
		+	chvt 6
		+	/usr/sbin/radeontool light off
		+
		+	# go to sleep
		+	sleep 5 && echo -n "mem" > /sys/power/state
		+
		+	# readjust the clock (it might be off a bit after suspend)
		+	/sbin/hwclock --adjust
		+	/sbin/hwclock --hctosys
		+
		+	# reload USB 1.1 driver
		+	modprobe uhci_hcd
		+
		+	XUSER=`ps aux\|grep -w x\\-session-manager\|cut -d' ' -f 1\|head -n1`
		+
		+	if [ ! -z "$XUSER" ] ; then
		+	if ! xscreensaver-command -time\|grep "screen locked" ; then
		+	su -c "DISPLAY=:0 /usr/bin/xscreensaver-command -lock" - $XUSER >/tmp/lid.log 2>&1
		+	fi
		+	fi
		+
		+	# turn on the backlight and switch back to X
		+	/usr/bin/radeontool light on
		+	chvt $FGCONSOLE
		+
		+	test -f /usr/sbin/laptop_mode \|\| exit 0
		+
		+	/usr/sbin/laptop_mode auto
		+
		+	[[User:Zubro\|Zubro]] 17:25, 21 May 2006 (CEST)

← Older revision		Revision as of 17:29, 20 March 2006
Line 230:		Line 230:

	Steve		Steve
		+	--[[User:Papi\|Papi]] 18:29, 20 March 2006 (CET)

← Older revision		Revision as of 17:28, 20 March 2006
Line 228:		Line 228:

	Whatever I try, I cannot get the Fn keys to do what they're supposed to in gentoo. Closest I get is pressing FnF3, the screen blanks for a second and turns back on. FnF4 shows no result, nor do the rest. This is disheartening! ....		Whatever I try, I cannot get the Fn keys to do what they're supposed to in gentoo. Closest I get is pressing FnF3, the screen blanks for a second and turns back on. FnF4 shows no result, nor do the rest. This is disheartening! ....
		+
		+	Steve

← Older revision		Revision as of 17:24, 20 March 2006
Line 224:		Line 224:
	[[User:Wyrfel\|Wyrfel]] 01:57, 10 March 2006 (CET)		[[User:Wyrfel\|Wyrfel]] 01:57, 10 March 2006 (CET)
	----		----
		+
		+	This ibm_acpi business and the way it's presented here is extremely confusing. The multitude of commands and methods scattered all around really make it difficult to follow. The lack of any working action scripts makes it all even worse. I realize that distros are different and people have different installations, but can't there be 1 generic tell-all method that ought to work regardless of distro used?
		+
		+	Whatever I try, I cannot get the Fn keys to do what they're supposed to in gentoo. Closest I get is pressing FnF3, the screen blanks for a second and turns back on. FnF4 shows no result, nor do the rest. This is disheartening! ....

← Older revision		Revision as of 00:57, 10 March 2006
Line 218:		Line 218:

	papi		papi
		+
		+	----
		+	Hi, the only repository we have is [[:Category:Scripts\|the Scripts category]]. I know it's not sufficient for your issues. In former times, everyone had to install ibm-acpi from the package which included good default scripts. since ibm-acpi is in the kernel now, the scripts from the package are just a bit too far away for most users to get the path to them. Maybe we should add the missing default scripts as single pages and categorize them under the Scripts category for a start.
		+
		+	[[User:Wyrfel\|Wyrfel]] 01:57, 10 March 2006 (CET)
		+	----