Bug 22001 - R4xxATOM option causes non-native LVDS modes to stop working properly on rv410
Summary: R4xxATOM option causes non-native LVDS modes to stop working properly on rv410
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-30 03:17 UTC by Chí-Thanh Christopher Nguyễn
Modified: 2018-06-12 19:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (87.97 KB, text/plain)
2009-05-30 03:17 UTC, Chí-Thanh Christopher Nguyễn
no flags Details

Description Chí-Thanh Christopher Nguyễn 2009-05-30 03:17:25 UTC
Created attachment 26302 [details]
Xorg.0.log

Due to bug 13353 comment 24, I have to use the R4xxATOM option in xorg.conf, however the following problem appears when trying to use a non-native LVDS mode:

Switching to a resolution other than 1280x800 with xrandr will display the picture only in the top left corner of the screen. The screen area to the right will remain dark. The screen area at the bottom will repeat the lowest line of the desktop.
xrandr --output LVDS --set scaler center/full does not make any difference.

Using a full-screen application which uses a non-native mode (eg. frozen-bubble) will cause the screen to display garbage at first and gradually become totally white.
xrandr --output LVDS --set scaler center/full does not make any difference, either. xrandr --output LVDS --set scaler off will make it work with a centered image.

If the R4xxATOM option is disabled, then non-native modes work. I also tried kernel modesetting from drm-next-radeon/radeon-gem-cs3 and  which exposes the same bug if I boot with the radeon.r4xx_atom=1 kernel parameter.
Comment 1 Chí-Thanh Christopher Nguyễn 2009-05-30 03:20:25 UTC
Sorry, I meant bug 13533 comment 24 and not #13353 above.
Comment 2 Adam Jackson 2018-06-12 19:10:37 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.