From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KLI0t-0000vz-Vz for mharc-grub-devel@gnu.org; Tue, 22 Jul 2008 09:34:48 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KLI0s-0000vN-21 for grub-devel@gnu.org; Tue, 22 Jul 2008 09:34:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KLI0q-0000ue-IZ for grub-devel@gnu.org; Tue, 22 Jul 2008 09:34:45 -0400 Received: from [199.232.76.173] (port=40629 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KLI0q-0000uM-9k for grub-devel@gnu.org; Tue, 22 Jul 2008 09:34:44 -0400 Received: from mail.gmx.net ([213.165.64.20]:38806) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1KLI0p-0007To-FP for grub-devel@gnu.org; Tue, 22 Jul 2008 09:34:44 -0400 Received: (qmail invoked by alias); 22 Jul 2008 13:34:38 -0000 Received: from unknown (EHLO archvile.hell) [92.117.71.150] by mail.gmx.net (mp032) with SMTP; 22 Jul 2008 15:34:38 +0200 X-Authenticated: #20154811 X-Provags-ID: V01U2FsdGVkX1/NKLV+Ja3NkLI9f0o8lUxC6ydAhrY2FKVMMULthA +xDx/wdTWepKx+ Received: by archvile.hell (Postfix, from userid 1000) id 2DE1642447D; Tue, 22 Jul 2008 15:34:16 +0200 (CEST) Date: Tue, 22 Jul 2008 15:34:16 +0200 From: Andy Kittner To: grub-devel@gnu.org Message-ID: <20080722133416.GB5524@archvile> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-07-21) X-Y-GMX-Trusted: 0 X-FuHaFi: 0.53 X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) Subject: Issue with boot != root and chainloading 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: Tue, 22 Jul 2008 13:34:46 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all, First of all I hope I've come to the right place with my little bug=20 (from what I've read this list seems to be preferred to the tracker?). Anyway here it goes: I have two hard drives in my notebook, and tried=20 installing grub (svn r1724) with it's root on the second one (/dev/sdb5=20 to be precise) grub-install /dev/sda Everything went smooth, however after rebooting I get dropped in rescue=20 mode with this message: "unknown device fd1,5" As I had a bit of free time I investigated where the fd1 might come=20 =66rom and it turned out that grub_root_device seems to contain a wrong=20 value: diff --git a/grub2/kern/i386/pc/init.c b/grub2/kern/i386/pc/init.c index e47cbfd..01e8d7d 100644 --- a/grub2/kern/i386/pc/init.c +++ b/grub2/kern/i386/pc/init.c @@ -236,8 +236,10 @@ grub_machine_init (void) void grub_machine_set_prefix (void) { + char *prefix =3D make_install_device(); /* Initialize the prefix. */ - grub_env_set ("prefix", make_install_device ()); + grub_env_set ("prefix", prefix); + grub_printf("0x%x, 0x%x, %s\n", grub_boot_drive, grub_root_drive, prefix= ? prefix : ""); } =20 void With this patch it prints "0x80, 0x1, (fd1,5)/boot/grub/" and I presume the 0x1 should actually be a 0x81, however I have no clue=20 why it is wrong and as it seems to be initialized in startup.S I thought=20 I'd leave it to the experts at this point.=20 After: set prefix=3D(hd1,5)/boot/grub set root=3D(hd1,5) insmod normal normal I end up in the menu and can boot my linux kernels just fine. Now for my second problem: If I try to chainload grub legacy on another partition it just hangs=20 after printing "GRUB ". The command I used to do this was: chainloader (hd0,5)+1 Chainloading my windows partition using: chainloader (hd0,1)+1 has a similar result, namely a blank screen with a blinking cursor. I would need some advice on how to debug this, but I guess the first=20 interesting bit would be if this is broken for others as well, or just=20 a peculiarity of my system. Best regards Andy --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkiF4dcACgkQp/ooA5on7H5W2gCgqNe/AXKTiBtE9a/6tX9YPlNs XcUAnA1wCYDmM6/xHDewDNWeqPSMJlqH =1Kc/ -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--