Comment 23 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

2009/3/23 Francisco Jerez <email address hidden>

> Daniel: according to your logs you have a monitor connected to the VGA
> output, is that right or is monitor detection failing?

No, I just have my IBM thinkpad 1200 series and no external monitor
selected....

For other tests, i can't do them before next saturday...

>
> If you really have a monitor connected, do you experience the DPMS problem
> with the external monitor?
>
> Could you try setting:
> > Option "UseBIOS" "off"
> in your xorg.conf, Section "Device"?
>
> You could also try to build the current development version from sources.
> To check out a copy from the git repository:
> > git clone git://
> anongit.freedesktop.org/xorg/driver/xf86-video-siliconmotion
>
> --
> 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