I'm not antisocial. I'm just not user friendly...
Open Linux Forums
No - grub loads at correct resolution 1680x1050(as does X), but if I switch to TTY1-6 it displays at 1280x1060 - so the console resolution doesn't appear to persist beyond grub...
i'm not sure which resolutions you are using, i've never seen 1280x1060, nor 1680x1050
anyways, using the vga= kernel option you can set the frame buffer mode.
i don't know the one for your card, but i found a nvidia code of 0x0369 for that resolution
so open your grub defaults file with an editor:
and change the following line to something like this:Code:gksudo gedit /etc/default/grub
of course you will have to check the resolution and the matching frame buffer code.Code:GRUB_CMDLINE_LINUX_DEFAULT="ro quiet splash vga=0x0369"
then run update-grub:
Code:sudo update-grub
I'm not antisocial. I'm just not user friendly...
Open Linux Forums
Thanks Leppie - that is the correct code (i was using it in my kernel line for versions up to 9.04).
My understanding was that "vga=xxxx" was deprecated in Grub2 and we weren't supposed to use it anymore: so is this a "hack" to get around that?
In any event, I'll try it this evening and see how it goes...
Last edited by miromiro; January 27th, 2010 at 10:15 PM. Reason: typo
I'm not antisocial. I'm just not user friendly...
Open Linux Forums
Sorry guys, I've been really busy, but I've follow the thread from time to time.
the vga kernel command is deprecated for grub2. I have tried it and ubuntu just boots like it isn't there.
This also brings us back to the first post in this thread, where I mentioned the role of fbcon and vesafb in booting with grub2 - people from most forums report getting the desired console resolution only with the ...payload=keep or whatever, does that mean somehow grub2 is able to replace fbcon (seems like it because grub2's resolution is right), did it interact with the ttys?
When I have time I would want to try some combinations of working with/without the kernel modules, of course someone who has the time can try that and we'll appreciate it very much.
I can confirm adding the vga value to the GRUB_CMD_LINE has no effect - resolution is still very low.
For reference, my full /etc/default/grub:
Code:GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT="10" GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="ro quiet splash vga=0x0369" GRUB_CMDLINE_LINUX="gfxpayload=true" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' GRUB_GFXMODE=1680x1050x24 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entrys #GRUB_DISABLE_LINUX_RECOVERY="true"
SOLVED
This post has the secret ingredient:
http://newyork.ubuntuforums.org/show...03&postcount=8
The key is to use the vga value PLUS changing the entries in /etc/grub.d/10_linux from linux and initrd to linux16 and initrd16
w00t!
Last edited by Leppie; January 28th, 2010 at 11:08 AM.
I'm not antisocial. I'm just not user friendly...
Open Linux Forums
Bookmarks