Bug 33668 - [regression] [nv4c] Screen corruption
Summary: [regression] [nv4c] Screen corruption
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
Depends on:
Reported: 2011-01-28 11:54 UTC by Tomasz Wasiak
Modified: 2013-08-18 18:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

X server log with ShadowFB option set (44.39 KB, application/octet-stream)
2011-01-28 11:54 UTC, Tomasz Wasiak
no flags Details
X server log without ShadowFB option set (46.16 KB, application/octet-stream)
2011-01-28 11:55 UTC, Tomasz Wasiak
no flags Details
dmesg output (30.53 KB, application/octet-stream)
2011-01-28 11:56 UTC, Tomasz Wasiak
no flags Details
X server configuration file (1.12 KB, application/octet-stream)
2011-01-28 11:57 UTC, Tomasz Wasiak
no flags Details

Description Tomasz Wasiak 2011-01-28 11:54:46 UTC
Created attachment 42666 [details]
X server log with ShadowFB option set

You can not use X Window System unless you use ShadowFB option because of massive screen corruption. ShadowFB means no acceloration at all.

Hardware: nVidia GeForce 6100 nForce 430 - integrated graphics @ GigaByte GA-M61PM-S2 mainboard
Software: kernel 2.6.38-rc2-git7 with nouveau drm driver snapshot fetched from http://people.freedesktop.org/~pq/nouveau-drm (dated 20110128), libdrm, mesa (both dated 20110128) and whole X system fetched from GIT and compiled from sources locally.

I had been running drm driver, libdrm, mesa and xf86-video-nouveau driver fetched from GIT in late November 2009 (on top of stable xorg-server) before hard disk crash on that machine and it was working without bigger issues.
Comment 1 Tomasz Wasiak 2011-01-28 11:55:46 UTC
Created attachment 42667 [details]
X server log without ShadowFB option set
Comment 2 Tomasz Wasiak 2011-01-28 11:56:27 UTC
Created attachment 42668 [details]
dmesg output
Comment 3 Tomasz Wasiak 2011-01-28 11:57:13 UTC
Created attachment 42669 [details]
X server configuration file
Comment 4 Tomasz Wasiak 2011-01-28 12:00:17 UTC
Forgot to mention that it is hardware (nv4c) specific. Took hard disk with that system to another machine (GeForce 6800 PCI-E which is identified as nv43, Gigabyte GA-M57SLI-S4 mainboard) reconfigured BusID in xorg.conf at it was working without ShadowFB!!!
Comment 5 Tomasz Wasiak 2011-02-04 22:49:09 UTC
Did some additional tests yesterday. Using newest sources from git I found using NoAccel is sufficient to make it working... But having no acceleration is not what I was looking for.
Comment 6 Tomasz Wasiak 2011-02-06 06:33:28 UTC
Found partial solution to that issue:
1. Patch ddx not to use tiled scanout
2. Use mesa-7.9 branch instead of master branch of mesa

That way 2D acceleration is quite usable. 3D using nouveau Gallium3D driver is still bad (even worse than before).
Comment 7 Lucas Stach 2011-02-09 02:59:05 UTC
There is a chance this issue is fixed in git since Ben pushed a fix regarding this. Could you please retest with kernel built from latest git and tiled scanout enabled in ddx?

Comment 8 Ilia Mirkin 2013-08-18 18:09:39 UTC
It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report.

In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one.


The Nouveau Team

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.