Need a little linux help

[hav0c]

Ok, I installed peanut linux on a box. I installed lilo to the MBR when I boot up all I get is "L 01 01 01 01 01 01 01 01 01 01" over and over. So I boot with a boot disk fdisk /mbr and reinstall peanut linux but this time I install lilo using the "superblock" method. Same thing happens as above the 01 01 01 stuff. I can boot the partition using the rescue disk. I tried running lilo again after booting using the rescue disk didn't help. I've even tried a different HD and the same thing happens. Any suggestions on how to fix this?

BTW I only have 2 partitions
/dev/hda1 *swap
/dev/hda2 *linux

Thanks

[nukes]

The L means LILO was only able to load the first stage (512b from the MBR) The 01010101 means "Illegal Command"
Is the disk fully supported by the BIOS? What version of Peanut Linux are you using - or rather (seeing as I don't use Peanut) what version of LILO?
What output does LILO give if you do "lilo -v -q" on the rescue disk?
I'm pretty sure this is to do with the BIOS though. What size HD, and what mobo/bios are you using?

[hav0c]

Well its a 10GB quantum HD, the system is 1GHz Athlon on a ECS K7VZA MB with the KT133A chip set and BIOS can see all of the disk. Here is the output from lilo:

LILO version 22.5, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2003 John Coffman
Released 04-Mar-2003 and compiled at 03:20:34 on Mar 23 2003.

Warning: LBA32 addressing assumed
Reading boot sector from /dev/hda
Installed: Mon Oct 20 12:12:45 2003

Global settings:
Delay before booting: 0.0 seconds
No command-line timeout
Enter boot prompt only on demand
Boot-time BIOS data saved
Large memory (>15M) is NOT used to load initial ramdisk
Non-RAID installation
Boot device WILL be used for the Map file
Serial line access is disabled
No message for boot prompt
No default boot command line
Images:
Linux *
No password
Boot command-line won't be locked
No single-key activation
VGA mode: NORMAL
Kernel is loaded "high"
No initial RAM disk
No fallback
Options: "ro root=302"

[nukes]

ok. That's lost me. Seems ok from there.
Another possibility is that the 2nd stage file isn't where is should be. Post the contents of your /etc/lilo.conf and tell me where the boot.map is.
Someone with experience with LILO help plz. I don't use it myself and its hard to troubleshoot something like this without access to a machine with LILO OR that distro.

[Ruler2112]

I had this EXACT same problem on my parent's computer about 8 or 9 months ago. Believe it or not, it was caused by a boot sector virus that had come from a floppy disk. It was the Stoned Empire Monkey virus; I'm guessing that it screwed with the LILO boot code somehow. I removed the virus using a free tool I downloaded and the problem disappeared.

[nukes]

root=302"

This is the only dodgy bit I see. Post your /etc/lilo.conf when you get the chance and hopefully we'll be able to get it sorted.
Its worth looking into what Ruler2112 says as well. Run a Virus scan on the drive if you have access to another machine.

[hav0c]

Here is my lilo.conf:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# For CD-Writer
#append="hdb=ide-scsi"

# For BMP Boot Image
#bitmap=/boot/ins64a.bmp
#bmp-colors=14,11,;15,9,0
#bmp-table=21,287p,2,4,175p
#bmp-timer=73,29,12,8,0
#install=/boot/boot-bmp.b

menu-scheme=Wb
boot = /dev/hda
prompt
timeout = 1200
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda2
label = Linux
read-only
# Linux bootable partition config ends

[nukes]

Doesn't seem to be any problems there. Is it a modern distro you're using? I'm not familiar with peanut Linux.
The only reason I can see is a problem with LBA addressing. Try adding "lba32" at the top and reinstall.

[hav0c]

Well I tried adding lba32 to the lilo.conf and then ran lilo, but it didn't work. Yeah peanut linux is a modren distro.
http://www.ibiblio.org/peanut/

[nukes]

How are you doing it when you run it from the liveCD? are you chrooting to wherever you mounted the partition, or just running LILO on its own?
When you say it didn't work, did it install, just not make any difference? or give you an error straight away?
Did it say "found Linux" or something similar when you ran lilo?