similar to: [Bug 66809] Compiz segfault with latest mesa-git

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

https://bugs.freedesktop.org/show_bug.cgi?id=66809 Marek Ol??k <maraeo at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mesa-dev at lists.freedesktop. |nouveau at lists.freedesktop.o |org |rg Component|Mesa core

https://bugs.freedesktop.org/show_bug.cgi?id=66809 --- Comment #6 from Roy <r.spliet at student.tudelft.nl> --- Eric: Could you install the debugging symbols (or, if you compiled it yourself, recompile with "-g" in your CFLAGS) for nouveau_dri and libdrm_nouveau please and reproduce your crash, regenerating this backtrace? I think it would be useful to see which function is trying

Hi David, With the recent opcode changes, does compiz need anything in order to use the newer X server? I updated glproto to 1.4.8, then built Mesa 6.5.1 release, then compiled Xserver from git then built compiz git and I get a white screen, but compiz cube shows all white/shaded when I attempt to drag the cube around. I have AIGLX used instead of Xgl. I'm testing out Xorg '7.2'

I have the same problem. I wrote this already here. I mean this problem is cause how is implemetated GL_texture_from_pixmap in new xserver, glproto and mesa and compiz is not ready yet.

Hello, I decided to try nouveau tonight and I followed the install instructions. 2D worked fine (a bit slower than nv/vesa), so I tried out 3D. I was able to get glxgears to work (1000 fps on my nv15) only after I patched the mesa driver. Attached is the patch to nouveau_screen.c that adds a stub to resolve the undefined symbol that all GL programs threw. I discussed it briefly with herve

Looks fine, except that you will need to lower FILE_SHADER_INPUT to FILE_MEMORY_SHARED for Tesla because input kernel parameters are located at s[0x10]. No need to do this for Fermi+ because it's already lowered to c0[]. Note that input kernel parameters will be probably sticked on c7[] after my changes but that doesn't change anything for you. I already have a patch for the nv50 bits

On Mon, May 19, 2014 at 12:16 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> > --- > src/gallium/drivers/nouveau/nvc0/nvc0_video.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/src/gallium/drivers/nouveau/nvc0/nvc0_video.c b/src/gallium/drivers/nouveau/nvc0/nvc0_video.c > index 5871f59..c9ab13a

Any one which, after using a geometry shader, enables an extra clip distance. i.e. none. On Mon, Jul 13, 2015 at 4:16 AM, Samuel Pitoiset <samuel.pitoiset at gmail.com> wrote: > What piglit test does this fix? > > On Sat, Jul 11, 2015 at 7:13 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> >> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> >>

Hello, I'm new to the list but I've been following it since its inception. First of all sorry for the length of this post, if you're not a Fedora user just skip it. I've been building Compiz packages since Fedora Core 5 came out (Xgl only) and updating since then with all the new stuff, AIGLX and whatever. I use them on a very large range of hardware. Attached are my source rpm

Thanks, Marek. Could someone with commit access pick this up? Let me know if you'd like me to reformat/resend/create a git tree/whatever. -ilia On Sun, Oct 13, 2013 at 9:16 AM, Marek Ol??k <maraeo at gmail.com> wrote: > For the series: > > Reviewed-by: Marek Ol??k <marek.olsak at amd.com> > > Marek > > On Sun, Oct 13, 2013 at 3:43 AM, Ilia Mirkin

Trying to run compiz on xorg-7.1 (aiglx), but getting the message: compiz: Root visual is not a double buffered GL visual compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 I'm on GNU/Linux with kernel 2.6.18 using DRI on ATI Radeon 9250 (rv280). I have mesa-6.5. Direct rendering is working fine. I've seen numerous people mention this problem, but

https://bugs.freedesktop.org/show_bug.cgi?id=106294 Bug ID: 106294 Summary: GM204/modesetting DDX: Odd corruption (red backgrounds) introduced by Mesa Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

Extend the MEMORY file support to differentiate between global, private and shared memory, as well as "input" memory. "MEMORY[x], INPUT" is intended to access OpenCL kernel parameters, a special memory type is added for this, since the actual storage of these (e.g. UBO-s) may differ per implementation. The uploading of kernel parameters is handled by launch_grid,

If a transform feedback buffer's size is 0, st_bufferobj_data doesn't end up creating a buffer for it. There's no point in trying to write to such a buffer, so just pretend as if it's not really there. This fixes arb_gpu_shader5-xfb-streams-without-invocations on nvc0. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/mesa/state_tracker/st_cb_xformfb.c | 2 +- 1

On Sat, Jan 5, 2019 at 2:40 PM Ilia Mirkin <imirkin at alum.mit.edu> wrote: > It looks like as of Chromium 71, nouveau is completely blacklisted. > That's rather unfortunate. :-( The intel mesa drivers were also blacklisted for quite some time a while back. I'm not really sure what we did to get blacklisted or what we did to get unblacklisted. > I don't really see

On Wed, May 21, 2014 at 2:57 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote: > On 21/05/14 00:39, Ilia Mirkin wrote: >> From: Christoph Bumiller <e0425955 at student.tuwien.ac.at> >> >> [imirkin: add logic to also clear the "regular" scissors] > Can you please share why are you've added the "regular" scissors ? Because I had to

On Fri, Apr 22, 2016 at 9:23 AM, Hans de Goede <hdegoede at redhat.com> wrote: > Hi, > > On 22-04-16 09:08, Marek Olšák wrote: >> >> On Thu, Apr 21, 2016 at 7:04 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >>> >>> [+radeon folk] >>> >>> Marek, Nicolai, Bas - please have a look at the doc change and let us >>> know

Hi Since a few days compiz fails to start on my system. It bails out with the message: compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 I'm using Ubuntu Edgy with the beta nvidia drivers and a recent git checkout of compiz. I read somewhere, that this error could be related to mesa

https://bugs.freedesktop.org/show_bug.cgi?id=28017 Summary: Compiz segfaults, backtrace log and patch included Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at