From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 50403] NV28 double cursor & ugly graphics & crashes
Date: Wed, 01 Aug 2012 19:26:33 +0000 [thread overview]
Message-ID: <bug-50403-8800-VnrWNP4CR7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-50403-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=50403
--- Comment #31 from tesloid-/E1597aS9LQAvxtiuMwx3w@public.gmane.org 2012-08-01 19:26:33 UTC ---
I am previewing the next release of Slackware, on a similar D800, and am seeing
even worse corruption than your screenshots indicate.
The problem is, the current version of Xorg will no long work with the
proprietary nvidia driver (Nvidia has not updated their legacy driver);
The "nv" driver segfaults (I have not been able to figure out why: this is
using a configuration that used to be fine).
The nouveau driver is all that will load in 1920x1200 now, and the graphics are
too corrupted to be used.
I cannot find a way to get 1920x1200, even unaccelerated, with an nv28 card
now.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-08-01 19:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 19:25 [Bug 50403] New: NV28 double cursor & ugly graphics & crashes bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-50403-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-05-27 19:41 ` [Bug 50403] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-27 20:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-27 23:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 1:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 6:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 6:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 6:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 7:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 8:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 8:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 8:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 8:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 8:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 8:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 9:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 9:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 11:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-29 0:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-29 1:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-29 6:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-29 7:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-29 7:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-29 7:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-29 20:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-29 21:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-29 21:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-30 14:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-30 15:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-12 23:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-13 6:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 20:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-01 19:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2012-09-09 18:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09 19:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 4:24 ` 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-50403-8800-VnrWNP4CR7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox