| 1 |
Well, I tried this, and didn't see any additional options which would explain |
| 2 |
the error. After copying the newly compiled kernel into the boot directory |
| 3 |
and re-running grub-install, I still get the same kernel panic error. |
| 4 |
|
| 5 |
I wonder what else could be going on which could explain this? |
| 6 |
|
| 7 |
Jeff |
| 8 |
|
| 9 |
On Sunday 18 November 2007 05:00:12 pm »Q« wrote: |
| 10 |
> Jeff Cranmer <jcranmer01@×××××××××.net> wrote: |
| 11 |
> > On Sunday 18 November 2007 03:42:53 pm b.n. wrote: |
| 12 |
> > > Jeff Cranmer ha scritto: |
| 13 |
> > > > I have just tried to install the latest 2.6.22-r9 kernel |
| 14 |
> > > > I copied the config file across from the present 2.6.17.r8 |
| 15 |
> > > > installed kernel, then recompiled. |
| 16 |
> > > |
| 17 |
> > > [...] |
| 18 |
> > > |
| 19 |
> > > > Can anyone point me in the direction of why the new kernel will |
| 20 |
> > > > not boot, while the old one boots fine? |
| 21 |
> > > |
| 22 |
> > > Didn't you run "make oldconfig" ? I don't know how safe it is to |
| 23 |
> > > copy and use a .config directly between different major revisions |
| 24 |
> > > of the kernel. |
| 25 |
> > |
| 26 |
> > I did not. What is the procedure for doing this, and what exactly |
| 27 |
> > does it accomplish? |
| 28 |
> |
| 29 |
> Copy the old .config file to /usr/src/[new kernel directory], and run |
| 30 |
> 'make oldconfig' in that directory. It picks out the changes and |
| 31 |
> prompts you to decide what to do about them. After that, IMO it's a |
| 32 |
> good idea to use 'make menuconfig' or 'make xconfig' to make sure the |
| 33 |
> new config makes sense before compiling the new kernel; this is |
| 34 |
> especially important if any of the questions asked by oldconfig didn't |
| 35 |
> quite make sense to you. |
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives