From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MGdHc-0007iR-Q2 for mharc-grub-devel@gnu.org; Tue, 16 Jun 2009 14:21:20 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MGdHa-0007hf-1a for grub-devel@gnu.org; Tue, 16 Jun 2009 14:21:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MGdHU-0007h5-Cp for grub-devel@gnu.org; Tue, 16 Jun 2009 14:21:16 -0400 Received: from [199.232.76.173] (port=55282 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MGdHU-0007h2-8R for grub-devel@gnu.org; Tue, 16 Jun 2009 14:21:12 -0400 Received: from eastrmmtao102.cox.net ([68.230.240.8]:48068) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MGdHT-0007Fh-Ti for grub-devel@gnu.org; Tue, 16 Jun 2009 14:21:12 -0400 Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmmtao102.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090616182109.DMIA14603.eastrmmtao102.cox.net@eastrmimpo02.cox.net> for ; Tue, 16 Jun 2009 14:21:09 -0400 Received: from [192.168.1.100] ([68.14.70.222]) by eastrmimpo02.cox.net with bizsmtp id 4iM91c0044nkWJk02iM9FR; Tue, 16 Jun 2009 14:21:09 -0400 X-VR-Score: -100.00 X-Authority-Analysis: v=1.0 c=1 a=uHfhhrM5HOgA:10 a=-KfIiNIlv0bUI9R5zCUA:9 a=R70mUrc5xkX85u3ivsw3K06En-wA:4 a=kviXuzpPAAAA:8 a=43v4sowt3QhGLaZ4CcEA:9 a=xqMMH8d9pVlAYqU8Ut-Tja30ioIA:4 a=sRbc0tItu94A:10 a=MNcmkZiEQYQA:10 a=bUBOKfpOkEEA:10 a=4vB-4DCPJfMA:10 X-CM-Score: 0.00 Message-ID: <4A37E264.4060501@cox.net> Date: Tue, 16 Jun 2009 14:20:20 -0400 From: "David A. Cobb" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090613 Shredder/3.1a1pre MIME-Version: 1.0 To: "GRUB (2) Developers List" Content-Type: multipart/mixed; boundary="------------080602060203050204020603" X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) Subject: A strange occurrence 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, 16 Jun 2009 18:21:18 -0000 This is a multi-part message in MIME format. --------------080602060203050204020603 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit This isn't a development question, but I'm hoping the list's knowledge of GRUB will help me understand it. Running Ubuntu 9.04, everything up-to-date, package "grub-pc" version 1.96+ GRUB-2 was installed after having GRUB 0.9x running for years. The installation involved letting GRUB chainload GRUB-2 until I saw it was ready for primetime, then running an upgrade script. I mention that because it's important to know that there is still a GRUB 0.9x image somewhere. Trying to get past a nasty problem involving the interaction between a 2003 Phoenix BIOS, and a big 160-GB disk that would not have been available in 2003. I used BIOS setup to change the disk detection to manual, and made sure the numbers that came up were the same as after a successful boot. Booted, and WHOA! I got the system-selection screen from GRUB 0.9x. But, it included versions of the kernel that were not installed until after I switched to GRUB-2. Actually, the only thing I'm sure was "wrong" was the lack of a colorful splash image. Well, no, actually, I'm fairly sure the console displays were not the same as the "WELCOME TO GRUB" that shows at the start of the GRUB-2 boot; but it goes past pretty quick, and I could be wrong about that. So, maybe I hosed my GRUB-2 installation. That wouldn't explain how a GRUB 0.9x image was found. Anyway, I re-installed the package and (re)ran grub-install. And rebooted. And got the same screen. So, eliminate the one variable I knew was changed: I reset the BIOS Setup to do automatic disk detection. Voilla!! I'm back with the GRUB-2 splash screen, and everything is cool. But, I'm puzzled [yeah, that is my normal state]. Did the BIOS actually read a different image? Or, did the "old" GRUB fail to chainload, even though there is no visible sign during a normal boot that the old GRUB is still around? If the latter, should I consider writing the GRUB-2 image onto the MBR again? Or, would that be just asking for trouble? TIA -- David A. Cobb, computing t-rex. --------------080602060203050204020603 Content-Type: text/x-vcard; charset=utf-8; name="superbiskit.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="superbiskit.vcf" begin:vcard fn:David A. Cobb n:Cobb;David A. email;internet:superbiskit@cox.net tel;home:+1-401-615-3895 tel;cell:+1-401-301-2207 note;quoted-printable:Semi-retired T-Rex Mainframe Programmer=0D=0A= Orthodox Christian=0D=0A= x-mozilla-html:TRUE version:2.1 end:vcard --------------080602060203050204020603--