From: Matthew Smith on 13 Oct 2009 01:30 Quoth green at 12/10/09 11:10... > Perhaps you need to look at acpid(8). Find out what the initscript is using, > and try running acpid manually with some of --debug, --foreground, --logevents. Well, that's interesting: vaio:/etc/init.d# acpi_listen acpi_listen: can't open socket /var/run/acpid.socket: No such file or directory vaio:/etc/init.d# acpid --debug --foreground --logevents acpid: can't open /proc/acpi/event: No such file or directory vaio:/etc/init.d# ps -efa |grep acpi root 84 2 0 14:46 ? 00:00:00 [kacpid] root 85 2 0 14:46 ? 00:00:00 [kacpi_notify] 108 2943 2919 0 14:47 ? 00:00:00 /usr/lib/hal/hald-addon-acpi Having done a search on my error messages, it appears that /proc/acpi/event is a deprecated kernel option, but may cause issues if turned off. Wonder if I need to get the source & config of this kernel and see if that is set. Cheers M -- Matthew Smith Smiffytech - Technology Consulting & Web Application Development Business: http://www.smiffytech.com/ Blog/personal: http://www.smiffysplace.com/ LinkedIn: http://www.linkedin.com/in/smiffy Skype: msmiffy Twitter: @smiffy -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
First
|
Prev
|
Pages: 1 2 Prev: virtualbox: RTR3Init failed with rc=-1912 (rc=-1912) Next: Computer overheating |