Jaswinder Singh Rajput writes: > > > No root device found. > > > Boot has failed, sleeping forever > > > > > > I am trying to determine the information about the SATA controller so > > > that I can choose the appropriate controller for SATA in kernel > > > config. I am not able to figure out the SATA information from above > > > dmesg and lsmod. How can I do so. > > > > In your working dmesg the disks are controlled by ata_piix, > > but you've disabled CONFIG_ATA_PIIX in the config you're trying. > > So it's not surprising that you can't boot. > > > > 1) re-enable CONFIG_ATA_PIIX and disable CONFIG_IDE > > I have enabled CONFIG_ATA_PIIX > and disabled CONFIG_IDE > > but still getting same error : > > No root device found. > Boot has failed, sleeping forever > > Am I missing some more options. > > > or > > 2) go into the bios and change the option that says whether to run > > the ATA controller in legacy/compatible mode or enhanced/ahci mode, > > you want ahci mode > > > > In my case, BIOS options are enhanced / legacy / disabled. I tried all > but of no use. So I am using enhanced to boot Fedora 13 kernel. We need to see the complete kernel messages from a failed boot to determine the root cause of that missing root device failure. I suggest hooking up a null-modem serial cable to a second machine and run minicom on that one to capture boot messages, but there may be other ways to capture boot messages: netconsole? firewire? -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
