On Sun, 2004-04-18 at 09:46, Adam Cooper wrote: > Ok I found a set of scripts. Seems simple enough, installed them as per > instructions and restarted acpid. Still not working. From what I've read > about the file '/var/log/acpid' whenever an event is processed it is > logged 'before' the appropriate event processing file is called. i.e. I > close my laptop lid and > > 'button0lid\ LID\ 00000080\ 00000001' appears in '/var/log/acpid' > > then the correct action is called based on how it's beens set up in the > events files. > > But this entry is not appearing which leads me to believe that the event > is not ever being caught. > > I'll continue to google it but if anybody has any advice I'd appreciate > it. Ok. Luckily my hardware supported ACPI out of the box so I have not had to venture into this area. You have a Dell right? If so have you compiled in the dell laptop extras in the kernel? I have the toshiba ones compiled in for my machine. You *may* have to update your ACPI [ /proc/acpi/ ] `fadt` and `dsdt` files for your hardware if they were not recognized. I have no experience with this though. The fadt seems to have the computer type in it. [root@woman acpi]# strings fadt FACP JTOSHIB750 TASM Both files are in binary, and the dsdt seems to have all the information about your hardware in it as it's strings output is much longer. You'll have to ask someone else for more info, or maybe someone else will chime in who has gone through this. Sorry, This is my stop. Chris -- Software Engineering IV, McMaster University PGP Public Key: http://nesser.org/pgp-key/ 11:46:30 up 2:38, 5 users, load average: 0.36, 0.36, 0.39 Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
Attachment:
signature.asc
Description: This is a digitally signed message part
