On Thu, Oct 23, 2008 at 2:10 AM, Michael Meskes <[EMAIL PROTECTED]> wrote: > On Wed, Oct 22, 2008 at 04:11:48PM -0600, Derrick Karpo wrote: >> 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. > > Could you please test with acpid_1.0.6-15? I'd expect it to fix your problem > or > I misjudged where your problem lies. > > Michael
Hello. acpid_1.0.6-15 exhibits the same issue and I confirmed that /proc/modules does exist at that point in the script. As a workaround, I've attached a patch to /etc/init.d/acpid to get past the modprobe when it fails. It's a hack but at least it allows acpid to start when there are no modules to load. There's likely something bigger at play here. Derrick
acpid-1.0.6-15-modprobe.patch.gz
Description: GNU Zip compressed data
