similar to: "unknown fragment shader param 17" error on NV46 when running glxgears

Add missing PIPE_SHADER_CAP_INTEGERS for frag shaders to nv30_screen_get_shader_param(). Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- src/gallium/drivers/nouveau/nv30/nv30_screen.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_screen.c b/src/gallium/drivers/nouveau/nv30/nv30_screen.c index db7c2d1..ece8af7 100644 ---

Hi, On 24-07-15 04:32, Ben Skeggs wrote: > On 24 July 2015 at 01:20, Hans de Goede <hdegoede at redhat.com> wrote: >> MSI interrupts appear to not work for nv46 based cards. Change the mc >> subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is >> identical to the nv44 mc code except that it does not use msi >> (it does not define a msi_rearm

Hi All, So I've been working~w banging my head against the nv46 vblank bug again and I've been finding out some interesting things. This is all using the latest kernel + ddx + mesa code. All of this was tested with *cold* (power removed from wall outlet for 20 seconds) boots in between the scenarios because this is really weird, all boots where into text mode. Scenario 1: a) startx

https://bugs.freedesktop.org/show_bug.cgi?id=69952 Priority: medium Bug ID: 69952 Assignee: nouveau at lists.freedesktop.org Summary: [NVAA] Xorg crash+restart after glxgears on 3.12-rc2 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter:

MSI interrupts appear to not work for nv46 based cards. Change the mc subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is identical to the nv44 mc code except that it does not use msi (it does not define a msi_rearm callback). BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=90435 Signed-off-by: Hans de Goede <hdegoede at redhat.com> ---

https://bugs.freedesktop.org/show_bug.cgi?id=53219 Bug #: 53219 Summary: glxgears crashes kernel Classification: Unclassified Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=33999 Summary: 2.6.37 - NV11 crashes X if glxgears maximised Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=73445 Priority: medium Bug ID: 73445 Assignee: nouveau at lists.freedesktop.org Summary: [NV4E] regression with 3.13 -rcX: glxgears etc. hard lockup/freezes machine, on 3.12 everything works Severity: critical Classification: Unclassified OS: Linux (All)

https://bugs.freedesktop.org/show_bug.cgi?id=107735 Bug ID: 107735 Summary: Xorg stops responding when running DRI_PRIME=1 glxgears Product: Mesa Version: 18.1 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

http://bugs.freedesktop.org/show_bug.cgi?id=10920 Summary: glxgears on AGP 10de0028 NV5 [RIVA TNT2/TNT2 Pro] works! (but slowly) Product: xorg Version: 7.2 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

http://bugs.freedesktop.org/show_bug.cgi?id=10858 Summary: glxgears with mesa-git on PCI 10de0322 (NV34) GeForce FX 5200 crashes X Product: xorg Version: 7.2 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Listmates, No response from the suse list, so I am trying here. I bought a new HIS Radeon x1650 card for my daughter's computer, and I cannot get the card to work with compiz. I thought I knew the fglrx driver pretty well, but I am stumped here. The card has 512M of Ram and sits in the AGP slot of an MSI KM2M board running openSuSE 11.0/KDE 3.59 and compiz-0.7.6-16.1. All bios setting are

https://bugs.freedesktop.org/show_bug.cgi?id=102860 Bug ID: 102860 Summary: Nvidia 940MX (NV118, GM108) is reported as a NV117, GM107 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: minor Priority: medium Component:

Hi Ben, Karol and Tom are seeing this on init with a nvif-enabled kernel + libdrm. What are we doing wrong? I think that route == NVIF_IOCTL_V0_ROUTE_NVIF (== 0), while owner is apparently 1, whatever that is. [362619.242238] nouveau: glxgears[6096]:00000000:00000000: ioctl: size 32 [362619.242240] nouveau: glxgears[6096]:00000000:00000000: ioctl: vers 0 type 00 object 0000000000000000 owner 00

https://bugs.freedesktop.org/show_bug.cgi?id=95095 Bug ID: 95095 Summary: NV46 (G72) Full screen artifacts in Freespace 2 SW OT mod Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

http://bugs.freedesktop.org/show_bug.cgi?id=11038 Summary: nouveau and NV17: glxinfo, glxgears and other gl-apps crash Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:

Hello there, With the use of CUDA and ptx I managed to make a disassembler for at least one of the nv50 microcode/shader formats. This might come in handy for some people, hence I'm posting it here: http://www.cs.rug.nl/~wladimir/decuda/ I'm not yet sure if pixel/vertex shaders use the same instruction format as the compute shaders used by CUDA, but you'd think so, as nv50 is

Hi, As I'm looking to add some support to nouveau for features like atomic counters and images, I'm running into some confusion about what the first word of the shader header means. Here is the definition as we have it today: https://github.com/envytools/envytools/blob/master/rnndb/graph/gf100_shaders.xml VS/HS/DS/GS: <reg32 offset="0" name="0"> <bitfield

On Thu, May 21, 2015 at 10:05 AM, Robert Morell <rmorell at nvidia.com> wrote: > Hi Ilia, > > On Sat, May 02, 2015 at 12:34:21PM -0400, Ilia Mirkin wrote: >> Hi, >> >> As I'm looking to add some support to nouveau for features like atomic >> counters and images, I'm running into some confusion about what the >> first word of the shader header

I have an Intel GMA 950 and I installed Sims 3 on vista. It works but crash after 10 min. I reinstalled Sims 3 on Ubuntu 9.04 with playonlinux script. Install works fine but when I start the game, I have this error : " impossible de d?marrer le jeu. L'appareil 0 ne peut pas ex?cuter ce titre. Votre carte vid?o ne semble pas prendre en charge Shader Model version 2 ou ult?rieure.