lid.sh acpi event will not run xvattr cmd

otkaz · 06-18-2009, 01:27 AM

I use my laptop with a docking station. I didn't like the way the default lid.sh script woke my laptop screen up on mouse movement so made a new one, but I cant get one part of it to work. I want to run a xvattr command to switch my overlay to play video on my monitor. This is the script I'm using

Code:

#!/bin/sh
state=`cat /proc/acpi/button/lid/LID/state | awk '{print $2}'`
if [ "$state" = "closed" ]
then
xvattr -a XV_CRTC -v 1
radeontool light off
else
radeontool light on
xvattr -a XV_CRTC -v 0
fi

the radeontool part works fine, but it will not run the xvattr commands when I trigger the lid button. If I launch the script manually with sh /etc/acpi/lid.sh it works though??? Is there some kind of limit on what commands can be run with acpi events?

TB0ne · 06-18-2009, 07:40 PM

Quote:

Originally Posted by otkaz

I use my laptop with a docking station. I didn't like the way the default lid.sh script woke my laptop screen up on mouse movement so made a new one, but I cant get one part of it to work. I want to run a xvattr command to switch my overlay to play video on my monitor. This is the script I'm using

Code:

#!/bin/sh
state=`cat /proc/acpi/button/lid/LID/state | awk '{print $2}'`
if [ "$state" = "closed" ]
then
xvattr -a XV_CRTC -v 1
radeontool light off
else
radeontool light on
xvattr -a XV_CRTC -v 0
fi

the radeontool part works fine, but it will not run the xvattr commands when I trigger the lid button. If I launch the script manually with sh /etc/acpi/lid.sh it works though??? Is there some kind of limit on what commands can be run with acpi events?

Try putting the fully qualified path in before the commands, like "/usr/bin/xvattr", or something like that.

otkaz · 06-19-2009, 02:55 PM

Quote:

Originally Posted by TB0ne

Try putting the fully qualified path in before the commands, like "/usr/bin/xvattr", or something like that.

tried it but no luck will only run the radeontool command but not xvattr...