Re: kernel 2.6.10 upgrade and ide drives go missing

[Anthony Tippett <atippett@etomic.net>]

I know nothing about build environments being in /tmp.. is this a joke? 
   What I don't understand is why initrd would not include ide-generic 
and ide-disk modules.  Aren't those the modules used to for ide drives 
which are most users setups?

Anyways I mounted my initrd.img-2.6.10-1-k7 image and the file 
loadmodules contained the following:
modprobe -k  scsi_mod
modprobe -k  sd_mod
modprobe -k  libata
modprobe -k  sata_sil
modprobe -k  ext3
modprobe -k  vesafb > /dev/null 2>&1
modprobe -k  fbcon 2> /dev/null
modprobe -k  unix 2> /dev/null


I also mounted my 2.6.8 initrd image and it contained the same 
information.  Now I don't need these modules to boot linux because my 
root image is on my SATA drive that is loaded with sata_sil.   Should 
hotplug or discover then take care of loading these modules?


I'm also using grub not lilo.  I know i could fix this by adding these 
modules to the /etc/mkinitrd/modules file and remaking my initrd image, 
but shouldn't these modules be loaded automatically?

I'm going to reboot and take a long look at dmesg to see if I see any 
errors.


Shaul Karl wrote:
> On Sat, Mar 19, 2005 at 07:39:34PM -0800, Anthony Tippett wrote:
>
> > I'm not really sure how to examine the an initrd image, I think you 
> > want my to mount it and look to see what modules are on it.  I did 
> > notice I had a directory /initrd but it didn't contain any files.?? 
> > abnormal?
>
>
>
>   Didn't you get a message about the build environment being kept in
> /tmp? Hopefully there is a file mentioning those modules. Alternatively,
> it might be quicker and dirtier to copy the new initrd image to /boot,
> possibly run lilo and then just reboot the machine.
>
>
>
> > I'll search for mounting initrd files.