• State Accepted Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 136 subscribers
  • Views 9532 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Help fix : Graphics and Compute Development on Samsung Chromebook

Sean

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

Parents
  • 0 in reply to Chris Varnsverry

    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:

    • for fbdev - ask the reader to run the cube in the SDK
    • for x11 - I'm not sure - do you provide an X11 example?  If not, find one.  I uses es2_info, but something graphical would be more approriate. I tried es2gears but had issues I haven't looked into.
Reply
  • 0 in reply to Chris Varnsverry

    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:

    • for fbdev - ask the reader to run the cube in the SDK
    • for x11 - I'm not sure - do you provide an X11 example?  If not, find one.  I uses es2_info, but something graphical would be more approriate. I tried es2gears but had issues I haven't looked into.
Children
No data