| 1 |
Am Dienstag 03 November 2009 23:29:59 schrieb Harry Putnam: |
| 2 |
|
| 3 |
> The thing is, I cannot find the culprit. For example, examining the |
| 4 |
> PIIX items in the working kernel and inserting here: |
| 5 |
|
| 6 |
Still the (IMHO) best way is to boot a LiveCD, run "lspci -vv" (two times "v") |
| 7 |
and write down which hardware is detected and which driver is used for it. |
| 8 |
From that you can directly determine what you need to compile into your |
| 9 |
kernel. Everything else is guesswork. |
| 10 |
|
| 11 |
Hint: menuconfig has a search function ("/"). You can directly search for the |
| 12 |
driver name you got from lspci and enable the corresponding option. |
| 13 |
|
| 14 |
If you're unsure as to what should be compiled into the kernel and what can be |
| 15 |
a module, always say "Y". You can try "M" in later iterations. As a rule of |
| 16 |
thumb: everything you need to access your root fs should get a "Y". That is |
| 17 |
Chipset->(S)ATA harddisk->Filesystem. |
| 18 |
|
| 19 |
If it still won't work, you can also post your kernel config and the output of |
| 20 |
lspci -vv here and somebody will find out what's wrong/missing. |
| 21 |
|
| 22 |
HTH... |
| 23 |
|
| 24 |
Dirk |
Archives