I'm hoping that someone around here will be able to help me with this
problem. I'm trying to make a bootable cd, where there's a kernel image
on the disc to boot and a ramdisk image that needs to be loaded as the
root filesystem. Here's the process I've been using:
- Make a kernel with "make boot".
- Put that kernel into the /kernels/generic.s/vmlinux.gz, of the root
directory of what will become the ISO image.
- Place the bootlx file created by building aboot into the root of the
ISO filesystem.
- Place the compressed ramdisk image into /images/color.gz of the ISO
filesystem.
- Make the ISO image using mkisofs as follows:
mkisofs -o /tmp/install.iso -R -V "Slackware Alpha Install" \
-v -T -d -D -N -L \
-m source \
-P "BSDi" \
-p "Chris Lumens <chris@slackware.com>" \
-A "Slackware -current `date +%d-%b-%y`" \
/ALPHA/slackware-alpha/slackware-current
(In case you're wondering, the cd is setup up just like the Intel
version as far as the directory structure).
- Run isomarkboot as follows:
isomarkboot /tmp/install.iso bootlx
Then I burn the disc and attempt to boot it from SRM as follows:
boot dqa0 -file /kernels/generic.s/vmlinux.gz \
-flags "root=/dev/ram initrd=/images/color.gz"
It sits there for a while, says that it's found a valid boot block on the
cd, spits out some numbers about the iso image, then says "kernel stack
not valid halt" and drops me back to the firmware prompt.
I've been able to boot a kernel off the hard drive and load the ramdisk
and mount it, so it's not a problem with that. I'm not really sure what
the problem is. But as soon as I can figure this part out, I'll be ready
to sync everything, cron up an iso, and open access to the rsync server.
Has anyone seen this before and knows what I am doing wrong?
--
Chris Lumens - chris@slackware.com - KG6CIH
@n=(-42,-85,-83,-19,65,2,-10,-10,-15,-3,2,-10,73,-4,8,-4,2,79,8,17,15,7,14,2);
print map{chr(-$n[$i++]+ord)} sort(split(//,'place random string here')),"\n";
This archive was generated by hypermail 2b30 : Fri May 09 2003 - 10:00:02 PDT