| 2007-10-30 17:27:42 |
Rafael Belmonte |
bug |
|
|
added bug |
| 2008-10-21 17:46:50 |
Dimitrios Symeonidis |
ubuntu-meta: status |
New |
Incomplete |
|
| 2008-10-21 17:46:50 |
Dimitrios Symeonidis |
ubuntu-meta: statusexplanation |
|
The answer is passing a "vga=xyz" parameter to the kernel during grub.
These are called vesa modes, and a list can be found here:
http://en.wikipedia.org/wiki/VESA_BIOS#Linux_video_mode_numbers
EagleScreen, is this what you were looking for? |
|
| 2008-10-22 20:54:27 |
Dimitrios Symeonidis |
ubuntu-meta: status |
Incomplete |
New |
|
| 2008-10-22 20:54:27 |
Dimitrios Symeonidis |
ubuntu-meta: statusexplanation |
The answer is passing a "vga=xyz" parameter to the kernel during grub.
These are called vesa modes, and a list can be found here:
http://en.wikipedia.org/wiki/VESA_BIOS#Linux_video_mode_numbers
EagleScreen, is this what you were looking for? |
|
|
| 2008-11-26 16:40:20 |
Colin Watson |
ubuntu-meta: status |
New |
Won't Fix |
|
| 2008-11-26 16:40:20 |
Colin Watson |
ubuntu-meta: assignee |
|
kamion |
|
| 2008-11-26 16:40:20 |
Colin Watson |
ubuntu-meta: statusexplanation |
|
Unfortunately, using a VESA mode (with vga=) has the side-effect of breaking suspend and resume. This is a fairly well-known problem and if it's ever fixed then we'll reconsider it, but for the time being having suspend and resume work by default is more important to us than a high console resolution. Of course you can change this for yourself if you think otherwise. |
|
