In the default tomsrtbt, both the kernel and the ramdisk are compressed with bzip2, and the kernel *only* supports bzip2 for the kernel and *only* supports bzip2 for the ramdisk.
On a normal bzImage, the kernel is compressed with gzip, and *only supports gzip for the ramdisk*. You *cannot* use the bzip2 ramdisk image from tomsrtbt with a normal bzImage kernel. When you re-run buildit.s with bzImage instead of bz2bzImage, it will compress the ramdisk with gzip instead of bzip2, so it will work. You *cannot* just replace the kernel and re-run lilo, unless the new kernel is patched to load a bzip2 ramdisk. Once you have built for bzImage, you could of course just re- install lilo, but, it may just be easier to re-run buildit.s. -Tom On 4 Feb 2003, Oliver Egginger wrote: > Date: 04 Feb 2003 16:24:03 +0100 > From: Oliver Egginger <[EMAIL PROTECTED]> > To: Mario Ohnewald <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [tomsrtbt] own Kernel - ram disk problem > > Hello Mario, > > maybe you have to reinstall lilo manual. > > 1. Mount the tomsrtbt disk image via loopback, for example: > mount -o loop -t minix ./tomsrtbt-2.0.103.288.img /mnt/tomsrtb > > 2. Create your lilo.conf. > > For example a working lilo.conf could look like this: > > --------------------------> SNIP > boot=/dev/ram0 > disk=/dev/ram0 > bios=0x00 > sectors=36 > heads=2 > cylinders=80 > install=/boot.b > message=/settings.s > backup=/dev/null > map=/map > read-write > vga=ask > image=/bz2bzImage > root=/dev/ram0 > initrd=/initrd.bz2 > append="parport=0x378,7" > --------------------------> SNIP > > The image parameter must point to the symbolic name of your kernel image > (well known as filename). > > 3. Copy your lilo.conf into the /mnt/toms directory. > > 4. after that try this: > lilo -r /mnt/toms -C lilo.conf > > 5. umount /mnt/tomsrtb > and do a test. > > > - oliver > > > Am Die, 2003-02-04 um 15.34 schrieb Mario Ohnewald: > > Hello! > > I build myself a new kernel, and then bootet the disk, but i got a > > "Could not find a valid Ram disk image starting at 867" ... > > I read in the archive that someone just renamed its bzImage kernel to > > bz2bzImage, SO DID I! > > ok, then i deleted the old kernel, copied mine on it and changed > > > > settings.s: > > ============== > > KERNEL=bz2bzImage --> KERNEL=bzImage > > > > > > > > build.s: > > ================= > > if [ $KERNEL = "bz2bzImage" ] > > then > > dd -q --retry-partial if=$RD bs=1k count=$RZ|bzip2 -9>$ID/root.raw.xz > > else > > dd -q --retry-partial if=$RD bs=1k count=$RZ|gzip -9>$ID/root.raw.xz > > fi > > > > --> > > > > if [ $KERNEL = "bzImage" ] > > then > > dd -q --retry-partial if=$RD bs=1k count=$RZ|gzip -9>$ID/root.raw.xz > > fi > > > > ------- > > > > image=$MP/bz2bzImage --> image=$MP/bzImage > > > > > > > > umounted tomsrtbt.raw again, wrote disk. booted, stillt the same error. > > I have minix and ramdisk support in my kernel (2.4.20). > > > > What did i do wrong? > > > > Cheers, Mario > > > > > > > > > >
