Re: loading module on boot
- To: debian-user@lists.debian.org
- Subject: Re: loading module on boot
- From: David Zelinsky <dzpost@dedekind.net>
- Date: 12 Jun 2006 22:53:53 -0400
- Message-id: <[🔎] 87r71tvk8u.fsf@localhost.localdomain>
- In-reply-to: <6mXj2-oJ-19@gated-at.bofh.it>
- References: <6myXi-6ec-3@gated-at.bofh.it> <6myXi-6ec-5@gated-at.bofh.it> <6myXi-6ec-7@gated-at.bofh.it> <6myXj-6ec-9@gated-at.bofh.it> <6myXi-6ec-1@gated-at.bofh.it> <6mFm8-7n6-17@gated-at.bofh.it> <6mXj2-oJ-19@gated-at.bofh.it>
Bob McGowan <bob_mcgowan@symantec.com> writes:
>
[..]
> >>>On Sat, Jun 10, 2006 at 00:18:26 -0400, David Zelinsky wrote:
> >>>[..]
> >>>
> >>>>The ide-cd entry in /etc/modules-2.6 _is_ getting read, because it
> >>>>prints something in the boot messages saying it's loading ide-cd. But
> >>>>either the load is failing for some reason, or it's getting unloaded by
> >>>>some other script.
[..]
>
> I would suggest looking into the /etc/rc?.d directories and determine
> what sequence of scripts is run as your system boots. On my system,
> the module-init-tools script is run from /etc/rcS.d as
> S20module-init-tools. You could add this to the beginning of each
> subsequent script:
>
> lsmod|grep -q ide_cd || echo lost it in $0
>
> to figure out when in the sequence it disappears. This should narrow
> down where you need to look.
Thanks, that was a good suggestion! I had grepped through
/etc/init.d/* but didn't find anything obvious. Using the above trick
I discovered that /etc/init.d/rcS called a script in /etc/boot.d that
called a script elsewhere in /etc that removed ide-cd, left over from
when I was using a 2.4 kernel and needed to use scsi emulation, or
something like that. Anyway, not it works!
-David
Reply to: