From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 62914] ZaphodHeads doesn't work after upgrading to xorg 1.14
Date: Wed, 08 May 2013 17:37:02 +0000 [thread overview]
Message-ID: <bug-62914-8800-RVQZp0b0bM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-62914-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 996 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=62914
--- Comment #9 from Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Can reproduce the issue but there is no "good" combination on my system, i.e.
any combination of
xf86-video-nouveau -> 1.0.6-1 1.0.7-1
xorg-server -> 1.13.2.901-1 1.14.0-2
produces "Failed to set drm interface version"
In terms of "how to bisect" the links provided are quite nice
Although I would suggest to confirm which package exactly caused the issue,
before jumping into blind bisection
1. Revert xorg-server to previous version (1.13.2.901-1)
2. Keep xf86-video-nouveau 1.0.7-1, but rebuild it on top of the old/good
xserver
and vice versa
Note: to avoid rebuilding the input drivers have SSH handy and observe Xorg.log
for the offending lines
Note: if unsure about the specific build options, patches and others take a
look at the distro packaging system
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1788 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2013-05-08 17:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 19:01 [Bug 62914] New: ZaphodHeads doesn't work after upgrading to xorg 1.14 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-62914-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-03-29 19:04 ` [Bug 62914] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-08 15:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-08 15:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-11 5:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-15 7:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-25 1:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-05 0:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-08 6:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-08 17:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-05-13 10:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-13 12:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-14 10:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-14 10:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-14 12:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 12:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 12:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 14:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 20:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 20:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-31 3:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-31 3:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-31 3:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-31 3:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-31 4:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-31 4:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-31 4:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-31 5:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-30 10:27 ` 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-62914-8800-RVQZp0b0bM@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.