Comment 7 for bug 1085596

Rune K. Svendsen (runeks) wrote :

To get back on topic, I'm experiencing the same issues as you, Andrew. Here's some hopefully relevant output from Xorg.0.log:

 OMAP5432 with PowerVR SGX544 MP, Mali-T60x
[ 545.869] (++) using VT number 7

[ 545.869] (WW) Falling back to old probe method for armsoc
[ 545.869] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 545.870] (II) ARMSOC(0): Creating default Display subsection in Screen section
 "DefaultScreen" for depth/fbbpp 24/32
[ 545.870] (**) ARMSOC(0): Depth 24, (--) framebuffer bpp 32
--
[ 545.903] (II) ARMSOC(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 545.903] (==) ARMSOC(0): DPMS enabled
[ 545.951] (--) RandR disabled
[ 545.974] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/armsoc_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/armsoc_dri.so: cannot open shared object file: No such file or directory)
[ 545.974] (EE) AIGLX: reverting to software rendering
[ 545.974] (II) AIGLX: Screen 0 is not DRI capable
[ 545.981] (II) AIGLX: Loaded and initialized swrast
[ 545.981] (II) GLX: Initialized DRISWRAST GL provider for screen 0

I can't find armsoc_dri.so in the Chrome OS filesystem though.