From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 33668] New: [regression] [nv4c] Screen corruption
Date: Fri, 28 Jan 2011 11:54:47 -0800 (PST) [thread overview]
Message-ID: <bug-33668-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=33668
Summary: [regression] [nv4c] Screen corruption
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: tjwasiak-wo4oW1Pw1HF3vZ0LZ0W7Rg@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=42666)
--> (https://bugs.freedesktop.org/attachment.cgi?id=42666)
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.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-01-28 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 19:54 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-33668-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-01-28 19:55 ` [Bug 33668] [regression] [nv4c] Screen corruption bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-28 19:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-28 19:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-28 20:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 6:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 14:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 10:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-33668-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.