similar to: Direct Firmware load error

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

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

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

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

Hm, well you can see the messages about failure to set plls, which is why you don't see anything. The only odd thing I see is that you're using vesa, which can definitely mess things up. Try not using that. Also try booting with nouveau.debug=debug drm.debug=0xe which might provide more relevant info. On Jun 12, 2015 8:34 AM, "Andre Campos Rodovalho" <andre.rodovalho at

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[

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

dmesg output: --------------------------------------------------------------------------------------------------------- [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.16.0-38-generic (buildd at allspice) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #52~14.04.1-Ubuntu

flight 9061 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/9061/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-amd 5 xen-boot fail REGR. vs. 8995 Tests which are failing intermittently (not blocking): test-amd64-i386-pv 5 xen-boot fail pass in 9054 test-i386-i386-pv

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

https://bugs.freedesktop.org/show_bug.cgi?id=109681 Bug ID: 109681 Summary: Nvidia GT710 => nouveau + wayland + swayWM => crash when use acceleration (open Firefox) Product: Mesa Version: 18.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical

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

These chipsets include the VP2 engine which is composed of a bitstream processor (BSP) that decodes H.264 and a video processor (VP) which can do iDCT/mo-comp/etc for MPEG1/2, H.264, and VC-1. Both of these are driven by separate xtensa chips embedded in the hardware. This patch provides the mechanism to load the kernel for the xtensa chips and provide the necessary interactions to do the rest of

Hey I wanted to try my hand at doing some GPU passthrough so on my ASUS M5A97 which in the pass worked with an older BIOS (but said BIOS had issues after S3 suspend) - but with a BIOS the PCI passthrough does not work. That is due to:: (XEN) IVHD Error: Invalid IO-APIC 0xff (XEN) AMD-Vi: Error initialization

Hey, I have a nighly build/test system that boots various machines with upstream Linux and randomly selects Xen 4.1, Xen 4.2, Xen 4.3 and unstable. After a bit of digging I found out that Xen 4.2 ''xl'' (but not ''xm'') has some badness in it. When "migrating" (''xl'' save followed by ''xl'' restore'') the PVHVM

On Sun, Jul 22, 2012 at 03:34:42PM +0200, Ingo Molnar wrote: > Linus, > > Please pull the latest timers-core-for-linus git tree from: > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-core-for-linus > > HEAD: eec19d1a0d04c80e66eef634f7b8f460f2ca5643 Merge branch ''linus'' into timers/core > > Continued cleanups of the core

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 >