I was looking for a way to install Linux with Mali GPU support on my Samsung chromebook, so I was excited to find the guide at : http://malideveloper.arm.com/develop-for-mali/features/graphics-and-compute-development-on-samsung-chromebook/
However, I've followed the above guide (twice) and I'm es2_info reports the Software Rasterizer. I expected it to report a MALI rasterizer. Is this guide correct or did I do something wrong (twice)?
Can you help me figure out what is going wrong?
es2_info
es2_info reports (full log here: Ubuntu Pastebin)
libEGL warning: failed to create a pipe screen for armsoc
libEGL warning: DRI2: failed to open armsoc (search paths /usr/lib/arm-linux-gnueabihf/dri)
I then tried copying armsoc_drv.so to that directory, but still got the same error
X Log info:
X reports and opens Mali-T6XX but AIGLX does report the following (full log here: Ubuntu Pastebin)
AIGLX: reverting to software rendering
I don't know if this revert applies to everything in OpenGL or just the GLX part
I think the guide would be helpful if it added a section on installing and running a test program (such as es2_info) to ensure the install was successful. Also a test program that used the fbdev would also be helpful to me.
Message was edited by: Sean
Hi spanyo,
Did you by any chance install the MESA libraries on the target after installation? These conflict with the ARM GLES libraries and will override them. Like chrs says, what is the output of "ldd es2_info"? This will tell us more.
Also a test program that used the fbdev would also be helpful to me.
For this purpose you could download the Mali GLES SDK from the Mali Developer Center, and build the examples on the target.
Thanks,
Chris
Thanks chrs and Chris,
I couldn't follow the ldd steps because my sdcard got corrupted. So I rebuilt the image.
As I about to apt-get install es2_info by installing the mesa-utils-extra package I noticed it was going to install some mesa libs. Per your warning about mesa, I decided to build es2_info from source instead using the GLES SDK header and libraries.
Now when I run es2_info in X I get: GL_RENDERER: Mali-T604.
Glad that was the only issue. You're not the only one to run into this issue however. We're open to suggestions if anyone knows something we could do better to avoid this situation in the future?
For me, the smallest change with the biggest impact would be to add a paragraph to each of the fbdev and x11 sections that identifies a specific test to run to confirm that the setup is correct.
for example: