Framebuffer graphics mode spontaneously changes, X resolution limited incorrectly (Intel 945GM)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| xorg (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I'm running Ubuntu 7.10 for amd64, with Intel 945GM graphics.
X has been running nicely at 1280x1024 since my fresh install of 7.10 a couple of weeks ago. However, today, it booted and started at 1280x768. 1280x1024 (the native resolution of my monitor) was no longer available, though 1280x800 was. Because those available modes look terrible on my monitor, I switched over to a virtual terminal (Shift-F1) to investigate.
By default, it was in an ugly, low-res graphics mode. So, I started experimenting in grub with the vga= kernel argument, trying different values in the hopes of improving the situation.
If I try vga=0, just to get the simple 80x25 text mode, and disable splash, it initially boots in text mode, displaying this much:
Starting up...
Kernel alive
Kernel direct mapping tables up to 100000000 @ 8000-d000
Then, right when (perhaps immediately after?) it displays this, it goes back into the ugly, low-res graphics mode:
[ 53.845084] i8042.c: No controller found
Loading, please wait...
At first, when I tried vga=795, to get 1280x1024 graphics mode, I got no virtual terminals at all, just a blinking cursor. Interestingly, X was now able to run at 1280x1024 again! I then found bug 129910, tried MOM2007's, workaround and now both the framebuffer and X are able to run at 1280x1024.
Before I tried the workaround for bug 129910, vga=791 did exactly the same thing as vga=0. I got the same ugly, low-res graphics mode and X was limited to 1280x800 (and defaulted to 1280x768). But now, after trying MOM2007's workaround, it works perfectly: I get 1024x768 in the framebuffer and 1280x1024 in X.
However, I still have the problem with vga=0, which is why I have filed this bug: I still get the spontaneous graphics mode change in the framebuffer and the incorrectly limited resolution in X. I have no idea how a framebuffer problem can affect X like this, so suggestions on how I can investigate this further would be most appreciated.
I will attach my xorg.conf and Xorg.0.log (from when I boot with vga=0 and the resolution gets incorrectly limited, of course).
Thanks!
| Dave Steinberg (dmsteinberg) wrote | #1 |
| Dave Steinberg (dmsteinberg) wrote | #2 |
| Dave Steinberg (dmsteinberg) wrote | #3 |
| Bryce Harrington (bryce) wrote | #4 |
| Changed in xorg: | |
| status: | New → Incomplete |
| Dave Steinberg (dmsteinberg) wrote | #5 |
| Timo Aaltonen (tjaalton) wrote | #6 |
| Changed in xorg: | |
| status: | Incomplete → Invalid |
One additional thought: I've been experiencing another problem in X. Even when it's running correctly at 1280x1024, it seems to somehow report the wrong height to some applications, notably compiz. This manifests in windows not properly maximizing, as discussed in bug 151586. I was able to work around this by installing compizconfig-