Comment 5 for bug 538377

No fglrx remnants showed up in the checks, but I followed the
reinstallation instructions anyway. I've also removed the xorg.conf and
rebooted, with a log as attached. The boot and xserver startup were
normal, but the problem remains, with HDMI output turning off after some
time.

Using the stock lucid kernel, the current version
linux-image-2.6.32-16-generic (2.6.32-16.25), the same HDMI problem
occurs. With both kernels, remote login and using xrandr to change the
mode restores the HDMI output.

However, I'm more sure now that having mplayer running continuously but
paused prevents the HDMI output turning off (at least, it has never
happened so far). 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.

On 19/03/10 20:28, Bryce Harrington wrote:
> Hi Daniel, okay I think we should forward this upstream to look at,
> however there's a couple things I'd just like to doublecheck first.
>
> I see you posted an xorg.conf. Pretty much it looks totally okay, but I
> think everything that is listed there are now defaults, and in fact
> should set up properly with no xorg.conf. Could you please try moving
> aside your xorg.conf and boot with no xorg.conf at all, and see if the
> issue reproduces?
>
> Second, you mentioned you'd had fglrx installed previously. Sometimes,
> depending on how it is uninstalled, it can leave some bits on the disk
> which then screw up the open source driver's 3D. I don't see any
> evidence this is happening here, but just in case please follow the
> directions at the following link to purge any remaining fglrx
> components:
> https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver
>
> Finally, I notice you're running the 2.6.33 kernel. Does the same thing
> happen when using the stock lucid kernel?
>
> ** Changed in: xserver-xorg-video-ati (Ubuntu)
> Status: Confirmed => Incomplete
>
>