similar to: [Bug 18336] New: nv10 : doesn't detect connected dvi monitor

http://bugs.freedesktop.org/show_bug.cgi?id=14823 Summary: nv10 hardware cursor corruption with randr1.2 Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Signed-off-by: Xavier Chantry <chantry.xavier at gmail.com> --- src/nv10_exa.c | 35 +++++++++++++++++++---------------- 1 files changed, 19 insertions(+), 16 deletions(-) diff --git a/src/nv10_exa.c b/src/nv10_exa.c index 1acb583..23a68e3 100644 --- a/src/nv10_exa.c +++ b/src/nv10_exa.c @@ -34,30 +34,33 @@ static struct pict_format { int exa; int hw; } nv10_tex_format_pot[] = { - {

Commit 8c8f15c9d3 added increased pitch alignment requirements to handle nv10-nv40 tiling (which must have a small number * PoT pitch). While NV4/NV5 do have tiling, this was never supported in nouveau. This change enables 1920x1200 resolutions since the maximum surface pitch has to be strictly less than 8192. The current logic will align 1920*4 up to 8192 unnecessarily. Signed-off-by: Ilia

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Copied from the (disabled) overlay code in xf86-video-nouveau. I verified that my nv34 indeed doesn't scale down by more than 2, didn't test the factor of 8. drivers/gpu/drm/nouveau/dispnv04/overlay.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/dispnv04/overlay.c

So I did a lot more debugging on this. I wrote a program that draws a triangle to an fbo, and then blits that to fb 0. If I draw the triangle with glBegin(GL_TRIANGLES); glColor3f(1, 0, 0); glVertex3f(-0.6*128 + 128, -0.75*128 + 128, 0.5); glColor3f(0, 1, 0); glVertex3f(0.6*128 + 128, -0.75*128 + 128, 0); glColor3f(0, 0, 1); glVertex3f(128, 0.75*128 + 128, 0); glEnd(); Then all

On 16MB cards it's too easy to hit ENOMEM with 2D use when this perf hack is enabled. This should fix https://bugs.freedesktop.org/show_bug.cgi?id=42384 Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Francisco Jerez <currojerez at riseup.net> --- drivers/gpu/drm/nouveau/nouveau_bo.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git

The higher 0x800 was getting overwritten by the 0x7ff anyways, so it wasn't doing any good. The mesa driver just uses 0x800 for the low portion and doesn't set the 8 bit in the higher portion, so do the same thing here. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/nv10_exa.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/nv10_exa.c

Before this patch they were being reset to zero on every context switch instead of leaving the saved value, causing some context switching weirdness (the most serious symptom was the memory manager corrupting the BOs it migrated because of a malfunctioning M2MF). Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- drivers/gpu/drm/nouveau/nv10_graph.c | 3 ++- 1 files changed,

Hello, I'm trying to debug why fbo-copyteximage-simple is failing, and I'm... failing. It's an extremely simple test. I'm pretty sure that the copyteximage part of it has nothing to do with the failure, at least it behaves identically when I just return tex instead of copiex_tex. Without any modifications, the test just renders one big red square. I think there's something

NV10TCL defines the vertex buffer registers both as arrays and as individual named registers. This causes duplicate register definitions and the individual registers are not used either by the DDX or by the Mesa driver. Francisco Jerez said to remove them all. Signed-off-by: Luca Barbieri <luca at luca-barbieri.com> --- renouveau.xml | 49

I'm looking to implement some basic CLASS features, using my own dialplans as well as those so thoughtfully contributed by "The Traveller" a few weeks back. However, instead of building my own dialing sequences (*69, *67, etc. etc.) for these features, I went looking for the standard list of CLASS dialing codes. I found this

https://bugs.freedesktop.org/show_bug.cgi?id=73459 Priority: medium Bug ID: 73459 Assignee: nouveau at lists.freedesktop.org Summary: nv10 get_rt_format: Assertion `0' failed. Severity: normal Classification: Unclassified OS: Linux (All) Reporter: dnietoc at gmail.com Hardware: x86 (IA32)

Otherwise none of the format checks pass, since the width was still in 16.16 encoding. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- This must have been some sort of last-second cleanup I made and forgot to test, because with this code, there's no way it could ever have worked... drivers/gpu/drm/nouveau/dispnv04/overlay.c | 17 +++++++++-------- 1 file changed, 9

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- This has received light testing on NV18 and NV34 cards, using the modetest tool. Userspace support to use this for xv is not yet ready. I decided against creating a new "pvideo" engine -- that just seems way too heavy-handed compared to the ~10 lines of code in disp/nv04.c to deal with the PVIDEO interrupts. Even though

Signed-off-by: Marcin Ko?cielnicki <koriakin at 0x04.net> --- drivers/gpu/drm/nouveau/nv04_fbcon.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nv04_fbcon.c b/drivers/gpu/drm/nouveau/nv04_fbcon.c index 813b25c..7cf9287 100644 --- a/drivers/gpu/drm/nouveau/nv04_fbcon.c +++ b/drivers/gpu/drm/nouveau/nv04_fbcon.c @@ -236,7 +236,7 @@

https://bugs.freedesktop.org/show_bug.cgi?id=63481 Priority: medium Bug ID: 63481 Assignee: nouveau at lists.freedesktop.org Summary: Nouveau driver - No monitor signal on chipset NV1A (family NV10) since bisected bad commit ebb945a94bba2ce8dff7b0942ff2b3f2a52a0a69 in kernel 3.7.9 QA

http://bugs.freedesktop.org/show_bug.cgi?id=26797 Summary: GeForce 6150SE: DVI-connector not detected Product: xorg Version: 7.4 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

I'm seeing a lot of these errors from a Samba 4.13.0 DC running on Debian Buster, the smb.conf is untouched from that which was created via a classic upgrade. =============================== Oct 24 10:25:43 srvr01 samba[26688]: [2020/10/24 10:25:43.886363, 0] ../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler) Oct 24 10:25:43 srvr01 samba[26688]: /usr/local/samba/sbin/samba_dnsupdate:

* Kill the A8+A8 hack. Recent enough X servers (>=1.7) fall back to ARGB glyphs for drivers not supporting A8 render targets. * Kill all the global state. It doesn't matter a lot yet but it might if we get multicard working at some point. * Other random clean-ups with no functional changes. Some numbers from x11perf -aa10text -aa24text -comppixwin10 -comppixwin500: * Before, with A

Am Freitag, den 07.09.2018, 22:11 +0200 schrieb wolle321 at freenet.de: > Hello , > > I'm new here but I hope I can describe my problem exactly. > > I'm trying to get my DVI-Monitor to work with nouveau. The monitor > is > automatically reported as not connected. LVDS is detected. Forcing it > on Xorg.conf didn't work, KMS does: > >