Somebody in the thread at some point said: > where it has the kernel panic you mention. So am I to understand that > the first two lines in grub.conf will have completed properly (root > ..., and kernel ...) and it's only the initrd where the failure occurs > (and only when trying to swap the kernel in RAM for the one on the > hard drive)? No, that's not how it works. What happens is that before doing anything with Linux, grub reads the kernel image and the initrd image both into RAM at different start addresses. If there is a problem doing that, then grub will error out before the kernel boot begins. Once it has them loaded, grub is completely done... it jumps into the Linux kernel image. Once the kernel decompresses and finishes getting started, it mounts the initrd copy in memory and starts running the "init" script it finds in there. That script loads some critical modules (to access the HDD controllers for example) from the initrd filesystem and then tries to mount the real root filesystem from the HDD. It is at that point Karl was dropping dead. > At this point it's for my own trouble shooting knowledge and > understanding of the boot process that I ask this seeing Karl has > resolved that portion of his problem. Well, yes Karl apparently made the problem go away somehow leaving nobody the wiser. -Andy -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
