| 1 |
On 11/03/2009 02:29 PM, Harry Putnam wrote: |
| 2 |
> I'll say right from the start, that building a new kernel, has always |
| 3 |
> been a problem for me. I don't remember ever not having a problem, in |
| 4 |
> 10+ yrs.. |
| 5 |
> |
| 6 |
> Many people here seem to find it completely easy... not me. |
| 7 |
> |
| 8 |
> So I'm back in the soup. |
| 9 |
> [I hope what I try to layout below is not overly confusing] |
| 10 |
> |
| 11 |
> (After install of gentoo-sources-2.6.31-r4) |
| 12 |
> |
| 13 |
> I started with `make oldconfig' |
| 14 |
> Moved from that to `make menuconfig'... |
| 15 |
|
| 16 |
There's no reason to use menuconfig after running oldconfig, If your |
| 17 |
old kernel was using all of the hardware, then the new kernel should, |
| 18 |
too, just with oldconfig. |
| 19 |
|
| 20 |
Volker makes an excellent point. Support for your disk controller and |
| 21 |
for your file system(s) must be built into the kernel unless you use |
| 22 |
initrd to load those modules *before* the kernel tries to mount /. |
| 23 |
|
| 24 |
That's a pain and isn't necessary for most machines because you know |
| 25 |
in advance what hardware you have and which file systems you use. |
| 26 |
(But your kernel doesn't know in advance unless the right drivers are |
| 27 |
compiled in ;o) |
Archives