similar to: [Bug 99499] [REGRESSION, bisected] KMS hard-freezes around fbcon initialization on NV1A

https://bugs.freedesktop.org/show_bug.cgi?id=99499 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #4 from Martin Peres

https://bugs.freedesktop.org/show_bug.cgi?id=50375 Bug #: 50375 Summary: NV11: KMS/fbcon accel failing after scrolling/tty switch Classification: Unclassified Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority:

https://bugs.freedesktop.org/show_bug.cgi?id=96656 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mesa-dev at lists.freedesktop. |nouveau at lists.freedesktop.o |org |rg QA

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

https://bugs.freedesktop.org/show_bug.cgi?id=34348 Summary: (regression/bisected) (2.6.37 nouveau/KMS) internal laptop display remains blank Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=63135 Priority: medium Bug ID: 63135 Assignee: nouveau at lists.freedesktop.org Summary: [bisected] G69/nv50 DisplayPort dual-head fails to switch to KMS QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)

Based on the xf86-video-nv code, NFORCE (NV1A) and NFORCE2 (NV1F) have a different way of retrieving clocks. See the nv_hw.c:nForceUpdateArbitrationSettings function in the original code for how these clocks were accessed. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=54587 Cc: stable at vger.kernel.org Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- According to several

http://bugs.freedesktop.org/show_bug.cgi?id=26555 Summary: nouveau fails to fully resume nforce1 (nv1a) after S3 Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=96656 --- Comment #2 from Ilia Mirkin <imirkin at alum.mit.edu> --- The problem was pre-existing, but a combination of factors made the readpixels cache expose it harder. Fixed by: commit b433cb51e50cab878cbaa023662bacd1f923a183 Author: Ilia Mirkin <imirkin at alum.mit.edu> Date: Thu Jun 23 22:33:59 2016 -0400 nvc0: when mapping

This is what was done prior to the big refactor in kernel 3.8, and what was done by xf86-video-nv. Experimentally, it seems like there's some sort of issue with the high-res lut to be used there. Tested on G92. This ends up mattering because fbcon/fbdev chooses the C8 fb format for low-vram systems, which can occur with some IGP-based configurations with little "stolen" vram.

Commit f4ebcd133b9 ("dri/nouveau: NV17_3D class is not available for NV1a chipset") fixed this partially by using the correct 3d class. However there were a lot of checks left over comparing against the chipset. Reported-and-tested-by: John F. Godfrey <jfgodfrey at gmail.com> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- I guess I didn't have to change the

https://bugs.freedesktop.org/show_bug.cgi?id=98690 Jani Nikula <jani.nikula at intel.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact| |xorg-team at lists.x.org Product|DRI |xorg Component|DRM/other

https://bugs.freedesktop.org/show_bug.cgi?id=96656 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are

Hiya, I sent the enclosed email to linux-kernel before realizing that it would, perhaps, be more proper to send it here, which I hereby do. I shall be happy to try out any and all patches. Best regards, Sune M?lgaard -------- Original Message -------- Subject: [bisected] nouveau failure with 3.9-rc1 and ongoing Date: Tue, 12 Mar 2013 19:57:55 +0100 From: Sune M?lgaard <sune at

commit 8613e7314ac254fdd67ed46192f021d76141e4c9 Author: Ben Skeggs <bskeggs at redhat.com> Date: Mon Oct 21 08:50:25 2013 +1000 drm/nouveau/fb: remove ram oclass argument from base fb constructor Introduced a unfortunate regression by using nv10 ram oclass for nv1a hardware, causing corruption and eventually system lockup. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=74866

This reverts commit 98c9e4edb58374f18249e5c9c53b392fb8b4a1d1. AFAIK it's no longer needed. Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- src/drmmode_display.c | 3 --- src/nv_driver.c | 2 -- src/nv_type.h | 1 - 3 files changed, 0 insertions(+), 6 deletions(-) diff --git a/src/drmmode_display.c b/src/drmmode_display.c index 7c45d9c..a91741d

While most of the functionality on Nvidia GPUs doesn't require using an explicit handle instead of the main VRAM handle + offset, there are a couple of places that do require explicit handles, such as CRC functionality. Since this means we're about to add another nouveau-chosen handle, let's just go ahead and move any hard-coded handles into a single header. This is just to keep things

While most of the functionality on Nvidia GPUs doesn't require using an explicit handle instead of the main VRAM handle + offset, there are a couple of places that do require explicit handles, such as CRC functionality. Since this means we're about to add another nouveau-chosen handle, let's just go ahead and move any hard-coded handles into a single header. This is just to keep things

While most of the functionality on Nvidia GPUs doesn't require using an explicit handle instead of the main VRAM handle + offset, there are a couple of places that do require explicit handles, such as CRC functionality. Since this means we're about to add another nouveau-chosen handle, let's just go ahead and move any hard-coded handles into a single header. This is just to keep things

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drm/nouveau/nv50_display.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drm/nouveau/nv50_display.c b/drm/nouveau/nv50_display.c index bdaba91..d9cba87 100644 --- a/drm/nouveau/nv50_display.c +++ b/drm/nouveau/nv50_display.c @@ -773,7 +773,6 @@ nv50_crtc_set_scale(struct nouveau_crtc *nv_crtc, bool update) */ if