[SLE] Messed up my bootloader

From: Trey Sizemore (trey_at_fastmail.fm)
Date: 02/28/04

  • Next message: McAllister, Andrew: "[SLE] mtrr: type mismatch for fd000000,800000 old: write-back new: write-combining" 
    To: "SuSE-Linux-English" <suse-linux-e@suse.com>
Date: Fri, 27 Feb 2004 18:58:14 -0800

    I was attempting to get my machine to multiboot with a few Linux OSs and
    Win2000. I have SUSE 9.0 installed and successfully triple booting Win2000
    and Mandrake 10 beta 2 with grub on the MBR. I installed Arch Linux as well,
    but inadvertantly had lilo installed as well (on the MBR) such that now when
    I start the machine I only get lilo and the ability to log into arch.

    So I edited my lilo.conf and added the following entry thinking I would be
    able to log back into SUSE and add grub back to the MBR with an entry for
    Arch:

    #
    # /etc/lilo.conf
    #

    boot=/dev/discs/disc0/disc
    # This line often fixes L40 errors on bootup
    # disk=/dev/discs/disc0/disc bios=0x80

    default=arch
    timeout=50
    lba32
    prompt

    image=/boot/vmlinuz26
            label=arch
            root=/dev/discs/disc0/part11
            read-only

    image=/boot/vmlinuz
            label=suse
            root=/dev/discs/disc0/part7
            read-only

    #other=/dev/discs/disc0/part1
    # label=dos

    # End of file

    However, I get a kernel panic when I select the suse option in lilo when it
    gets to the point of loading the kernel. I have Win2000 on /dev/hda1,
    a /data1 SUSE partition on hda5, swap on hda6, and my 48Gb root SUSE
    partition on hda7.

    Any help getting this back is greatly appreciated 

    -- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: McAllister, Andrew: "[SLE] mtrr: type mismatch for fd000000,800000 old: write-back new: write-combining"

    Relevant Pages