On Fri, Oct 31, 2008 at 4:35 AM, Loïc Minier <[EMAIL PROTECTED]> wrote: > On Fri, Oct 31, 2008, Loïc Minier wrote: >> Actually I dropped that part when rewriting the init script; any idea >> what could set MODPROBE_OPTIONS for you? > > Could you either try the attached module-init-tools patch, or prepend > MODPROBE_OPTIONS="" to the modprobe --all --use-blacklist call in the > init script? > > If the latter works, I'll push a new acpid with this workaround while > waiting for the former to be merged. > > -- > Loïc Minier >
Hi Loïc. The culprit appears to be inside initrd. The 'init' script in the initrd image is setting MODPROBE_OPTIONS="-qb". This cascades down through the init.d scripts and is picked up by /etc/init.d/acpid which fails. I've tested both 'unset MODPROBE_OPTIONS' and 'MODPROBE_OPTIONS=""' in /etc/init.d/acpid and both methods work to start acpid when no modules are available. Derrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
