I have tried everything I possibly could in order to get knoppmyth to boot. I did a fresh auto-install and whenever I boot, the BIOS finishes it's thing, and then it just sits there. The I did a manual install. When it asked for either MBR or Root partition. I have tried both with the same result. I'm installing v3 to a new 160gb hard drive. V2 didn't give me this trouble. What is the problem?

Did you ever get this resolved? I have the same problem. I installed R4V4 and had everything working great, but then broke some things when updating. I went to do auto install again and it hangs after checking the boot record (which returns ..OK). Just to be sure it wasn't the drive, I install WinXP on it and it booted fine, but again the R4V4 failed when tried again.

Enable your BIOS messages and look for something along the lines of "no bootable disk found". You didn't supply hardware details but certain drives and chipsets are fussy about how you jumper your hard drive. In particular a WD disk used with an NForce2 chipset must be jumpered for cable select or it will give symptoms like this.

Test your ISO disk..I had a downloaded image that passed teh M5 check but my writer was not creating perfect disks....I needed to slow the writter down

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

Here are the basics of my hardware.

Motherboard ECS K7S5A
MAXTOR 80G
GEFORCE3
SoundBlaster Live!

I believe the iso is OK since I've installed successfully more than once. I did find another post where someone had a problem where the partition wasn't marked as bootable. I found this to be the case for me too, but it didn't fix the problem. I installed Debian on this drive tonight successfully, so now both WinXP and Debian work ok on this drive. I'm stumped.

Fixed it by using the software that came with the drive. It was a pain since I had to pull a floppy drive out of another PC as I didn't plan to have one in a settop box.

Details will help the next poor mothers son to come along. What was really wrong? Which software? What did you do with it to fix the problem?

I wish I could tell you what the problem was, but I still don't know. I used the MAXTOR formatting/partitioning software that came with the drive to re-format and set up a FAT32 partition just for the heck of it (just like if it was a new drive). I then tried to re-install R4V4 again and everything magically worked.

I had problems formating a new Maxtor 80 gig too, and used Maxblast3 software to fix them. As a bonus, format time is reduced to a couple of seconds.

Available free on Maxtor site.

http://www.maxtor.com/en/support/downloads/maxblast3.htm

_________________
Tyan Trinity 1854S - VIA Apollo Pro 133
P3-1000, 768mb PC-133, GF2 MX400 64mb
Avermedia M179, ATI TV Wonder w/remote, Maxtor 160 gig, DVD burner.R5E50.
Second FE - Thinkpad T22, 900, 384mb. Ubuntu Dapper, Mythtv FE 0.20

Hi!
I am having the same issue as JoeyJoe.....black screen-no boot.I have a feeling lilo is not writing the mbr in the correct place.
My suystem is based on the tyan 2460s (duak amd XP 1600+) which uses the AMD MPX chipset.I have tried both auto config and manual config as LBA in the bios settings for diskk drives with the same results-BLACK SCREEN with blinking cursor.


Any ideas?

UPDATE:
I have just tried both the auto install AND the manual install with no luck.I can installl Win XP,Red Hat and Mandrake with no issues (as this used to be a Mandrake 9.1 box and was a reh hat 8 box before that).

Since noone else besides myself and JoeJoe are complaining I guess it must be a chipset issue? Whats your mobo chipset JoeJoe???

I am unable to install it either. I have tried installing other OSs and they all work. I have a gigabyte bored....Duron 950, with a WD drive

Dave

I have a 200 gig seagates and the exact same problem. System worked fine, upgraded to R4 and it worked (few things broken), then did complete re-install and BLAMMO, not working. Gets past bios, checks for CDROM then sits and stares at me... with those evil computer eyes...

I tried upgrading the MBR and reconfig for fat32 and ntfs...nothing.

I think lilo is not starting up in certain cases.

anyhelp appreciated.

kb9nwo...I agree 100%
Must be a lilo issue cause the kernel doesnt even attempt to start.I have tried 2 different drives....both 20 Gb with same results

Help

Cheers

This topic is also alive in Tier 3 if you want to monitor this issues progreess there,here is the link: http://mysettopbox.tv/phpBB2/viewtopic.php?t=2056