Hi meo, Thanks for the tip. That makes perfect sense in a normal full Linux install. I seem to be too slow however, to recognize the darn default kernel in DSL! Booting a DSL CD with toram cheatcode should put the whole filesystem in RAM, and I can't find a vmlinuz* in there anywhere.
Looking back on my dev environment at /boot/grub/menu.1st there is no reference to vmlinuz either. The default 0 entry starts with:
Code Sample
kernel /boot/linux24 root=/dev/hda2
then has some cheatcode parameters, and then ends with:
Code Sample
initrd /boot/minirt24.gz
I see the linux24 file in /boot but if I just point the default entry to /boot/vmlinuz-2.4.26 I wonder what I will be losing by not using linux24? Easy enough to try it, I suppose.
Also, I have a vmlinuz file that is symlinked to the vmlinuz-2.4.26 image, and they have the same timestamps (I noticed this upon kernel compile). I will try pointing the grub menu just to /boot/vmlinuz
thx
EDIT: OK, after more searching, I see that linux24 is the actual kernel image. I changed the menu.1st to /boot/vmlinuz but it still fails. For reference, it goes through: The initial screen where you can enter cheatcodes, then:
Scanning for USB devices... Done Accessing DSL image at /dev/scd0... Total memory found: 386692 kB Creating /ramdisk (dynamic size=302168k) on shared memory... Done. Creating directories and symlinks on ramdisk...Done. Starting init process. INIT: version 2.78-knoppix booting
And there it stops.I found that the initlal splash is still trying to load the linux24 kernel, even though I have edited /boot/grub/menu.1st to point to /boot/vmlinuz-2.4.26 (I can probably use the vmlinuz symlink, but one thing at a time.
I finally found isolinux.cfg full of "default linux24" references. This was extracted from the original ISO file with ISOMASTER in the /boot directory of /mnt/sda1/source. I saved it locally (all ISOMASTER actions are outside of the chroot environment, back in the native Linux environment). Next is to change all linux24 references to vmlinuz-2.4.26 and insert it into the ISO. I then saved off the ISO... and it fails at the initial splash with Could not find kernel image: vmlinuz-2-4.26
But I'm getting different errors now, at least! I will look at it tomorrow, it's late. I can see that using the symlink for vmlinuz in the isolinux.cfg would be much preferred. You could potentially keep compiling kernels without having to also keep editing isolinux.cfg
meo, backtracking a bit, this might all be easier now trying your last suggestion, now that I know what the kernel is named. Perhaps I should just replace/rename vmlinuz-2.4.26 to linux24 and then perhaps could leave more things as they were.Now I have changed references in both isolinux.cfg and menu.1st to vmlinuz-2.4.26, I get 'can't find vmlinuz-2.4.26 image'.
I changed both references to the vmlinuz (which is a symlink to vmlinuz-2.4.26) same 'can't find' error.
I reloaded the original isolinux.cfg, mv /boot/vmlinuz-2.4.26 /boot/linux24. linux24 still retains the symlink to vmlinuz-2.4.26
Now it finds/loads the image, and again fails on: INIT: version 2.78-knoppix booting.
I'm about out of ideas now, where should I look? thxThis should really be in another thread IMO (but that's up to you).
Try removing "quiet" from the bootcode args - this will allow kernel messages to be shown during boot.Hi guys, i'm searching for an how-to, reading backwards all the 300+ answers is too much time consuming....