[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #19074] Grub: Boot into Suse Linux 10.2 fails on dual OS PC

From: Evita Wagner
Subject: [bug #19074] Grub: Boot into Suse Linux 10.2 fails on dual OS PC
Date: Sat, 17 Feb 2007 21:29:57 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20061023 SUSE/2.0-30 Firefox/2.0


                 Summary: Grub: Boot into Suse Linux 10.2 fails on dual OS PC
                 Project: GNU GRUB
            Submitted by: ewagner
            Submitted on: Saturday 02/17/2007 at 21:29
                Category: Booting
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Private
             Assigned to: None
         Originator Name: Evita Wagner
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: Grub 0.97
         Reproducibility: Every Time
         Planned Release: 




I recently installed openSuse 10.2 as a secondary system on my machine. I
installed grub later and I'm happy to say that the selection between Suse and
my Windows XP works. However, when trying to boot into Suse, I got an error
message "error 19: linux kernel must be loaded before initrd - press any key
to continue". The only way for me to boot into Suse was by way of the
installation DVD.

I messed around with Grub under Linux quite a bit (including adding the path
for the Linux kernel and the initial ram disk), but this didn't relieve the
problem. I only later checked the menu.lst file and found that the initrd
line was written in the file BEFORE the kernel path line (which didn't really
make sense considering the error message I used to get).

I switched both lines around and everything works great now.

My suspicion is that Grub writes the two lines in the wrong order into the
menu.lst file (the form on the grub interface also asks for the initial ram
disk path before asking for the kernel path).

I'm new to Linux and I'm unsure if there isn't more to the problem, but if
not, that should be an easy fix.




Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]