Re: My custom kernel doesnt boot.

["nate" <debian-user@aphroland.org>]

<quote who="Dr. Sachin Kale">
> Hello everybody,
>
> (debian 2.2 r5)
>
> installed kernel-headers & kernel-src2.2.19 package.
> in /usr/src/linux did as follows -
>
> make config
> make dep
> make clean
> make bzImage
> (no errors)
> cp vmlinux /vmlinux_custom1
>
> edited /etc/lilo.conf

did you install the new kernel? if you did make bzImage
the kernel would end up in
/usr/src/linux/arch/i386/boot/bzImage

then you'd copy that to wherever you want to store it. since
you did not mention this step i am confused if you even installed
the new kernel.


to be sure your kernel works, i would recompmile the kernel
using the configuration of the debian kernel, that way you know
it has all the options that your system requires to boot.
the debian's configiuration is stored in /boot/config-2.2.19
if its a 2.2.19 kernel, if your in /usr/src, just
cp .config .config-old
cp /boot/config-2.2.19 .config

to use the debian config. then compile and boot the new kernel,
if it works you can login and do 'uname -a' and it will show
the time/date the kernel was built and you can see if your
using the new kernel. once that works try to customize it.


the message you recieved makes me thing something very basic
is wrong, not the kernel config, if the kernel did not even
START to boot(e.g. you did not even get the first line of
the boot process) that makes me think that lilo is misconfigured
or the kernel is not loaded.

the 'debian' way to compile a kernel is using the 'kernel-package'
package, it works pretty good if you want to try it out, if
your just playing around though it can take much longer as it
makes a bunch of different packages, rather then just 1, and
can take quite a bit longer then just building a kernel.

good luck

nate




-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org