[Jeff]

Are you using the 2.6.39 kernel with any of those? Also what X server version?

~Jeff

[jimf]

Jeff,
Debian sid kernel is 2.6.39
xserver-xorg is 1.10

ubuntu 10.10
kernel 2.6.35
xserver xorg is 1.9.0

ubuntu 11.04
kernel 2.6.38
xserver-xorg 1.10

I think that mesa is the problem based
on Raster's comment concerning GLSL.
I know nothing about shaders but
this is implemented in mesa?

JimF

[Jeff]

I *think* it is in th mesa, but not 100% on that.

~Jeff

[jimf]

Jeff,
I was going to try and
locally build mesa 7.9
from ubuntu maverick.
Unfortunately the bodhi libxcb-dev
packages for 1.6 don't seem to be available.
So I can't help any further.

JimF

[jimf]

Jeff,
I decided to rebuild needed packages
to use mesa 7.9 from maverick
on one of my Bodhi installations.
I encountered some problems with
libdrm-dev and might not get back to this
for a few day's.
JimF

[Jeff]

Busy the next couple days but will look into those issues as soon as possible. Thanks for th debugging help thus far.

~Jeff

[mech]

Don't know if this might help track the problem but I found this after 1.1.0 failed the live session at the choose profile screen on my laptop with intel gma x3100 graphics. Yes, I checked the md5 and verified the burn.

My link

[jimf]

Jeff,
I will also have to wait for the weekend
for further updates. Mesa build keeps
failing for nouveau dri drivers.
It seems these drivers are real moving
targets with many issues getting them
to build.
JimF

[jimf]

Jeff,
I actually got mesa 7.10 from natty to build
and install. No joy though, glxgears runs
but E17 blanks the screen every second or so,
not very usable. Perhaps upgrading mesa
means rebuilding E17.
JimF

[jimf]

Jeff,
I can't do much more for this issue
without breaking my installation.
I have mixed various packages from
maverick and natty to get the latest
mesa packages installed. Then rebuilt
evas opengl module to see if that would help
but desktop just keeps flickering when
opengl engine is enabled. Hope you find
a solution.
JimF

[Jeff]

Yea... After rebuilding evas you need to rebuild ALL of E along with the updated packages.

~Jeff

[jimf]

Jeff,
It might be easier to base a later release
on ubuntu 11.04. I was very suprised that
pulling the source from natty for mesa
does not even build cleanly. Simple apt-get source mesa and
dpkg-buildpackage fails miserably with many include
directives missing from the nouveau driver source that
the debian and ubuntu patches do not correct. I
don't understand at this point how the package
maintainer's were getting them to build. I guess
it's a matter of how important the opengl module
is to your users. I have been using e17 for quite
so time and must admit I had never turned opengl
backend on until I read this forum, so for me
it is not that important. I guess though if
you tell peaple that an option exists you have to make it work.
JimF

[Jeff]

Intel just needs better driver reallys - it works 100 percent fine with current nvidia drivers. Plus compositing works just fine with the software engine if people really want it (but like you said - its not needed really).

We will not base off of non-LTS releases. 18 months is far too short of a life span. I will be playing around with newer mesa builds and E in the testing repo later this week.

~Jeff

[jimf]

Jeff,
I decided to do a fresh install
of lubuntu 10.04 to see if this could
be solved easily.
I update only drm2 and mesa from
maverick 10.10 these install from
packages no rebuilding needed.
Built e from svn turned on
composite chose opengl engine
and no warning message.
This seems to be a easy solution.
JimF

[jimf]

Jeff,
These are specific packages
from maverick :
libdrm2_2.4.21-1ubuntu2_i386.deb
libdrm-dev_2.4.21-1ubuntu2_i386.deb
libdrm-intel1_2.4.21-1ubuntu2_i386 (1).deb
libdrm-intel1_2.4.21-1ubuntu2_i386.deb
libdrm-nouveau1_2.4.21-1ubuntu2_i386.deb
libdrm-radeon1_2.4.21-1ubuntu2_i386.deb
libkms1_2.4.21-1ubuntu2_i386.deb
libgl1-mesa-dev_7.9~git20100924-0ubuntu2_i386.deb
libgl1-mesa-dri_7.9~git20100924-0ubuntu2_i386.deb
libgl1-mesa-glx_7.9~git20100924-0ubuntu2_i386.deb
libglu1-mesa_7.9~git20100924-0ubuntu2_i386.deb
libglu1-mesa-dev_7.9~git20100924-0ubuntu2_i386.deb
mesa-common-dev_7.9~git20100924-0ubuntu2_i386.deb
JimF

[jimf]

Note to Bodhi users,
This will not work on
installed systems.
E and efl need to be
rebuilt.
JimF

[jimf]

jimf, on 07 June 2011 - 11:21 AM, said:

Jeff,
These are specific packages
from maverick :
libdrm2_2.4.21-1ubuntu2_i386.deb
libdrm-dev_2.4.21-1ubuntu2_i386.deb
libdrm-intel1_2.4.21-1ubuntu2_i386 (1).deb
libdrm-intel1_2.4.21-1ubuntu2_i386.deb
libdrm-nouveau1_2.4.21-1ubuntu2_i386.deb
libdrm-radeon1_2.4.21-1ubuntu2_i386.deb
libkms1_2.4.21-1ubuntu2_i386.deb
libgl1-mesa-dev_7.9~git20100924-0ubuntu2_i386.deb
libgl1-mesa-dri_7.9~git20100924-0ubuntu2_i386.deb
libgl1-mesa-glx_7.9~git20100924-0ubuntu2_i386.deb
libglu1-mesa_7.9~git20100924-0ubuntu2_i386.deb
libglu1-mesa-dev_7.9~git20100924-0ubuntu2_i386.deb
mesa-common-dev_7.9~git20100924-0ubuntu2_i386.deb
JimF

I decided to ignore my own advice
and installed libgl1-mesa-dri_7.9, libgl1-mesa-glx_7.9
and libglu1-mesa_7.9 from maverick using gdebi on
two bodhi installations. One with enlightenment from 5/23
the other with enlightenment from testing (6/7?).
In both cases the compositor warning is gone.
JimF

[Jeff]

Can you link to the .deb downloads all that you used? I'd like to get them into the test repo and then the main repo if all goes well. Thanks for your searching on this issue!

~Jeff

[jimf]

Jeff, on 09 June 2011 - 03:02 PM, said:

Can you link to the .deb downloads all that you used? I'd like to get them into the test repo and then the main repo if all goes well. Thanks for your searching on this issue!

~Jeff

Jeff,

Mesa-glx
Glu-mesa
Mesa-dri

JimF

[Dick]

I've followed this discussion (from a distance) with interest. I'm also experiencing the OpenGL warning. I'm not sure whether it will make a big difference on my netbook but it's nice to see that all the work what JimF has done (a big thanks to you!) is being picked up by Jeff.
It's nice to see how these thing develop and eventually will make a difference for some (maybe a lot) Bodhi users.

So, thank you both for your efforts!