Bug 9888 - Grub2 loading black screen with blue bar
Summary: Grub2 loading black screen with blue bar
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: High normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 5beta2
Keywords: NEEDINFO, Triaged
Depends on:
Blocks:
 
Reported: 2013-04-27 16:36 CEST by Arnaud Vacquier
Modified: 2015-09-22 21:23 CEST (History)
8 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
blue bar (13.35 KB, image/jpeg)
2013-04-27 16:36 CEST, Arnaud Vacquier
Details
1 - Select Mageia on Grub 2 (86.12 KB, image/jpeg)
2013-04-27 18:20 CEST, Arnaud Vacquier
Details
2- Grub 2 loading black screen and blue/with bar progress (32.86 KB, image/jpeg)
2013-04-27 18:20 CEST, Arnaud Vacquier
Details
Initial /etc/default/grub from Cauldron Alpha 2 (325 bytes, application/octet-stream)
2013-09-15 03:28 CEST, Doug Laidlaw
Details
The output of hwinfo --log hwinfo.txt (136.31 KB, text/plain)
2013-10-09 14:59 CEST, papoteur
Details
grub.cfg with problematic configuration (11.30 KB, text/plain)
2014-01-25 13:06 CET, papoteur
Details
screenshot of stretched low res menu (71.10 KB, image/jpeg)
2014-01-27 15:53 CET, claire robinson
Details
shows the theme now in use (47.73 KB, image/jpeg)
2014-01-27 15:55 CET, claire robinson
Details

Description Arnaud Vacquier 2013-04-27 16:36:59 CEST
Created attachment 3832 [details]
blue bar

Hi,

After select Mageia 3 in grub2 menu, the loader is black screen with blue bar 

it is not possible to put picture ? :/
it's look not job finish and many peoples want grub2

thank you.
Arnaud Vacquier 2013-04-27 16:37:13 CEST

Priority: Normal => High
Severity: major => normal

Comment 1 Xavier BERTAUX 2013-04-27 16:49:01 CEST
idem here.
I tried to plymouth-set-default-theme Mageia-Default -R but idem.

CC: (none) => bertauxx

Comment 2 Barry Jackson 2013-04-27 17:25:32 CEST
(In reply to Arnaud Vacquier from comment #0)
> Created attachment 3832 [details]
> blue bar
> 
> Hi,
> 
> After select Mageia 3 in grub2 menu, the loader is black screen with blue
> bar 
> 
> it is not possible to put picture ? :/
> it's look not job finish and many peoples want grub2
> 
> thank you.

Do you have a grub legacy on that hardware in maybe a different installation?

If so could you please attach /boot/grub/menu.lst from it.

Also please attach /etc/default/grub from your Mageia3.

I am suspecting that a vga=xxx is needed to set the correct display resolution for plymouth - if you know the correct setting (or can see it in a menu.lst) this may be added to /etc/default/grub (see Mga3 errata for details)
after adding this you must run:
update-grub2 before re-booting.

Keywords: (none) => NEEDINFO
CC: (none) => zen25000

Comment 3 Barry Jackson 2013-04-27 17:36:53 CEST
You may find this useful:-

http://pierre.baudu.in/other/grub.vga.modes.html

I find that the 16 bit values are correct e.g. vga=791 for 1024x768
Comment 4 Arnaud Vacquier 2013-04-27 18:01:28 CEST
It is do that bar / black screen on Virtualbox (install with DVD full Mageia KDE 32 bits)
And my laptop from Mageia Beta 4 (DVD Full Mageia KDE 32 too)

I search file and put here
Comment 5 Arnaud Vacquier 2013-04-27 18:15:32 CEST
The bug is for grub2 not grub1

For :

/boot/grub/menu.lst = i haven't this file, only menu.lst.example



I look in grub2, i found the theme
Comment 6 Arnaud Vacquier 2013-04-27 18:20:24 CEST
Created attachment 3833 [details]
1 - Select Mageia on Grub 2
Comment 7 Arnaud Vacquier 2013-04-27 18:20:56 CEST
Created attachment 3834 [details]
2- Grub 2 loading black screen and blue/with bar progress
Comment 8 Xavier BERTAUX 2013-04-27 18:24:27 CEST
on grub2.cfg I have these line :
set gfxpayload=text
on each entry
Comment 9 Barry Jackson 2013-04-27 19:05:34 CEST
There was no mention of VirtualBox in the original report :\

OK, follow this in your Vbox installation:

1. mcc -> hardware -> set up the graphical server.

On the 'Monitor' line read your resolution e.g. 1280x1024
Then exit and close mcc.

2. Check the correct vga mode for your resolution from the chart here: http://pierre.baudu.in/other/grub.vga.modes.html

e.g. 1280x1024 = 794 (on the 16 bit line)

3. As root edit /etc/default/grub so the line starting with GRUB_CMDLINE_LINUX_DEFAULT="splash quiet ....

now includes your vga mode e.g. :-

GRUB_CMDLINE_LINUX_DEFAULT="splash quiet vga=794 ....
(assuming the above example)

Save the file.

You can start a graphical editor as root from the command line using
$ su -
# kwrite (or e.g. gedit in gnome)

4. Now run update-grub2 (enter root password when asked if running as normal user)

5. Reboot
Comment 10 Arnaud Vacquier 2013-04-27 19:26:38 CEST
@Barry

it is my laptop with Mageia 3 from Beta 4 AND virtualbox
Comment 11 Barry Jackson 2013-04-27 19:29:41 CEST
OK - so apply the above changes to both the real machine and the Vbox installation and report the results :)
Comment 12 Arnaud Vacquier 2013-04-27 19:48:22 CEST
Okay, i try in first in VB

1 -> it is okay, 1024 -> 1280
2-> okay i add as you ask

3> during edit i see :
GRUB_CMDLINE_LINUX_DEFAULT=" splash quiet vga=794 resume=UUID=88579b11-2769-46a3-b067-1f0ad799147b"

vga is already here

4-> don't run :

[root@localhost aranud]# run update-grub2


i wait for 5
Comment 13 Arnaud Vacquier 2013-04-27 19:49:09 CEST
okay it run with run lol

[root@localhost ~]# update-grub2
Création de grub.cfgâ¦
Thème trouvé : /boot/grub2/themes/maggy/theme.txt
Image Linux trouvée : /boot/vmlinuz-desktop
Image mémoire initiale trouvée : /boot/initrd-desktop.img
Image Linux trouvée : /boot/vmlinuz-3.8.10-desktop-1.mga3
Image mémoire initiale trouvée : /boot/initrd-3.8.10-desktop-1.mga3.img
Image Linux trouvée : /boot/vmlinuz-3.8.8-desktop-1.mga3
Image mémoire initiale trouvée : /boot/initrd-3.8.8-desktop-1.mga3.img
fait


i reboot VB
Comment 14 Arnaud Vacquier 2013-04-27 19:50:31 CEST
Great VB is fixed ;)
Comment 15 Arnaud Vacquier 2013-04-28 02:23:18 CEST
For my computer :

1- i don't change résolution
2- in configure boot system in CCM i have :
ro nokmsboot splash quiet root=UUID=7f6fd47e-82af-470f-81e1-a7391bf427d8 resume=UUID=748f1125-7f9a-47c5-9e1e-f4de9cc6a2d5

there are nokmsboot ? may be add automaticly in beta4 during install?

i am in laptop 1440x900, i add 834

3 & 4 = done


I reboot for confirm
Comment 16 Arnaud Vacquier 2013-04-28 02:43:37 CEST
So, it don't run :/

when i reboot the screen is here but just after i have a message (i try in english) :

"The display driver has been modified, the computer must be restarted .... you have 30 seconds"

i have Ok or abort :

Ok : the computer reboot and i come back with blue bar (Mageia open)
Abort : loading finish and i have black screen (Mageia not open).


tomorrow, i re-try with your graphical resolution "1280x1024"
Comment 17 Barry Jackson 2013-04-28 10:53:13 CEST
(In reply to Arnaud Vacquier from comment #16)

> tomorrow, i re-try with your graphical resolution "1280x1024"

No, first try vga=868

Don't forget to:
update-grub2
before reboot.
Comment 18 Barry Jackson 2013-04-28 14:25:31 CEST
If you cannot boot because of the incorrect vga= value then:
At the grub2 boot menu, you can hit 'e' to edit the menu entry that is highlighted, so simply change or remove the value there. You can then edit /etc/default/grub from the running system and update-grub2 to make the change permanent.
Comment 19 Arnaud Vacquier 2013-04-28 16:40:27 CEST
So....

1. mcc -> hardware -> set up the graphical server.

On the 'Monitor' line read your resolution e.g. 1280x1024
Then exit and close mcc.

==> I have 1440x... to 19..x..., i keep 1440x900

2. Check the correct vga mode for your resolution from the chart here: http://pierre.baudu.in/other/grub.vga.modes.html

e.g. 1280x1024 = 794 (on the 16 bit line)


===> okay you say to put "vga=868"


3. As root edit /etc/default/grub so the line starting with GRUB_CMDLINE_LINUX_DEFAULT="splash quiet ....

now includes your vga mode e.g. :-

GRUB_CMDLINE_LINUX_DEFAULT="splash quiet vga=794 ....
(assuming the above example)

Save the file.

==> Okay i edit file i put vga=868 but there is "nokmsboot" in line, i remove it.

4. Now run update-grub2 (enter root password when asked if running as normal user)

==> done

5. Reboot

==> still bugged, it is ask me the graphical material have been modified reboot computer.... after reboot i have still black screen with blue bar :(


thank you
Comment 20 Barry Jackson 2013-04-28 16:51:54 CEST
(In reply to Arnaud Vacquier from comment #19)

> ==> Okay i edit file i put vga=868 but there is "nokmsboot" in line, i
> remove it.

Why? :\

Don't remove nokmsboot - replace it and re-run:
update-grub2

Please also run:
su
rpm -q --quiet hwinfo || urpmi hwinfo && hwinfo --framebuffer

...and post the output here.
Comment 21 Samuel Verschelde 2013-08-27 15:36:52 CEST
Hi Arnaud, you haven't answered to comment #20.

Source RPM: (none) => grub2
CC: (none) => stormi
Component: Installer => RPM Packages

Samuel Verschelde 2013-08-27 15:37:09 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => zen25000

Comment 22 Doug Laidlaw 2013-09-14 13:06:17 CEST
(In reply to Barry Jackson from comment #20)
> (In reply to Arnaud Vacquier from comment #19)
> 
> > ==> Okay i edit file i put vga=868 but there is "nokmsboot" in line, i
> > remove it.
> 
> Why? :\
> 
> Don't remove nokmsboot - replace it and re-run:
> update-grub2
> 
> Please also run:
> su
> rpm -q --quiet hwinfo || urpmi hwinfo && hwinfo --framebuffer
> 
> ...and post the output here.

I had a problem with nokmsboot but it may be different.  In Mga4A2 nokmsboot was the first thing in the line, with a blank character space between it and the opening quote.  I kept getting a message that nokmsboot wan't there.  I removed the whitespace: no change.  I replaced the line with the one that works in Mga3:

GRUB_CMDLINE_LINUX_DEFAULT="splash quiet vga=792 nokmsboot"

Success!.

CC: (none) => laidlaws

Comment 23 Barry Jackson 2013-09-14 19:27:22 CEST
(In reply to Doug Laidlaw from comment #22)

> I had a problem with nokmsboot but it may be different.  In Mga4A2 nokmsboot
> was the first thing in the line, with a blank character space between it and
> the opening quote.  I kept getting a message that nokmsboot wan't there.  I
> removed the whitespace: no change.  I replaced the line with the one that
> works in Mga3:
> 
> GRUB_CMDLINE_LINUX_DEFAULT="splash quiet vga=792 nokmsboot"
> 
> Success!.

Can you reproduce this?
It would be good to see the command line (and /etc/default/grub) as it was originally.
Comment 24 Doug Laidlaw 2013-09-15 00:13:11 CEST
Unfortunately, only the current version of /etc/default/grub is in my backups. I have space to try a clean extra installation.  Then I will report back.

The only change was in the command line. Originally it began:

GRUB_CMDLINE_LINUX_DEFAULT=" nokmsboot..."

The first thing I suspected was the leading space.  When that didn't fix it, I wondered if the sequence of the options was important.

I got "vga=792" from the Mga3 Errata.  It wasn't in the line I replaced.  I read somewhere that it is now deprecated. It seems to be covered lower down.
Comment 25 Doug Laidlaw 2013-09-15 03:28:16 CEST
Created attachment 4353 [details]
Initial /etc/default/grub from Cauldron Alpha 2

This is from a separate fresh installation.  It loads a normal KDE desktop with the nVidia driver, even after rebooting.  Wouldn't it!

My symptoms were different.  I would get a normal bootup until the message box appeared saying that nokmsboot wasn't among my options and might inhibit the display.  Then I would click "OK" or "Continue."  The system would eventually drop me to a rescue shell.

My up-to-date Cauldron has all kinds of problems, but substituting the command line above gave me a desktop again (with nouveau, I think.)

If I get the same problem after updating the fresh Cauldron, I will post details here.
Comment 26 Doug Laidlaw 2013-09-16 14:37:01 CEST
My bootloader couldn't find the additional Cauldron.  I reinstalled the existing one and have had no problem eoither with Grub or with nVidia.
Comment 27 Barry Jackson 2013-09-16 15:55:10 CEST
(In reply to Doug Laidlaw from comment #26)
> My bootloader couldn't find the additional Cauldron.

You did run 'update-grub' in your main system after installing it?

> I reinstalled the
> existing one and have had no problem eoither with Grub or with nVidia.

Ah well !
Comment 28 Doug Laidlaw 2013-09-16 16:02:44 CEST
(In reply to Barry Jackson from comment #27)
> (In reply to Doug Laidlaw from comment #26)
> > My bootloader couldn't find the additional Cauldron.
> 
> You did run 'update-grub' in your main system after installing it?
> 
I think so. I did find that out at some point.  Initially, of course, the installer put in its own bootloader, but that wasn't visible either.

The existing Cauldron was a complete shambles.  I thought that the team must have taken a step backwards!  The current one is fine, but after 3 installs, I am being warned that I am running out of bandwidth for the month.
Comment 29 Barry Jackson 2013-09-21 11:40:59 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED

Comment 30 papoteur 2013-10-06 22:13:59 CEST
Hello,
I see the problem Arnaud reported with mageia 4 alpha 3 installed from LiveDVD-KDE-i586 in VirtualBox.
I saw also the same problem With Mageia 3.
I have put vga = 791 in the options line to the grub entry from MCC. After that, the boot is correct.
hwinfo --framebuffer gives no output.

Status: RESOLVED => REOPENED
CC: (none) => yves.brungard_mageia
Resolution: OLD => (none)

Comment 31 Barry Jackson 2013-10-06 23:00:19 CEST
(In reply to papoteur from comment #30)
> Hello,
> I see the problem Arnaud reported with mageia 4 alpha 3 installed from
> LiveDVD-KDE-i586 in VirtualBox.
> I saw also the same problem With Mageia 3.
> I have put vga = 791 in the options line to the grub entry from MCC. After
> that, the boot is correct.

Good.

> hwinfo --framebuffer gives no output.

No output? Not even file not found?

Try:
su
rpm -q hwinfo || urpmi hwinfo && hwinfo --framebuffer
Comment 32 Doug Laidlaw 2013-10-08 14:42:36 CEST
I don't have hwinfo either.  But I did get:

sudo: hwinfo: command not found
Comment 33 papoteur 2013-10-09 14:59:47 CEST
Created attachment 4421 [details]
The output of hwinfo --log hwinfo.txt
Comment 34 Barry Jackson 2013-10-09 15:38:28 CEST
So your resolution is 1024x768 which I guess is default for a VBox installation.
The mode for 1024x768 (16 bits) is 0x0317 or 791 so that is correct.
Comment 35 Barry Jackson 2014-01-12 17:25:01 CET
I think this needs looking at by a drakx developer, since any required vga=xxx is inserted into /etc/default/grub (and hence kernel command line) by drakxtools code.

Assignee: zen25000 => bugsquad
Source RPM: grub2 => (none)

Barry Jackson 2014-01-12 17:25:58 CET

Version: 3 => Cauldron

Comment 36 Doug Laidlaw 2014-01-12 17:33:23 CET
I have had no problem with this for some time.

vga=xxx is no longer correct for Grub2.  My /etc/default/grub has a line:

GRUB_GFXMODE=1024x768x32

That is now how it should be done.
Comment 37 Barry Jackson 2014-01-12 20:02:30 CET
(In reply to Doug Laidlaw from comment #36)
> I have had no problem with this for some time.
> 
> vga=xxx is no longer correct for Grub2.  My /etc/default/grub has a line:
> 
> GRUB_GFXMODE=1024x768x32
> 
> That is now how it should be done.

I agree in theory and that is default, however when installed to a virtualbox VM the problem persists unless vga=791 is added. This also seems to apply to some hardware installations as reported above unless something has been fixed and not reported here.

Grub2 passes command line arguments unmodified to the kernel, so if vga=xxx is needed then it's up to us to add it to /etc/default/grub, in the same way that it is added in menu.lst for grub.
Comment 38 Doug Laidlaw 2014-01-12 20:21:47 CET
That is the vital difference.  I am not using Virtualbox.

I believe that in the early stages of Grub2, vga=791 was normal.

How do you suggest that the RPM should be modified?  Can the installer know that it is installing to an emulator?

Grub2 seems to be under development still, and to have a number of bugs.  One that irritates me, is that it sees my drives as being in a different format from what they really are, and advises me to run fsck.  But there are others.
Comment 39 Barry Jackson 2014-01-12 21:16:22 CET
Well irrespective of whether a VM is in use or not, a working vga mode can be extracted as follows:
e.g. in a VM:

# xdpyinfo | grep 'dimensions:'
dimensions: 1024x768 pixels

# hwinfo --framebuffer | grep 1024x768 | grep '16 bits'
  Mode 0x0317: 1024x768 (+2048), 16 bits

0x0317 (hex) = 791

I have no idea how to extract the above info in perl, but if the installer were to do something similar to the above and insert either vga=0x0317 OR vga=791 into /etc/default/grub it would fix the VM issue and maybe others.

Regarding the other bugs you mention, are there bug reports anywhere?
Comment 40 Doug Laidlaw 2014-01-15 02:20:33 CET
(In reply to Barry Jackson from comment #39)

> 
> Regarding the other bugs you mention, are there bug reports anywhere?

No, I was quoting only mentions I have seen.
Comment 41 claire robinson 2014-01-15 11:12:17 CET
Valid 4RC Classic DVD 64

Installing with Grub1 shows plymouth artwork after reboot

Installing with grub2 shows the 3 bars only


If I'm understanding correctly with a quick scan through the bug, it just needs the correct vga= inserting by the installer when grub2 is configured?

CC: (none) => eeeemail, thierry.vignaud

claire robinson 2014-01-15 11:12:48 CET

Whiteboard: (none) => 4RC

Comment 42 Doug Laidlaw 2014-01-15 11:33:54 CET
I have been using Legacy GRUB to get rebootin.

As a test, I just installed Grub2 as the bootloader.  Apart from a bit of text, Cauldron booted normally.  My VGA setting is as Comment 36 says.

It seems to happen only under VBox.

I will just sit on the side.
Comment 43 papoteur 2014-01-22 19:19:42 CET
Hello,
I have installed M4-RC from DVD-i586. I get the 3bars, as started from Mageia 3.
It' a real install, not VB.
Comment 44 Barry Jackson 2014-01-23 00:18:14 CET
(In reply to papoteur from comment #43)
> Hello,
> I have installed M4-RC from DVD-i586. I get the 3bars, as started from
> Mageia 3.
> It' a real install, not VB.

I don't understand "as started from Mageia 3."

Is this with grub or grub2?

Can you attach /boot/grub/menu.lst or /boot/grub2/grub.cfg as appropriate.

Also the outputs of the commands in comment #39

This output may also be useful:
su
monitor-edid
Comment 45 Doug Laidlaw 2014-01-23 00:27:35 CET
I would read papoteur to mean:

"I am getting the same 3 bars I got when booting Mga3."
Comment 46 papoteur 2014-01-24 23:01:00 CET
Doug Laidlaw understood what I wanted say.

# monitor-edid
Name: NEC LCD71VM
EISA ID: NEC661c
EDID version: 1.3
EDID extension blocks: 0
Screen size: 33.7 cm x 27.0 cm (17.00 inches, aspect ratio 5/4 = 1.25)
Gamma: 2.2
Analog signal
Max video bandwidth: 140 MHz

	HorizSync 31-81
	VertRefresh 56-75

	# Monitor preferred modeline (60.0 Hz vsync, 64.0 kHz hsync, ratio 5/4, 96 dpi)
	ModeLine "1280x1024" 108 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync


#  xdpyinfo | grep 'dimensions:'
  dimensions:    1280x1024 pixels (342x271 millimeters)

#  hwinfo --framebuffer | grep 1024x768 | grep '16 bits'
  Mode 0x0317: 1024x768 (+2048), 16 bits
Comment 47 Barry Jackson 2014-01-25 00:37:20 CET
Having established the dimensions as 1280x1024 using xdpyinfo the command to get the Mode would be:
# hwinfo --framebuffer | grep 1280x1024 | grep '16 bits'

In my case this offers:
  Mode 0x031a: 1280x1024 (+2560), 16 bits
  Mode 0x037e: 1280x1024 (+2560), 16 bits

Which would indicate either 794 or 894 (in decimal)
 
What output do you see on your system?
Comment 48 papoteur 2014-01-25 08:28:59 CET
OK, yes, I adapted the resolution :

hwinfo --framebuffer | grep 1280x1024 | grep '16 bits'
  Mode 0x031a: 1280x1024 (+2560), 16 bits
Comment 49 Barry Jackson 2014-01-25 11:23:43 CET
OK so now try adding vga=0x031a (it works with hex or decimal) into the GRUB_CMDLINE_LINUX_DEFAULT= line in /etc/default/grub
You must then run:
update-grub
to re-generate grub.cfg and then reboot.
Does that fix the boot graphic?
Comment 50 papoteur 2014-01-25 13:06:42 CET
Created attachment 4871 [details]
grub.cfg with problematic configuration

From papoteur's box.
Comment 51 papoteur 2014-01-25 13:23:19 CET
Barry,
I tried the trick of comment  49.
I get yet a splash screen, without the blue bar.
However, the background image is too big. The cauldron is cropped at the edge of the screen.
But it is yet already better.
Comment 52 Doug Laidlaw 2014-01-25 13:30:43 CET
I will remove my address from this bug.  It hasn't troubled me for some time.  It seems to matter only under Vbox, which I don't have installed.
Doug Laidlaw 2014-01-25 13:31:10 CET

CC: laidlaws => (none)

Barry Jackson 2014-01-25 18:08:25 CET

Attachment 4871 mime type: application/octet-stream => text/plain

Comment 53 Barry Jackson 2014-01-26 17:22:23 CET
(In reply to papoteur from comment #51)
> Barry,
> I tried the trick of comment  49.
> I get yet a splash screen, without the blue bar.
> However, the background image is too big. The cauldron is cropped at the
> edge of the screen.

I see that too and after seeing comments in #mageia-atelier I was expecting a fix but it has not happened - maybe needs a separate bug report.

> But it is yet already better.

Ok good.

I have done some testing today and maybe have a solution that could be set as default if it works for all.

Could you try the following changes in your /etc/default/grub please.

1. Remove the vga=xxx from GRUB_CMDLINE_LINUX_DEFAULT
2. Set GRUB_GFXMODE=auto
3. Set GRUB_GFXPAYLOAD_LINUX=keep
4. Run update-grub and re-boot
Comment 54 Barry Jackson 2014-01-26 17:34:58 CET
Note for anyone else testing the above - ignore 1 if vga= is not already there.
We still need to know if the other changes break anything for anyone.
Thanks.
Comment 55 papoteur 2014-01-26 20:42:57 CET
Hi Barry.
With this modifications, I get:
- the first screen with the entries selection in 640x480 resolution :( It is usable, except a help sentence which is truncated.
- the splash screen is correct.
Thanks
Comment 56 Barry Jackson 2014-01-27 12:56:54 CET
OK thanks - yes I see the chopped off help issue in VBox but I can fix that by shortening the lines.

Anyone else tested this on real hardware?
Comment 57 claire robinson 2014-01-27 13:41:40 CET
I don't have vga= here but do have GRUB_GFXMODE=1024x768x32 and GRUB_GFXPAYLOAD_LINUX=text and a 1920x1080 monitor.


Changed both and rebooted but still the 3 bars. No regression though.
I notice the /boot/grub2/themes/maggy/theme.txt sets 1024x768 too.
Comment 58 claire robinson 2014-01-27 13:44:52 CET
oh, forgot to update-grub, sorry.

Once run and rebooted grub2 is as papoteur found, very low resolution with text truncated. The theme is back though.
Comment 59 Barry Jackson 2014-01-27 15:49:59 CET
(In reply to claire robinson from comment #58)
> oh, forgot to update-grub, sorry.
> 
> Once run and rebooted grub2 is as papoteur found, very low resolution with
> text truncated. The theme is back though.

OK thanks - so this is not a fix for all cases then.
On your system does vga=xxx work correctly with the original /etc/default/grub settings, using the value for xxx derived as in #39 ?
i.e. use xdpyinfo to get dimensions and hwinfo --framebuffer to get available modes?
Comment 60 claire robinson 2014-01-27 15:53:50 CET
Created attachment 4888 [details]
screenshot of stretched low res menu

I'll attach these and then try that Barry
Comment 61 claire robinson 2014-01-27 15:55:49 CET
Created attachment 4889 [details]
shows the theme now in use
Comment 62 claire robinson 2014-01-27 16:09:14 CET
No 1920x1080 listed by hwinfo. Nothing 16 bit that looks 16:9 either


# hwinfo --framebuffer
02: None 00.0: 11001 VESA Framebuffer                           
  [Created at bios.459]
  Unique ID: rdCR._78UnaO58VA
  Hardware Class: framebuffer
  Model: "NVIDIA BIOS-P/N@N5601"
  Vendor: "NVIDIA Corporation"
  Device: "BIOS-P/N@N5601"
  SubVendor: "NVIDIA"
  SubDevice: 
  Revision: "Chip Rev"
  Memory Size: 14 MB
  Memory Range: 0xcf000000-0xcfdfffff (rw)
  Mode 0x0300: 640x400 (+640), 8 bits
  Mode 0x0301: 640x480 (+640), 8 bits
  Mode 0x0303: 800x600 (+800), 8 bits
  Mode 0x0305: 1024x768 (+1024), 8 bits
  Mode 0x0307: 1280x1024 (+1280), 8 bits
  Mode 0x030e: 320x200 (+640), 16 bits
  Mode 0x030f: 320x200 (+1280), 24 bits
  Mode 0x0311: 640x480 (+1280), 16 bits
  Mode 0x0312: 640x480 (+2560), 24 bits
  Mode 0x0314: 800x600 (+1600), 16 bits
  Mode 0x0315: 800x600 (+3200), 24 bits
  Mode 0x0317: 1024x768 (+2048), 16 bits
  Mode 0x0318: 1024x768 (+4096), 24 bits
  Mode 0x031a: 1280x1024 (+2560), 16 bits
  Mode 0x031b: 1280x1024 (+5120), 24 bits
  Mode 0x0330: 320x200 (+320), 8 bits
  Mode 0x0331: 320x400 (+320), 8 bits
  Mode 0x0332: 320x400 (+640), 16 bits
  Mode 0x0333: 320x400 (+1280), 24 bits
  Mode 0x0334: 320x240 (+320), 8 bits
  Mode 0x0335: 320x240 (+640), 16 bits
  Mode 0x0336: 320x240 (+1280), 24 bits
  Mode 0x033d: 640x400 (+1280), 16 bits
  Mode 0x033e: 640x400 (+2560), 24 bits
  Mode 0x0360: 1280x800 (+1280), 8 bits
  Mode 0x0361: 1280x800 (+5120), 24 bits
  Mode 0x0362: 768x480 (+768), 8 bits
  Mode 0x037b: 1280x720 (+5120), 24 bits
  Config Status: cfg=new, avail=yes, need=no, active=unknown
Comment 63 claire robinson 2014-01-27 16:43:57 CET
Summarising what was tested on irc.

Installed grub and it uses vga=788 for some installs here, so added vga=0x0314 to /etc/default/grub and returned the other two settings to their original values and ran update-grub. On reboot things had returned to normal, legible, but the theme was now shown. 

Both menu and theme appear to be using a lower resolution than the monitor though, possibly the 1024x768x32?
Comment 64 claire robinson 2014-01-27 16:45:27 CET
To clarify 'using a lower resolution than the screen', I mean it is almost full screen but with a pixelated appearance as if it has been stretched from a lower resolution.
Comment 65 Barry Jackson 2014-01-27 20:15:38 CET
788 is 0x0314 which according to your hwinfo output is 800x600x16

Could you please try 0x0317 (791) (which is 1024x768x16) ?

That should reduce the pixelation.

Also out of interest what does your monitor say it supports?
# monitor-edid
Comment 66 Nic Baxter 2015-03-31 03:29:15 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: REOPENED => RESOLVED
CC: (none) => nic
Resolution: (none) => OLD

Comment 67 papoteur 2015-04-06 19:27:06 CEST
This was always valid in Mageia Cauldron 5 beta 2.
As I have poor Internet connection this time, I can't download RC candidate to more investigate. I there a package to update?

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

Marja Van Waes 2015-04-06 19:54:37 CEST

CC: (none) => marja11
Whiteboard: 4RC => 5beta2

Comment 68 Nic Baxter 2015-04-06 20:10:23 CEST
Would yoy please respond to comment 65. There was a request for more information
Comment 69 papoteur 2015-04-06 20:30:32 CEST
Hi Nic,
Thanks for dealing with bugs.
The question was for Claire.
Barjac said me that for solving, drakx tools should be altered, what he can't do.
Papoteur
Comment 70 Barry Jackson 2015-04-06 20:35:07 CEST
Nic - Yes, that was 15 months ago :)

@ Papoteur
Maybe you should discuss this with Thierry, as you are one of the few people with this issue on real hardware?
Comment 71 Nic Baxter 2015-04-06 23:29:42 CEST
Sorry, I lost sense of the thread. I'll leave this one alone now.
Comment 72 Barry Jackson 2015-04-07 00:44:32 CEST
Tonight I added vga=788 to the /etc/default/grub of an Mga4 VM.

vga=788 was in the menu.lst of it's grub legacy install, so I copied it.

The plymouth screen was fine after this addition (and update-grub).

I then upgraded the VM to Mageia 5 and the same vga-788 worked.

So whatever applies this to grub legacy should also add it to /etc/default/grub.
Comment 73 Mageia Robot 2015-04-07 17:44:56 CEST
commit f56bb7cd1c44fabf610ada962b494e66ff2852f9
Author: Thierry Vignaud <thierry.vignaud@...>
Date:   Tue Apr 7 10:03:43 2015 -0400

    keep vga= arg when switching to grub2 (mga#9888)
---
 Commit Link:
   http://gitweb.mageia.org/software/drakx/commit/?id=f56bb7cd1c44fabf610ada962b494e66ff2852f9
Comment 74 Marja Van Waes 2015-09-22 21:23:50 CEST
(In reply to Mageia Robot from comment #73)
> commit f56bb7cd1c44fabf610ada962b494e66ff2852f9
> Author: Thierry Vignaud <thierry.vignaud@...>
> Date:   Tue Apr 7 10:03:43 2015 -0400
> 
>     keep vga= arg when switching to grub2 (mga#9888)
> ---
>  Commit Link:
>   
> http://gitweb.mageia.org/software/drakx/commit/
> ?id=f56bb7cd1c44fabf610ada962b494e66ff2852f9

So closing as fixed

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.