On Wed, Nov 4, 2009 at 12:49 PM, Dirk Heinrichs
<dirk.heinri...@online.de> wrote:
> Am Dienstag 03 November 2009 23:29:59 schrieb Harry Putnam:
>
>> The thing is, I cannot find the culprit. For example, examining the
>> PIIX items in the working kernel and inserting here:
>
> Still the (IMHO) best way is to boot a LiveCD, run "lspci -vv" (two times "v")
> and write down which hardware is detected and which driver is used for it.
> From that you can directly determine what you need to compile into your
> kernel. Everything else is guesswork.
>
> Hint: menuconfig has a search function ("/"). You can directly search for the
> driver name you got from lspci and enable the corresponding option.
>
> If you're unsure as to what should be compiled into the kernel and what can be
> a module, always say "Y". You can try "M" in later iterations. As a rule of
> thumb: everything you need to access your root fs should get a "Y". That is
> Chipset->(S)ATA harddisk->Filesystem.
>
> If it still won't work, you can also post your kernel config and the output of
> lspci -vv here and somebody will find out what's wrong/missing.
>
> HTH...
>
> Dirk
>
And on a reasonably new version of pciutils...
lcpci -k
lists devices and drivers, less extras to dig through.
--
Poison [BLX]
Joshua M. Murphy
