Might be the cause of bug 349655. Finally got around to doing something on an i915 atom machine and noticed that mesa now has appened the gallium name (g) to the drivers in /usr/lib64/mesa but the sym links in /usr/lib64/dri point to the classic named, ie no g. app-emulation/emul-linux-x86-opengl seems to be providing the links. In any case no GL support exists due to this. Reproducible: Always Steps to Reproduce: 1. emerge mesa 2. run glxinfo 3. run glxgears Actual Results: Both fail as xorg doensn't having an gl rendering capabilities Expected Results: both should work - did work when the sym link was changed
You probably should have used 'eselect mesa'.
Didn't and still doesn't work. Tried the --auto and that did bugger all. Tried setting the family option and decided after 3 attempts it was easier to simlink directly. But anyway, I decided I didn't want gallium as its not very good for the i915 according the distributed wisdom. > You probably should have used 'eselect mesa'. >
Do you mean this eselect mesa? tmp ~ # eselect mesa list i915 (Intel 915, 945) i965 (Intel 965, G/Q3x, G/Q4x) r300 (Radeon R300-R500) r600 (Radeon R600-R700, Evergreen) sw (Software renderer) tmp ~ # eselect mesa show tmp ~ # eselect mesa set --auto tmp ~ # eselect mesa show
what is the output of "emerge -pv mesa"?
I have just removed the gallium and added gles flag so currently it is: Calculating dependencies... done! [ebuild R ] media-libs/mesa-7.9-r1 USE="gles nptl -classic -debug -gallium* -llvm -motif -pic (-selinux)" VIDEO_CARDS="intel -mach64 -mga -nouveau -r128 -radeon -savage -sis -tdfx -via -vmware" 0 kB but it was as follows at the time of the "incident": Calculating dependencies... done! [ebuild R ] media-libs/mesa-7.9-r1 USE="gallium nptl -classic -debug -gles* -llvm -motif -pic (-selinux)" VIDEO_CARDS="intel -mach64 -mga -nouveau -r128 -radeon -savage -sis -tdfx -via -vmware" 0 kB
actually will go back to classic.
You disabled the classic driver. This you do at your own risk, especially as the intel gallium driver is not usable for anything.
Thanks, but all I wanted was to see the gles implementation. (I know about gallium, but what more interested in something to do with openGL ES). Thanks > You disabled the classic driver. This you do at your own risk, especially as > the intel gallium driver is not usable for anything. >
So, do I need a -gallium in the make.conf in order to get classic to work with intel? Has this changed recently? > Thanks, but all I wanted was to see the gles implementation. (I know about > gallium, but what more interested in something to do with openGL ES). Thanks > > You disabled the classic driver. This you do at your own risk, especially as > > the intel gallium driver is not usable for anything. > > >
No. If you build both classic and gallium drivers, then classic will be selected as default. However, if you disable classic, then gallium will be selected by default. This will not be reverted even if you additionally enable classic later. You have to switch back to classic i915/i965 manually with eselect mesa.
ok, thanks for clarifying that. > No. If you build both classic and gallium drivers, then classic will be > selected as default. > > However, if you disable classic, then gallium will be selected by default. This > will not be reverted even if you additionally enable classic later. You have to > switch back to classic i915/i965 manually with eselect mesa. >
