Well, I tried this, and didn't see any additional options which would explain the error. After copying the newly compiled kernel into the boot directory and re-running grub-install, I still get the same kernel panic error.
I wonder what else could be going on which could explain this? Jeff On Sunday 18 November 2007 05:00:12 pm »Q« wrote: > Jeff Cranmer <[EMAIL PROTECTED]> wrote: > > On Sunday 18 November 2007 03:42:53 pm b.n. wrote: > > > Jeff Cranmer ha scritto: > > > > I have just tried to install the latest 2.6.22-r9 kernel > > > > I copied the config file across from the present 2.6.17.r8 > > > > installed kernel, then recompiled. > > > > > > [...] > > > > > > > Can anyone point me in the direction of why the new kernel will > > > > not boot, while the old one boots fine? > > > > > > Didn't you run "make oldconfig" ? I don't know how safe it is to > > > copy and use a .config directly between different major revisions > > > of the kernel. > > > > I did not. What is the procedure for doing this, and what exactly > > does it accomplish? > > Copy the old .config file to /usr/src/[new kernel directory], and run > 'make oldconfig' in that directory. It picks out the changes and > prompts you to decide what to do about them. After that, IMO it's a > good idea to use 'make menuconfig' or 'make xconfig' to make sure the > new config makes sense before compiling the new kernel; this is > especially important if any of the questions asked by oldconfig didn't > quite make sense to you. -- [EMAIL PROTECTED] mailing list
