linux-kernel - Re: How to determine the information about SATA controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 11 Sep 2010 15:34:23 +0200
From:	Mikael Pettersson <mikpe@...uu.se>
To:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>
Cc:	Mikael Pettersson <mikpe@...uu.se>,
	Jeff Garzik <jgarzik@...ox.com>, linux-ide@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: How to determine the information about SATA controller

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/