From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 112070] New: H/W Acceleration sufficiently buggy on Debian to hard lock machine GeForce 7600 GO
Date: Sat, 19 Oct 2019 17:35:40 +0000 [thread overview]
Message-ID: <bug-112070-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3105 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=112070
Bug ID: 112070
Summary: H/W Acceleration sufficiently buggy on Debian to hard
lock machine GeForce 7600 GO
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: other
Status: NEW
Severity: critical
Priority: not set
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: dooby.dave-J1btbF6uMEmsTnJN9+BGXg@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 145774
--> https://bugs.freedesktop.org/attachment.cgi?id=145774&action=edit
logs
So. I have big problems with nouveau driver or implementation of nouveau driver
(by Debian). I emailed debian-x-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org team but have heard nothing
back.
Straight out the box, some graphical features do not work / are buggy / might
hang the system - depending on which DE you use and what eye-candy it has
enabled by default. XFCE/LXQT appear unaffected yet KDE Plasma is producing
many graphical anomalies/artefacts and gdm did hang.
In every DE and version of Debian since Jessie, 360 degree videos (in browser)
just display noise. This behaviour changes when using the proprietary 304xx
nvidia driver, but the videos still do not function properly - though you do
now see the correct video patchwork the 360deg video is generated from.
In trying to exercise this problem, I discovered glxgears works fine, yet
glmark2 will always crash with a segmentation fault between tests 2 and 3. With
nvidia driver installed, glmark2 fails to start at all and gives this :-
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 24 (X_GLXCreateNewContext)
Value in failed request: 0x0
Serial number of failed request: 39
Current serial number in output stream: 40
Might be worth noting that after installation of the proprietary driver apt was
reporting:-
ldconfig: /usr/lib/x86_64-linux-gnu/libGL.so.1 is not a symbolic link
I had a brief fling with Piglit. It crashed however. And when trying to use
valgrind it looked like it was going to take over a day.
Attached are a Xorg.0.log (should module "nv" be being loaded?) and a dmesg
output - both from a Debian Stretch install. I have concurrent installs of
Buster and Wheezy I can fire up if it will help.
The issue might not exist (or is different) in Wheezy. The 360 degree videos
after a fresh install look like the other releases after the proprietary driver
has been installed, ie I can see the patchwork video rather than just noise.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4548 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2019-10-19 17:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 17:35 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-112070-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-10-19 17:42 ` [Bug 112070] H/W Acceleration sufficiently buggy on Debian to hard lock machine GeForce 7600 GO bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-19 17:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-19 17:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-19 17:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-19 18:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-19 18:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-19 19:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-19 19:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-20 13:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-20 16:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-21 10:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-21 10:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-21 12:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-21 13:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-21 18:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-21 18:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-21 19:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-21 19:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-22 15:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-22 15:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-22 16:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-22 19:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-22 19:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-26 14:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-26 14:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-26 14:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-26 17:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-26 18:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-27 12:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-27 12:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-27 13:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-28 10:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:54 ` 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-112070-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.