M. Fioretti wrote: > On Sun, January 18, 2009 12:57 am, Roger Heflin wrote: > > >> The base problem is the new MB likely has a *different* sata device >> controlling the drives... >> The typical fix is to boot a rescue, figure out from the rescue what >> driver is needed and update modprobe.conf and rebuilt the initial ram >> disk with that driver, and try again.? > > As I already answered to Craig, for reasons not worth discussing here, it > would be much easier for me to connect the drive to my (other distro) > linux laptop and work from there, only using the mb datasheet to figure > out which modules are needed. Is this possible? > How should I proceed, exactly > Read the man page for mkinitrd - it tells you how to include specific modules, as well as an option to overwrite the current initrd. But you have to know the module you need for the new controller. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
