From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1JLi5z-00086g-C6 for mharc-grub-devel@gnu.org; Sun, 03 Feb 2008 11:53:31 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JLi5y-00086E-64 for grub-devel@gnu.org; Sun, 03 Feb 2008 11:53:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JLi5w-00085w-FV for grub-devel@gnu.org; Sun, 03 Feb 2008 11:53:29 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JLi5w-00085t-D5 for grub-devel@gnu.org; Sun, 03 Feb 2008 11:53:28 -0500 Received: from ns39764.ovh.net ([91.121.25.85] helo=nexedi.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JLi5w-0000Z0-6B for grub-devel@gnu.org; Sun, 03 Feb 2008 11:53:28 -0500 Received: from [10.8.0.46] (unknown [10.8.0.46]) by nexedi.com (Postfix) with ESMTP id 889123EB23 for ; Sun, 3 Feb 2008 18:00:14 +0100 (CET) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Sun, 3 Feb 2008 17:53:23 +0100 User-Agent: KMail/1.9.4 References: <47A4E372.2050000@comcast.net> <47A5D3F5.8030009@comcast.net> <20080203151843.GA1863@thorin> In-Reply-To: <20080203151843.GA1863@thorin> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802031753.23905.okuji@enbug.org> X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) Subject: Re: root seems to be incorrectly set after install X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2008 16:53:30 -0000 On Sunday 03 February 2008 16:18, Robert Millan wrote: > On Sun, Feb 03, 2008 at 09:47:17AM -0500, George Lengel wrote: > > Dear Robert, > > > > I now get a 0x80 at the top of the screen just before the rescue mode > > line. This indicates I am using my compiled version and also confirms > > your suspicion about the BIOS, right? > > > > >What version of GRUB Legacy did you install in that system? Did you > > > modify GRUB Legacy when you installed it, or something like that? > > > > I use Grub legacy from Debian which is 0.97. It has worked for years and > > years without any problem and I never did anything past a simple apt-get > > and accept the defaults when configuring it. > > Can you check if you can override the root device by invoking grub-setup > manually with --root-device parameter? I have looked at this problem deeply, and I think the following changes would be required: - A variable to specify where grub.cfg and modules are present. Currently, we have it only for a prefix without a drive. So grub_root_drive or something must be added. It could be added to kern/i386/pc/startup.S, but boot/i386/pc/boot.S might be more appropriate (if there is space large enough). - grub-setup must handle a root drive independently, of a boot drive or an embedding drive. - kern/i386/pc/init.c must be modified accordingly. The scinarii would be the following: - If a core image is embedded, and a grub directory is in the same drive, all drives should be set to -1, thus a boot drive passed by BIOS or another boot loader will be used. - If a core image is embedded, and a grub directory is in a different drive, a root drive must be explicitly set by grub-setup. The other drives will be set by BIOS or another boot loader. - If a core image is not embedded, and it is in the same drive, the same as the first example. - If a core image is not embedded, and it is in a different drive, an embedding drive is identical to a root drive, and must be set explicitly by grub-setup. I am planning to fix it myself, but if I look too slow, please feel free to fix it instead of me. Okuji