Comment 31 for bug 136853

Revision history for this message
Daniel Durand (durand-d) wrote : Re: [Bug 136853] Re: Screen blanks and freezes after a few minutes of idling, possibly due to broken DPMS

I've just updated jaunty_tormod.
Great, I see the screen !
I see the toolbar on top
the 2nd half of the screen is block with xdhmc marked
but the screen seems freezed and I've no mouse cursor.
But it's a great progress to have a xwindow !
I've not the time today to send a log but I'll send to morrow afternoon...
Tanks
Daniel

2009/3/30 Tormod Volden <email address hidden>

> I uploaded an 1.7.0-1ubuntu1~tormod3 to my PPA which includes
> Francisco's patch, for those of you who are not able to build drivers
> from git. The package is built with CFLAGS="-DSMI_DEBUG". Please test
> it, as well as the xset test suggested by Francisco.
>
> --
> Screen blanks and freezes after a few minutes of idling, possibly due to
> broken DPMS
> https://bugs.launchpad.net/bugs/136853
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in xf86-video-siliconmotion: Confirmed
> Status in “xserver-xorg-video-siliconmotion” source package in Ubuntu:
> Confirmed
>
> Bug description:
> Since switching to Gutsy to verify whether the packages I maintain still
> operate as expected, I have noticed that after a few minutes of idle
> operation, the screen goes blank and cannot be returned to normal. The only
> way to get screen content again is to reboot, which is possible either by
> pressing the ACPI-enabled power button or a remote SSH connection. Broken
> DPMS is suspected, although I have no way of confirming this.
>
> Purposely downgrading xserver-xorg-core and anything that depend on it,
> then pining it to that version, while keeping all the rest of the packages
> to Gutsy versions solves it, which suggests something related to X.org
> upgrade from 1.2 to 1.3 might be at play.
>
> Note: someone on #ltsp mentions a similar situation using
> xserver-xorg-video-amd, yet the exact same AMD driver doesn't exhibit this
> behavior when compiled and used with earlier X releases.
>

--
Daniel Durand