Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 02-25-09, 03:40 PM   #37
Nait
Registered User
 
Join Date: Feb 2009
Posts: 4
Default Re: 180.08 & red checkerboard

I can confirm that flashes are connected to amarok on my Ubuntu8.10 64 with 180.29 drivers. I'll check 180.35 next week. I didn't seen flashes when I was using totem-xine so I think that it's not xine. I think animated icon is also NOT connected, because even volume manager icon changes when I change volume...but maybe it's not the same. However it may be QT3 related.
Nait is offline   Reply With Quote
Old 02-25-09, 03:45 PM   #38
FRLinux
Big Freakin Guinness
 
Join Date: Dec 2008
Location: Dublin
Posts: 13
Default Re: 180.08 & red checkerboard

Quote:
Originally Posted by Nait View Post
I can confirm that flashes are connected to amarok on my Ubuntu8.10 64 with 180.29 drivers. I'll check 180.35 next week.
Connected as in, if you close amarok then all is fine ?!
FRLinux is offline   Reply With Quote
Old 02-25-09, 04:11 PM   #39
Nait
Registered User
 
Join Date: Feb 2009
Posts: 4
Default Re: 180.08 & red checkerboard

Yes, when I turned off amarok everything was back to normal. However I'm confused a bit now, because it flashed only once now when I was opening amarok again, so maybe I have written about connection to early, or cache have something to do with that...K3b have no caused any flickering so it's rather not a general qt problem.

EDIT: I have reopened it once again-it was flickering as long as it was in tray only..once I clicked on icon(which opened amarok window) flickering disappeared..I'm even more confused now because on first run it was flickering even if amarok was running in window mode.
Nait is offline   Reply With Quote
Old 02-26-09, 07:32 AM   #40
smury353
Registered User
 
Join Date: Feb 2009
Location: Sligo/Brussels
Posts: 6
Default Re: 180.08 & red checkerboard

it's a bit inconsistent if one opens and closes amarok/kaffeine a few times but on a clean boot, there are flashes only when amarok has been started.
i've updated to 180.29 and i also checked if it was only with the packman version of amarok - it isn't.
it is worth checking if the problem is there when amarok is using a different plugin (eg yauap/gstreamer). maybe the problem is with the amarok-xine package
smury353 is offline   Reply With Quote
Old 03-08-09, 05:09 AM   #41
Malvineous
Registered User
 
Join Date: Sep 2006
Posts: 17
Default Re: 180.08 & red checkerboard

I've had this same problem for a while as well, using Compiz Fusion. First there were flashes of black frames and black checkerboard patterns, then with the 180 series it changed to red frames and red checkerboard pattern.

I'm only running mplayer, no amarok, etc. and the only solution I've found is to quit and rerun mplayer until the flashes drop to a frequency where the video is somewhat watchable. Seems to be something to do with redirecting the video overlay to an OpenGL texture.

Running an 8600GT.

Malvineous is offline   Reply With Quote
Old 03-23-09, 07:37 PM   #42
roalter
Registered User
 
Join Date: Mar 2008
Posts: 21
Default Re: 180.08 & red checkerboard

Just wanted to report back that the same checkerboard pattern problem still occurs with 180.41 driver... with mplayer and vo XV, on a GeForce 8600 GTS (G84), only on the 2nd output (HDMI). My xorg.0.log, grepped for NV:

(--) PCI:*(5:6:0) nVidia Corporation NV44A [GeForce 6200] rev 161, Mem @ 0xd4000000/24, 0xc0000000/28, 0xd5000000/24
(II) Module glx: vendor="NVIDIA Corporation"
(II) NVIDIA GLX Module 180.41 Thu Mar 19 12:58:26 PST 2009
(II) Module nvidia: vendor="NVIDIA Corporation"
(II) NVIDIA dlloader X Driver 180.41 Thu Mar 19 12:32:54 PST 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(--) Chipset NVIDIA GPU found
(--) Chipset NVIDIA GPU found
(--) Chipset NVIDIA GPU found
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NoLogo" "true"
(**) NVIDIA(0): Option "TwinView" "0"
(**) NVIDIA(0): Option "MetaModes" "nvidia-auto-select +0+0"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce 8600 GTS (G84) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 262144 kBytes
(--) NVIDIA(0): VideoBIOS: 60.84.5e.00.00
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 8600 GTS at PCI:1:0:0:
(--) NVIDIA(0): LG W2242 (DFP-0)
(--) NVIDIA(0): Philips L06HD v1 16:9 (DFP-1)
(--) NVIDIA(0): LG W2242 (DFP-0): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): LG W2242 (DFP-0): Internal Dual Link TMDS
(--) NVIDIA(0): Philips L06HD v1 16:9 (DFP-1): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): Philips L06HD v1 16:9 (DFP-1): Internal Dual Link TMDS
(II) NVIDIA(0): Assigned Display Device: DFP-0
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select+0+0"
(II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
(--) NVIDIA(0): DPI set to (87, 83); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(1): RGB weight 888
(==) NVIDIA(1): Default visual is TrueColor
(==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(1): Option "NoLogo" "true"
(**) NVIDIA(1): Option "TwinView" "0"
(**) NVIDIA(1): Option "MetaModes" "DFP-0: nvidia-auto-select +0+0"
(**) NVIDIA(1): Enabling RENDER acceleration
(II) NVIDIA(1): NVIDIA GPU GeForce 6200 (NV44) at PCI:5:6:0 (GPU-1)
(--) NVIDIA(1): Memory: 524288 kBytes
(--) NVIDIA(1): VideoBIOS: 05.44.a2.10.01
(--) NVIDIA(1): Interlaced video modes are supported on this GPU
(--) NVIDIA(1): Connected display device(s) on GeForce 6200 at PCI:5:6:0:
(--) NVIDIA(1): LG W2242 (DFP-0)
(--) NVIDIA(1): LG W2242 (DFP-0): 155.0 MHz maximum pixel clock
(--) NVIDIA(1): LG W2242 (DFP-0): Internal Single Link TMDS
(II) NVIDIA(1): Display Device found referenced in MetaMode: DFP-0
(II) NVIDIA(1): Assigned Display Device: DFP-0
(II) NVIDIA(1): Validated modes:
(II) NVIDIA(1): "DFP-0:nvidia-auto-select+0+0"
(II) NVIDIA(1): Virtual screen size determined to be 1680 x 1050
(--) NVIDIA(1): DPI set to (87, 83); computed from "UseEdidDpi" X config
(--) NVIDIA(1): option
(==) NVIDIA(1): Enabling 32-bit ARGB GLX visuals.
(**) NVIDIA(2): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(2): RGB weight 888
(==) NVIDIA(2): Default visual is TrueColor
(==) NVIDIA(2): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(2): Option "NoLogo" "true"
(**) NVIDIA(2): Option "TwinView" "0"
(**) NVIDIA(2): Option "MetaModes" "DFP-1: nvidia-auto-select +0+0"
(**) NVIDIA(2): Enabling RENDER acceleration
(II) NVIDIA(2): NVIDIA GPU GeForce 8600 GTS (G84) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(2): Memory: 262144 kBytes
(--) NVIDIA(2): VideoBIOS: 60.84.5e.00.00
(II) NVIDIA(2): Detected PCI Express Link width: 16X
(--) NVIDIA(2): Interlaced video modes are supported on this GPU
(--) NVIDIA(2): Connected display device(s) on GeForce 8600 GTS at PCI:1:0:0:
(--) NVIDIA(2): LG W2242 (DFP-0)
(--) NVIDIA(2): Philips L06HD v1 16:9 (DFP-1)
(--) NVIDIA(2): LG W2242 (DFP-0): 330.0 MHz maximum pixel clock
(--) NVIDIA(2): LG W2242 (DFP-0): Internal Dual Link TMDS
(--) NVIDIA(2): Philips L06HD v1 16:9 (DFP-1): 330.0 MHz maximum pixel clock
(--) NVIDIA(2): Philips L06HD v1 16:9 (DFP-1): Internal Dual Link TMDS
(II) NVIDIA(2): Display Device found referenced in MetaMode: DFP-1
(II) NVIDIA(2): Assigned Display Device: DFP-1
(II) NVIDIA(2): Validated modes:
(II) NVIDIA(2): "DFP-1:nvidia-auto-select+0+0"
(II) NVIDIA(2): Virtual screen size determined to be 1920 x 1080
(--) NVIDIA(2): DPI set to (73, 74); computed from "UseEdidDpi" X config
(--) NVIDIA(2): option
(==) NVIDIA(2): Enabling 32-bit ARGB GLX visuals.
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Setting mode "nvidia-auto-select+0+0"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(II) Loading extension NV-CONTROL
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): Setting mode "DFP-0:nvidia-auto-select+0+0"
(II) NVIDIA(1): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(1): Disabling shared memory pixmaps
(II) NVIDIA(1): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(1): Backing store disabled
(==) NVIDIA(1): Silken mouse enabled
(II) NVIDIA(2): Initialized GPU GART.
(II) NVIDIA(2): Setting mode "DFP-1:nvidia-auto-select+0+0"
(II) NVIDIA(2): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(2): Disabling shared memory pixmaps
(II) NVIDIA(2): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(2): Backing store disabled
(==) NVIDIA(2): Silken mouse enabled
(WW) NVIDIA(1): The GPU driving screen 1 is incompatible with the rest of the
(WW) NVIDIA(1): GPUs composing the desktop. OpenGL rendering will be
(WW) NVIDIA(1): disabled on screen 1.
(II) NVIDIA(0): Setting mode "nvidia-auto-select+0+0"
roalter is offline   Reply With Quote
Old 03-23-09, 07:44 PM   #43
FRLinux
Big Freakin Guinness
 
Join Date: Dec 2008
Location: Dublin
Posts: 13
Default Re: 180.08 & red checkerboard

Quote:
Originally Posted by roalter View Post
Just wanted to report back that the same checkerboard pattern problem still occurs with 180.41 driver... with mplayer and vo XV, on a GeForce 8600 GTS (G84), only on the 2nd output (HDMI). My xorg.0.log, grepped for NV:
I used to have the same issue on my gentoo system until i upgraded my Xorg (was running 1.3 and bumped onto version 1.5). Since then, no more issue mon my card (GTX280)

Steph
FRLinux is offline   Reply With Quote
Old 03-24-09, 02:19 PM   #44
roalter
Registered User
 
Join Date: Mar 2008
Posts: 21
Default Re: 180.08 & red checkerboard

Quote:
Originally Posted by FRLinux View Post
I used to have the same issue on my gentoo system until i upgraded my Xorg (was running 1.3 and bumped onto version 1.5). Since then, no more issue mon my card (GTX280)

Steph
Yeah, I reckon this is the way to go... would probably also solve my graphic tablet problems, which seem also be related to my x version (is 1.4.0.90)
roalter is offline   Reply With Quote

Old 03-31-09, 09:50 AM   #45
3.14159
Registered User
 
Join Date: Sep 2007
Posts: 3
Default Re: 180.08 & red checkerboard

Still exists in 180.44 with mplayer. It seems to be worse if there's a blinking icon on the task bar while playing full screen. Hiding the KDE bar makes it somewhat better, but it's still there sometimes.
3.14159 is offline   Reply With Quote
Old 05-23-09, 08:05 PM   #46
Malvineous
Registered User
 
Join Date: Sep 2006
Posts: 17
Default Re: 180.08 & red checkerboard

Yup, finally figured out how to upgrade to 180.51 without X11 crashing (leftover libraries from the old version) but the red full-frame flash and red checkerboard flash are still there :-(

I'm running dual monitors and it seems to flash more often when there's activity on the second monitor. Maybe it's related to the sync-to-vblank issue whereby one screen is incorrectly syncing to the vertical refresh of the other screen? (which results in tearing as if sync to vblank is switched off.)
Malvineous is offline   Reply With Quote
Old 05-24-09, 07:42 AM   #47
FRLinux
Big Freakin Guinness
 
Join Date: Dec 2008
Location: Dublin
Posts: 13
Default Re: 180.08 & red checkerboard

Quote:
Originally Posted by Malvineous View Post
Yup, finally figured out how to upgrade to 180.51 without X11 crashing (leftover libraries from the old version) but the red full-frame flash and red checkerboard flash are still there :-(

I'm running dual monitors and it seems to flash more often when there's activity on the second monitor. Maybe it's related to the sync-to-vblank issue whereby one screen is incorrectly syncing to the vertical refresh of the other screen? (which results in tearing as if sync to vblank is switched off.)
I noticed that when KDE animations happen on the desktop, i get this problem, otherwise it is just gone.
FRLinux is offline   Reply With Quote
Old 05-27-09, 08:25 AM   #48
Malvineous
Registered User
 
Join Date: Sep 2006
Posts: 17
Default Re: 180.08 & red checkerboard

Yeah I think it must be related to that. Although I don't run KDE or any sort of desktop (so no animations on the primary screen) there are little animated widgets like GKrellM sitting on the second screen. But since they're both being powered by the same video card, it must be some sort of conflict/race condition in the drivers.
Malvineous is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
Saw Red: Frozen Synapse Expands, Gains Co-op News Archived News Items 0 05-30-12 05:26 AM
red hat 7.3 driver problems please help war18 NVIDIA Linux 7 09-16-02 01:25 PM
red hat distros gadido NVIDIA Linux 3 09-02-02 06:17 PM
Nvidia 1.0-2960 and Red Hat 7.3 Kernal 2.4.18-5 Cheetah NVIDIA Linux 30 08-23-02 11:50 AM
Source RPMS for GCC3.2 - Red Hat 8.0? chrisw01 NVIDIA Linux 4 08-21-02 09:17 AM

All times are GMT -5. The time now is 04:51 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.