Displaying 20 results from an estimated 3000 matches similar to: "[Bug 69029] New: GT218 (NVA8): GPU lockup since kernel 3.11 upgrade"
2019 Jul 27
0
Video Hardware Decoding: Jittery Rectangles on Nvidia GT218 NVA8 VP4.
On Sat, Jul 27, 2019 at 7:37 AM Ralph Corderoy <ralph at inputplus.co.uk> wrote:
> The video plays, CPU load is less (my aim), but there's ‘tearing’ of the
> picture as if small rectangles that are updates are appearing in the
> wrong location, off by a little. If I step through the frames with
> mpv's ‘.’ and ‘,’ then I've found a pattern: one frame's picture is
2019 Jul 29
1
Video Hardware Decoding: Jittery Rectangles on Nvidia GT218 NVA8 VP4.
Às 14:46 de 27/07/2019, Ilia Mirkin escreveu:
> On Sat, Jul 27, 2019 at 7:37 AM Ralph Corderoy <ralph at inputplus.co.uk> wrote:
>> The video plays, CPU load is less (my aim), but there's ‘tearing’ of the
>> picture as if small rectangles that are updates are appearing in the
>> wrong location, off by a little. If I step through the frames with
>> mpv's
2019 Jul 27
3
Video Hardware Decoding: Jittery Rectangles on Nvidia GT218 NVA8 VP4.
Hi,
I'm having trouble with hardware decoding of video with mpv(1) having
switched from Nvidia's proprietary driver to nouveau due to Arch Linux
removing its nvidia-340xx package.
The machine is an Acer Revo.
$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [ION] [10de:0a64] (rev a2)
I think this is codename NVA8 with the
2019 Aug 14
1
Video Hardware Decoding: Jittery Rectangles on Nvidia GT218 NVA8 VP4.
Hi Ilia,
A fortnight ago, you wrote:
> > The video plays, CPU load is less (my aim), but there's ‘tearing’ of
> > the picture as if small rectangles that are updates are appearing in
> > the wrong location, off by a little. If I step through the frames
> > with mpv's ‘.’ and ‘,’ then I've found a pattern: one frame's
> > picture is good, followed by
2012 Nov 06
3
Fix for vblank on nvc0
The vblank on nvc0 was not working correctly and would freeze X, I managed
to track it down and fix it with some help from m.b.lankhorst, see
https://bugs.freedesktop.org/show_bug.cgi?id=56692 for details.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20121106/27ceb48e/attachment.html>
--------------
2015 Jan 14
5
[Bug 88415] New: [NVA8] nouveau GPU lockup when reclocking
https://bugs.freedesktop.org/show_bug.cgi?id=88415
Bug ID: 88415
Summary: [NVA8] nouveau GPU lockup when reclocking
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee:
2010 Mar 09
72
[Bug 26980] New: GT230M/nouveau: X server hangs spontaneously
http://bugs.freedesktop.org/show_bug.cgi?id=26980
Summary: GT230M/nouveau: X server hangs spontaneously
Product: xorg
Version: 7.5
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau at lists.freedesktop.org
2014 Jan 16
2
[PATCH] drm/nv50/graph: add more trap names to print on error
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
---
I made the assumption that showing the address is generally useful. Worst
case, it won't make sense but still be displayed. Seems simpler than
special-casing things.
drivers/gpu/drm/nouveau/core/engine/graph/nv50.c | 117 ++++++++++++-----------
1 file changed, 63 insertions(+), 54 deletions(-)
diff --git
2017 Sep 30
0
Nouveau nullptr on NVIDIA NVA8
Starting with the drm merge af3c8d98508d37541d4bf57f13a984a7f73a328c for
4.13-rc1, the NVidia NVS3100M display on Dell Latitude E6410 had a
nullptr crash on startup. As a result later the suspend2ram was locking
up. Traced to a null ptr in nv50_mstm_service(), which seems to be
called only from
nouveau_connector_hotplug().
Fixed by checking if mstm is not NULL before calling the service
2008 Sep 08
7
[Bug 17484] New: lots of PGRAPH_ERROR/PROTECTION_ERROR
http://bugs.freedesktop.org/show_bug.cgi?id=17484
Summary: lots of PGRAPH_ERROR/PROTECTION_ERROR
Product: xorg
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau at lists.freedesktop.org
2008 Sep 10
2
UID&GID no same at two server...
Hello world!!!!
I realized that my samba_Server1 did not even UID & GID that the other
samba_Server1 ..
In summary: the share from the windows works very well. samba 1 and 2.
When i run wbinfo-u (samba 1 and 2.) i'have :
GUEST
ADMINITRATOR
..
but not
[DOMAIN] GUEST
[DOMAIN] ADMINITRATOR
..
(strange...)
When I run on samba_Server1: getent passwd
guest: *: 604:608:
2015 Feb 21
6
[Bug 89273] New: [NVA8] nouveau screen corruption and X lockup when reclocking
https://bugs.freedesktop.org/show_bug.cgi?id=89273
Bug ID: 89273
Summary: [NVA8] nouveau screen corruption and X lockup when
reclocking
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
2012 Feb 24
43
[Bug 46557] New: nouveau: nv40 display corruption in framebuffer and X lockups unless nouveau.noaccel=1
https://bugs.freedesktop.org/show_bug.cgi?id=46557
Bug #: 46557
Summary: nouveau: nv40 display corruption in framebuffer and X
lockups unless nouveau.noaccel=1
Classification: Unclassified
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity:
[Bug 105174] New: [regression] BUG unable to handle kernel NULL pointer dereference in kernel 4.15.3
2018 Feb 20
25
[Bug 105174] New: [regression] BUG unable to handle kernel NULL pointer dereference in kernel 4.15.3
https://bugs.freedesktop.org/show_bug.cgi?id=105174
Bug ID: 105174
Summary: [regression] BUG unable to handle kernel NULL pointer
dereference in kernel 4.15.3
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
Severity: normal
Priority: medium
2012 Jun 29
35
[Bug 51579] New: Xv video support is black on NVidia NVa8 Chipset in latest git
https://bugs.freedesktop.org/show_bug.cgi?id=51579
Bug #: 51579
Summary: Xv video support is black on NVidia NVa8 Chipset in
latest git
Classification: Unclassified
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: All
Status: NEW
Severity: critical
Priority:
2013 Aug 30
0
[Bug 46597] [NVA8/NV50 gallium] nv50_pc.h:351: nv_alloc_instruction: Assertion `pc->num_instructions < 2048' failed.
https://bugs.freedesktop.org/show_bug.cgi?id=46597
Ilia Mirkin <imirkin at alum.mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|nv50_pc.h:351: |[NVA8/NV50 gallium]
|nv_alloc_instruction: |nv50_pc.h:351:
|Assertion
2011 Jul 09
1
[Bug 39101] New: [NVA8] VirtualBox segfault when accelerating 3D
https://bugs.freedesktop.org/show_bug.cgi?id=39101
Summary: [NVA8] VirtualBox segfault when accelerating 3D
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
AssignedTo: nouveau at
2016 Jun 06
4
[Bug 96411] New: [NVA8] reclocking not working. screen glitches.
https://bugs.freedesktop.org/show_bug.cgi?id=96411
Bug ID: 96411
Summary: [NVA8] reclocking not working. screen glitches.
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
2014 Jan 17
19
[Bug 73744] New: Constant lock ups with NVIDIA GeForce 8400 GS
https://bugs.freedesktop.org/show_bug.cgi?id=73744
Priority: medium
Bug ID: 73744
Assignee: nouveau at lists.freedesktop.org
Summary: Constant lock ups with NVIDIA GeForce 8400 GS
QA Contact: xorg-team at lists.x.org
Severity: blocker
Classification: Unclassified
OS: Linux (All)
Reporter: grave_123 at
2013 Oct 01
0
[Bug 46597] [NVA8/NV50 gallium] nv50_pc.h:351: nv_alloc_instruction: Assertion `pc->num_instructions < 2048' failed.
https://bugs.freedesktop.org/show_bug.cgi?id=46597
Ilia Mirkin <imirkin at alum.mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Ilia Mirkin <imirkin at