On Wed, 2007-09-26 at 15:32 -0600, Karl Larsen wrote: > OK the disk is the new one. What modules are being talked about? > What is a module? A module is extra routines that the kernel uses for some function, that can be loaded as needed, or not bothered with. The functions could all be put permanently into the kernel, but that means it gets bigger and bigger, needlessly (*most* people do not use *all* the modules). I think, from reading your threads, that when you moved from one drive to another, you've moved from one type of drive to another (IDE to SATA), and a different driver may be needed to read from the other drive, with that driver being in a module that's not currently incorporated into your initrd. If that's the case, you need to remake the initrd (the mkinitrd command), so it includes the module. Organising re-making it's something I've only done in the dusty path, so I couldn't really advise too well about it. But if this is the issue at hand, someone ought to be able to step in and help with it. Educated guesswork: If you can still boot from the other drive, and it can access the new one, you might be able to simply mkinitrd in that environment, and it'll include all the modules currently being used that it needs to. -- (This box runs FC5, my others run FC4 & FC6, in case that's important to the thread.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
