Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#13009 - Grub - VGA parameter table - strange behaviour of kernel vga parameter
Attached to Project:
Arch Linux
Opened by Vladislav Guberinic (neosisani) - Tuesday, 27 January 2009, 18:56 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 27 January 2009, 19:59 GMT
Opened by Vladislav Guberinic (neosisani) - Tuesday, 27 January 2009, 18:56 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 27 January 2009, 19:59 GMT
|
DetailsDescription:
/boot/grub/menu.lst gives a table of vga modes and as example # TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line. However in my case vga=795 doesn't work, nor does vga=0x31B. However passing vga=31B seems to work. Also, part of irc session from ##kernel @ freenode <neosisani> does kernel vga parameter (at boot) accept hex or decimal value? (eg should i type vga=795 or vga=31B) <j_eng> strange as it is, the values are hex even without a leading 0x prefix Additional info: * package version(s) grub 0.97-15 Steps to reproduce: try a few vga parameters for kernel (eg vga=795) |
This task depends upon
Closed by Aaron Griffin (phrakture)
Tuesday, 27 January 2009, 19:59 GMT
Reason for closing: Not a bug
Tuesday, 27 January 2009, 19:59 GMT
Reason for closing: Not a bug
Comment by Aaron Griffin (phrakture) -
Tuesday, 27 January 2009, 19:03 GMT
795 may be out of range for your system. 773 and 791 work fine on my system. Try a lower resolution or lower color depth. I'm sure the decimal numbers work fine, they just may be out of range for your hardware
Comment by Vladislav Guberinic (neosisani) -
Tuesday, 27 January 2009, 19:50 GMT
Fixed it. 31b actually booted 1024 resolution.