Re: Kernel weirdness
On Sun, 5 Oct 2003, Rob wrote:
> I've installed the kernel-image-2.4.22-1-686 package. Until now, I've
> been running the 2.4.18-bf2.4 kernel. Though I didn't change what
> modules I load, with this new kernel package have come a whole bunch of
> new modules that are being loaded. I've run modconfig and removed them,
> but they continue to to load at boot.
This insane behaviour is caused by initrd:
,----
| # cat /initrd/loadmodules
| modprobe -k vesafb > /dev/null 2>&1
| modprobe -k unix 2> /dev/null
| modprobe -k ide-mod
| modprobe -k pdc202xx_new > /dev/null 2>&1
| modprobe -k adma100 > /dev/null 2>&1
| modprobe -k aec62xx > /dev/null 2>&1
| modprobe -k alim15x3 > /dev/null 2>&1
| modprobe -k amd74xx > /dev/null 2>&1
| modprobe -k cmd640 > /dev/null 2>&1
| modprobe -k cmd64x > /dev/null 2>&1
| modprobe -k cs5530 > /dev/null 2>&1
| modprobe -k cy82c693 > /dev/null 2>&1
| modprobe -k generic > /dev/null 2>&1
| modprobe -k hpt34x > /dev/null 2>&1
| modprobe -k hpt366 > /dev/null 2>&1
| modprobe -k ns87415 > /dev/null 2>&1
| modprobe -k opti621 > /dev/null 2>&1
| modprobe -k pdc202xx_old > /dev/null 2>&1
| modprobe -k piix > /dev/null 2>&1
| modprobe -k rz1000 > /dev/null 2>&1
| modprobe -k sc1200 > /dev/null 2>&1
| modprobe -k serverworks > /dev/null 2>&1
| modprobe -k siimage > /dev/null 2>&1
| modprobe -k sis5513 > /dev/null 2>&1
| modprobe -k slc90e66 > /dev/null 2>&1
| modprobe -k triflex > /dev/null 2>&1
| modprobe -k trm290 > /dev/null 2>&1
| modprobe -k via82cxxx > /dev/null 2>&1
| modprobe -k ide-probe-mod
| modprobe -k ide-disk
`----
Up to kernel-image-2.4.20 a more moderate approach was chosen:
,----
| # cat /initrd/loadmodules
| modprobe -k vesafb > /dev/null 2>&1
| modprobe -k unix 2> /dev/null
| modprobe -k ide-mod
| modprobe -k ide-probe-mod
| modprobe -k ide-disk
`----
I was going to put the whole blame on hotplug, but I would have been
wrong. I still think it's weird it starts from /etc/rcS.d _and_ all run
levels (except 0 and 6).
Cheers,
Cristian
Reply to: