Re: [Nouveau] [PATCH v2] gr: fallback to legacy paths during firmware lookup
On Sun, Nov 6, 2016 at 12:12 AM, Peter Wu wrote:
> On Fri, Nov 04, 2016 at 06:36:17PM +0900, Alexandre Courbot wrote:
>> Look for firmware files using the legacy ("nouveau/nvxx_fuc") path
>> if they cannot be found in the new, "official" path. User setups were
>> broken by the switch, which is bad.
>>
>> There are only 4 firmware files we may want to look up that way, so
>> hardcode them into the lookup function. All new firmware files should
>> use the standard "nvidia//gr/" path.
>>
>> Fixes: 8539b37acef7 ("drm/nouveau/gr: use NVIDIA-provided external
>> firmwares")
>> Signed-off-by: Alexandre Courbot
>> ---
>> Changes since v1:
>> * Moved file name translation into the legacy function
>>
>> drm/nouveau/nvkm/engine/gr/gf100.c | 53
>> +++---
>> 1 file changed, 49 insertions(+), 4 deletions(-)
>>
>> diff --git a/drm/nouveau/nvkm/engine/gr/gf100.c
>> b/drm/nouveau/nvkm/engine/gr/gf100.c
>> index eccdee04107d..ed45f923442f 100644
>> --- a/drm/nouveau/nvkm/engine/gr/gf100.c
>> +++ b/drm/nouveau/nvkm/engine/gr/gf100.c
>> @@ -1756,6 +1756,53 @@ gf100_gr_ = {
>> };
>>
>> int
>> +gf100_gr_ctor_fw_legacy(struct gf100_gr *gr, const char *fwname,
>> + struct gf100_gr_fuc *fuc, int ret)
>> +{
>> + struct nvkm_subdev *subdev = &gr->base.engine.subdev;
>> + struct nvkm_device *device = subdev->device;
>> + const struct firmware *fw;
>> + char f[32];
>> +
>> + /* see if this firmware has a legacy path */
>> + if (!strcmp(fwname, "fecs_inst"))
>> + fwname = "fuc409c";
>> + else if (!strcmp(fwname, "fecs_data"))
>> + fwname = "fuc409d";
>> + else if (!strcmp(fwname, "gpccs_inst"))
>> + fwname = "fuc41ac";
>> + else if (!strcmp(fwname, "gpccs_data"))
>> + fwname = "fuc41ad";
>> + else
>> + fwname = NULL;
>> +
>> + /* nope, let's just return the error we got */
>> + if (!fwname) {
>> + nvkm_error(subdev, "failed to load %s\n", fwname);
>
> Due to the rename from legacy_fwname -> fwname, this can be NULL.
> What about replacing the else branch above by this block?
Ah, stupid me - I wanted to save a variable and here is the result.
Thanks for catching this, I will send a fixup patch to Ben.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 97462] Graphics deadlock "ILLEGAL_MTHD" in nouveau with mesa version 11.2.2 when visiting Google Maps with firefox 49.0b5
https://bugs.freedesktop.org/show_bug.cgi?id=97462 --- Comment #15 from Paviluf --- (In reply to wadev from comment #13) > Paviluf, could you please mention your firefox version and the output of > your glxinfo - at least the core profile one pertaining to mesa version? I can't since I'm on Nvidia proprietary drivers for now. If I switch back to nouveau I will do it, if I remember :D I recently tried Fedora 25 and it seem to work with nouveau dri2 and dri3 now. -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 97462] Graphics deadlock "ILLEGAL_MTHD" in nouveau with mesa version 11.2.2 when visiting Google Maps with firefox 49.0b5
https://bugs.freedesktop.org/show_bug.cgi?id=97462 --- Comment #16 from Paviluf --- By the way, are we reporting this at the right place ? There is also Mesa/DRI/Nouveau that seem more appropriate to me. -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98609] New: Firefox right click corrupted with DRI3
https://bugs.freedesktop.org/show_bug.cgi?id=98609 Bug ID: 98609 Summary: Firefox right click corrupted with DRI3 Product: Mesa Version: unspecified Hardware: All OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau@lists.freedesktop.org Reporter: jeremy9...@gmail.com QA Contact: nouveau@lists.freedesktop.org Hello, Firefox right click is corrupted with DRI3 enabled. It works with DRI2. Fedora 24/25 I don't know if you need more info. If it's the case just ask me what you need. Thanks ! -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 92057] nouveau hard crash seems to poke arbitrary mmio address
https://bugs.freedesktop.org/show_bug.cgi?id=92057 roucaries.bastien+b...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from roucaries.bastien+b...@gmail.com --- Fixed in 4.2 -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 97620] [REGRESSION, bisected] KMS can't initialize GeForce GTX 460 after commit a6a0f67ca7aae2e6bec7ebf55d1e4853dc220816
https://bugs.freedesktop.org/show_bug.cgi?id=97620 --- Comment #29 from roucaries.bastien+b...@gmail.com --- Some symptoms with a GFX970. Something strange is without signed firmware I can get something work but in lower resolution with kernel > 4.5 With signed firmware it crash during kms and black screen. no reboot except with button -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 97620] [REGRESSION, bisected] KMS can't initialize GeForce GTX 460 after commit a6a0f67ca7aae2e6bec7ebf55d1e4853dc220816
https://bugs.freedesktop.org/show_bug.cgi?id=97620 --- Comment #30 from Pierre Moreau --- (In reply to roucaries.bastien+bugs from comment #29) > Some symptoms with a GFX970. > > Something strange is without signed firmware I can get something work but in > lower resolution with kernel > 4.5 > > With signed firmware it crash during kms and black screen. no reboot except > with button This is most likely https://bugs.freedesktop.org/show_bug.cgi?id=94990 -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98609] Firefox right click corrupted with DRI3
https://bugs.freedesktop.org/show_bug.cgi?id=98609 Peter Wu changed: What|Removed |Added CC||pe...@lekensteyn.nl --- Comment #1 from Peter Wu --- Do you have a screenshot, Xorg/dmesg logs or anything more detailled? What hardware and software? Laptop/desktop? -- 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 https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98611] New: nouveau not working on gtx 970
https://bugs.freedesktop.org/show_bug.cgi?id=98611 Bug ID: 98611 Summary: nouveau not working on gtx 970 Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau@lists.freedesktop.org Reporter: doc...@gmx.de QA Contact: xorg-t...@lists.x.org http://ptpb.pw/-Fjc -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98611] nouveau not working on gtx 970
https://bugs.freedesktop.org/show_bug.cgi?id=98611 Ilia Mirkin changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #1 from Ilia Mirkin --- Feel free to reopen if you care to provide information. Please also search through existing bugs, a number of GTX 970 owners have had various issues. -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 94990] [GM204] GTX 970 + 4GB VRAM fails at secboot (v4.6+)
https://bugs.freedesktop.org/show_bug.cgi?id=94990 --- Comment #83 from DocMAX --- same issue http://ptpb.pw/-Fjc -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98609] Firefox right click corrupted with DRI3
https://bugs.freedesktop.org/show_bug.cgi?id=98609 --- Comment #2 from Paviluf --- Created attachment 127801 --> https://bugs.freedesktop.org/attachment.cgi?id=127801&action=edit screenshot 1 Firefox right click corrupted -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98609] Firefox right click corrupted with DRI3
https://bugs.freedesktop.org/show_bug.cgi?id=98609 --- Comment #3 from Paviluf --- Created attachment 127802 --> https://bugs.freedesktop.org/attachment.cgi?id=127802&action=edit screenshot 2 Firefox right click corrupted -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98609] Firefox right click corrupted with DRI3
https://bugs.freedesktop.org/show_bug.cgi?id=98609 --- Comment #5 from Paviluf --- Created attachment 127804 --> https://bugs.freedesktop.org/attachment.cgi?id=127804&action=edit dmesg -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98609] Firefox right click corrupted with DRI3
https://bugs.freedesktop.org/show_bug.cgi?id=98609 --- Comment #4 from Paviluf --- Created attachment 127803 --> https://bugs.freedesktop.org/attachment.cgi?id=127803&action=edit screenshot 3 Firefox right click corrupted -- 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 https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98609] Firefox right click corrupted with DRI3
https://bugs.freedesktop.org/show_bug.cgi?id=98609 --- Comment #6 from Paviluf --- (In reply to Peter Wu from comment #1) > Do you have a screenshot, Xorg/dmesg logs or anything more detailled? > > What hardware and software? Laptop/desktop? I uploaded 3 screenshots that show the Firefox right click corrupted. I happen on X11 and wayland. I can add that sometimes it can be all black or sometimes (at least on wayland) it can be "colorized". You can also find a dmesg log. I use desktop with a Nvidia GT430. That happen on Fedora 24 and 25. If you need anything more just say it. Oh, by the way I'm not sure that this other bug is reported at the right place ? Mesa/DRI/Nouveau seem more appropriate to me. https://bugs.freedesktop.org/show_bug.cgi?id=97462 Thank you ! -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] NVAC "No Signal"
http://goo.gl/Gm4ffO mmiotrace-nouveau/ ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Atomic modesetting + DisplayPort MST
okay, I managed to bisect this issue and it comes down to this commit: https://github.com/skeggsb/linux/commit/f6795bda9c2ee8173398533cab355fe259a9c1f1 with that commit, a 00ed EDID is read out and using that display fails. It's a display connected with a miniDP to DVI listed as "DP-1" in xrandr 2016-11-04 10:41 GMT+01:00 Ben Skeggs : > Hey all, > > I've just pushed out the initial Nouveau support for $subject \o/ > > As the atomic modesetting transition is basically a rewrite of the KMS > portion of the driver, I would be very grateful for any additional > testing that people could provide (even as simple as just booting and > making sure you get a display is valuable). > > There's a Linux tree at > https://github.com/skeggsb/linux/tree/linux-4.10, and the code also > exists in my usual development tree[1] on the master branch (which is > currently based on Dave's drm-next tree for Linux 4.10). > > There's another branch (devel-kms) in the same repository, which is the > same code on top of what's currently Linux 4.9. If you have problems > with the 4.10 code, I'd definitely be interested in seeing if they exist > on the 4.9 branch too. > > Thanks in advance! > Ben. > > [1] https://github.com/skeggsb/nouveau > > > ___ > Nouveau mailing list > Nouveau@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/nouveau > ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98609] Firefox right click corrupted with DRI3
https://bugs.freedesktop.org/show_bug.cgi?id=98609
--- Comment #7 from Paviluf ---
Forgot to mention that I opened an other issue on Firefox bug tracker and that
I use this user.js in Firefox
https://bugzilla.mozilla.org/show_bug.cgi?id=1315529
// PERFORMANCE
user_pref("layers.acceleration.force-enabled", true);
user_pref("layers.offmainthreadcomposition.enabled", true);
user_pref("layers.offmainthreadcomposition.async-animations", true);
user_pref("layout.frame_rate.precise", true);
user_pref("webgl.force-enabled", true);
user_pref("webgl.msaa-force", true);
user_pref("html5.offmainthread", true);
user_pref("gfx.content.azure.backends", "skia");
user_pref("browser.tabs.remote.force-enable", true);
// PRIVACY
user_pref("loop.enabled", false);
user_pref("extensions.pocket.enabled", false);
user_pref("privacy.trackingprotection.enabled", true);
user_pref("browser.safebrowsing.enabled", false);
user_pref("browser.safebrowsing.malware.enabled", false);
user_pref("dom.event.clipboardevents.enabled", false);
user_pref("browser.send_pings", false);
user_pref("dom.battery.enabled", false);
// USABILITY
user_pref("browser.tabs.loadBookmarksInBackground", true);
user_pref("reader.parse-on-load.enabled", false);
user_pref("reader.parse-on-load.force-enabled", false);
It seem that without the user.js file the right click works. But that user.js
is not an option since without it there is tearing.
--
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
https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98609] Firefox right click corrupted with DRI3
https://bugs.freedesktop.org/show_bug.cgi?id=98609 --- Comment #8 from Paviluf --- (In reply to Paviluf from comment #7) > But that user.js is not an option since without it there is tearing. There is not tearing with wayland but wayland (mutter) is not ready yet. -- 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 https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 98611] nouveau not working on gtx 970
https://bugs.freedesktop.org/show_bug.cgi?id=98611 Karol Herbst changed: What|Removed |Added Resolution|INVALID |DUPLICATE --- Comment #2 from Karol Herbst --- I am 99% sure this is a duplicate of #94990 *** This bug has been marked as a duplicate of bug 94990 *** -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 94990] [GM204] GTX 970 + 4GB VRAM fails at secboot (v4.6+)
https://bugs.freedesktop.org/show_bug.cgi?id=94990 Karol Herbst changed: What|Removed |Added CC||doc...@gmx.de --- Comment #84 from Karol Herbst --- *** Bug 98611 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Atomic modesetting + DisplayPort MST
another issue: whenever I stop X with your patches, the display becomes black and the display disabled. Works with 4.8.4 2016-11-04 10:41 GMT+01:00 Ben Skeggs : > Hey all, > > I've just pushed out the initial Nouveau support for $subject \o/ > > As the atomic modesetting transition is basically a rewrite of the KMS > portion of the driver, I would be very grateful for any additional > testing that people could provide (even as simple as just booting and > making sure you get a display is valuable). > > There's a Linux tree at > https://github.com/skeggsb/linux/tree/linux-4.10, and the code also > exists in my usual development tree[1] on the master branch (which is > currently based on Dave's drm-next tree for Linux 4.10). > > There's another branch (devel-kms) in the same repository, which is the > same code on top of what's currently Linux 4.9. If you have problems > with the 4.10 code, I'd definitely be interested in seeing if they exist > on the 4.9 branch too. > > Thanks in advance! > Ben. > > [1] https://github.com/skeggsb/nouveau > > > ___ > Nouveau mailing list > Nouveau@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/nouveau > ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 93828] Xorg hangs randomly with nouveau driver
https://bugs.freedesktop.org/show_bug.cgi?id=93828 --- Comment #11 from derrie...@gmail.com --- With newer kernel I've got new messages... If it can help. ov 6 16:26:49 wizz kernel: nouveau :01:00.0: fifo: DMA_PUSHER - ch 13 [flux[28527]] get 00 put 00 ib_get ib_put 0002 state c000 (err: MEM_FAULT) push 00400040 Nov 6 16:26:49 wizz kernel: nouveau :01:00.0: fb: trapped read at 002001 on channel 13 [3eebf000 flux[28527]] engine 05 [PFIFO] client 08 [PFIFO_READ] subclient 00 [PUSHBUF] reason 000f [DMAOBJ_LIMIT] Nov 6 16:26:49 wizz kernel: nouveau :01:00.0: fifo: DMA_PUSHER - ch 13 [flux[28527]] get 00 put 00 ib_get 0002 ib_put 0004 state c000 (err: MEM_FAULT) push 00400040 Nov 6 16:26:49 wizz kernel: nouveau :01:00.0: fb: trapped read at 0020010010 on channel 13 [3eebf000 flux[28527]] engine 05 [PFIFO] client 08 [PFIFO_READ] subclient 00 [PUSHBUF] reason 000f [DMAOBJ_LIMIT] Nov 6 16:26:49 wizz kernel: nouveau :01:00.0: fifo: DMA_PUSHER - ch 13 [flux[28527]] get 00 put 00 ib_get 0004 ib_put 0007 state c000 (err: MEM_FAULT) push 00400040 Nov 6 16:26:49 wizz kernel: nouveau :01:00.0: fb: trapped read at 0020010020 on channel 13 [3eebf000 flux[28527]] engine 05 [PFIFO] client 08 [PFIFO_READ] subclient 00 [PUSHBUF] reason 000f [DMAOBJ_LIMIT] -- You are receiving this mail because: You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [PATCH] gr: fixup for legacy paths firmware lookup
The code would print a NULL string if no legacy firmware was found.
Signed-off-by: Alexandre Courbot
Reported-by: Peter Wu
---
Hi Ben,
Sorry about the obvious mistake (and thanks Peter for reporting it!). You
may want to squash this one into the previous patch if there still is time.
drm/nouveau/nvkm/engine/gr/gf100.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drm/nouveau/nvkm/engine/gr/gf100.c
b/drm/nouveau/nvkm/engine/gr/gf100.c
index ed45f92..60a1b5c 100644
--- a/drm/nouveau/nvkm/engine/gr/gf100.c
+++ b/drm/nouveau/nvkm/engine/gr/gf100.c
@@ -1773,11 +1773,8 @@ gf100_gr_ctor_fw_legacy(struct gf100_gr *gr, const char
*fwname,
fwname = "fuc41ac";
else if (!strcmp(fwname, "gpccs_data"))
fwname = "fuc41ad";
- else
- fwname = NULL;
-
- /* nope, let's just return the error we got */
- if (!fwname) {
+ else {
+ /* nope, let's just return the error we got */
nvkm_error(subdev, "failed to load %s\n", fwname);
return ret;
}
--
2.10.1
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] Disable L2 cache on nvidia gpu
Dear all, Is there a command or low level instruction to disable the L2 cache in GPUs. Can a certain section of memory be defined as uncachable. Can you please point me the approach to do it. Thank you Vishwas ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
