XF86Config-4 as created during installation had the DPMS option.
Subsequently I had an intermittent problem with the monitor going to sleep
every few seconds, even though I kept pressing a key to get the screen back
The problem has not recurred since I commented that option.
GeForce2 GTS card, Iiyama VisionMaster MF-8617E monitor, Abit KAy-100 m/b
The problem has actually come back, even though I still have the DPMS option commented out. This may be something to do with the ACPI problems in 2.4.
When it started happening today I got the following message several times in the log: (WW) Cannot open APM
We (Red Hat) should really try to resolve this before next release.
NVidia cards are proprietary. As such there are no specifications available
with which to understand how their cards work without signing an NDA.
Doing so would exclude any fixes from being included in the official open
source. As such, if this problem is caused by the nvidia driver all I can
do is send it upstream.
Not what you want to hear but... ATI Radeon cards are very well supported in
contrast. Worth it to upgrade, but obviously that doesn't help if you can't
afford it. Just a suggestion.
I understand what you're saying, but I should point out that this problem occurs
with the 'nv' driver, which is written and maintained by the XFree86 team, not
NVidia's 'nvidia' binary driver. Whilst I did install the nvidia driver in 7.0,
I haven't done so yet in Fisher.
Sorry, but I was in fact refering to the nv driver as supplied by the
XFree86 team. It is undocumented whichever driver you're using.
This must be a glitch in APM or ACPI as you postulated.. Reassigning
to apmd package with hopes someone at meridian handling apm can look into
this with the right hardware.
This has nothing whatsoever to do with apmd (which is just responsible for
If it's an ACPI problem, it's a kernel problem - but I'd rather think it's an
XFree86 problem (DPMS). Does this happen in text mode?
Our kernel doesn't use ACPI anymore.
Must be an X problem
This problem hasn't occurred in Wolverine at all.
Closing bug, submitter indicates it is fixed now...
This just started happening again tonight, but I think it is actually caused
by xscreensaver. I've killed the xscreensaver process and it seems to have