On Tue, Oct 21, 2008 at 3:51 AM, Loïc Minier <[EMAIL PROTECTED]> wrote: > On Mon, Oct 20, 2008, Derrick Karpo wrote: >> I can confirm this same behaviour under 2.6.17.1 (amd64). With ACPI >> compiled into the kernel acpid fails to start on boot however when >> ACPI is compiled in as modules then acpid starts correctly. In my >> case, ACPI also started correctly with the stock Debian >> linux-image-2.6.26-1-amd64 (2.6.26-9) image which was different than >> the experience Anders had with the 686 kernel. > > Ok, that's interesting; I don't think the modprobe --all is failing, > but the "sed -rn" might. Could you please add set -x at the top of > /etc/init.d/acpid and send us the output of /etc/init.d/acpid start? > > Thanks, > -- > Loïc Minier >
Hello. Along with the 'set -x' I also added logging statements before and after the modprobe in /etc/init.d/acpid. modprobe is called correctly and $MODULES is propagated with the MODULES that are defined in /etc/default/acpid. However, the /etc/init.d/acpid script doesn't get past the modprobe. I'm a little short on testing time (as this is occurring on my primary work machine) however I'll try take a look at it later today. Derrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
