From: José R. M. <j.r...@gm...> - 2012-10-12 04:17:23
|
On Fri, Oct 12, 2012 at 11:39:45AM +0900, Carsten Haitzler wrote: > On Thu, 11 Oct 2012 18:03:13 -0300 José Romildo Malaquias <j.r...@gm...> > said: > > > On Fri, Oct 12, 2012 at 12:00:58AM +0900, Carsten Haitzler wrote: > > > On Thu, 11 Oct 2012 10:02:18 -0300 José Romildo Malaquias > > > <j.r...@gm...> said: > > > > > > > I am experimenting E17 on my notebook running gentoo linux. I am using > > > > the official enlightenment overlay to install E17. > > > > > > > > There are two graphic devices on my sytem: nvidia (optimus) and intel > > > > integrated. As there is not easy support for nvidia optimus on linux, > > > > the nvidia device is not used. > > > > > > > > When running E17 for the first time and choosing "Hardware Accelerated > > > > (OpengGL)" for the "Compositing" configuration dialog that is presented > > > > before the desktop is launched, I get a non-functional system: the > > > > screen becomes black and the only visible thing is a mouse pointer. > > > > > > > > If the option "Hardware Accelerated (OpenGL)" is disabled, it works. > > > > > > > > I remember that some months ago when I have also tried E17, it worked > > > > with OpenGL and the intel graphics card. > > > > > > > > Any clues? > > > > > > intel gfx works just fine here. i'm sitting on a sandybridge laptop. it also > > > works just fine on my i7 sandybridge desktop. no optimus there. i suspect > > > its an issue with drivers and maybe evas is at runtime linking to nvidia > > > driver blobs and thus having problems as maybe the nvidia drivers detect > > > the gpu and kind-of-work BUt don't actually manage to display. i suggest > > > double-checking how many libGL's you have and where they ere etc. (or > > > libGLESv2's and libEGL's) :) > > > > nvidia driver is not even installed on my system. Only > > xf86-video-intel-2.20.9 is installed. > > > > I have the following libraries installed on my system: > > > > app-emulation/emul-linux-x86-opengl-20120520 (/usr/lib32/libEGL.so -> > > libEGL.so.1) app-emulation/emul-linux-x86-opengl-20120520 > > (/usr/lib32/libGLESv2.so.2.0.0) app-emulation/emul-linux-x86-opengl-20120520 > > (/usr/lib32/libEGL.so.1.0) app-emulation/emul-linux-x86-opengl-20120520 > > (/usr/lib32/opengl/xorg-x11/lib/libGL.so -> libGL.so.1) > > app-emulation/emul-linux-x86-opengl-20120520 > > (/usr/lib32/opengl/xorg-x11/lib/libGL.so.1.2) > > app-emulation/emul-linux-x86-opengl-20120520 (/usr/lib32/libGLESv2.so -> > > libGLESv2.so.2) media-libs/mesa-9.0 > > (/usr/lib64/opengl/xorg-x11/lib/libGL.so.1.2.0) media-libs/mesa-9.0 > > (/usr/lib64/opengl/xorg-x11/lib/libEGL.so -> libEGL.so.1.0.0) > > media-libs/mesa-9.0 (/usr/lib64/opengl/xorg-x11/lib/libEGL.so.1.0.0) > > media-libs/mesa-9.0 (/usr/lib64/opengl/xorg-x11/lib/libGL.so -> > > libGL.so.1.2.0) > > i see both EGL/GLES libs AND GL (desktop gl). at least in the past gles/egl vs > gl has been flakey and you should not have stuck to gl. mix and match has been > problematic. evas may have detected gles/egl and built that support. > double-check on that. fyi egl/gels works fine even mixed with gl(x) on my i7 > desktop so at least on some latest master git src of mesa/intel drver it does > work. evas was compiled without gles support, as can be seen in the output of its configure script: [...] ------------------------------------------------------------------------ evas 1.7.99.77860 ------------------------------------------------------------------------ Configuration Options Summary: Engines: Software Memory Buffer.....: yes Software X11...............: yes (Xlib: yes) (XCB: no) OpenGL X11.................: yes (Xlib: yes) (XCB: no) (GLES: no) Software GDI...............: no Software DirectDraw........: no Direct3d...................: no OpenGL SDL.................: no OpenGL Cocoa...............: no Software Framebuffer.......: no DirectFB...................: no PSL1GHT....................: no Software 8bit grayscale....: no Wayland Shm................: no Wayland Egl................: no [...] Recompiling evas and mesa with support for gles (by setting the gles use flag in gentoo) fixes the issue I am having with the intel graphics on my system. With that explicitly set, the evas configure script reports: [...] ------------------------------------------------------------------------ evas 1.7.99.77927 ------------------------------------------------------------------------ Configuration Options Summary: Engines: Software Memory Buffer.....: yes Software X11...............: yes (Xlib: yes) (XCB: no) OpenGL X11.................: yes (Xlib: yes) (XCB: no) (GLES: yes) Software GDI...............: no Software DirectDraw........: no Direct3d...................: no OpenGL SDL.................: no OpenGL Cocoa...............: no Software Framebuffer.......: no DirectFB...................: no PSL1GHT....................: no Software 8bit grayscale....: no Wayland Shm................: no Wayland Egl................: no [...] I do not know much about gl and gles, but it seems that something should be done to make E17 work out of the box for intel graphics on gentoo linux. Maybe the experts could take a closer look at it. []s Romildo |