*** This bug is a duplicate of bug 391215 ***
https://bugs.launchpad.net/bugs/391215
As far as I've been able to determine by experiment, the Karmic kernels
completely ignore the vga= option, and rely on EDID to work out what
resolution to use. For those of us unfortunate enough to own screens
with bogus EDID, this fails.
In my case, I'm trying to use an Acer AL1511 LCD panel and the only
resolution listed in its EDID is 640x350 even though its native
resolution is 1024x768. With GRUB 2, adding vga=791 (which calls for a
1024x768x16 framebuffer) to the kernel boot options prompts whining
about vga= being deprecated, then ignores it (I get nasty-looking
620x350 text consoles); with GRUB, there's no whining but the option is
still ignored.
Booting a Hardy live CD on the same box and adding vga=791 to the boot
options using F6 gives me the 1024x768 text consoles I'm expecting
(although the live CD's GUI is broken because X also believes what the
monitor tells it).
I know that monitors exist whose EDID reports resolutions they can't
actually display. If Anton is unlucky enough to have one of those, and
the kernel is simply ignoring his vga=791 option at boot time, that
would explain all his symptoms.
--
[Karmic] kernel >= 2.6.30-10 with vga=791 tty consoles not accessible and not
showing dmesg.
https://bugs.launchpad.net/bugs/391705
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu (via bug
391215).
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
