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