On Sun, Nov 02, 2008, Derrick Karpo wrote:
> 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.
Ah right, forgot to update this b
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, o
On Thu, Oct 30, 2008 at 10:27:47PM -0600, Derrick Karpo wrote:
> Just to recount and answer some of Michael's questions, none of the
> acpid modules exist in this test as they are all compiled in. If all
Loic, this means we catch this failure by changing the default, right?
Michael
--
Michael M
On Fri, Oct 31, 2008, Michael Meskes wrote:
> Loic, this means we catch this failure by changing the default, right?
Yup, but it would still be exposed to people who have a custom list of
modules in /etc/default/acpid and who don't merge the new conffile.
:-/
--
Loïc Minier
--
To UNSUBSCRI
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 th
On Fri, Oct 31, 2008, Loïc Minier wrote:
> MODPROBE_OPTIONS in the acpid init script. This is only set if
> VERBOSE is false.
Actually I dropped that part when rewriting the init script; any idea
what could set MODPROBE_OPTIONS for you?
--
Loïc Minier
--
To UNSUBSCRIBE, email to [EMA
On Thu, Oct 30, 2008, Derrick Karpo wrote:
> Just to recount and answer some of Michael's questions, none of the
> acpid modules exist in this test as they are all compiled in. If all
> acpi modules are compiled into the kernel then the acpid fails to
> start at boot. If they are left as modules
On Thu, Oct 30, 2008 at 3:29 AM, Loïc Minier <[EMAIL PROTECTED]> wrote:
>Hi Derrick,
>
> Could you please edit /etc/init.d/acpid as root, and change the
> "set -e" into:
>
> set -e
> set -x
> initlogfile="$(mktemp -t acpid.init.)"
> exec 2>"$initlogfile"
>
> This will record the
Hi Derrick,
Could you please edit /etc/init.d/acpid as root, and change the
"set -e" into:
set -e
set -x
initlogfile="$(mktemp -t acpid.init.)"
exec 2>"$initlogfile"
This will record the execution of acpid's init script to a log file in
/tmp.
Please send us the resulting /t
On Fri, Oct 24, 2008 at 08:57:09PM -0600, Derrick Karpo wrote:
> My previous tests confirmed that $MODULES is not empty and contains
> well defined space-delimited modules as defined in /etc/default/acpid.
And all these modules do exist? Do you get meaningful output by removing the
"2>/dev/null"?
On Fri, Oct 24, 2008, Derrick Karpo wrote:
> In looking at the /etc/init.d/acpid script from Ubuntu it appears to
> solve many of the modprobe issues that I am seeing. It checks to
> ensure the modules exist before loading them and won't attempt to load
> modules twice. Perhaps it's worth merging
On Fri, Oct 24, 2008 at 2:57 AM, Michael Meskes <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 24, 2008 at 10:19:55AM +0200, Loïc Minier wrote:
>> On Fri, Oct 24, 2008, Michael Meskes wrote:
>> > if [ $MODULES ]; then
>> > modprobe --all --use-blacklist $MODULES 2>/dev/null
>> > fi
>>
>> Err you pro
On Fri, Oct 24, 2008 at 11:00:28AM +0200, Loïc Minier wrote:
> > No. For some strange reasons the "if [ $MODULES ]" works for me as does
> > "if [ ! -z $MODULES ]" but "if [ -n $MODULES ]" does not.
>
> Err because you need to quote it!
> ...
Sorry, incorrectly pasted (in fact I typed this) int
On Fri, Oct 24, 2008 at 10:19:55AM +0200, Loïc Minier wrote:
> On Fri, Oct 24, 2008, Michael Meskes wrote:
> > if [ $MODULES ]; then
> > modprobe --all --use-blacklist $MODULES 2>/dev/null
> > fi
>
> Err you probably lack a -n here, but FYI there's already:
No. For some strange reasons the "
On Fri, Oct 24, 2008, Michael Meskes wrote:
> No. For some strange reasons the "if [ $MODULES ]" works for me as does
> "if [ ! -z $MODULES ]" but "if [ -n $MODULES ]" does not.
Err because you need to quote it!
if [ -n $MODULES ] becomes if [ -n ] when MODULES is empty; what you
want is if [
On Fri, Oct 24, 2008, Michael Meskes wrote:
> if [ $MODULES ]; then
> modprobe --all --use-blacklist $MODULES 2>/dev/null
> fi
Err you probably lack a -n here, but FYI there's already:
if [ -z "$MODULES" ]; then
return
fi
I think modprobe --all always returns 0 (which is p
unmerge 502704
reopen 502704
thanks
> > 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 poin
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
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. Howev
19 matches
Mail list logo
