Subject: LILO woes.
        Date: Fri, Mar 27, 1998 at 12:45:28AM -0500

In reply to:Nathan C. Burnett

Quoting Nathan C. Burnett([EMAIL PROTECTED]):
> 
> I have a non-fatal albeit annoying problem.  I'm running debian 1.3 and I
> absolutly cannot get LILO to work properly.  When the machine starts to
> boot the 'LI' shows up the the machine locks (have to use the reset button
> ctrl-alt-del doesn't work).  The LILO is version 19.  
> 
> I'm running a Cyrix 6x86MX, with a 2.1 GB samsung (I think) HD on a
> Matsonic MS-5120 motherboard, which incidentally came with a really weak
> manual so I don't know what IDE chipset it uses...
> 
> When I had RedHat 5 installed on this machine LILO 20 worked fine.
> 
> 
> My lilo.conf looks like:
> 
> 
> boot=/dev/hda1
> root=/dev/hda1
> compact
> install=/boot/boot.b
> map=/boot/map
> vga=normal
> prompt
> timeout = 50
> 
> image=/vmlinuz
>    label=Linux
>    read-only
> image=/vmlinuz.old
>    label=old
>    read-only
> 
> 
> Any ideas?
> 
> Tnx, Nate
> 

  Nate

  Here is my lilo.conf. which is somewhat different then yours. ( it
works too).
    #LILO configuration file
    # generated by 'liloconfig'
    #
    # Start LILO global section
 boot = /dev/hda
    #read-only
    #compact        # faster, but won't work on all systems.
 prompt
 vga = normal    # force sane state
    # ramdisk = 0     # paranoia setting
    # End LILO global section
    # Linux bootable partition config begins
 image = /vmlinuz
 root = /dev/hda1
 label = slack33
    # read-only # Non-UMSDOS filesystems should be mounted read-only for
    # checking
    # Linux bootable partition config ends
    # Linux bootable partition config begins
 image = /vmlinuz
 root = /dev/hda2
 label = debian13
    #   

HTH

> 
> ---
> Nathan C. Burnett              "Everyone is born right-handed, but 
> [EMAIL PROTECTED]                      only the greatest overcome it."
> http://www.cps.msu.edu/~burnet26    -Slogan, Left-Handers' Club of Ireland
>             ( ( (((In Stereo Where Available))) ) )
> 
> 
> 
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
> 
> .

-- 
The problem with program verifiers is that they tend to cheat at toy
problems in order to get results.
_______________________________________________________
Wayne T. Topa <[EMAIL PROTECTED]>


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to