search for: nvgrusefw

...lass = (void *)bclass; > struct nouveau_device *device = nv_device(parent); > struct nvc0_graph_priv *priv; > + bool use_fw; Perhaps "ext_fw" or "use_ext_fw" would be more accurate. > int ret, i; > > + use_fw = nouveau_boolopt(device->cfgopt, "NvGrUseFW", false); > + > ret = nouveau_graph_create(parent, engine, bclass, > - (oclass->fecs.ucode != NULL), &priv); > + (oclass->fecs.ucode != NULL) || use_fw, > + &priv); Or perhaps a more intuitive way would be to name the variable "enable&quot...

...ch a use-case is valid. > > Relax the conditions enabling the GR engine to also include the case > where an external firmware has also been loaded. I'm happy to take this patch as-is. I do wonder if we should do something like this though: if (nouveau_boolopt(device->cfgopt, "NvGrUseFW", oclass->fecs.ucode == NULL)) Which will automatically switch to external firmware if there's no internal implementation available. Thoughts? This could be a separate patch even, if preferred. Thanks, Ben. > > Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> &...

https://bugs.freedesktop.org/show_bug.cgi?id=73373 Priority: medium Bug ID: 73373 Assignee: nouveau at lists.freedesktop.org Summary: [NVE4] GPU lockup after opening many tabs in Chromium web browser Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: mbarrera at gmx.com

...in gpccs_inst.bin gpccs_data.bin Now I installed a new system from scratch on same computer. Used **exactly same kernel config** (it means it is valid for all *FIRMWARE* values), but newer kernel version 4.7.10-r1. I put same firmware files into /lib/firmware/nvidia/gk106, put nouveau.config="NvGrUseFw=1" in grub kernel line, but it is not loading, I can't see line in `dmesg | grep nouveau` gr: using external firmware, as it was in my old 4.4.8 setup. After that, I tried to copy these blobs to old naming space, /lib/firmware/nouveau/fuc*, tried to include them in kernel directly, tried...

...glance at the wiki page you got > that from for clues as to why.] > "You basically never need to do the mmiotrace, unless you're a nouveau developer."? I did everything by the book[1]. Though I don't need this, I still wanted to see how it works with 'nouveau.config=NvGrUseFW=1'. Bummer. [1] https://wiki.ubuntu.com/X/MMIOTracing >> >> $ modinfo nvidia -F version >> 304.123 >> >> $ stat -c %s mmiotrace.log >> 134659197 >> >> $ file mmiotrace.log >> mmiotrace.log: ASCII text >> >> $ grep -i lost mmi...

...7424 Mar 17 15:29 vuc-vp4-mpeg4-0 -rw-r--r--. 1 root root 7424 Mar 17 15:29 vuc-vp4-mpeg4-1 -rw-r--r--. 1 root root 7424 Mar 17 15:29 vuc-vp4-vc1-0 -rw-r--r--. 1 root root 8448 Mar 17 15:29 vuc-vp4-vc1-1 -rw-r--r--. 1 root root 8448 Mar 17 15:29 vuc-vp4-vc1-2 with: options nouveau config=NvGrUseFW=1 in my modprobe configuration, and that made no obvious difference, even in the kernel logs. --Andy

https://bugs.freedesktop.org/show_bug.cgi?id=92863 Bug ID: 92863 Summary: Complete freeze even with NvGrUseFW=1 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org...

...deo, except for the mouse pointer, hangs until reboot. It is possible to SSH into the machine for a while until it freezes completely. Video card: NVIDIA Corporation GK104M [GeForce GTX 670MX] (rev a1) Operating system: Archlinux with linux 3.19.3-3-ARCH nouveau-fw is installed and nouveau.config=NvGrUseFW=1 is in the kernel parameters. I logged in via SSH into the blocked machine and dumped dmesg's output, it produced a 6MiB sized file of only: [ 432.267634] nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ch 6 [gstglcontext[1984]] subc 0 mthd 0x000c data 0x2001054e [ 432.267645] nouveau E[ PFIFO...

...nvc0_graph_ctor(struct nouveau_object *parent, struct nouveau_object *engine, struct nvc0_graph_oclass *oclass = (void *)bclass; struct nouveau_device *device = nv_device(parent); struct nvc0_graph_priv *priv; + bool use_fw; int ret, i; + use_fw = nouveau_boolopt(device->cfgopt, "NvGrUseFW", false); + ret = nouveau_graph_create(parent, engine, bclass, - (oclass->fecs.ucode != NULL), &priv); + (oclass->fecs.ucode != NULL) || use_fw, + &priv); *pobject = nv_object(priv); if (ret) return ret; @@ -1146,7 +1150,7 @@ nvc0_graph_ctor(struct nouv...

...vice *device = nv_device(parent); >> struct nvc0_graph_priv *priv; >> + bool use_fw; > > Perhaps "ext_fw" or "use_ext_fw" would be more accurate. > >> int ret, i; >> >> + use_fw = nouveau_boolopt(device->cfgopt, "NvGrUseFW", false); >> + >> ret = nouveau_graph_create(parent, engine, bclass, >> - (oclass->fecs.ucode != NULL), &priv); >> + (oclass->fecs.ucode != NULL) || use_fw, >> +...

...*)bclass; struct nouveau_device *device = nv_device(parent); struct nvc0_graph_priv *priv; + bool use_ext_fw, enable; int ret, i; - ret = nouveau_graph_create(parent, engine, bclass, - (oclass->fecs.ucode != NULL), &priv); + use_ext_fw = nouveau_boolopt(device->cfgopt, "NvGrUseFW", false); + enable = use_ext_fw || oclass->fecs.ucode != NULL; + + ret = nouveau_graph_create(parent, engine, bclass, enable, &priv); *pobject = nv_object(priv); if (ret) return ret; @@ -1272,7 +1275,7 @@ nvc0_graph_ctor(struct nouveau_object *parent, struct nouveau_object *engin...

...clues as to why.] >>> >> >> "You basically never need to do the mmiotrace, unless you're a nouveau developer."? >> >> I did everything by the book[1]. >> Though I don't need this, I still wanted to see how it works with 'nouveau.config=NvGrUseFW=1'. >> Bummer. > > You don't just not need it -- you can't possibly use it. Context > switching firmware of this sort only exists on nvc0+ (fermi and > newer). As the page you got the instructions from suggests > (NVC0_Firmware). > > -ilia > AHA! Maxw...

...6-video-nouveau has no support for the GM20x family? Note that even if it did load, you wouldn't get any acceleration -- may as well just use the 'xf86-video-modesetting' driver. > > I tried to use the nvidia firmware: > [...] > > with: > > options nouveau config=NvGrUseFW=1 > > in my modprobe configuration, and that made no obvious difference, > even in the kernel logs. Right, that's expected. GM20x requires signed firmware. We haven't even gotten as far as being able to figure out what all the *proprietary* firmware is, never mind even loading it....

...st feasible since the > actual video decoding is done with firmware that's on the card (or > with dedicated hardware, who knows) so all that's left is providing > the little "os" running on the connected falcon processors. > > Unless you're booting with nouveau.NvGrUseFW=1, you don't need the > pgraph firmware. It generally tends to work for nve0 cards nowadays, > although some people have issues with hangs (e.g. > https://bugs.freedesktop.org/show_bug.cgi?id=70354, > https://bugs.freedesktop.org/show_bug.cgi?id=72180). I believe there > were a b...

https://bugs.freedesktop.org/show_bug.cgi?id=101184 Bug ID: 101184 Summary: [bisected] Panic on boot with GK106 Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau at

...gt; > Relax the conditions enabling the GR engine to also include the case > > where an external firmware has also been loaded. > I'm happy to take this patch as-is. I do wonder if we should do > something like this though: > > if (nouveau_boolopt(device->cfgopt, "NvGrUseFW", oclass->fecs.ucode == NULL)) > > Which will automatically switch to external firmware if there's no > internal implementation available. I think that makes a lot of sense. Perhaps outputting a warning or so at runtime when this happens would be helpful in reminding people t...

...; >> Relax the conditions enabling the GR engine to also include the case >> where an external firmware has also been loaded. > I'm happy to take this patch as-is. I do wonder if we should do > something like this though: > > if (nouveau_boolopt(device->cfgopt, "NvGrUseFW", oclass->fecs.ucode == NULL)) > > Which will automatically switch to external firmware if there's no > internal implementation available. > > Thoughts? This could be a separate patch even, if preferred. Sure, that should work. Do you mind if I come with a follow-up pat...

...t >> that from for clues as to why.] >> > > "You basically never need to do the mmiotrace, unless you're a nouveau developer."? > > I did everything by the book[1]. > Though I don't need this, I still wanted to see how it works with 'nouveau.config=NvGrUseFW=1'. > Bummer. You don't just not need it -- you can't possibly use it. Context switching firmware of this sort only exists on nvc0+ (fermi and newer). As the page you got the instructions from suggests (NVC0_Firmware). -ilia

...was in beta, I tried it and then reverted back. Now I don't know what to do... nvidia drivers also don't work well. I tried mesa 18 but sddm does not start. My setup: mesa 17.2.8 (considered latest stable in gentoo) Gentoo hardened 4.9.24-grsec Nvidia GTX 660 (GK106) nouveau.config="NvGrUseFw=1" (and a few blobs, without this system freeze and image is damaged) everything else is updated to latest ~amd64 versions. 4 monitors Please help. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. -------------- next part --------...

...e that is probably the most feasible since the actual video decoding is done with firmware that's on the card (or with dedicated hardware, who knows) so all that's left is providing the little "os" running on the connected falcon processors. Unless you're booting with nouveau.NvGrUseFW=1, you don't need the pgraph firmware. It generally tends to work for nve0 cards nowadays, although some people have issues with hangs (e.g. https://bugs.freedesktop.org/show_bug.cgi?id=70354, https://bugs.freedesktop.org/show_bug.cgi?id=72180). I believe there were a bunch of fixes to the fuc...