A lot of these bugs end up being a broken initrd due to bugs in mkinitrd.
Get the user to attach their initrd for their kernel to the bz, and also their /etc/modprobe.conf, or have them examine the contents themselves if they are capable of that.
Picking apart the initrd of a working and failing kernel and doing a diff of the init script can reveal clues. To take apart an initrd, do the following ..
mkdir initrd cd initrd/ gzip -dc /boot/initrd-2.6.23-0.104.rc3.fc8.img | cpio -id
I wish to understand what exactly is being done here.
initrd to do with anything?
Where are we supposed to create the directory