9:43 a.m.
Hi;
I have started this thread again as a new thread. The previous "Double
checking grub-install ??" lead off in all kinds of plausible directions.
I think I now have more of a focus.
To recap:
I am getting a double Fedora grub splashimage at boot. I have a dual
boot system with WindowsXP on sda and Fedora 9 on sdb. I have some
experience with installing grub but made a typo type mistake during a
grub install a month ago and I think (??) that might have been the root
of my double splashimage problem.
To check the mbr, I ran on /dev/sda:
~]# dd bs=512 count=1 if=/dev/sda | od -Ax -tx1z -v
it returned:
...
000160 7c be 85 7d e8 40 00 eb 0e be 8a 7d e8 38 00 eb
|..}.@.....}.8..<
000170 06 be 94 7d e8 30 00 be 99 7d e8 2a
00 eb fe 47
...}.0...}.*...G<
000180 52 55 42 20 00 47 65 6f 6d 00 48 61
72 64 20 44 >RUB .Geom.Hard
D<
000190 69 73 6b 00 52 65 61 64 00 20 45 72 72 6f 72 00 >isk.Read.
Error.<
0001a0 bb 01 00 b4 0e cd 10 ac 3c 00 75 f4 c3 00 00 00
........<.u.....<
...
[Notice the GRUB string on the second and third line and Error on the
fourth line]
Then, I ran on /dev/sdb:
]# dd bs=512 count=1 if=/dev/sdb | od -Ax -tx1z -v
it returned:
...
000160 7c be 85 7d e8 40 00 eb 0e be 8a 7d e8 38 00 eb
|..}.@.....}.8..<
000170 06 be 94 7d e8 30 00 be 99 7d e8 2a
00 eb fe 47
...}.0...}.*...G<
000180 52 55 42 20 00 47 65 6f 6d 00 48 61
72 64 20 44 >RUB .Geom.Hard
D<
000190 69 73 6b 00 52 65 61 64 00 20 45 72 72 6f 72 00 >isk.Read.
Error.<
0001a0 bb 01 00 b4 0e cd 10 ac 3c 00 75 f4 c3 00 00 00
........<.u.....<
...
[Notice the GRUB string on the second and third line as well, and Error
on the fourth line]
Could this double grub be the source of my problem ?
If it is, how do I remove it (from sdb -- I presume)?
Others have suggested that the double splashimage is just a video mode
switch but then how do I account for the grub appearing on both mbr's
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
10:32 a.m.
On Wed, 02 Jul 2008 10:43:04 -0400, William Case wrote:
Hi;
I have started this thread again as a new thread. The previous "Double
checking grub-install ??" lead off in all kinds of plausible directions.
I think I now have more of a focus.
To recap:
I am getting a double Fedora grub splashimage at boot.
What exactly does that mean?
Can you hit keys to enter the first GRUB menu and stop it
from booting any entry automatically?
I have a dual
boot system with WindowsXP on sda and Fedora 9 on sdb.
And what does your boot sequence look like? NTLDR on sda?
Do you chainload from sda into sdb?
And what does your sdb GRUB config look like? Is it really
GRUB in the MBR of sdb instead of the boot sector of your
boot/root partition?
I have some
experience with installing grub but made a typo type mistake during a
grub install a month ago and I think (??) that might have been the root
of my double splashimage problem.
To check the mbr, I ran on /dev/sda:
~]# dd bs=512 count=1 if=/dev/sda | od -Ax -tx1z -v
it returned:
...
000160 7c be 85 7d e8 40 00 eb 0e be 8a 7d e8 38 00 eb
>|..}.@.....}.8..<
What does it print for the line at offset 0?
12:56 p.m.
On Wed, 2008-07-02 at 19:35 +0200, Michael Schwendt wrote:
On Wed, 02 Jul 2008 12:50:31 -0400, William Case wrote:
> I checked and low and behold I found GRUB listed in the first block
> (mbr ??) of both disks. So I thought I should chase that down before I
> filed an inappropriate bug report.
Then what happens if you overwrite sda's mbr with NTLDR?
To me it is still not clear what your boot sequence looks like.
You say this is a dual-boot machine. Unless you prefer ntldr, you
would store grub in sda. However, you say you store it in sdb.
So, how exactly do you boot? Do you really chainload sdb from sda?
Sorry Michael, I was trying to avoid re-telling a long tale of woe.
Here it is;
About four weeks ago my commercial boot loader (BootMagic) was blown
away by the WindowsXP sp3 download and install. Fine and good: that
didn't surprise me -- it was an old version of BootMagic kept out of
stubbornness. I had paid for it before I started using Linux so I was
going to use it.
I had climbed the grub learning curve a couple of years ago, so I am
fairly confident about using the grub shell or grub-install.
When BootMagic was blown away, I just installed grub. During a first
attempt at a grub install I had an ooops! So I just re-installed grub
and everything seemed fine. The intent was to install grub on /dev/sda
dual booting to sdb /boot. (BIOS loads in the natural hd0, hd1 order.)
Because it was an oops (typo) and not a confusion, I didn't pay
attention to the mistake, so now a month later I have forgotten exactly
what I did wrong. Besides I thought I had recovered.
About a week ago (I don't re-boot very often), I noticed the Fedora
grub splash screen appear for 1/2 second or less, then go blank and
pause for a second or two. Then a new splash screen appeared and
everything progressed fine from there. This occurs definitely during
the grub stage of bootup.
I didn't do anything then because I was going to fresh install Fedora 9
with a new grub. Which I have done. But the double splash screen still
appears.
To add to the confusion, I installed a new motherboard with a new and
different video chip three months ago. Since I don't boot often, I
could have not noticed the double splashimage for some time. This would
support the changing video mode suggestion.
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
2:02 p.m.
Hi Michael;
On Wed, 2008-07-02 at 19:54 +0200, Michael Schwendt wrote:
On Wed, 02 Jul 2008 13:10:29 -0400, William Case wrote:
> > Can you hit keys to enter the first GRUB menu and stop it
> > from booting any entry automatically?
> No. The image is incomplete in the first instance and disappers too
> quickly.
Can you influence it by editing /boot/grub/grub.conf and
- disabling the splash image
commenting-out splashimage produces a grub basic menu
without double
loading.
- disabling the hidden menu
commenting hiddenmenu or not, does not prevent the loading of a double
splashimage.
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
11:35 p.m.
Hi Tim;
On Thu, 2008-07-03 at 13:28 +0930, Tim wrote:
On Wed, 2008-07-02 at 10:43 -0400, William Case wrote:
> If it is, how do I remove it (from sdb -- I presume)?
Extra stuff shouldn't matter, if you configure the first thing to take
over.
i.e. I can have ten discs in a box, GRUB on all of them. But if the
first thing the BIOS does is read GRUB on the first drive, and that then
loads the next stage properly, it doesn't matter what's on any other
drive.
Did you do what I suggested, long ago, issuing manual GRUB commands to
set up your system? (i.e. NOT using grub-install script).
No, I haven't yet. I will in the morning. I am not arguing with your
suggestion. I, in fact, saved those instructions and went back to the
manual to make sure I thoroughly understood what I was doing. I will
use them in the morning.
If you remember, except for the double splashimage, my system is booting
as it should. Rather than simply getting things to work, the challenge
to me over the last couple of days has been to fully understand what has
been happening. I have managed to dig into the workings of the mbr,
grub stages, video modes much deeper than if I had simply left things as
a booting problem to fix. As I have said, I have climbed the grub
learning curve in the past. This time I wanted to take an active role
in actually undoing something or fixing something.
grub
root (hd..... (where /boot is)
setup (hd.... (where BIOS starts to boot from)
quit (write the changes)
Perhaps I am being just a bit stubborn, but I wanted to learn how to
diagnose the problem first, not just write something over top of it.
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
5:52 a.m.
On Thu, 2008-07-03 at 00:35 -0400, William Case wrote:
Perhaps I am being just a bit stubborn, but I wanted to learn how to
diagnose the problem first, not just write something over top of it.
Understanding what's going on is fine, and good. I don't discount the
importance of it.
The solution for a duff MBR is to rewrite the MBR with what you want.
You don't uninstall an unwanted bootloader, you put another boot record
(that you want) over the top.
--
[tim@localhost ~]$ uname -r
2.6.25.9-76.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
2:13 p.m.
New subject: Double checking grub-install -- [SOLVED]
For those who helped.
On Thu, 2008-07-03 at 13:58 -0400, William Case wrote:
Hi Tim and others who may have been watching this thread.
[snip]
So the answer must be grub is switching video modes.
I wonder if I should report this as a Fedora bug against grub ?
I bought a new Samsung LCD display, plugged it in as a DVI. Double grub
splash screen went away.
That's that.
--
Regards Bill;
Fedora 9, Gnome 2.22.3
Evo.2.22.3.1, Emacs 22.2.1
2:13 p.m.
On Wed, 02 Jul 2008 14:33:10 -0400, William Case wrote:
the video mode problem seems to be with grub2 -- not
grub-0.97-33.fc9.x86_64
?? Can't comment on grub2 yet as I've seen it only once or twice, I think,
and it's a different code base. Your recent description of the symptoms
sounds like the image data are loaded prior to setting a video mode.
That's something to report to grub2 upstream, especially if Fedora 9's
grub works for you.
12:58 p.m.
New subject: Double checking grub-install -- LAST POST
Hi Tim and others who may have been watching this thread.
On Thu, 2008-07-03 at 20:22 +0930, Tim wrote:
On Thu, 2008-07-03 at 00:35 -0400, William Case wrote:
> Perhaps I am being just a bit stubborn, but I wanted to learn how to
> diagnose the problem first, not just write something over top of it.
Understanding what's going on is fine, and good. I don't discount the
importance of it.
The solution for a duff MBR is to rewrite the MBR with what you want.
You don't uninstall an unwanted bootloader, you put another boot record
(that you want) over the top.
Messed around a bit more; but the final outcome was the double
splashimages continue:
1) I ran "fixmbr" from my WindowsXP istallation/rescue disk.
in case there was some ghost of something left over from BootMagic.
2) then, I ran from my Fedora installation/rescue disk
on the rescue command line:
grub
root (hd1,4)
setup (hd0)
quit
Everything grub-like installed fine.
So the answer must be grub is switching video modes.
I wonder if I should report this as a Fedora bug against grub ?
I seem to be the only one with this issue -- and it is not a major
issue, just something I was hoping to clean up.
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
10:58 p.m.
On Wed, 2008-07-02 at 10:43 -0400, William Case wrote:
If it is, how do I remove it (from sdb -- I presume)?
Extra stuff shouldn't matter, if you configure the first thing to take
over.
i.e. I can have ten discs in a box, GRUB on all of them. But if the
first thing the BIOS does is read GRUB on the first drive, and that then
loads the next stage properly, it doesn't matter what's on any other
drive.
Did you do what I suggested, long ago, issuing manual GRUB commands to
set up your system? (i.e. NOT using grub-install script).
grub
root (hd..... (where /boot is)
setup (hd.... (where BIOS starts to boot from)
quit (write the changes)
--
[tim@localhost ~]$ uname -r
2.6.25.6-55.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
4 p.m.
Hi;
On Wed, 2008-07-02 at 14:33 -0400, William Case wrote:
On Wed, 2008-07-02 at 13:15 -0500, Mikkel L. Ellertson wrote:
> William Case wrote:
> > Hi Mikkel;
> >
[snip]
Just to see what happens how would I go about safely removing the stage1
of Grub from /dev/sdb ??
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
3:50 p.m.
On Wed, 2008-07-02 at 21:13 +0200, Michael Schwendt wrote:
On Wed, 02 Jul 2008 14:33:10 -0400, William Case wrote:
> the video mode problem seems to be with grub2 -- not
> grub-0.97-33.fc9.x86_64
?? Can't comment on grub2 yet as I've seen it only once or twice, I think,
and it's a different code base. Your recent description of the symptoms
sounds like the image data are loaded prior to setting a video mode.
That's something to report to grub2 upstream, especially if Fedora 9's
grub works for you.
You got it backwards. I was saying I don't have grub2, that is why I am
persisting with solving this problem. Fedora 9's grub isn't working for
me!
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
1:33 p.m.
On Wed, 2008-07-02 at 13:15 -0500, Mikkel L. Ellertson wrote:
William Case wrote:
> Hi Mikkel;
>
>>
> Yes. And that was where I was going to leave it. There was a suggestion
> on the list that I should file a bug against grub. I was about to do
> that this morning and thought that I should check the first 512 bytes of
> each disk just to be sure.
>
> I checked and low and behold I found GRUB listed in the first block
> (mbr ??) of both disks. So I thought I should chase that down before I
> filed an inappropriate bug report.
>
This should not be a problem. Because the part of Grub on the MBR
does not display anything - it just loads the next part of Grub.
I understand the difference between stage1, (stage1_5) and stage2.
The
MBR on the second hard disk would not be used unless it was chained
to by another copy of Grub,
That is the only possiblity left, I would think. In all the searching I
have done, the video mode problem seems to be with grub2 -- not
grub-0.97-33.fc9.x86_64
or if you tell the BIOS to boot from the
second hard drive instead of the first. (Or if you swap the drives,
or remove the first drive...)
>
>> Didn't the problem go away when you turned off the splash screen,
>> and ran Grub in the text mode?
>>
> Yes, it does. Which makes the problem a Fedora grub problem, not just a
> grub problem -- I would think.
>
Unless Fedora modified Grub to use splash images, it would be a Grub
problem. It may be specific to your hardware combination.
I believe Fedora has substituted it's own splashimage, at least the
splash image has the Fedora colours and logo + containing the grub menu
selection rectangle .
Mikkel
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
1:23 p.m.
Hi Michael;
On Wed, 2008-07-02 at 20:10 +0200, Michael Schwendt wrote:
On Wed, 02 Jul 2008 13:56:20 -0400, William Case wrote:
> On Wed, 2008-07-02 at 19:35 +0200, Michael Schwendt wrote:
> > On Wed, 02 Jul 2008 12:50:31 -0400, William Case wrote:
> >
> > > I checked and low and behold I found GRUB listed in the first block
> > > (mbr ??) of both disks. So I thought I should chase that down before I
> > > filed an inappropriate bug report.
> >
> > Then what happens if you overwrite sda's mbr with NTLDR?
> >
> > To me it is still not clear what your boot sequence looks like.
> >
> > You say this is a dual-boot machine. Unless you prefer ntldr, you
> > would store grub in sda. However, you say you store it in sdb.
> > So, how exactly do you boot? Do you really chainload sdb from sda?
> >
> Sorry Michael, I was trying to avoid re-telling a long tale of woe.
>
> Here it is;
A long tale, but the details are missing.
To reinstall grub, you run "grub-install /dev/sda", right?
Yes that was the intent and that was what I used on the second attempt.
I might have mis-typed "grub-install /dev/sdb" the first time by
mistake.
And what do /boot/grub/grub.conf and /boot/grub/device.map contain?
/boot/grub/grub.conf is as it should be:
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,4)/grub/splash.xpm.gz
## hiddenmenu
title Fedora (2.6.25.6-55.fc9.x86_64)
root (hd1,4)
kernel /vmlinuz-2.6.25.6-55.fc9.x86_64 ro
root=UUID=884ffe2a-42ff-4835-bf57-b80bc45c3baa rhgb quiet
initrd /initrd-2.6.25.6-55.fc9.x86_64.img
title Fedora (2.6.25-14.fc9.x86_64)
root (hd1,4)
kernel /vmlinuz-2.6.25-14.fc9.x86_64 ro
root=UUID=884ffe2a-42ff-4835-bf57-b80bc45c3baa rhgb quiet
initrd /initrd-2.6.25-14.fc9.x86_64.img
title WindowsXP sp3
rootnoverify (hd0,0)
chainloader +1
and /boot/grub/device.map is:
# this device map was generated by anaconda
(hd0) /dev/sda
(hd1) /dev/sdb
> and everything seemed fine. The intent was to install grub on /dev/sda
> dual booting to sdb /boot. (BIOS loads in the natural hd0, hd1 order.)
Still, one question remains. With grub in the mbr of sda, how do
you boot from sdb? Do you point grub.conf to your /boot partition?
Yes.
Or perhaps you do some unusual chain-loading to the mbr of sdb?
Perhaps -- inadvertently. That is what I am trying to ascertain and solve.
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
1:15 p.m.
William Case wrote:
Hi Mikkel;
> If I remember correctly from the first thread, you would get a brief
> flash on the screen with Fedora at the top of the screen, a short
> pause, and then the proper splash screen with Fedora on the bottom.
> This is a good indication that ether the video card or the monitor
> are changing modes to properly display the splash screen. I would
> suspect that it is the monitor changing modes to match the video output.
>
Yes. And that was where I was going to leave. There was a suggestion
on the list that I should file a bug against grub. I was about to do
that this morning and thought that I should check the first 512 bytes of
each disk just to be sure.
I checked and low and behold I found GRUB listed in the first block
(mbr ??) of both disks. So I thought I should chase that down before I
filed an inappropriate bug report.
This should not be a problem. Because the part of Grub on the MBR
does not display anything - it just loads the next part of Grub. The
MBR on the second hard disk would not be used unless it was chained
to by another copy of Grub, or if you tell the BIOS to boot from the
second hard drive instead of the first. (Or if you swap the drives,
or remove the first drive...)
> Didn't the problem go away when you turned off the splash screen,
> and ran Grub in the text mode?
>
Yes, it does. Which makes the problem a Fedora grub problem, not just a
grub problem -- I would think.
Unless Fedora modified Grub to use splash images, it would be a Grub
problem. It may be specific to your hardware combination.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
1:10 p.m.
On Wed, 02 Jul 2008 13:56:20 -0400, William Case wrote:
On Wed, 2008-07-02 at 19:35 +0200, Michael Schwendt wrote:
> On Wed, 02 Jul 2008 12:50:31 -0400, William Case wrote:
>
> > I checked and low and behold I found GRUB listed in the first block
> > (mbr ??) of both disks. So I thought I should chase that down before I
> > filed an inappropriate bug report.
>
> Then what happens if you overwrite sda's mbr with NTLDR?
>
> To me it is still not clear what your boot sequence looks like.
>
> You say this is a dual-boot machine. Unless you prefer ntldr, you
> would store grub in sda. However, you say you store it in sdb.
> So, how exactly do you boot? Do you really chainload sdb from sda?
>
Sorry Michael, I was trying to avoid re-telling a long tale of woe.
Here it is;
A long tale, but the details are missing.
To reinstall grub, you run "grub-install /dev/sda", right?
And what do /boot/grub/grub.conf and /boot/grub/device.map contain?
and everything seemed fine. The intent was to install grub on
/dev/sda
dual booting to sdb /boot. (BIOS loads in the natural hd0, hd1 order.)
Still, one question remains. With grub in the mbr of sda, how do
you boot from sdb? Do you point grub.conf to your /boot partition?
Or perhaps you do some unusual chain-loading to the mbr of sdb?
12:54 p.m.
On Wed, 02 Jul 2008 13:10:29 -0400, William Case wrote:
> Can you hit keys to enter the first GRUB menu and stop it
> from booting any entry automatically?
No. The image is incomplete in the first instance and disappers too
quickly.
Can you influence it by editing /boot/grub/grub.conf and
- disabling the splash image
- disabling the hidden menu
?
12:35 p.m.
On Wed, 02 Jul 2008 12:50:31 -0400, William Case wrote:
I checked and low and behold I found GRUB listed in the first block
(mbr ??) of both disks. So I thought I should chase that down before I
filed an inappropriate bug report.
Then what happens if you overwrite sda's mbr with NTLDR?
To me it is still not clear what your boot sequence looks like.
You say this is a dual-boot machine. Unless you prefer ntldr, you
would store grub in sda. However, you say you store it in sdb.
So, how exactly do you boot? Do you really chainload sdb from sda?
12:10 p.m.
On Wed, 2008-07-02 at 17:32 +0200, Michael Schwendt wrote:
On Wed, 02 Jul 2008 10:43:04 -0400, William Case wrote:
> Hi;
>
> I have started this thread again as a new thread. The previous "Double
> checking grub-install ??" lead off in all kinds of plausible directions.
> I think I now have more of a focus.
>
> To recap:
>
> I am getting a double Fedora grub splashimage at boot.
What exactly does that mean?
About a week ago (I don't re-boot very often), I
noticed the Fedora
grub splash screen appear for 1/2 second or less, then go blank and
pause for a second or two. Then a new splash screen appeared and
everything progressed fine from there. This occurs definitely during
the grub stage of bootup.
Can you hit keys to enter the first GRUB menu and stop it
from booting any entry automatically?
No. The image is incomplete in the first
instance and disappers too
quickly.
> I have a dual
> boot system with WindowsXP on sda and Fedora 9 on sdb.
And what does your boot sequence look like? NTLDR on sda?
Do you chainload from sda into sdb?
And what does your sdb GRUB config look like? Is it really
GRUB in the MBR of sdb instead of the boot sector of your
boot/root partition?
> I have some
> experience with installing grub but made a typo type mistake during a
> grub install a month ago and I think (??) that might have been the root
> of my double splashimage problem.
>
> To check the mbr, I ran on /dev/sda:
> ~]# dd bs=512 count=1 if=/dev/sda | od -Ax -tx1z -v
>
> it returned:
> ...
> 000160 7c be 85 7d e8 40 00 eb 0e be 8a 7d e8 38 00 eb
> >|..}.@.....}.8..<
What does it print for the line at offset 0?
[root@CASE ~]# dd bs=512 count=1 if=/dev/sda | od -Ax -tx1z -v
1+0 records in
1+0 records out
512 bytes (512 B) copied, 6.288e-05 s, 8.1 MB/s
000000 eb 48 90 8e d0 bc 00 7c fb 8e d8 be 00 7c 8e c0
.H.....|.....|..<
000010 bf 00 06 b9 00 01 f3 a5 e9 00 8a be
ae 07 b9 04
................<
000020 00 83 c6 10 80 3c 80 74 09 80 3c 00
75 5d e2 f1
.....<.t..<.u]..<
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
11:50 a.m.
Hi Mikkel;
On Wed, 2008-07-02 at 10:54 -0500, Mikkel L. Ellertson wrote:
William Case wrote:
> Hi;
>
> I have started this thread again as a new thread. The previous "Double
> checking grub-install ??" lead off in all kinds of plausible directions.
> I think I now have more of a focus.
>
> To recap:
>
> I am getting a double Fedora grub splashimage at boot. I have a dual
> boot system with WindowsXP on sda and Fedora 9 on sdb. I have some
> experience with installing grub but made a typo type mistake during a
> grub install a month ago and I think (??) that might have been the root
> of my double splashimage problem.
>
If I remember correctly from the first thread, you would get a brief
flash on the screen with Fedora at the top of the screen, a short
pause, and then the proper splash screen with Fedora on the bottom.
This is a good indication that ether the video card or the monitor
are changing modes to properly display the splash screen. I would
suspect that it is the monitor changing modes to match the video output.
Yes. And that was where I was going to leave. There was a suggestion
on the list that I should file a bug against grub. I was about to do
that this morning and thought that I should check the first 512 bytes of
each disk just to be sure.
I checked and low and behold I found GRUB listed in the first block
(mbr ??) of both disks. So I thought I should chase that down before I
filed an inappropriate bug report.
While it will not prove this isn't the problem, it would be
interesting to see what happens if you log into the GUI, and then
hit Ctrl-Alt-F1 and see if you get the same kind behavior.
Ctrl-Alt-F1 gives me normal behaviour. No pauses or anything but
straight to:
Fedora 9 (Sulphur)
kernel-2.6-etc. (tty1)
CASE login:
Didn't the problem go away when you turned off the splash screen,
and ran Grub in the text mode?
Yes, it does. Which makes the problem a Fedora grub problem, not just a
grub problem -- I would think.
Mikkel
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
10:54 a.m.
William Case wrote:
Hi;
I have started this thread again as a new thread. The previous "Double
checking grub-install ??" lead off in all kinds of plausible directions.
I think I now have more of a focus.
To recap:
I am getting a double Fedora grub splashimage at boot. I have a dual
boot system with WindowsXP on sda and Fedora 9 on sdb. I have some
experience with installing grub but made a typo type mistake during a
grub install a month ago and I think (??) that might have been the root
of my double splashimage problem.
If I remember correctly from the first thread, you would get a brief
flash on the screen with Fedora at the top of the screen, a short
pause, and then the proper splash screen with Fedora on the bottom.
This is a good indication that ether the video card or the monitor
are changing modes to properly display the splash screen. I would
suspect that it is the monitor changing modes to match the video output.
While it will not prove this isn't the problem, it would be
interesting to see what happens if you log into the GUI, and then
hit Ctrl-Alt-F1 and see if you get the same kind behavior.
Didn't the problem go away when you turned off the splash screen,
and ran Grub in the text mode?
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
9:11 p.m.
New subject: Double checking grub-install -- LAST POSSSSSSS
On Fri, 2008-07-04 at 11:31 +0930, Tim wrote:
William Case stands high up on the bridge, puts his trumpet to his
lips,
and plays the last post.... taaah taah taaaaaaaahhhhhhh:
> So the answer must be grub is switching video modes.
> I wonder if I should report this as a Fedora bug against grub ?
Well, if it is switching video modes, it probably needs to do so. I
wouldn't call that a bug.
One of the posts in this thread suggested that grub should be able to
start with the correct mode -- not start then switch. But... what do I
know?
If the blanking is your monitor blacking out while it resyncs,
that's
also an expected behaviour.
Yes. If it hasn't selected the right mode in the first place.
Just checking the obvious, but does your grub.conf file have two
splashimage commands?
No -- only one splashimage.
I don't recall if you've shown us the file.
Yes, I have shown it a couple of times. Most recently yesterday, July
2, in response to Michael Schwendt.
--
Regards Bill;
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
9:01 p.m.
New subject: Double checking grub-install -- LAST POST
William Case stands high up on the bridge, puts his trumpet to his lips,
and plays the last post.... taaah taah taaaaaaaahhhhhhh:
So the answer must be grub is switching video modes.
I wonder if I should report this as a Fedora bug against grub ?
Well, if it is switching video modes, it probably needs to do so. I
wouldn't call that a bug.
If the blanking is your monitor blacking out while it resyncs, that's
also an expected behaviour.
Just checking the obvious, but does your grub.conf file have two
splashimage commands? I don't recall if you've shown us the file.
--
[tim@localhost ~]$ uname -r
2.6.25.9-76.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
5764
days inactive
5796
days old
22 comments
4 participants
participants (4)
-
Bill Case -
Michael Schwendt -
Mikkel -
Tim