This answer is all over the forums, but it is a little buried in most topics, so I figured I would put it at the top of this one. This problem occurs in (at least) R5A30.2 when you are either trying to dual boot, or (like me), you have an old copy of an OS on a secondary HD. The symptoms are an uneventful install process, followed by a normal POST after reboot, and nothing else.
The install program puts an eroneous line at the top of the /etc/lilo.conf file. To check this boot to the cd, when the install screen comes up, press ctrl-alt-f2. Then type
mount /dev/hdxx /mnt/hdxx (where hdxx is the drive and partition / is located on).

now type
chroot /mnt/hdxx

now type lilo

If lilo does not complain then this post is not for you (sorry).
If lilo does complain, then vi /etc/lilo.conf and comment out the line that lilo complains about ( for me it was the first 2 lines).

now run lilo again and reboot.

good luck

Could you please post those two lines so I can see what they are to be sure it doesn't happen?

Sure no problem, I'm not able to get that for you right now, but I'll get logged on soon. I can tell you this, the lines were the first 2 in the file, and they were refering to the two partitions that I have on a secondary HD formated fat32. Again I'm not able to get to that system right now, but I will soon. Just didn't want you to think I was blowing you off.

Hi Dale,

Since I happen to have them handy Here are the top three lines after install / upgrade. Doesn't seem to bother after an upgrade so assuming the lilo isn't re-run but has to be fixed with an install. My changes are in green.

lilo.conf
vga=788
#part: /dev/sda1, typ: 222 (always adds these for me)
#part: /dev/sda2, typ: 7 (and I just rem them out)

and since I dual boot,(only as needed) I may need an extra minute sometimes ...to remember that I need to arrow down one step

# message=/boot/bootmess.txt
prompt
timeout=1200 (was 150)

Thanks
Mike

Yep thats them. Obviously particular to drive configuration.