| 1 |
Tanstaafl wrote: |
| 2 |
> On 2010-03-09 8:36 PM, Walter Dnes wrote: |
| 3 |
> |
| 4 |
>> Today is when running a lilo menu with "production" and "experimental" |
| 5 |
>> kernels saved me. "production" is 2.6.30-r8. "experimental" is |
| 6 |
>> 2.6.31-r6 or 2.6.31-r10 (same problems with either one). I set |
| 7 |
>> /usr/src/linux to point at 2.6.31-r6 (or 10), copied .config from |
| 8 |
>> 2.6.30-r8 and ran "make oldconfig". |
| 9 |
>> |
| 10 |
> I *never* use make oldconfig between major kernel versions... |
| 11 |
> |
| 12 |
> I do as the kernel upgrade guide says - when going between major |
| 13 |
> versions (yes, even one), copy the old .config to the new kernel dir, |
| 14 |
> then run make menuconfig, and make sure all of your critical options are |
| 15 |
> set. This is much safer, though it does take more time. |
| 16 |
> |
| 17 |
> I've been wondering though - how well does genkernel work now? I've |
| 18 |
> never used it... |
| 19 |
> |
| 20 |
> |
| 21 |
|
| 22 |
I use make oldconfig all the time and have only had problems with it |
| 23 |
once. I would trust make oldconfig looong before I would even think to |
| 24 |
trust genkernel. I have never got it to work for me. |
| 25 |
|
| 26 |
Using make oldconfig should be fine for the OP. I wouldn't use it if I |
| 27 |
were going from 2.6.1* to a current version tho. It would be faster to |
| 28 |
start from scratch. That would be a lot of questions to answer. |
| 29 |
|
| 30 |
Dale |
| 31 |
|
| 32 |
:-) :-) |
Archives