Bug#347720: Correction for description of the effects of this bug
I mixed two things up when I was submitting this bug. The effect of this
bug is *not* that the module load order changes but that too many
modules get loaded.
The problem I had with this, apart from having a bloated initrd image,
was that the USB driver on the affected box was causing severe hardware
problems, blocking interrupts for other PCI cards, and the image created
by mkinitrd would always load the USB driver module at boot time
regardless of what I put into /etc/mkinitrd/mkinitrd.conf
With the suggested fix, only those modules which are really needed at
boot time are loaded. Here's a comparison of the modules loaded with and
without the fix:
With the fix:
-------------
modprobe -k piix
modprobe -k pdc202xx_new
modprobe -k vesafb > /dev/null 2>&1
modprobe -k fbcon 2> /dev/null
modprobe -k unix 2> /dev/null
modprobe -k megaraid
modprobe -k aic7xxx
modprobe -k sd_mod
Without the fix:
----------------
modprobe -k piix
modprobe -k pdc202xx_new
modprobe -k vesafb > /dev/null 2>&1
modprobe -k fbcon 2> /dev/null
modprobe -k unix 2> /dev/null
modprobe -k megaraid
modprobe -k aic7xxx
modprobe -k vesafb
modprobe -k font
modprobe -k sd_mod
modprobe -k ide-cd
modprobe -k ide-disk
modprobe -k ide-generic
modprobe -k psmouse
modprobe -k evdev
modprobe -k mousedev
modprobe -k tsdev
modprobe -k raid0
modprobe -k e100
modprobe -k 3c59x
modprobe -k pci_hotplug
modprobe -k ehci-hcd # <-- one of those caused
modprobe -k ohci-hcd # <-- hardware problems
modprobe -k rtc
modprobe -k pcspkr
modprobe -k parport_pc
modprobe -k floppy
modprobe -k lp
Reply to: