Hokay...The normal sequence for the Syslinux boot process is:
1) It loads itself into memory.
2) It reads its config file.
3) It loads root.lrp which is the initrd for LEAF/LRP.
4) It loads the kernel.
5) It sets some parameters for the kernel.
6) It passes control to the kernel.
The boot process is dying in step 3. Therefore Linux is not your problem
because the kernel never gets loaded let alone actually start executing.
Syslinux is having problems reading the CF disk.
I keep coming back to CHS parameters as being your problem. Something is
wrong there. Try some more CHS values.
There may be a 32MB barrier problem. Try a much smaller drive size.
I'd probably try making the CF disk boot DOS. Once I got that figured out
the rest should fall into place.
At 07:48 PM 07/10/2001 -0700, Billy Jacobs wrote
>The kernel image itself is not corrupt. Filesizez match, as well as
>diffs between kernels. I placed the IDE kernel onto the LRP floppy that
>I have, and it booted fine, including seeing the IDE device:
> hda: Hitachi CVM1.1.1, 30MB w/1kB Cache, CHS=736/5/17
> <snip>
> Partition check:
> hda: hda1
>
>I can mount the device w/msdos filesystem without a problem. I copied
>everything from the floppy over to /dev/hda1. When I reboot after
>copying the files over, it starts loading root.lrp, then craps out and
>reboots:
> Loading root.lrp...
>When it comes up next time, it complains about an Invalid of corrupt
>kernel. From then on, it will give the same error upon reboot.
>
>The strange thing is that it only starts loading root.lrp after I copy
>the files back over to the CF disk. AND, when it does start loading
>root.lrp, it always stops at 3 dots.
>
>Just to rule out a possible problem with syslinux, I used GRUB, and
>when trying to boot off Partition 0, it exhibits the same problem
>(therefore, not a problem with syslinux).
>
>In my syslinux.cfg file, I have set both boot and PKGPATH to /dev/hda1.
>
>I mentioned before that I have to specify the drive type in my BIOS by
>sectors, heads, cylinders, etc. Since a CF disk doesn't have any such
>parts, what is the best setting to use? I know by specifying different
>values, it changes whether or not the BIOS can see the boot sector of
>the CF.
>
>This is a strange one...any help would be appreciated.
>
>Thanks,
>Billy
