search for: pbsp

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #16 from Stefan Ringel <mail at stefanringel.de> --- (In reply to comment #15) > Created attachment 97014 [details] > correct profile in vdpauinfo + vainfo dmseg: [ 97.292274] nouveau T[ PBSP][0000:01:00.0] inc() == 4 [ 97.341821] nouveau T[ PBSP][0000:01:00.0] use(+1) == 1 [ 97.341827] nouveau T[ PBSP][0000:01:00.0] initialising... [ 97.341831] nouveau T[ PBSP][0000:01:00.0] resetting... [ 97.341840] nouveau D[ PBSP][0000:01:00.0] reset [ 97.341847] nouveau D[...

...uveau 0000:01:00.0: Direct firmware load failed with error -2 [ 619.350193] nouveau 0000:01:00.0: Falling back to user helper [ 619.352536] nouveau 0000:01:00.0: Direct firmware load failed with error -2 [ 619.352543] nouveau 0000:01:00.0: Falling back to user helper [ 619.354243] nouveau E[ PBSP][0000:01:00.0] unable to load firmware data [ 619.354253] nouveau E[ PBSP][0000:01:00.0] init failed, -12 01:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce GT 220] (rev a2) 8.550547] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x0a5000a2 [ 8.550552] nouveau [ DEVICE][0...

Hi, just a note for everybody who stumble across this thread in the future in order to bring this thread to a proper end. If I run the kernel with nouveau.debug="PVP=debug,PBSP=debug,PPPP=debug" I see messages about the firmware files gettings loaded. If the firmware files are missing, I get some warnings/errors. So far everything works as expected. But if I invoke "mplayer" with the "-vo vdpau -vc ..." option either way mplayer claims to use...

...64] nouveau E[ PTHERM][0000:01:00.0] unhandled intr 0x00000161 I believe this is unrelated. > > When I use the kernel option nouveau.config=PCRYPT=0 it doesn't eliminate > the errors and X still hangs when resuming. It should eliminate the 10200c error. The others are from PVP and PBSP, you could do like nouveau.config=PCRYPT=0,PVP=0,PBSP=0,PMPEG=0 -- that should have the same effect as my patch for your hardware. (I think.) > I was not sure if I have to set the parameter in quotes. Not necessary, but I *think* it'll work with quotes as well. Not sure. > As you can s...

https://bugs.freedesktop.org/show_bug.cgi?id=86935 Bug ID: 86935 Summary: unknown kepler chipset Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org

...iv { static struct nouveau_oclass nv98_bsp_sclass[] = { + { 0x88b1, &nouveau_object_ofuncs }, + { 0x85b1, &nouveau_object_ofuncs }, + { 0x86b1, &nouveau_object_ofuncs }, {}, }; /******************************************************************************* - * BSP context + * PBSP context ******************************************************************************/ static struct nouveau_oclass nv98_bsp_cclass = { .handle = NV_ENGCTX(BSP, 0x98), .ofuncs = &(struct nouveau_ofuncs) { - .ctor = _nouveau_engctx_ctor, - .dtor = _nouveau_engctx_dtor, - .init = _n...

In https://nouveau.freedesktop.org/KernelModuleParameters.html, there is: Here is a list of engines: DEVICE DMAOBJ PBSP PCE0 PCE1 PCE2 PCRYPT PDISP PFIFO PGRAPH PMPEG PPM PPPP PVP SW Also, in debug: CLIENT I have tried to find a description of those. https://envytools.readthedocs.io/en/latest/ help a bit, but I don't find a precise correlation. https://nouveau...

Hello, I run the Gentoo Linux distribution and use a self-compiled Linux 3.10.17 kernel. According to [1] http://nouveau.freedesktop.org/wiki/InstallDRM/ [2] http://nouveau.freedesktop.org/wiki/VideoAcceleration/ I need the original firmware from the binary driver in order to sucessully use DRM and to use VDPAU video acceleration. I used the python script from [2] and I had a look at the ebuild

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #44 from Ilia Mirkin <imirkin at alum.mit.edu> --- Try commenting the same line out and see what happens... (i.e. the one with 0x74c1) FWIW I do remember seeing some PCRYPT-related (and PVP/PBSP-related) errors on start in the form of MMIO write failures in your log and thinking it odd: nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000010 FAULT at 0x10200c Which of course is an enable of FIFO_ACCESS... probably pretty important. (See https://github.com/envytools/envytools/blob/mast...

...1:00.0] BIT signature found nouveau [ VBIOS][0000:01:00.0] version 60.86.49.00.27 (...) nouveau [ PMPEG][0000:01:00.0] hardware is marked as disabled nouveau [ PVP][0000:01:00.0] hardware is marked as disabled nouveau [ PCRYPT][0000:01:00.0] hardware is marked as disabled nouveau [ PBSP][0000:01:00.0] hardware is marked as disabled and also, everything is fine afterwards (as PCRYPT seems to indeed have been properly disabled). :-) What do you say? Do you agree that everything turned out as expected from my nvpeek results? Thanks & BR, Andreas -- You are receiving this mai...

...re if I have to set the parameter in quotes. > > No, you don't (and AFAIK, you even must not). Ilia has already proposed the > correct workaround for the distortion issue (until your distro of choice has > integrated the new fix) - add this: > > nouveau.config=PCRYPT=0,PVP=0,PBSP=0,PMPEG=0 > > to your grub kernel parameters. Having done so, all "MMIO write" errors in > dmesg must be gone (they are for me!), otherwise something else is still > wrong for you in addition. Ok, now after adding the whole bunch to the kernel opts the three PBUS errors are...

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #10 from Ilia Mirkin <imirkin at alum.mit.edu> --- Would you mind booting with nouveau.debug=PBSP=trace and putting up a dmesg from that (after the vdpauinfo, that is). BTW, silly question -- do you have a libvdpau_nouveau.so? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://li...

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #11 from Stefan Ringel <mail at stefanringel.de> --- (In reply to comment #10) > Would you mind booting with > > nouveau.debug=PBSP=trace > > and putting up a dmesg from that (after the vdpauinfo, that is). BTW, silly > question -- do you have a libvdpau_nouveau.so? yes I have libvdpau_nouveau.so. It is installed in /usr/lib64/vdpau . -- You are receiving this mail because: You are the assignee for the bug. -------...

...But I do > not see any dmesg output about loading the firmware. I do not see any dmesg > output about nouveau failing to do so either. I neither do no see any > "nouveau <pci id>: firmware: requesting nouveau/" in my kernel output. Try booting with nouveau.debug=PVP=debug,PBSP=debug,PPPP=debug Note the new-found kernel output. > > Anyway VDPAU seems to work. If I call mplayer with "-vo vdpau -vc > ffmpeg12vdpau,...", I don't get any error message and my CPU load drops from > 30% to 7% for a recent mpeg transport stream 1080p video. > > I...

...le version? > I was not sure if I have to set the parameter in quotes. No, you don't (and AFAIK, you even must not). Ilia has already proposed the correct workaround for the distortion issue (until your distro of choice has integrated the new fix) - add this: nouveau.config=PCRYPT=0,PVP=0,PBSP=0,PMPEG=0 to your grub kernel parameters. Having done so, all "MMIO write" errors in dmesg must be gone (they are for me!), otherwise something else is still wrong for you in addition. Hope this helps & best regards, Andreas BTW @ Ilia: Did you already have a chance to contact Ben...

On Mon, 4 Dec 2023 at 05:04, Paul Dufresne <dufresnep at zoho.com> wrote: > > In https://nouveau.freedesktop.org/KernelModuleParameters.html, there is: > Here is a list of engines: > DEVICE > DMAOBJ > PBSP > PCE0 > PCE1 > PCE2 > PCRYPT > PDISP > PFIFO > PGRAPH > PMPEG > PPM > PPPP > PVP > SW > Also, in debug: > CLIENT > > I have tried to find a description of those. > https://envytools.readthedocs.io...

https://bugs.freedesktop.org/show_bug.cgi?id=82835 Priority: medium Bug ID: 82835 Assignee: nouveau at lists.freedesktop.org Summary: GeForce 8800 GS VDPAU h264 decoding hang QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: randrik at mail.ru

https://bugs.freedesktop.org/show_bug.cgi?id=37922 Summary: NV86: too high power usage. Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: maximlevitsky

..., > { > struct nv84_bsp_priv *priv; > int ret; > + const struct firmware *fw; > + struct nouveau_device *device = nv_device(parent); > > ret = nouveau_engine_create(parent, engine, oclass, true, > "PBSP", "bsp", &priv); > @@ -78,16 +120,105 @@ nv84_bsp_ctor(struct nouveau_object *parent, struct nouveau_object *engine, > nv_subdev(priv)->unit = 0x04008000; > nv_engine(priv)->cclass = &nv84_bsp_cclass; > nv_engine(priv)->sclass = nv...

..., @@ -68,6 +108,8 @@ nv84_bsp_ctor(struct nouveau_object *parent, struct nouveau_object *engine, { struct nv84_bsp_priv *priv; int ret; + const struct firmware *fw; + struct nouveau_device *device = nv_device(parent); ret = nouveau_engine_create(parent, engine, oclass, true, "PBSP", "bsp", &priv); @@ -78,16 +120,105 @@ nv84_bsp_ctor(struct nouveau_object *parent, struct nouveau_object *engine, nv_subdev(priv)->unit = 0x04008000; nv_engine(priv)->cclass = &nv84_bsp_cclass; nv_engine(priv)->sclass = nv84_bsp_sclass; + + ret = request_firmw...