on my (currently up to date) f11 beta system, every so often while i'm in gnome, the screen goes black. no, it's not the screensaver kicking in after a certain idle period. i might have just typed something and, two seconds later, blackness. move the mouse, i get my display back. no harm, just weird.
i'm currently running the latest radeon driver, with "XAA" in xorg.conf. it's not fatal, obviously, just unusual -- i've never had that behaviour in previous versions of fedora.
rday --
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================
I have this problem too. In my case I have an Nvidia board in a laptop:
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 160M (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 0233 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f5000000 (32-bit, non-prefetchable) Memory at e0000000 (64-bit, prefetchable) Memory at f2000000 (64-bit, non-prefetchable) I/O ports at df00 Capabilities: <access denied> Kernel modules: nouveau
This is actually driving two displays -- one is the laptop monitor itself and the second is a Dell 2408WFP 24" wide screen flat panel monitor. The screen goes black on both these monitors, but the laptop's monitor recovers first and the Dell flat panel about 2-3 seconds later. The display contents seem to be preserved and there is no visible harm. But it is very disconcerting and obviously shouldn't be happening.
Bob
On 05/17/2009 08:20 AM, Robert P. J. Day wrote:
on my (currently up to date) f11 beta system, every so often while i'm in gnome, the screen goes black. no, it's not the screensaver kicking in after a certain idle period. i might have just typed something and, two seconds later, blackness. move the mouse, i get my display back. no harm, just weird.
i'm currently running the latest radeon driver, with "XAA" in xorg.conf. it's not fatal, obviously, just unusual -- i've never had that behaviour in previous versions of fedora.
rday
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================
On 05/17/2009 08:20 AM, Robert P. J. Day wrote:
on my (currently up to date) f11 beta system, every so often while i'm in gnome, the screen goes black. no, it's not the screensaver kicking in after a certain idle period. i might have just typed something and, two seconds later, blackness. move the mouse, i get my display back. no harm, just weird.
i'm currently running the latest radeon driver, with "XAA" in xorg.conf. it's not fatal, obviously, just unusual -- i've never had that behaviour in previous versions of fedora.
On Sun, May 17, 2009 at 09:22:47AM -0400, Robert L Cochran wrote:
I have this problem too. In my case I have an Nvidia board in a laptop:
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 160M (rev a1) (prog-if 00 [VGA controller])
Same here. I've seen it on both my laptop:
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
and desktop:
01:00.0 VGA compatible controller: ATI Technologies Inc RV380 [Radeon X600 (PCIE)] 01:00.1 Display controller: ATI Technologies Inc RV380 [Radeon X600]
On Mon, May 18, 2009 at 10:51:58AM -0400, Chuck Anderson wrote:
On 05/17/2009 08:20 AM, Robert P. J. Day wrote:
on my (currently up to date) f11 beta system, every so often while i'm in gnome, the screen goes black. no, it's not the screensaver kicking in after a certain idle period.
Same here. I've seen it on both my laptop:
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
and desktop:
01:00.0 VGA compatible controller: ATI Technologies Inc RV380 [Radeon X600 (PCIE)] 01:00.1 Display controller: ATI Technologies Inc RV380 [Radeon X600]
Like this? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243022
I am seeing that at least on one machine with F9 currently installed on it. Not as often like with F7 where it was _really_ annoying. So fra my rawhide test box did not suffer from that but maybe I was not waiting long enough.
Michal
On Mon, May 18, 2009 at 09:14:16AM -0600, Michal Jaegermann wrote:
On Mon, May 18, 2009 at 10:51:58AM -0400, Chuck Anderson wrote:
On 05/17/2009 08:20 AM, Robert P. J. Day wrote:
on my (currently up to date) f11 beta system, every so often while i'm in gnome, the screen goes black. no, it's not the screensaver kicking in after a certain idle period.
Same here. I've seen it on both my laptop:
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
and desktop:
01:00.0 VGA compatible controller: ATI Technologies Inc RV380 [Radeon X600 (PCIE)] 01:00.1 Display controller: ATI Technologies Inc RV380 [Radeon X600]
Like this? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243022
I am seeing that at least on one machine with F9 currently installed on it. Not as often like with F7 where it was _really_ annoying. So fra my rawhide test box did not suffer from that but maybe I was not waiting long enough.
No, not like that at all. The black outs I've seen are not accompanied by log messages. So much has changed since 2007 that it is probably worthwhile opening a new bug.
On Mon, May 18, 2009 at 03:24:55PM -0400, Chuck Anderson wrote:
On Mon, May 18, 2009 at 09:14:16AM -0600, Michal Jaegermann wrote:
Like this? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243022
No, not like that at all. The black outs I've seen are not accompanied by log messages.
A hypothetical correlation of blackouts and log entries is most likely bogus. Logs of X are unfortunately not time stamped. I do not think I can find anything of that sort for what I am observing _right now_ with F9 installation. The gist of the issue is that a monitor signal from time to time seems to disappear, without any observable reason, for a short few seconds and this was not happening at all some years ago.
So much has changed since 2007 that it is probably worthwhile opening a new bug.
I have doubts about real changes in this area but by any means open a new bug.
Michal
Le 18/05/2009 16:51, Chuck Anderson a écrit :
the screen goes black. no, it's not the screensaver
kicking in after a certain idle period. i might have just typed something and, two seconds later, blackness. move the mouse, i get my display back. no harm, just weird.
i'm currently running the latest radeon driver, with "XAA" inxorg.conf. it's not fatal, obviously, just unusual -- i've never had that behaviour in previous versions of fedora.
This happens 2 or 3 times a day, with a nvidia gpu, using proprietary driver and a Hyundai W220D (plugged on the DVI connector) monitor.
udi = '/org/freedesktop/Hal/devices/pci_10de_407' info.linux.driver = 'nvidia' (string) info.parent = '/org/freedesktop/Hal/devices/pci_8086_2a01' (string) info.product = 'GeForce 8600M GT' (string) info.subsystem = 'pci' (string) info.udi = '/org/freedesktop/Hal/devices/pci_10de_407' (string) info.vendor = 'nVidia Corporation' (string) linux.hotplug_type = 2 (0x2) (int) linux.subsystem = 'pci' (string) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0' (string) pci.device_class = 3 (0x3) (int) pci.device_protocol = 0 (0x0) (int) pci.device_subclass = 0 (0x0) (int) pci.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0' (string) pci.product = 'GeForce 8600M GT' (string) pci.product_id = 1031 (0x407) (int) pci.subsys_product_id = 5682 (0x1632) (int) pci.subsys_vendor = 'ASUSTeK Computer Inc.' (string) pci.subsys_vendor_id = 4163 (0x1043) (int) pci.vendor = 'nVidia Corporation' (string) pci.vendor_id = 4318 (0x10de) (int)
On Mon, 2009-05-18 at 17:24 +0200, Axel wrote:
Le 18/05/2009 16:51, Chuck Anderson a écrit :
the screen goes black. no, it's not the screensaver
kicking in after a certain idle period. i might have just typed something and, two seconds later, blackness. move the mouse, i get my display back. no harm, just weird.
i'm currently running the latest radeon driver, with "XAA" inxorg.conf. it's not fatal, obviously, just unusual -- i've never had that behaviour in previous versions of fedora.
This happens 2 or 3 times a day, with a nvidia gpu, using proprietary driver and a Hyundai W220D (plugged on the DVI connector) monitor.
I'm seeing the same thing on a Dell Inspiron 9300 running the nvidia driver. It might happen once a day.
01:00.0 VGA compatible controller: nVidia Corporation NV41.8 [GeForce Go 6800] (rev a2)
Screen goes blank (like the screensaver is turning on, but I'm typing at the time) and then comes back up again.
Weird!
R.
Rodd Clarkson wrote:
Screen goes blank (like the screensaver is turning on, but I'm typing at the time) and then comes back up again.
Same here on a notebook with Intel graphics.
I also noticed that up to F10, a frame rate of 50 Hz was offered and set for the notebook display. On F11, there is no 50 Hz setting, and the display is set to 65 Hz (if I remember correctly, I don't have the notebook here right now).
Maybe the frame rate slightly exceeds the upper limit of the display's specifications, and the display blanks for a short moment because of that?
On Tue, 19 May 2009, Richard Körber wrote:
Rodd Clarkson wrote:
Screen goes blank (like the screensaver is turning on, but I'm typing at the time) and then comes back up again.
Same here on a notebook with Intel graphics.
i'm feeling so much better now that i know it's not just me. misery shared and all that. :-)
rday --
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================
On 05/17/2009 02:20 PM, Robert P. J. Day wrote:
on my (currently up to date) f11 beta system, every so often while i'm in gnome, the screen goes black. no, it's not the screensaver kicking in after a certain idle period. i might have just typed something and, two seconds later, blackness. move the mouse, i get my display back. no harm, just weird.
i'm currently running the latest radeon driver, with "XAA" in xorg.conf. it's not fatal, obviously, just unusual -- i've never had that behaviour in previous versions of fedora.
rday
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================
This is an already reported bug of gnome-power-manager, IIRC
On Tue, May 19, 2009 at 12:23:27PM +0200, Harald Hoyer wrote:
On 05/17/2009 02:20 PM, Robert P. J. Day wrote:
on my (currently up to date) f11 beta system, every so often while i'm in gnome, the screen goes black. no, it's not the screensaver kicking in after a certain idle period. i might have just typed something and, two seconds later, blackness. move the mouse, i get my display back. no harm, just weird.
i'm currently running the latest radeon driver, with "XAA" in xorg.conf. it's not fatal, obviously, just unusual -- i've never had that behaviour in previous versions of fedora.
This is an already reported bug of gnome-power-manager, IIRC
Could this be https://bugzilla.redhat.com/498041 rearing its head again? I am experiencing this, too, using the build that supposedly fixed that bug. I'm going to enable some verbosity to see if I can catch it in the act before reopening.
"Paul W. Frields" stickster@gmail.com writes:
Could this be https://bugzilla.redhat.com/498041 rearing its head
I wonder if there is a second related bug. I was running with the "dim when idle" enabled just to see if I liked it. After each dimming the display would only be brightened back part way to the previous levels. After a few cycles of this the display was much to dim to read.
-wolfgang
On Tue, 2009-05-19 at 12:51 -0400, Paul W. Frields wrote:
On Tue, May 19, 2009 at 12:23:27PM +0200, Harald Hoyer wrote:
On 05/17/2009 02:20 PM, Robert P. J. Day wrote:
on my (currently up to date) f11 beta system, every so often while i'm in gnome, the screen goes black. no, it's not the screensaver kicking in after a certain idle period. i might have just typed something and, two seconds later, blackness. move the mouse, i get my display back. no harm, just weird.
i'm currently running the latest radeon driver, with "XAA" in xorg.conf. it's not fatal, obviously, just unusual -- i've never had that behaviour in previous versions of fedora.
This is an already reported bug of gnome-power-manager, IIRC
Could this be https://bugzilla.redhat.com/498041 rearing its head again? I am experiencing this, too, using the build that supposedly fixed that bug. I'm going to enable some verbosity to see if I can catch it in the act before reopening.
It's not the same bug, because I had that bug, and I don't have it now. :) But it could somehow be related to that. What timeout do you guys all have set in gnome-power-preferences for 'Put display to sleep when...'?
On Tue, 19 May 2009, Adam Williamson wrote:
On Tue, 2009-05-19 at 12:51 -0400, Paul W. Frields wrote:
On Tue, May 19, 2009 at 12:23:27PM +0200, Harald Hoyer wrote:
On 05/17/2009 02:20 PM, Robert P. J. Day wrote:
on my (currently up to date) f11 beta system, every so often while i'm in gnome, the screen goes black. no, it's not the screensaver kicking in after a certain idle period. i might have just typed something and, two seconds later, blackness. move the mouse, i get my display back. no harm, just weird.
i'm currently running the latest radeon driver, with "XAA" in xorg.conf. it's not fatal, obviously, just unusual -- i've never had that behaviour in previous versions of fedora.
This is an already reported bug of gnome-power-manager, IIRC
Could this be https://bugzilla.redhat.com/498041 rearing its head again? I am experiencing this, too, using the build that supposedly fixed that bug. I'm going to enable some verbosity to see if I can catch it in the act before reopening.
It's not the same bug, because I had that bug, and I don't have it now. :) But it could somehow be related to that. What timeout do you guys all have set in gnome-power-preferences for 'Put display to sleep when...'?
for the display, mine's set for 30 minutes but it's *absolutely* not a function of that time value since, as others have mentioned, the screen can go black totally arbitrarily, like when i'm literally in the middle of typing something. can i assume that's pretty much what's happening to some of the others who have confirmed this?
rday --
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================
On 05/19/2009 09:44 PM, Robert P. J. Day wrote:
for the display, mine's set for 30 minutes but it's *absolutely* not a function of that time value since, as others have mentioned, the screen can go black totally arbitrarily, like when i'm literally in the middle of typing something. can i assume that's pretty much what's happening to some of the others who have confirmed this?
Yup
30 minutes here same symptom
On Tue, 2009-05-19 at 23:24 +0000, "Jóhann B. Guðmundsson" wrote:
On 05/19/2009 09:44 PM, Robert P. J. Day wrote:
for the display, mine's set for 30 minutes but it's *absolutely* not a function of that time value since, as others have mentioned, the screen can go black totally arbitrarily, like when i'm literally in the middle of typing something. can i assume that's pretty much what's happening to some of the others who have confirmed this?
Yup
30 minutes here same symptom
Can you guys set it to 'never' and see if the behaviour changes?
On Tue, 19 May 2009, Adam Williamson wrote:
On Tue, 2009-05-19 at 23:24 +0000, "Jóhann B. Guðmundsson" wrote:
On 05/19/2009 09:44 PM, Robert P. J. Day wrote:
for the display, mine's set for 30 minutes but it's *absolutely* not a function of that time value since, as others have mentioned, the screen can go black totally arbitrarily, like when i'm literally in the middle of typing something. can i assume that's pretty much what's happening to some of the others who have confirmed this?
Yup
30 minutes here same symptom
Can you guys set it to 'never' and see if the behaviour changes?
ok, that's just the "display" setting under System -> Preferences -> Power Management, right?
rday --
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================
On Wed, 2009-05-20 at 00:42 -0400, Robert P. J. Day wrote:
On Tue, 19 May 2009, Adam Williamson wrote:
On Tue, 2009-05-19 at 23:24 +0000, "Jóhann B. Guðmundsson" wrote:
On 05/19/2009 09:44 PM, Robert P. J. Day wrote:
for the display, mine's set for 30 minutes but it's *absolutely* not a function of that time value since, as others have mentioned, the screen can go black totally arbitrarily, like when i'm literally in the middle of typing something. can i assume that's pretty much what's happening to some of the others who have confirmed this?
Yup
30 minutes here same symptom
Can you guys set it to 'never' and see if the behaviour changes?
ok, that's just the "display" setting under System -> Preferences -> Power Management, right?
Yup.
On Tue, May 19, 2009 at 10:09:10PM -0700, Adam Williamson wrote:
On Wed, 2009-05-20 at 00:42 -0400, Robert P. J. Day wrote:
On Tue, 19 May 2009, Adam Williamson wrote:
On Tue, 2009-05-19 at 23:24 +0000, "Jóhann B. Guðmundsson" wrote:
On 05/19/2009 09:44 PM, Robert P. J. Day wrote:
for the display, mine's set for 30 minutes but it's *absolutely* not a function of that time value since, as others have mentioned, the screen can go black totally arbitrarily, like when i'm literally in the middle of typing something. can i assume that's pretty much what's happening to some of the others who have confirmed this?
Yup
30 minutes here same symptom
Can you guys set it to 'never' and see if the behaviour changes?
ok, that's just the "display" setting under System -> Preferences -> Power Management, right?
Yup.
Sorry to hit this thread late. My setting was already "never."
I filed a new bug, and the time to error was a little under 4 hours IIRC.
https://bugzilla.redhat.com/show_bug.cgi?id=501601
On Wed, May 20, 2009 at 04:31:56PM -0400, Paul W. Frields wrote:
On Tue, May 19, 2009 at 10:09:10PM -0700, Adam Williamson wrote:
On Wed, 2009-05-20 at 00:42 -0400, Robert P. J. Day wrote:
On Tue, 19 May 2009, Adam Williamson wrote:
On Tue, 2009-05-19 at 23:24 +0000, "Jóhann B. Guðmundsson" wrote:
On 05/19/2009 09:44 PM, Robert P. J. Day wrote:
for the display, mine's set for 30 minutes but it's *absolutely* not a function of that time value since, as others have mentioned, the screen can go black totally arbitrarily, like when i'm literally in the middle of typing something. can i assume that's pretty much what's happening to some of the others who have confirmed this?
Yup
30 minutes here same symptom
Can you guys set it to 'never' and see if the behaviour changes?
ok, that's just the "display" setting under System -> Preferences -> Power Management, right?
Yup.
Sorry to hit this thread late. My setting was already "never."
I filed a new bug, and the time to error was a little under 4 hours IIRC.
By the way, I apologize for the inadvertent thread pollution. My issue is clearly different from the original issue, although it might be related.
On 05/19/2009 09:35 PM, Adam Williamson wrote:
It's not the same bug, because I had that bug, and I don't have it now. :) But it could somehow be related to that. What timeout do you guys all have set in gnome-power-preferences for 'Put display to sleep when...'?
30 minutes ( think default )
-
"Jóhann B. Guðmundsson" -
Adam Williamson -
Axel -
Christopher Beland -
Chuck Anderson -
Harald Hoyer -
Michal Jaegermann -
Paul W. Frields -
Richard Körber -
Robert L Cochran -
Robert P. J. Day -
Rodd Clarkson -
Wolfgang S. Rupprecht