Resolution not correct after install on a Toshiba Tecra 8000 laptop

Bug #25079 reported by Etienne Goyer
8
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Confirmed
Medium
Ubuntu-X

Bug Description

The resolution is not correct after install on a Toshiba Tecra 8000 laptop. It
is currently 640x480, should be 1024x768. It seem to be reported correctly by
DPMS (see attached X.org log), but the resolution is still 640x480 for some
reasons I can't figure out.

See attached X.org log and x.org original config file.

Revision history for this message
Etienne Goyer (etienne-goyer-outlands) wrote :

Created an attachment (id=4889)
X.org log

Revision history for this message
Etienne Goyer (etienne-goyer-outlands) wrote :

Created an attachment (id=4890)
original x.org file

Revision history for this message
Daniel Stone (daniels) wrote :

does it work if you add:
HorizSync 36-52
VertRefresh 36-60

to the Monitor section of xorg.conf?

Revision history for this message
Etienne Goyer (etienne-goyer-outlands) wrote :

(In reply to comment #3)
> does it work if you add:
> HorizSync 36-52
> VertRefresh 36-60
>
> to the Monitor section of xorg.conf?

It work wonderfully !

Revision history for this message
Daniel Stone (daniels) wrote :

okay, thanks

Revision history for this message
John C Barstow (jbowtie) wrote :

Fix doesn't seem to be 100%; latest testing with Flight 3 has wrong HorizSync and resolution on install. Didn't write down the numbers but was something like 18-36.

Manually changing HorizSync to above numbers fixes it (also needed to list 1024x768 as a supported resolution, but I suspect that was defaulted based on the bad HorizSync numbers)

Changed in xorg:
status: Fix Committed → Fix Released
Revision history for this message
Etienne Goyer (etienne-goyer-outlands) wrote :

With Dapper, the problem manifest itself otherwise. Using the desktop live installation image, the system still boot with an incorrect resolution (640x480).

Then, when I try to launch the live installation from the Gnome desktop, the installer window spill out of the desktop and I can't see the buttons (see bug #51442).

Revision history for this message
arty (spamtrap-paradise) wrote :

Stuck on 640x480 during install.

Looked in xorg.conf and it had correctly detected my card as a geforce4 mmx.

I restarted x and my new resolution was 1280x1024.

So I went from the lowest possible resolution to the highest possible just by restarting x.

Revision history for this message
Conrad Knauer (atheoi) wrote :

Still broken using the Edgy Knot 3 Live CD, but the 36-52/36-60 fix still works too :)

Revision history for this message
Conrad Knauer (atheoi) wrote :

Basically a repeat of my previous comment; still broken using the Feisty Herd 2 Live CD, but the 36-52/36-60 fix still works too :)

Revision history for this message
Conrad Knauer (atheoi) wrote :

I guess this would be a regression...

Changed in xorg:
status: Fix Released → Confirmed
Daniel Stone (daniels)
Changed in xorg:
assignee: daniels → ubuntu-x-swat
Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

I installed feisty beta (from the alternate install cd), and was stuck in a 720x400 resolution in X.
I then removed the two lines:

HorizSync 28-36
VertRefresh 43-60

After that I got the correct 1024x768 resolution.

Revision history for this message
ph0nph0n (rockinfed) wrote :

Hi,

I had roughly the same problem, but i'd like to add some details. I was stuck at 800x600, despite setting the resolution to 1024x768 in xorg.conf. Moreover, my mouse was going out of the screen on the left edge, and couldn't reach the right one. And it was the same story with the top and bottom edge. Therefore, to click on any icon, i had to click further on the left, and higher, which was like a guessing game (that's fun at first but quickly get boring!).
All those problems have been resolved by setting HorizSync and VertRefresh. However, i first set too low values for HorizSync, hence i was still stuck in 800x600. Log said HorizSync was "out of range" for 1024x768". That may have been the problem of Ralf (right above), since i first used his values. Using the values provided by Daniel just worked fine (HorizSync 36-52, VertRefresh 36-60).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.