similar to: GP10x failures on 4.12rc1

On Thu, Apr 30, 2020 at 12:15:28AM -0400, Ilia Mirkin wrote: > Hi Alexey, > > On Fri, Apr 24, 2020 at 10:52 PM Alexey Dobriyan <adobriyan at gmail.com> wrote: > > > > gp104 refuses to switch to "graphic" mode and show anything past > > this line: > > > > fb0: switching to nouveaufb from EFI VGA > > > > Machine is fine, as

gp104 refuses to switch to "graphic" mode and show anything past this line: fb0: switching to nouveaufb from EFI VGA Machine is fine, as it I can press Ctrl+Alt+Delete and reboot it normally. 5.5 is OK. 5.6 is broken. Bisecting is kinda painful with miscompilation and init/main.c breakage. BTW do I need all those megabytes of firmware? [ 0.923273] fb0: switching to nouveaufb

Nouveau driver shows unknown chipset (136000a1) for GTX 1060, so it only gives VGA resolution on screen. Use the same chipset as nv134 then it shows FullHD. This commit copies fields from nv134_chipset to nv136_chipset for GTX 1060. Signed-off-by: Chris Chiu <chiu at endlessm.com> --- drivers/gpu/drm/nouveau/nvkm/engine/device/base.c | 29 +++++++++++++++++++++++ 1 file changed, 29

Hello Alexandre Courbot, The patch 5429f82f3415: "drm/nouveau/secboot: add gp102/gp104/gp106/gp107 support" from Jan 26, 2017, leads to the following static checker warning: drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gp102.c:63 gp102_run_secure_scrub() warn: passing zero to 'PTR_ERR' drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gp102.c 46 static int 47

https://bugs.freedesktop.org/show_bug.cgi?id=107003 Bug ID: 107003 Summary: Timeout in nvkm_falcon_v1_clear_interrupt on gp104 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

--- man/nouveau.man | 9 ++++++++- src/nv_driver.c | 8 ++++++-- 2 files changed, 14 insertions(+), 3 deletions(-) diff --git a/man/nouveau.man b/man/nouveau.man index 07d53c8..4878f24 100644 --- a/man/nouveau.man +++ b/man/nouveau.man @@ -63,7 +63,14 @@ GF100, GF104, GF106, GF108, GF110, GF114, GF116, GF117, GF119 GK104, GK106, GK107, GK110, GK208 .TP 22 .B GeForce GTX 750 -GM107 +GM107,

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit a0b694d0af21c9993d1a39a75fd814bd48bf7eb4 ] HW has error checks in place which check that pixel depth is explicitly provided on DP, while HDMI has a "default" setting that we use. In multi-display configurations with identical modelines, but different protocols (HDMI + DP, in this case), it was possible for the DP head to

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit a0b694d0af21c9993d1a39a75fd814bd48bf7eb4 ] HW has error checks in place which check that pixel depth is explicitly provided on DP, while HDMI has a "default" setting that we use. In multi-display configurations with identical modelines, but different protocols (HDMI + DP, in this case), it was possible for the DP head to

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit a0b694d0af21c9993d1a39a75fd814bd48bf7eb4 ] HW has error checks in place which check that pixel depth is explicitly provided on DP, while HDMI has a "default" setting that we use. In multi-display configurations with identical modelines, but different protocols (HDMI + DP, in this case), it was possible for the DP head to

Hi Alexey, On Fri, Apr 24, 2020 at 10:52 PM Alexey Dobriyan <adobriyan at gmail.com> wrote: > > gp104 refuses to switch to "graphic" mode and show anything past > this line: > > fb0: switching to nouveaufb from EFI VGA > > Machine is fine, as it I can press Ctrl+Alt+Delete and reboot it > normally. > > 5.5 is OK. 5.6 is broken. I've heard

Hi,everyone I use the centos 7 of 4.14.12-rt10 kernel with the GP104M [GeForce GTX 1070 Mobile] display card.BUT,I did not find the support of it in the nouveau drivers. I clone the branch 4.14 of nouveau.git. After compile it with my kernel ,I found the GP104m had been not support. Could I get the newest updates? Thanks in advance Best Wishes Aiolia -------------- next part

On 12/12/2016 09:26 PM, Chris Chiu wrote: > Nouveau driver shows unknown chipset (136000a1) for GTX 1060, so it > only gives VGA resolution on screen. Use the same chipset as nv134 > then it shows FullHD. This commit copies fields from nv134_chipset > to nv136_chipset for GTX 1060. I have one of these sitting on my desk, but won't be merging support for it until it's been

https://bugs.freedesktop.org/show_bug.cgi?id=105669 Bug ID: 105669 Summary: can not support GP104M Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=100676 Bug ID: 100676 Summary: gp104 - messy(random green and/or missing pixel lines) then no output at and after boot Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=100567 Bug ID: 100567 Summary: Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hey! This is quick email to notify you that with 4.10-rc2 I can actually see graphic cursor in X making graphic environment usable. fb: switching to nouveaufb from EFI VGA nouveau 0000:01:00.0: NVIDIA GP104 (134000a1) nouveau 0000:01:00.0: bios: version 86.04.1e.00.01 nouveau 0000:01:00.0: fb: 8192 MiB GDDR5 nouveau 0000:01:00.0: priv: HUB0: 00d054 00000007 (1e408216) nouveau 0000:01:00.0: DRM:

https://bugs.freedesktop.org/show_bug.cgi?id=108857 Bug ID: 108857 Summary: display becomes unresponsive and keyboard input fails Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=99900 --- Comment #27 from aaron.hamid at gmail.com --- I am encountering the same "kernel rejected pushbuf: Device or resource busy" crash/lock cited here and in https://bugs.freedesktop.org/show_bug.cgi?id=100567 I'm posting here as I don't see SCHED_ERROR in my systemd journal, and I can reliably trigger it by running qemu android

After observing random crashes on Tegra devices when patch "fb/gf100: defer DMA mapping of scratch page to oneinit() hook" was applied, I noticed that moving the 100c10 page allocation to the oneinit() hook resulted in that page being now allocated for Tegra as well, and accesses be made to members of gf100_fb which were not accessible because gk20a_fb_new() called nvkm_fb_new_()

gm20b's FB has the same capabilities as gm200, minus the ability to allocate RAM. Create a device that reflects this instead of re-using the gk20a device which may be incorrect. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> --- drm/nouveau/include/nvkm/subdev/fb.h | 1 + drm/nouveau/nvkm/engine/device/base.c | 2 +- drm/nouveau/nvkm/subdev/fb/Kbuild | 1 +