All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David A. Cobb" <superbiskit@cox.net>
To: "GRUB (2) Developers List" <grub-devel@gnu.org>
Subject: A strange occurrence
Date: Tue, 16 Jun 2009 14:20:20 -0400	[thread overview]
Message-ID: <4A37E264.4060501@cox.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]

  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.


[-- Attachment #2: superbiskit.vcf --]
[-- Type: text/x-vcard, Size: 271 bytes --]

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


             reply	other threads:[~2009-06-16 18:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 18:20 David A. Cobb [this message]
2009-06-16 18:30 ` A strange occurrence Felix Zielcke
2009-06-17 18:48   ` David A. Cobb
2009-06-16 19:38 ` BandiPat
2009-06-16 19:41   ` Vladimir 'phcoder' Serbinenko
2009-06-16 19:59     ` BandiPat
2009-06-16 19:55       ` Felix Zielcke
2009-06-16 21:39         ` BandiPat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A37E264.4060501@cox.net \
    --to=superbiskit@cox.net \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.