search for: gt218

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

...ort a modesetting DDX bug that manifests only on an NVidia GPU? Directly against the server https://gitlab.freedesktop.org/xorg/xserver? Here are some particulars: How can I tell whether this should be reported to kernel tracker or to freedesktop tracker as driver or server problem? HDMI output on GT218 10de:0a65 GPU is limited to 1920x1200. When connected to 2560x1440 display, vttys are supported at display's supported 1920x1080 mode, but X with modesetting DDX puts display in unsupported mode (functionally asleep) regardless of various attempts to force 1920x1080 at 60 or 1600x900 at 60, whi...

À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

Hello all, I am trying to debug an elusive memory corruption bug on my arm64 machine which appears to be in the nouveau driver. I got the following splat from the refcount debugging code: """ refcount_t: underflow; use-after-free. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 3366 at lib/refcount.c:128 refcount_sub_and_test+0xe8/0x108 Modules linked in: fuse nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=69029 Priority: medium Bug ID: 69029 Assignee: nouveau at lists.freedesktop.org Summary: GT218 (NVA8): GPU lockup since kernel 3.11 upgrade QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fred at crozat.net Hardware: x86-64 (AMD64) Status: NEW Version:...

...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 video-accleration engine VP4.0. I've these packages installed, following https://wiki.archlinux.org/index.php/Nouveau and https://wiki.archlinux.org/index.php/Hardware_video_acceleration $ pacman -Q | egrep 'nvidia|nou...

Hello, I'm facing issues with a Point of View GT210/218 and nouveau drivers. I'm using ubuntu server with LXDE on top of it... *lshw -c video* output: *-display description: VGA compatible controller product: GT218 [GeForce 210] vendor: NVIDIA Corporation physical id: 0 bus info: pci at 0000:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:82...

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

.../xorg/xserver? I don't know if anyone (from nouveau) looks at gitlab, so mailing list is probably best anyways. > > Here are some particulars: > How can I tell whether this should be reported to kernel tracker or to freedesktop > tracker as driver or server problem? HDMI output on GT218 10de:0a65 GPU is limited > to 1920x1200. When connected to 2560x1440 display, vttys are supported at > display's supported 1920x1080 mode, but X with modesetting DDX puts display in > unsupported mode (functionally asleep) regardless of various attempts to force > 1920x1080 at 60 or...

Hello my hardware has: 03:00.0 VGA compatible controller: NVIDIA Corporation GT218 [ION] (rev a2) rpm -qa | grep nvidia nvidia-detect-410.78-1.el7.elrepo.x86_64 kmod-nvidia-340xx-340.107-2.el7_6.elrepo.x86_64 nvidia-x11-drv-340xx-340.107-1.el7.elrepo.x86_64 rpm -qa | grep libva libva-vdpau-driver-0.7.4-19.el7.x86_64 libva-utils-1.8.3-4.el7.x86_64 libva-devel-1.8.3-1.el7.x86_64...

...working with the 3.10 from Centos - but video was freezing. SO I thought I would try the elrepo kernel. I installed that and X does not come up? How do I re-make the nvidia module for 4.14.5 kernel? I want to make sure the kmod kernel did it. I 'm thinking it did not. lspci | grep VGA says GT218 Or what do I look at now to see why X is not coming up? Thanks, Jerry uname -r 4.14.5-1.el7.elrepo.x86_64 grep EE /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 136.998] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 136....

Hello, We recently tracked down a bug on Tesla GPUs (i.e. G80-GT218) whereby it appears that instructions like 00000028: b5000409 08000780 add rn f32 $r2 $r2 neg c0[$a1] 00000040: b500060d 08004780 add rn f32 $r3 $r3 neg c0[$a1+0x4] or with nvdisasm: .headerflags @"EF_CUDA_SM12 EF_CUDA_PTX_SM(EF_CUDA_SM12)" /*0000*/ F...

...te: >> >>> Hello looks like the device is not supported, the logs are as >>> follows: >>> >>> --- >>> # dmesg | grep nouve >>> [ 2.789899] fb: switching to nouveaufb from VESA VGA >>> [ 2.790060] nouveau 0000:01:00.0: NVIDIA GT218 (0a8d00b1) >>> [ 2.815596] nouveau 0000:01:00.0: bios: version 70.18.7f.00.14 >>> [ 2.816421] nouveau 0000:01:00.0: bios: OOB 1 01452301 01452301 >>> [ 2.816427] nouveau 0000:01:00.0: bios: OOB 1 22234d20 22234d20 >>> [ 2.816431] nouveau 0000:01:00.0:...

https://bugs.freedesktop.org/show_bug.cgi?id=105626 Bug ID: 105626 Summary: BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium

On Fri, Jul 15, 2016 at 12:41:49PM -0400, Ilia Mirkin wrote: > On Fri, Jul 15, 2016 at 12:36 PM, Peter Wu <peter at lekensteyn.nl> wrote: > > On Fri, Jul 15, 2016 at 12:10:23PM -0400, Ilia Mirkin wrote: > >> On Fri, Jul 15, 2016 at 9:12 AM, Peter Wu <peter at lekensteyn.nl> wrote: > >> > Hi, > >> > > >> > Here are two patches to fix

...ll. Signed-off-by: Ard Biesheuvel <ard.biesheuvel at linaro.org> --- I am sure there is a much better way to address this, but this fixes the problem I get on AMD Seattle with a GeForce 210 PCIe card: nouveau 0000:02:00.0: enabling device (0000 -> 0003) nouveau 0000:02:00.0: NVIDIA GT218 (0a8280b1) nouveau 0000:02:00.0: bios: version 70.18.a6.00.00 nouveau 0000:02:00.0: fb ctor failed, -14 nouveau: probe of 0000:02:00.0 failed with error -14 v2: replace incorrect comparison of dma_addr_t type var against NULL v3: rework code to get rid of DMA_ERROR_CODE references, which...

...face v0.103 [ 3.787805] ACPI: bus type drm_connector registered <--- boot stops here. It should continue with this: [ 3.795491] Console: switching to colour dummy device 80x25 [ 3.801933] nouveau 0000:03:00.0: vgaarb: deactivate vga console [ 3.808303] nouveau 0000:03:00.0: NVIDIA GT218 (0a8c00b1) [ 3.931002] nouveau 0000:03:00.0: bios: version 70.18.83.00.08 [ 3.941731] nouveau 0000:03:00.0: fb: 512 MiB DDR3 [ 4.110348] tsc: Refined TSC clocksource calibration: 3591.349 MHz [ 4.116627] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x33c466a1ab5, max_idle_ns:...

...ns, which is currently leading us to return bogus ior -> head assignments through nvif, which causes WARN_ON(). So - fix this by verifying that we actually know that there's a head assigned to an ior before allowing it to be inherited through nvif. This -should- hopefully fix the WARN_ON on GT218 reported by Borislav. Signed-off-by: Lyude Paul <lyude at redhat.com> Cc: Borislav Petkov <bp at alien8.de> --- drivers/gpu/drm/nouveau/nvkm/engine/disp/uoutp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/disp/uoutp.c b/drive...

...of the issues you're seeing. On Sep 18, 2017 11:23 PM, <ygrishin-lists at mail2.ca> wrote: Hello looks like the device is not supported, the logs are as follows: --- # dmesg | grep nouve [ 2.789899] fb: switching to nouveaufb from VESA VGA [ 2.790060] nouveau 0000:01:00.0: NVIDIA GT218 (0a8d00b1) [ 2.815596] nouveau 0000:01:00.0: bios: version 70.18.7f.00.14 [ 2.816421] nouveau 0000:01:00.0: bios: OOB 1 01452301 01452301 [ 2.816427] nouveau 0000:01:00.0: bios: OOB 1 22234d20 22234d20 [ 2.816431] nouveau 0000:01:00.0: bios: OOB 1 22234d20 22234d20 [ 2.816434] nouvea...

OK I got access to the hardware, it's Toshiba Satellite L730. One of the obvious problems is that there's no video in VLC nor in Dragon Player. Is this expected? Some output: --- yuriy at yuriy-Satellite-L730:~$ dmesg | grep NVID [ 2.752675] nouveau 0000:01:00.0: NVIDIA GT218 (0a8d00b1) ... root at yuriy-Satellite-L730:/home/yuriy# dpkg -l | grep nouv ii libdrm-nouveau2:amd64 2.4.76-1 amd64 Userspace interface to nouveau-specific kernel DRM services -- runtime ii xserver-xorg-video-n...