[Nouveau] [Bug 90871] NV30: Xfwm4 use_compositing - garbled display
https://bugs.freedesktop.org/show_bug.cgi?id=90871 --- Comment #39 from poma --- Has there been any progress, any preliminary patch to test? -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 92307] NV50: WARNING: ... at include/drm/drm_crtc.h:1577 drm_helper_choose_encoder_dpms+0x8a/0x90 [drm_kms_helper]()
https://bugs.freedesktop.org/show_bug.cgi?id=92307 --- Comment #2 from poma --- Tested with the latest http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=794a63c warnings are still occurring. -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Chipset & Family
On 07.10.2015 03:55, Ben Skeggs wrote: > NACK. > > All the relevant information is shown, "nouveau" (video driver) > detected an "NVIDIA G98" (complete with full chip identification > register value for specifics). I'm not bikeshedding this topic any > further than that. > > Thanks, > Ben. > Gaudeamus igitur. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Chipset & Family
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/07/2015 11:49 AM, poma wrote: > > dmesg -t | grep -i nvidia nouveau :02:00.0: NVIDIA G98 > (098200a2) input: HDA NVidia Rear Mic as > /devices/pci:00/:00:07.0/sound/card0/input6 input: HDA > NVidia Front Mic as > /devices/pci:00/:00:07.0/sound/card0/input7 input: HDA > NVidia Line as /devices/pci:00/:00:07.0/sound/card0/input8 > input: HDA NVidia Line Out Front as > /devices/pci:00/:00:07.0/sound/card0/input9 input: HDA > NVidia Line Out Surround as > /devices/pci:00/:00:07.0/sound/card0/input10 input: HDA > NVidia Line Out CLFE as > /devices/pci:00/:00:07.0/sound/card0/input11 input: HDA > NVidia Line Out Side as > /devices/pci:00/:00:07.0/sound/card0/input12 input: HDA > NVidia Front Headphone as > /devices/pci:00/:00:07.0/sound/card0/input13 > > - patched: $ dmesg -t | grep -i chipset nouveau :02:00.0: GPU > NVIDIA Chipset: G98 (098200a2) NACK. All the relevant information is shown, "nouveau" (video driver) detected an "NVIDIA G98" (complete with full chip identification register value for specifics). I'm not bikeshedding this topic any further than that. Thanks, Ben. > > Signed-off-by: poma > > Nvidia is not just about video, but also audio, so be more > descriptive on device type and chipset as well. > > --- drm/nouveau/nvkm/engine/device/base.c | 2 +- 1 file changed, 1 > insertion(+), 1 deletion(-) > > diff --git a/drm/nouveau/nvkm/engine/device/base.c > b/drm/nouveau/nvkm/engine/device/base.c index bbc9824..932a29a > 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++ > b/drm/nouveau/nvkm/engine/device/base.c @@ -2467,7 +2467,7 @@ > nvkm_device_ctor(const struct nvkm_device_func *func, goto done; } > > - nvdev_info(device, "NVIDIA %s (%08x)\n", + > nvdev_info(device, > "GPU NVIDIA Chipset: %s (%08x)\n", device->chip->name, boot0); > > /* determine frequency of timing crystal */ > -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWFHt0AAoJEHYLnGJQkpH7R3QP/AxIi2o4/gkiAmHpZMwnHOOd aWnlbQTushA47fO0GF56/mjFMz/l91IIqUp2hBdwb/hVSUxK/EZhmBYGeB90iy4N hw3SLb+dx2cOImqcFNHU1UKy3pOEbDVEsBNwSRBNgSYJ4jGzFvzOAQMg8Od6paPQ 4yEYlI7UmG/nJZZ6cnerH2ljv2G6txog40Q9TdqlNNC/Pqk+IFP4LCvRSNHPUPuE yVEiCF49qUWoEBCohN4+gMqpV41frz/dgS1rZlxToC+c1TrkRaygjtVvxC29e7n4 W1nsCqGQxAdI7YN10eYWDWVLC35rwIi3ijXHg7DDu/CEKVABw+Xs2yrQSBNTrnLG +jahvPmLQY0wSCAe0eigZSGbGsjkpKgjVBVNi9zJcWBcG/KTwwgM3AnHh6JMKY8j N2dcVWOKEn1ix7XeBiyM4xIi/H14rLswwrsAnW3IeJ7nmwcsyMHqyByL8jXkWhJc TYRvkKhJDGc7Yt/8gsweJYqpt5daSjU3rGs2vSUzf9p4N6EWvpxxm9kwFcu5BCU+ 6HdGS9NU58fF1sB61CxSVzr4+TziSk5LHhTyPkll+L44Os7xGEjmfUFgEbCTsAiZ Y2XlxJUrL/gZ0SmD/yhV2jrHQ5rBZXRCey1bbQOIW31DOaI0k72AGT8lyWShtgY1 6QpxNGUxeyMRDNmx6cZC =mebB -END PGP SIGNATURE- ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Chipset & Family
dmesg -t | grep -i nvidia nouveau :02:00.0: NVIDIA G98 (098200a2) input: HDA NVidia Rear Mic as /devices/pci:00/:00:07.0/sound/card0/input6 input: HDA NVidia Front Mic as /devices/pci:00/:00:07.0/sound/card0/input7 input: HDA NVidia Line as /devices/pci:00/:00:07.0/sound/card0/input8 input: HDA NVidia Line Out Front as /devices/pci:00/:00:07.0/sound/card0/input9 input: HDA NVidia Line Out Surround as /devices/pci:00/:00:07.0/sound/card0/input10 input: HDA NVidia Line Out CLFE as /devices/pci:00/:00:07.0/sound/card0/input11 input: HDA NVidia Line Out Side as /devices/pci:00/:00:07.0/sound/card0/input12 input: HDA NVidia Front Headphone as /devices/pci:00/:00:07.0/sound/card0/input13 - patched: $ dmesg -t | grep -i chipset nouveau :02:00.0: GPU NVIDIA Chipset: G98 (098200a2) Signed-off-by: poma Nvidia is not just about video, but also audio, so be more descriptive on device type and chipset as well. --- drm/nouveau/nvkm/engine/device/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index bbc9824..932a29a 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++ b/drm/nouveau/nvkm/engine/device/base.c @@ -2467,7 +2467,7 @@ nvkm_device_ctor(const struct nvkm_device_func *func, goto done; } - nvdev_info(device, "NVIDIA %s (%08x)\n", + nvdev_info(device, "GPU NVIDIA Chipset: %s (%08x)\n", device->chip->name, boot0); /* determine frequency of timing crystal */ -- 2.6.0 ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Chipset & Family
On 06.10.2015 21:07, Pierre Moreau wrote: > Hello poma, > > The chipset didn't disappear and is still displayed: it is the G98 you get on > the "[2.483843] nouveau :02:00.0: NVIDIA G98 (098200a2)" line. The > "NV98" was the "Nouveau" chipset, but the switch was made to use the same > naming as NVIDIA. So rather than displaying both the Nouveau version of the > chipset and the NVIDIA one, it make sense to only use one, and to prefer the > NVIDIA naming. (FYI, files name has been modified to follow the NVIDIA naming > as well, along with envytools.) > If you decided to follow NVIDIA naming scheme, OK it is your concern as developers. But it's not just the actual version and revision of the chipset, but also descriptive string itself - "Chipset". > As for the family, it can be easily deduced from the chipset in most cases: > GMxxx are Maxwell cards, GKxxx are Kepler cards, GFxxx are Fermi cards, GTxxx > are Tesla cards, and most reasonably, GPxxx will be Pascal cards. NV50, G8x, > G9x, MCPxx are also Tesla cards. They do not follow the same pattern as newer > cards and so it might not be as easy to identify their family. But there is > the wiki page to help for that. > > Regards, > Pierre > (ALL!) all of the people around us they say Can they be that close Just let me state for the record We're giving love in a family dose We are family I got all my sisters with me We are family Get up ev'rybody and sing ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Struggle with GPU lockups and console deadlock using kernel-space modifications
There were some genuine GPU lockups (with older drivers), but in the previous mail I misidentified my current problem, that turned out to be a deadlocked Xorg. It possibly is caused by hardware malfunction, as there is a plenty of Oct 6 21:46:35 duk kernel: [ 686.096701] nouveau :01:00.0: fb: trapped read at 0020014110 on channel 1 [0fcae000 DRM] engine 0c [SEMAPHORE_BG] client 08 [PFIFO_READ] subclient 00 [] reason 000f [DMAOBJ_LIMIT] Oct 6 21:46:36 duk kernel: [ 686.273035] nouveau :01:00.0: fb: trapped read at 0020012040 on channel 1 [0fcae000 DRM] engine 0c [SEMAPHORE_BG] client 08 [PFIFO_READ] subclient 00 [] reason 000f [DMAOBJ_LIMIT] Oct 6 21:46:36 duk kernel: [ 686.303822] nouveau :01:00.0: fifo: CACHE_ERROR - ch 1 [DRM] subc 7 mthd 1ffc data 00ff Oct 6 21:46:36 duk kernel: [ 686.303843] nouveau :01:00.0: fifo: CACHE_ERROR - ch 1 [DRM] subc 7 mthd 1ffc data 00ff in kern.log, but GPU actually runs software and I even can move a mouse pointer sometimes. When switching VC from the Xorg’s console is requested (no matter with which keys or API), the kernel sends Xorg the SIGUSR1 signal. When Xorg is locked up, it won’t allow to proceed with switching consoles. > • «⧦->devinit->post = true; nvkm_device_init(⧦);» without reset — >to be tested. Not very interesting. Video signal dies out (just as with config=NvForcePost=1), but nouveau technically continues to work, and locked up Xorg wastes CPU time. Also, programmed reboot becomes impossible (system crashes on attempt to do it). Regards, Incnis Mrsi ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Chipset & Family
Hello poma, The chipset didn't disappear and is still displayed: it is the G98 you get on the "[2.483843] nouveau :02:00.0: NVIDIA G98 (098200a2)" line. The "NV98" was the "Nouveau" chipset, but the switch was made to use the same naming as NVIDIA. So rather than displaying both the Nouveau version of the chipset and the NVIDIA one, it make sense to only use one, and to prefer the NVIDIA naming. (FYI, files name has been modified to follow the NVIDIA naming as well, along with envytools.) As for the family, it can be easily deduced from the chipset in most cases: GMxxx are Maxwell cards, GKxxx are Kepler cards, GFxxx are Fermi cards, GTxxx are Tesla cards, and most reasonably, GPxxx will be Pascal cards. NV50, G8x, G9x, MCPxx are also Tesla cards. They do not follow the same pattern as newer cards and so it might not be as easy to identify their family. But there is the wiki page to help for that. Regards, Pierre > On 06 Oct 2015, at 15:01, poma wrote: > >> On 06.10.2015 02:21, poma wrote: >> 4.1.8-200.fc22.x86_64 dmesg: >> [ 11.809467] nouveau [ DEVICE][:02:00.0] BOOT0 : 0x098200a2 >> [ 11.809493] nouveau [ DEVICE][:02:00.0] Chipset: G98 (NV98) >> [ 11.809508] nouveau [ DEVICE][:02:00.0] Family : NV50 >> >> >> 4.3.0-0.rc4.git0.1.fc24.x86_64 dmesg: >> [2.483843] nouveau :02:00.0: NVIDIA G98 (098200a2) >> >> >> Where vanished these Chipset & Family super cool lines? > > http://cgit.freedesktop.org/~darktama/nouveau/commit/drm/nouveau/nvkm/engine/device/base.c?id=6cc9e47 > > commit 6cc9e47f7f574cb3df6b14caebf15b35408b106d > Author: Ben Skeggs > Date: Thu Aug 20 14:54:13 2015 +1000 > >device: switch to dev_printk macros > >Signed-off-by: Ben Skeggs > > drm/nouveau/nvkm/engine/device/base.c | 11 +++ > ... > > > -nv_info(device, "BOOT0 : 0x%08x\n", boot0); > -nv_info(device, "Chipset: %s (NV%02X)\n", > -device->cname, device->chipset); > -nv_info(device, "Family : NV%02X\n", device->card_type); > +nvdev_info(device, "NVIDIA %s (%08x)\n", device->cname, boot0); > > > > These lines were useful as basic device information, > and as reference to wiki "CodeNames" > http://nouveau.freedesktop.org/wiki/CodeNames > > "This page contains a list of some NVIDIA chip code names and their > corresponding official GeForce number. If you're running a recent version > nouveau, you can find your chipset by doing dmesg | grep -i chipset. This > will always be correct, whereas the lists below are approximate." > > Notice "dmesg | grep -i chipset" > > BTW "NVIDIA" is already visible via 'lspci' - lspci | grep VGA > > So only gain is unnecessary information reduction and redundancy. > > Please bring Chipset & Family back. > > > ___ > Nouveau mailing list > Nouveau@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/nouveau ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 92287] Display errors in Qt applications after using Android Virtual Devices
https://bugs.freedesktop.org/show_bug.cgi?id=92287 --- Comment #7 from Guido Winkelmann --- One more addendum: Since upgrading to mesa-git yesterday, the problem seems to randomly solve itself every once in a while, whereas before, it could only be solved by rebooting... -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Chipset & Family
On 06.10.2015 02:21, poma wrote: > 4.1.8-200.fc22.x86_64 dmesg: > [ 11.809467] nouveau [ DEVICE][:02:00.0] BOOT0 : 0x098200a2 > [ 11.809493] nouveau [ DEVICE][:02:00.0] Chipset: G98 (NV98) > [ 11.809508] nouveau [ DEVICE][:02:00.0] Family : NV50 > > > 4.3.0-0.rc4.git0.1.fc24.x86_64 dmesg: > [2.483843] nouveau :02:00.0: NVIDIA G98 (098200a2) > > > Where vanished these Chipset & Family super cool lines? > http://cgit.freedesktop.org/~darktama/nouveau/commit/drm/nouveau/nvkm/engine/device/base.c?id=6cc9e47 commit 6cc9e47f7f574cb3df6b14caebf15b35408b106d Author: Ben Skeggs Date: Thu Aug 20 14:54:13 2015 +1000 device: switch to dev_printk macros Signed-off-by: Ben Skeggs drm/nouveau/nvkm/engine/device/base.c | 11 +++ ... - nv_info(device, "BOOT0 : 0x%08x\n", boot0); - nv_info(device, "Chipset: %s (NV%02X)\n", - device->cname, device->chipset); - nv_info(device, "Family : NV%02X\n", device->card_type); + nvdev_info(device, "NVIDIA %s (%08x)\n", device->cname, boot0); These lines were useful as basic device information, and as reference to wiki "CodeNames" http://nouveau.freedesktop.org/wiki/CodeNames "This page contains a list of some NVIDIA chip code names and their corresponding official GeForce number. If you're running a recent version nouveau, you can find your chipset by doing dmesg | grep -i chipset. This will always be correct, whereas the lists below are approximate." Notice "dmesg | grep -i chipset" BTW "NVIDIA" is already visible via 'lspci' - lspci | grep VGA So only gain is unnecessary information reduction and redundancy. Please bring Chipset & Family back. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 92287] Display errors in Qt applications after using Android Virtual Devices
https://bugs.freedesktop.org/show_bug.cgi?id=92287 --- Comment #6 from Guido Winkelmann --- It looked good yesterday, but today the problem is back... -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 91319] Nouveau driver cannot extract FCODE ROM / DCB Block from OpenFirmware Device tree
https://bugs.freedesktop.org/show_bug.cgi?id=91319 --- Comment #13 from Peter Saisanas --- I can confirm that the patch works with my config which is great news. However, the patch does not apply cleanly to vanilla 4.3-rc4, it seems to reject parts of the patch to shadowof.c. After manually changing shadowof.c, i.e. the parts of the patch that was rejected, compiled and hooray, it works! Awesome, thanks imirkin! Do you require any more info? -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 92306] GL Excess demo renders incorrectly on nv43
https://bugs.freedesktop.org/show_bug.cgi?id=92306 Andrew Randrianasulu changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 92306] GL Excess demo renders incorrectly on nv43
https://bugs.freedesktop.org/show_bug.cgi?id=92306 --- Comment #5 from Andrew Randrianasulu --- Hm, apparently this is regression - tried few mesa versions - 10.1.6 was OK, but 10.2.9 already broken. Attempt to disable few new (in 10.2) extensions not fixed this. "Mesa 10.2.9 implementation error: Trying to disable a permanently enabled extension: GL_ARB_multi_bind" - this one can't be disabled, it seems (commandline used MESA_EXTENSION_OVERRIDE="-GL_ARB_multi_bind" wine GLExcess.exe) MESA_EXTENSION_OVERRIDE="-GL_ARB_buffer_storage" wine GLExcess.exe - not resulted in anything. Apparently those two types of corruption related (no image and parts of scene filled with rainbow lines) - at least they both started to appear in 10.2.9 -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau