Resolution issue: default screen resolution impossible to get with ATI Radeon Xpress (regression)

Bug #155501 reported by viktor
4
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.22 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-ati

I upgraded an up-to-date Feisty amd64 to Gutsy, knowing of the caveats concerning bug #132716.
On reboot with the upgrade I got the blank screen (more exactly no output signal which causes the display to go on stand-by) on X window described in that bug then installed xserver-xorg-video-ati_6.7.195+git20071020tv_amd64.deb which got X window to work, only with bad resolution.
I had also activated the proprietary ATI driver in the 'Restricted Driver Manager' menu.

Then I could never get the correct resolution through menu 'Screen & resolution'. Chosing the correct 1400x1050 even at the default 60Hz suggested (LCD supports 75Hz) doesn't work.

Forcing thru xrandr -s 1400x1050 -r 75 (or 60) gives the same blank screen (i.e. display goes on standby).
Installed Samsung windows .inf driver to add the display to the list in the S&R menu but it choses resolution 1600x1200 (unsupported) on reboot and 1400x1050 is nowhere to be found.

I tried dpkg reconfigure, then to manually edit the xorg.conf file, to no avail.

Currently working with 1280x1024 which is the biggest.

Revision history for this message
viktor (lfraisse) wrote :

Here's my xorg.conf file, at least the one that gets me an acceptable 1280x1024 to work on, not a widescreen 1280x960 (or the unsupported 1600x1200).

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Are you using fglrx, the proprietary driver, instead of xserver-xorg-video-ati?

Revision history for this message
viktor (lfraisse) wrote :

Yes, I had tried a few changes but fglrx is what gives me the most stable solution.
Sorry if the bug is not filed under the correct category.

Revision history for this message
viktor (lfraisse) wrote :

Cleanly downgraded from an optimistic 8.40+ ATI driver to 8.37.6
No change. The best I can get is still 1280x1024, with proprietary fglrx (activating the ATI restricted driver seems to help).
The windows Samsung .inf driver has been installed since PnP wasn't ok with gutsy, yet the native 1400x1050 resolution doesn't appear in the 'Screen & Resolution' menu/screen reference, jumping from 1280 to 1600 (not supported)!
Forcing 1400 crashes X window.

Revision history for this message
viktor (lfraisse) wrote :

Here's the xorg.conf file generated after clean ATI driver reinstall (although I switched from comand line the catalyst install manager at some point) and chosing PnP screen with 1400 (loads 1280).
Don't know where the 1600x1200 resolution comes from...

Revision history for this message
viktor (lfraisse) wrote :

I eventually came back to the pre-upgrade xorg.conf file. My 1400x1050 screen resolution is now fine (although refresh freq could go to 75Hz).
Proprietary ATI drivers still enabled.

I hope this will help to mend the ugly regression that came in with the Gutsy release.

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi lfraisse,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in linux-restricted-modules-2.6.22:
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for fglrx bugs, which now includes a process for upstreaming bugs to AMD.

  http://bugs.launchpad.net/ubuntu/+source/fglrx-installer

To transition your bug into the new fglrx-package, we need your help. Please do the following:

 a. Verify the bug occurs in Intrepid.
     (Intrepid ISOs: http://cdimage.ubuntu.com)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Click 'Also affects distribution'
 d. Set 'Source Package Name' to 'fglrx-installer'
 e. Click Continue

Thank you. This will assist us in reviewing and upstreaming your fglrx bug, as appropriate.

[We'll expire the fglrx bugs in l-r-m-* in a month or so.]

Revision history for this message
viktor (lfraisse) wrote :

My hardware configuration has changed (and I can't smoothly remove the new
Nvidia card from my tiny barebone) so I can't try and replicate the bug
under Intrepid.
Sorry,
LF

>
>>
>>
>> On Fri, Oct 31, 2008 at 02:13, Bryce Harrington <
>> <email address hidden>> wrote:
>>
>>>
>>> [This is an automated message]
>>>
>>> As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for
>>> fglrx bugs, which now includes a process for upstreaming bugs to AMD.
>>>
>>> http://bugs.launchpad.net/ubuntu/+source/fglrx-installer
>>>
>>> To transition your bug into the new fglrx-package, we need your help.
>>> Please do the following:
>>>
>>> a. Verify the bug occurs in Intrepid.
>>> (Intrepid ISOs: http://cdimage.ubuntu.com)
>>> b. If you haven't already, please include in the bug:
>>> * Your /var/log/Xorg.0.log
>>> * The output of `lspci -vvnn`
>>> * Steps to reproduce the issue
>>> c. Click 'Also affects distribution'
>>> d. Set 'Source Package Name' to 'fglrx-installer'
>>> e. Click Continue
>>>
>>> Thank you. This will assist us in reviewing and upstreaming your fglrx
>>> bug, as appropriate.
>>>
>>> [We'll expire the fglrx bugs in l-r-m-* in a month or so.]
>>>
>>> --
>>> Resolution issue: default screen resolution impossible to get with ATI
>>> Radeon Xpress (regression)
>>> https://bugs.launchpad.net/bugs/155501
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>>
>>
>>
>

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

OK, it would probably be best to close this since you can't reproduce it any more due to your new hardware. Thanks for the report all the same.

Changed in linux-restricted-modules-2.6.22 (Ubuntu):
status: Incomplete → Invalid
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.