Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is ok)

Bug #83072 reported by Boris Dušek on 2007-02-03
2
Affects Status Importance Assigned to Milestone
xserver-xorg-video-vesa (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg

Hello,

I tried Feisty Herd 2 (as live CD), and it has the same problem as Edgy Eft:
The screen in graphical environment is skewed; autodetection uses the vesa driver.

This is a regression from Dapper - there it worked fine.
I have some photos of the problem at flickr:http://www.flickr.com/photos/76746644@N00/378412923/http://www.flickr.com/photos/76746644@N00/378411688/

My screen is 1400x1050, Graphics card is Mobility Radeon X1450, laptop is ASUS F2JE.

I tried to follow instructions at DebuggingXAutoconfiguration, I will attach the outputs soon.
But what surprises me is that the xorg.conf for Dapper and Feisty is the same, but there is no problem in Dapper.

I tried to reconfigure xserver-xorg, and the screen was no longer skewed, but, the resolution was 1024x768, which is not desirable. (This happened even though only 1400x1050 was set in the config.)
The only difference between Dapper's, skewed and low-resolution xorg.conf is always the HorizSync and VertRefresh parameters.

The problem is present no matter if I choose default boot options, or if I remove "quiet splash" and add "vga=771" (or "vga=791").

I will be glad if I can help to resolve this issue by providing additional information.

Thanks,
Boris Dušek

Boris Dušek (dusek) wrote :
Boris Dušek (dusek) wrote :

discover --disable=parallel,serial,usb,ide,scsi,pcmcia

Output is empty.

Boris Dušek (dusek) wrote :
Boris Dušek (dusek) wrote :

This is for the reconfigured server, where the screen is not skewed, but resolution is only 1024x768

Boris Dušek (dusek) wrote :

Feisty autodetected configuration

Boris Dušek (dusek) wrote :

Feisty - configuration after sudo dpkg-reconfigure xserver-xorg

description: updated
description: updated
Boris Dušek (dusek) on 2007-02-03
description: updated
Boris Dušek (dusek) wrote :

Still present in Herd 5 (Feisty).

Boris Dušek (dusek) wrote :

Wow, in Feisty Beta it's fixed. However, part of boot is displayed in text mode, I don't know if this is intentional.

Timo Aaltonen (tjaalton) wrote :

Thanks for testing! The new vesa driver did the trick, I think.

Changed in xorg:
status: Unconfirmed → Fix Released
Boris Dušek (dusek) wrote :

btw., why fglrx (ATI's binary driver) is not used for my card when we have the restricted driver manager?

Boris Dušek (dusek) wrote :

sadly, X crashes on start with Feisty RC
here is diff between xorg.conf from beta to RC:
< Modes "1400x1050" "(pitch" "1400)"
---
> Modes "1024x768" "800x600" "640x480"
122c115
< Modes "1400x1050" "(pitch" "1400)"
---
> Modes "1024x768" "800x600" "640x480"
126c119
< Modes "1400x1050" "(pitch" "1400)"
---
> Modes "1024x768" "800x600" "640x480"
130c123
< Modes "1400x1050" "(pitch" "1400)"
---
> Modes "1024x768" "800x600" "640x480"
134c127
< Modes "1400x1050" "(pitch" "1400)"
---
> Modes "1024x768" "800x600" "640x480"
138c131
< Modes "1400x1050" "(pitch" "1400)"
---
> Modes "1024x768" "800x600" "640x480"

To clarify, in Beta, where it was working, the line with "(pitch" was used. In RC, the line where "1400x1050" resolution was missing was used

The most important part of Xorg.0.log (the very end):

(II) VESA(0): Total Memory: 256 64KB banks (16384kB)
(II) VESA(0): Generic Monitor: Using hsync value of 63.98 kHz
(II) VESA(0): Generic Monitor: Using vrefresh value of 60.02 Hz
(II) VESA(0): Not using mode "1024x768" (no mode of this name)
(II) VESA(0): Not using mode "800x600" (no mode of this name)
(II) VESA(0): Not using mode "640x480" (no mode of this name)
(II) VESA(0): Not using built-in mode "1400x1050" (hsync out of range)
(II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
(II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
(II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
(WW) VESA(0): No valid modes left. Trying less strict filter...

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xffffe420]
2: /usr/X11R6/bin/X(InitOutput+0x9aa) [0x80a5b9a]
3: /usr/X11R6/bin/X(main+0x27b) [0x807456b]
4: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7dabebc]
5: /usr/X11R6/bin/X(FontFileCompleteXLFD+0x1e1) [0x8073ab1]

Fatal server error:
Caught signal 11. Server aborting

I will attach some full version of relevant files soon.

Boris Dušek (dusek) wrote :
Timo Aaltonen (tjaalton) wrote :

that is bug 89853

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

Other bug subscribers