search for: nv130

Hello, Acceleration for Pascal cards is coming in Linux 4.12, support for Pascal cards in xorg-video-nouveau is in 1.0.15, and if I remember correctly, on the Mesa-side, you will need >=17.0. Pierre On 02:04 am - May 04 2017, Karl Schmidt wrote: > This is probably the problem > May 3 16:44:45 kernel: [ 7.068336] nouveau E[ DEVICE][0000:08:00.0] unknown chipset, 0x137000a1 > May

First things first -- I've alluded to this before, but let me be clear -- there is no global database that contains monitor-specific information which is used by any linux drivers. Please forget any notions you had of such a thing existing or being used. The information comes from the EDID blob supplied by the monitor. Presumably hwinfo has a primitive EDID parser, which is where that

On 05/06/2017 12:38 PM, Ilia Mirkin wrote: > The information comes from the EDID blob supplied by the monitor. > Presumably hwinfo has a primitive EDID parser, which is where that > information comes from. A more complete EDID parser is available at > > https://cgit.freedesktop.org/xorg/app/edid-decode/ > > For example, > > $ ./src/edid-decode/edid-decode

This is probably the problem May 3 16:44:45 kernel: [ 7.068336] nouveau E[ DEVICE][0000:08:00.0] unknown chipset, 0x137000a1 May 3 16:44:45 kernel: [ 7.068401] nouveau E[ DRM] failed to create 0x80000080, -22 May 3 16:44:45 kernel: [ 7.068723] nouveau: probe of 0000:08:00.0 failed with error -22 I can make this card available - if you can tell me an older card that can do the

This is sort of working -- but I can't get it to do a 4k output. Not sure how the monitor resolution is detected - This monitor is supposed to do 3480x1200 60hz 4:4:4 But the info I get from hwinfo is different. How does nouveau get this information? If it is from an ID - with a list - the list is probably is wrong. # hwinfo --monitor 95: None 00.1: 10002 LCD Monitor [Created at

On 05/04/2017 04:00 AM, Pierre Moreau wrote: > Hello, > > Acceleration for Pascal cards is coming in Linux 4.12, support for Pascal cards > in xorg-video-nouveau is in 1.0.15, and if I remember correctly, on the > Mesa-side, you will need >=17.0. Thanks - I suspected it was too new. I'm finding the monitor capabilities miss identified even if I use an older card - I'm

Hi, I am slightly stuck in a corner case I don't know how to debug. I have an optimus setup in a dell xps 9560 with a discrete gpu nvidia geforce 1050 (Pascal - NV130). I installed Fedora and if I do not boot with nouveau.modeset=0, then the computer crashes as soon as I try to start Xorg (I have disabled wayland). So, gdm starts but then as soon as I get into i3 or gnome, the computer crashes and hangs. How can I debug what's happening or generate enough...

...developer.nvidia.com/nvidia-video-codec-sdk#NVDECFeatures), we know Pascal cards support up to 8192*8192 resolution video decoding acceleration with HEVC codec. From Nouveau feature matrix ( https://nouveau.freedesktop.org/wiki/FeatureMatrix/), we know the progress of video decoding acceleration on NV130 family ( https://nouveau.freedesktop.org/wiki/CodeNames/#NV130) is TODO. In Nouveau VideoAcceleration page ( https://nouveau.freedesktop.org/wiki/VideoAcceleration/), we can see that each element in VP6+ row is TODO as well. I can imagine there is a long way to go to fulfill my requirements. But I...

...e parsed as hex when they include a leading 0x, + * octal when they include a leading 0, otherwise they are parsed as decimals. + * + * Supported key-value pairs include: + * + * * GP100MmuLayout (boolean): If false, the old pre-GP100 VMM backend is used; + * defaults to true and is only valid on NV130-NV138 chips. + * + * * <engine-name> (boolean): disable the given engine; all engines are enabled + * by default. + * + * * NvAcrWpr (integer): This configuration option is for debugging signed + * firmware blobs and is not for end users; defaults to -1 + * + * * NvAcrWprCompare (boolean)...

...e parsed as hex when they include a leading 0x, + * octal when they include a leading 0, otherwise they are parsed as decimals. + * + * Supported key-value pairs include: + * + * * GP100MmuLayout (boolean): If false, the old pre-GP100 VMM backend is used; + * defaults to true and is only valid on NV130-NV138 chips. + * + * * <engine-name> (boolean): disable the given engine; all engines are enabled + * by default. + * + * * NvAcrWpr (integer): ; defaults to -1 + * * NvAcrWprCompare (boolean): ; defaults to false. + * * NvAcrWprPrevAddr (integer): ; defaults to 0. + * + * * NvBar2Halve (bo...

...ude a leading 0x, > + * octal when they include a leading 0, otherwise they are parsed as decimals. > + * > + * Supported key-value pairs include: > + * > + * * GP100MmuLayout (boolean): If false, the old pre-GP100 VMM backend is used; > + * defaults to true and is only valid on NV130-NV138 chips. > + * > + * * <engine-name> (boolean): disable the given engine; all engines are enabled > + * by default. > + * > + * * NvAcrWpr (integer): ; defaults to -1 > + * * NvAcrWprCompare (boolean): ; defaults to false. > + * * NvAcrWprPrevAddr (integer): ; defau...