Looking at this post
Graphics and Compute Development on Samsung Chromebook « Mali Developer Center Mali Developer Center
I have see that is possible to have Mali GPU hardware acceleration on Samsung ARM Chromebook with Ubuntu.
On the post you guide all the process to prepare an sd card to install ubuntu with mail support on chromebook, could you provide even the imagefile of the generated sd card?
Thanks
The Xorg.0.log from startx just now:
http://pastebin.com/raw.php?i=QReXsgXC
The whole log is included above, but...
parts of that which caught my attention:
[ 18.346] (II) LoadModule: "armsoc"
[ 18.346] (II) Loading /usr/lib/xorg/modules/drivers/armsoc_drv.so
[ 18.352] (II) Module armsoc: vendor="X.Org Foundation"
[ 18.352] compiled for 1.15.1, module version = 0.6.0
[ 18.352] Module class: X.Org Video Driver
[ 18.352] ABI class: X.Org Video Driver, version 15.0
[ 18.352] (II) ARMSOC: Driver for ARM compatible chipsets: Mali-4XX, Mali-T6XX
[ 18.352] (--) using VT number 7
...
[ 18.357] (WW) Falling back to old probe method for armsoc
[ 18.357] (II) No BusID or DriverName specified - opening /dev/dri/card0
[ 18.357] (II) Got BusID platform:exynos-drm:00
[ 18.478] (II) Opened DRM
[ 18.479] (II) DeviceName is [/dev/dri/card0]
[ 18.479] (II) bus_id is [platform:exynos-drm:00]
[ 18.479] (II) DriverName is [exynos]
[ 18.479] (II) version is [1.0.0]
[ 18.710] (II) ARMSOC(0): [DRI2] Setup complete
[ 18.710] (II) ARMSOC(0): [DRI2] DRI driver: armsoc
[ 18.710] (==) ARMSOC(0): Backing store enabled
[ 18.710] (==) ARMSOC(0): Silken mouse enabled
[ 18.713] (II) ARMSOC(0): HW cursor init()
[ 18.714] (EE) ARMSOC(0): ERROR: Failed driver-specific cursor initialization
[ 18.735] (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)
[ 18.735] (EE) AIGLX: reverting to software rendering
[ 18.852] (II) AIGLX: Loaded and initialized swrast
Are these indications that I've loaded the wrong driver, or normal messages?
What can I do, if you do happen to recognize the problem
Thanks,
Kingdon