Bug 25496 (Perry)

Summary:

RV770 + KMS + resolution change = black screen for 1 minute.

Product:

xorg

Reporter:

Perry3D <perry3d>

Component:

Driver/Radeon

Assignee:

xf86-video-ati maintainers <xorg-driver-ati>

Status:

RESOLVED INVALID

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

medium

Version:

7.5 (2009.10)

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
Xorg.0.log	none
/var/log/kernel.log	none

Description Perry3D 2009-12-07 11:41:38 UTC

Hi, i am using Arch Linux with this set:
- kernel 26.6.32 with radeon as module
- xorg 7.5
- libdrm from git
- mesa from git
- radeon from git
- no xorg.conf

Hardware: 
- VGA compatible controller: ATI Technologies Inc RV770 [Radeon HD 4850] - 1 GB Ram
- Hyundai W241D (1920x1200)
- x64 System
- Mainboard: Foxconn A7DA-S, 790GX (IGP disabled)

When i switch my resolution the screen gets black for ca. 1 minute and then the screen appears. This also happens at boot time (before X11 starts) when the machine switch to the resolution of my TFT.

/var/log/kernel.log shows the following:
Dec  7 20:23:55 perry64 kernel: Unpin not necessary for ffff880096d02800 !
Dec  7 20:23:55 perry64 kernel: executing set pll
Dec  7 20:23:55 perry64 kernel: executing set crtc timing
Dec  7 20:23:55 perry64 kernel: [drm] TMDS-9: set mode  2b

Comment 1 Perry3D 2009-12-07 11:43:34 UTC

Created attachment 31823 [details] [review]
Xorg.0.log

Comment 2 Perry3D 2009-12-07 11:44:06 UTC

Created attachment 31824 [details]
/var/log/kernel.log

Comment 3 Alex Deucher 2010-10-19 18:53:14 UTC

Make sure you have the proper firmware images installed.  Is this still an issue with a newer kernel?

Comment 4 Adam Jackson 2018-06-12 19:09:07 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.