Bug 31689 - Radeon 5650: only flickering while using krandrtray - not while booting with second screen
Summary: Radeon 5650: only flickering while using krandrtray - not while booting with ...
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-17 14:29 UTC by Tobias Kaminsky
Modified: 2010-11-17 23:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Tobias Kaminsky 2010-11-17 14:29:41 UTC 
Hello,

if I add ad second screen and enable it via krandrtray I only get a flickering screen.
If I boot my Sony Vaio VPCEB1Z1E with this second screen connected everything is fine. Even the boot messages are shown.

Here are my versions:
2.6.36
mesa-7.9 with gallium
xf86-video-ati from git
xorg-server-1.9.2

I have followed this guide: http://en.gentoo-wiki.com/wiki/Radeon

Thank you
Tobias Kaminsky
Comment 1 Alex Deucher 2010-11-17 14:31:27 UTC 
try 2.6.37 or boot your current kernel with radeon.new_pll=0
Comment 2 Tobias Kaminsky 2010-11-17 14:59:54 UTC 
Thank you very very much.
I added radeon.new_pll=0 to 2.6.36 and changed to libdrm-9999 and mesa-9999 and now it is working :)

very great!!

Thank you
Tobi
Comment 3 Tobias Kaminsky 2010-11-17 22:48:31 UTC 
As it is working now, which packages need to be a SVN/GIT version? As I do not want to have so many unstable version.

Thank you
Comment 4 Alex Deucher 2010-11-17 23:16:35 UTC 
(In reply to comment #3)
> As it is working now, which packages need to be a SVN/GIT version? As I do not
> want to have so many unstable version.

You just need a 2.6.37 kernel or an older kernel with radeon.new_pll=0, you don't have to change any other software.

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.