Bug 27259

Summary: HD3450 HDMI output intermittently turns off
Product: xorg Reporter: Bryce Harrington <bryce>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: high CC: dmn, hramrach
Version: 7.4 (2008.09)   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg.conf
none
dmesg.txt
none
Xorg.0.log none

Description Bryce Harrington 2010-03-23 04:19:58 UTC 
Forwarding this bug from Ubuntu reporter Daniel Newman:
http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/538377

[Problem]
Intermittently with HDMI the display turns off and the monitor reports no HDMI output.

[Workaround]
When this occurs, issue the following commands:

xrandr -d :0 --output DVI-0 --mode 1024x768

which makes the display visible again, in the lower resolution, then

xrandr -d :0 --output DVI-0 --mode 1920x1200

which restores the original display. Things then function normally until the next random HDMI output failure.

[Original Description]
1) lsb_release -rd
Description:	Ubuntu lucid (development branch)
Release:	10.04

2) apt-cache policy xserver-xorg-video-radeon
xserver-xorg-video-radeon:
  Installed: 1:6.12.191+git20100306.e7b41f8c-0ubuntu0sarvatt
  Candidate: 1:6.12.191+git20100306.e7b41f8c-0ubuntu0sarvatt
  Version table:
 *** 1:6.12.191+git20100306.e7b41f8c-0ubuntu0sarvatt 0
        500 http://ppa.launchpad.net lucid/main Packages
        100 /var/lib/dpkg/status
     1:6.12.191-1ubuntu2 0
        500 http://archive.ubuntu.com lucid/main Packages

3) The HD3450 DVI-HDMI output is connected by HDMI cable to an ASUS MK241H monitor.  It should provide a 1920x1200 display + audio via the monitor.  When it does so, xrandr reports:

xrandr -q
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
DIN disconnected (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-0 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200      60.0*+
   1920x1080      60.0  
   1600x1200      60.0  
   1680x1050      60.0  
   1600x1024      60.2  
   1400x1050      70.0     60.0     60.0  
   1280x1024      75.0     60.0  
   1440x900       75.0     59.9  
   1280x960       60.0  
   1360x765       59.8  
   1360x768       60.0     59.8  
   1280x800       74.9     59.8  
   1152x864       75.0     75.0     70.0     60.0  
   1280x768       74.9     59.9  
   1280x720       60.0  
   1024x768       75.1     75.0     70.1     60.0  
   832x624        74.6  
   800x600        72.2     75.0     60.3     56.2  
   720x576        50.0  
   848x480        60.0  
   720x480        59.9  
   640x480        75.0     72.8     72.8     72.8     75.0     60.0     59.9     59.9  
   720x400        70.1  


4) The display generally starts fine, but intermittently, after apparently random times and with random programs running, the display turns off and the monitor reports no HDMI output.  Logging in from another machine, everything appears to be normal and xrandr reports the same as above.  However, there is no HDMI output to the monitor.  This can be fixed by xrandr, using first:

xrandr -d :0 --output DVI-0 --mode 1024x768

which makes the display visible again, in the lower resolution, then

xrandr -d :0 --output DVI-0 --mode 1920x1200

which restores the original display.  Things then function normally until the next random HDMI output failure.


Previously, under karmic, I used the closed source "fglrx" driver on the system. It functioned correctly, without any drop-outs.

Having mplayer running continuously but paused seems to prevent the HDMI output turning off.  Maybe this is some power management issue, where
having mplayer running prevents the HDMI output getting into some low
power state from which it cannot return.
Comment 1 Bryce Harrington 2010-03-23 04:21:27 UTC 
Created attachment 34355 [details]
xorg.conf
Comment 2 Bryce Harrington 2010-03-23 04:21:44 UTC 
Created attachment 34356 [details]
dmesg.txt
Comment 3 Bryce Harrington 2010-03-23 04:22:05 UTC 
Created attachment 34357 [details]
Xorg.0.log
Comment 4 Alex Deucher 2010-03-23 08:18:42 UTC 
you might try loading the radeon drm with new_pll=0 or try this patch:
http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commit;h=383be5d1789d9a7a2e77dca1cb0aca89507d069e
if your drm doesn't already have it.
Comment 5 Dan Newman 2010-03-23 17:35:58 UTC 
Using the ubuntu 2.6.33-020633-generic kernel, setting new_pll=0 makes 
the system unusable.

 From the time it goes into graphics mode just prior to gdm starting, 
the screen blinks to black every few seconds, then returns to normal for 
a second or two, then repeats this sequence.

How can I check if this patch has been applied to a ubuntu kernel image?


On 24/03/10 02:18, bugzilla-daemon@freedesktop.org wrote:
> http://bugs.freedesktop.org/show_bug.cgi?id=27259
>
>
>
>
>
> --- Comment #4 from Alex Deucher<agd5f@yahoo.com>   2010-03-23 08:18:42 PST ---
> you might try loading the radeon drm with new_pll=0 or try this patch:
> http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commit;h=383be5d1789d9a7a2e77dca1cb0aca89507d069e
> if your drm doesn't already have it.
>
>
>
Comment 6 Alex Deucher 2010-03-23 17:50:14 UTC 
(In reply to comment #5)
> Using the ubuntu 2.6.33-020633-generic kernel, setting new_pll=0 makes 
> the system unusable.
> 
>  From the time it goes into graphics mode just prior to gdm starting, 
> the screen blinks to black every few seconds, then returns to normal for 
> a second or two, then repeats this sequence.
> 
> How can I check if this patch has been applied to a ubuntu kernel image?
>

Bryce would know for sure, but it was only applied after 2.6.33 was released, so I suspect it's not in the ubuntu kernel.  The 2.6.34rcX kernels should have it.
Comment 7 Bryce Harrington 2010-03-23 17:56:10 UTC 
I've filed a request for the kernel team to include it, on a separate bug report.
Comment 8 Bryce Harrington 2010-03-23 17:56:54 UTC 
(Actually, it was the downstream bug report for this bug report *grin*)
Comment 9 Alex Deucher 2012-04-25 05:58:45 UTC 
Is this still an issue with a newer driver/kernel?
Comment 10 Dan Newman 2012-04-25 06:26:28 UTC 
Sorry, I've moved on to newer hardware and can't check the current kernel


On 25/04/12 22:58, bugzilla-daemon@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=27259
>
> --- Comment #9 from Alex Deucher<agd5f@yahoo.com>  2012-04-25 05:58:45 PDT ---
> Is this still an issue with a newer driver/kernel?
>

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.