How to determine the information about SATA controller

[Jaswinder Singh Rajput]

Hello,

My old IDE hard disk is broken so I installed new SATA drive on my box with F13:

dmesg :
http://userweb.kernel.org/~jaswinder/P4_HT/dmesg_2633_fc13.txt

lsmod:
http://userweb.kernel.org/~jaswinder/P4_HT/lsmod_2633_fc13.txt

lspci:
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM
Controller/Host-Hub Interface (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated
Graphics Controller (rev 02)
00:06.0 System peripheral: Intel Corporation 82865G/PE/P Processor to
I/O Memory Interface (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC
Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE
Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)

I am trying to build the kernel with this config:
http://userweb.kernel.org/~jaswinder/P4_HT/config-ht-test.txt

But I am getting error :

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.

Thanks,
--
Jaswinder Singh.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

[Mikael Pettersson]

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
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

[Jaswinder Singh Rajput]

Hello,

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.

Thanks,
--
Jawinder Singh.

[Mikael Pettersson]

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?

[Jaswinder Singh Rajput]

>  > >
>  >
>  > 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?
>

Netbook is also using SATA Intel controller :
http://userweb.kernel.org/~jaswinder/acer_netbook/config-2636rc3-netbook.txt

I used netbook config and with little bit modification as CPU and
network device is changed, I am able to boot the kernel :

dmesg :
http://userweb.kernel.org/~jaswinder/P4_HT/dmesg_2636_test_netbook.txt

config:
http://userweb.kernel.org/~jaswinder/P4_HT/config-ht-test-netbook.txt

Thanks for your help,
--
Jaswinder Singh.