🚀 go-pugleaf

"Barry" <hammers@poboxes.com> writes:

>I tried my hand at a custom kernel. It compiled ok, but can't get loadlin
>to load it. Will only load a file called vmlinuz not vmlinux (result of
>recompile). Is there something I have to do to make it loadable?
>Thanks in advance.

That's not the thing that loadlin (or lilo) is supposed to load. What 
basically happens is this:

1)You compile your kernel
2)This generates a file called vmlinux in /usr/src/linux/
3)This is compressed to a file called zImage (assuming you did 'make 
zImage') which is located in /usr/src/linux/arch/i386/boot/

Now, loadlin or lilo will need to load THIS compressed kernel image. So, 
if you are using loadlin, copy the zImage file to where the old one used 
to be (the old one was probably called vmlinuz) and make sure linux.bat 
knows what you've called it. BACK UP THE OLD KERNEL FIRST, preferably with a 
boot disk (make zdisk or maybe zDisk creates a boot disk with the new 
kernel... read the README)

It's compressed to allow somewhat easier kernel loading (I think it's 
just gzipped but I could be wrong), that's why when you boot it says 
'Uncompressing kernel...'. Kernels get rather large when you have lots of 
options compiled in.

All this info is in the kernel compile howto, which is definitely worth a 
read, particularly if you have never done a compile before. Also read the 
README and other docs included with the kernel source.

Good luck!
-- 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
< Daniel Franklin >><< drf03@uow.edu.au >><< 2nd Year Electrical Engineer >
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<