http://qa.mandrakesoft.com/show_bug.cgi?id=3012

           Product: lilo
         Component: lilo
           Summary: Lilo bootloading freeze on i586 Pentium 233
           Version: 22.4.1-2mdk
          Platform: PC
        OS/Version: All
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


In the current release of Mandrake 9.1 RC2, when doing an initial install after
all has been configured, lilo attempts to mount itself on the MBR of hda1.  This
is fine, but it seems that on this hardware spec, it cannot mount.  It simply
doesn't seem to be able to complete the mount.  I don't have a dump of the
error, due to the freeze.  I attempted to reinstall/upgrade after the fact twice
with identical results.  I then installed Mandrake 9.0 final, and lilo mounted
properly and it's now running it as I type this.  The hardware specs are:

Intel Pentium 233 CPU
96 MB SDRAM
1- 4 Gig hard drive(HDA)- reiserfs with /boot and / mounted
1- 4 GIg hard drive(HDB)- reiserfs with /usr and "linux swap" mounted
Sound blaster live audio pci
ATI rage pro 4 Meg video pci
ps2 MS intellimouse 
serial AT keyboard
FIC 503+ motherboard

The latest bios was installed on the motherboard(late 1999 vintage)

I wish I could give you more exact error codes, but I don't know how to do so
when I can't even mount lilo.  Perhaps I should attempt to install the cooker
version onto the 9.0 release, and check the error out.  But it's compiled for
the newer glib/gcc, so that may not be an option.. Hrm.  Maybe doing a "linux
single" load with a rescue floppy and attempt to /sbin/lilo -v.  That may work
much better methinks. 

Let me know if you need any more information.  I hope I'm the only one with this
issue.  The hardware is old, but that's what linux's main attractants.  It could
be a cpu bottleneck for the currently compiled lilo binary.  But that's a
layman's guess.  Take care.

John Heidingsfelder
[EMAIL PROTECTED]



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

Reply via email to