> On 28 Feb 2017, at 14:58, Emil Velikov <emil.l.veli...@gmail.com> wrote: > > On 28 February 2017 at 12:09, Boyan Ding <boyan.j.d...@gmail.com > <mailto:boyan.j.d...@gmail.com>> wrote: >> 2017-02-28 18:55 GMT+08:00 Christophe de Dinechin <dinec...@redhat.com>: >>> Newbie question… >>> >>> I’ve been investigating a regression in Fedora 25 between mesa-dri-drivers >>> versions 12.0.3 and 13.0.3 >>> (https://bugzilla.redhat.com/show_bug.cgi?id=1426549). >>> >>> The output with the Fedora version of Mesa is: >>> >>> GL_RENDERER = Gallium 0.4 on virgl >>> >>> So virgl is enabled and working in this VM. >>> >>> When I build Mesa from sources, and configure it with >>> “—with-galium-drivers=virtgl”, I get this from glxgears -info: >> >> Should be 'virgl' instead of 'virtgl' >> > Hmm not sure about that — [should be --] it errors out in here. The > major things is the missing second L in galLium -> > --with-gallium-drivers. > If the latter is correct we have a nice error message at configure ;-)
Indeed, the typo is in the e-mail, not the command line. For some reason, copy-paste stopped working and I just re-typed it in e-mail, with two typos. Sorry. I just checked. If you mistype “virtgl” instead of “virgl”, you get a configure error “Unknown Gallium driver: virtgl”. If you type galium instead of gallium, you get a warning early on. That one is probably harder to see, because it is scrolled off-screen pretty rapidly. But it’s unmissable if you watch the screen. In any case, I don’t think that’s the problem, I checked in my config.log that things were OK. > >> Also, you can see fedora's configure parameters at >> https://src.fedoraproject.org/cgit/rpms/mesa.git/tree/mesa.spec#n399 >> <https://src.fedoraproject.org/cgit/rpms/mesa.git/tree/mesa.spec#n399> >> > Tl;Dr: If you are not too sure just copy the lot (literally) from your > distro ;-) Thanks. There are a few options I did not try. My vote goes for —enable-selinux. Unfortunately, I just had a disk loss on the machine where I was testing this, so I will need a bit of time to re-try on a different machine. That being said, my question really was: is there some logging regarding which driver is being selected. Looking at the source code, I don’t see any. I think that would be useful information to add to LIBGL_DEBUG=verbose output. I'll add some instrumentation to understand what is going on, and I’ll submit a patch with whatever proves useful to understand my issue. Christophe > > -Emil > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org <mailto:mesa-dev@lists.freedesktop.org> > https://lists.freedesktop.org/mailman/listinfo/mesa-dev > <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
