On Tue, 11 Nov 2014 12:27:33 -0500 mh <[email protected]> said:

> On 11/11/2014 12:15 PM, Carsten Haitzler wrote:
> > On Tue, 11 Nov 2014 10:46:47 -0500 mh <[email protected]> said:
> >
> >> On 11/11/2014 09:28 AM, Carsten Haitzler wrote:
> >>> On Tue, 11 Nov 2014 08:39:36 -0500 mh <[email protected]> said:
> >>>
> >>>> I continue to see the Compositor Warning, "Your display driver does not
> >>>> support OpenGL, GLSL shaders or not OpenGL engines were compiled or
> >>>> installed for Evas or Ecore-Evas..." when I start enlightenment.
> >>>>
> >>>> I have EFL 1.12,  evas generic player 1.12, emotion 1.12, enlightenment
> >>>> 0.19.1 installed. System is Debian sid using nvidia-driver v. 340.46-4.
> >>>> If I remove nvidia packages and use nouveau I do not see this warning.
> >>>>
> >>>> I created a ticket, T1817, on phabricator. I thought this problem was
> >>>> previously corrected, but I am still seeing it.
> >>> i have nvidia drivers (not nouveau) at home and i dont see it. i have no
> >>> idea what is wrong with your machine. nvidia 343.22 drivers on arch.
> >>> everything is fine and dandy.
> >>>
> >>> some things to try:
> >>>
> >>>     rm -rf ~/.cache/evas*
> >>>
> >>> maybe:
> >>>
> >>>     export EINA_LOG_LEVEL=4
> >>>     export ELM_ACCEL=gl
> >>>     export EVAS_GL_INFO=1
> >>>     elementary_test >& log
> >>>
> >>> share that log file
> >>
> >> deleted the evas cache file, still same warning. exported the variables
> >> and started elementary_test. it started fine, but no output to the log
> >> file. should there be something?
> > zero output to log file? i don't believe that. the eina log level env var
> > should have turned on tonnes of debugging even in basic init of efl like
> > loading module lists, initting mempools, adding eina prefix and then in eo
> > as well etc. unless a release builg turns off all DBG macros... the evas gl
> > info env var would dump gl info out on init... but it'd need to succeed. at
> > least a build from it gets ou a massive file
> >
> 
> oops, sorry. found my mistake. I posted the log contents here: 
> http://pastebin.com/AAgEzMJ7

ooooh. you compiled for egl/gles not opengl/glx. i can only guess hat the
nvidia drivers have a problem with this for you - you can something wrong with
them. nvidia ADDED egl/gles libs/drivers recently. they work for me for apps
when i was fixing some context/visual stuff 2 weeks back. i build for egl/gles
as well as opengl/glx on nvidia - ut my drivers were newer than yours. why are
you building for gles? (efl here). but thats a major difference. i know 100%
for sure that the mesa drivers work with gles/egl and enlightenment and
compositing is fine, but i didnt test nvidia at the time, but clients do work
there on newer nvidia drivers.

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    [email protected]


------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to