similar to: [Bug 77102] gallium nouveau has no profile in vdpau and libva

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

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

https://bugs.freedesktop.org/show_bug.cgi?id=77102 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mesa-dev at lists.freedesktop. |nouveau at lists.freedesktop.o |org |rg Component|Other

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #7 from Stefan Ringel <mail at stefanringel.de> --- Created attachment 96999 --> https://bugs.freedesktop.org/attachment.cgi?id=96999&action=edit ls -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #8 from Ilia Mirkin <imirkin at alum.mit.edu> --- OK, so it seems like the firmware is correctly in place, and there are no errors coming from dmesg, which means it's getting loaded (or at least isn't failing to load). What version of Mesa are you using? I recently added a feature which auto-detects if firmware is

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #9 from Stefan Ringel <mail at stefanringel.de> --- (In reply to comment #8) > OK, so it seems like the firmware is correctly in place, and there are no > errors coming from dmesg, which means it's getting loaded (or at least isn't > failing to load). > > What version of Mesa are you using? I recently

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #12 from Stefan Ringel <mail at stefanringel.de> --- Created attachment 97000 --> https://bugs.freedesktop.org/attachment.cgi?id=97000&action=edit dmesg -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #13 from Ilia Mirkin <imirkin at alum.mit.edu> --- Created attachment 97009 --> https://bugs.freedesktop.org/attachment.cgi?id=97009&action=edit firmware present patch OK, upon further code reading, it looks like the way nouveau does class id's is a bit off. That doesn't strictly matter for BSP, but there's

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #14 from Stefan Ringel <mail at stefanringel.de> --- (In reply to comment #13) > Created attachment 97009 [details] [review] > firmware present patch > > OK, upon further code reading, it looks like the way nouveau does class id's > is a bit off. That doesn't strictly matter for BSP, but there's a

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #15 from Stefan Ringel <mail at stefanringel.de> --- Created attachment 97014 --> https://bugs.freedesktop.org/attachment.cgi?id=97014&action=edit correct profile in vdpauinfo + vainfo -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment

https://bugs.freedesktop.org/show_bug.cgi?id=77102 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #17 from Ilia Mirkin <imirkin at

Hi Folks Getting a considerable number of these showing up at the moment [ 619.350185] nouveau 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[

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #81 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #80) > Hello, > > I have the same NVIDIA GeForce NVS 130M with the disabled functions. > I checked with nvapeek: > 0000154c: 0000009c > 00001540: b1010001 > > uname -a delivers > Linux mobuntu 3.11.0-15-generic #23-Ubuntu SMP Mon

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

For NV98+, BSP/VP/PPP are all FUC-based engines. Hook them all up in the same way as NVC0, but with a couple of different values. Also make sure that the PPP engine is handled in the fifo/mc/vm. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- It seems like VP4.0 is basically working here... only mpeg2/vc1 work, but I'm pretty sure that's just a user-side issue. My guess is

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

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

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #77 from Andreas Loew <awl1 at gmx.net> --- Sorry that it took me longer to get back here - I needed an additional rpmbuild run due to running out of disk space for my first attempt... But I can give an all clear signal - at least for my machine, AFAIK, everything seems to be fine: Kernel command line: ro

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #85 from Thomas <tomshere at t-online.de> --- (In reply to comment #82) > > I also have these errors in dmesg > > > > [ 18.985158] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000000 > > FAULT at 0x00fd94 > > [ 18.986213] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000000 >

On Thu, Dec 12, 2013 at 2:32 AM, Matthias Nagel <matthias.h.nagel at gmail.com> wrote: > 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