Samsung Chromebook uses software rendering when hardware rendering can work. Please whitelist Software Rasterizer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Nux |
New
|
Undecided
|
Unassigned | |
| nux (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Chromebook uses software rendering when hardware rendering is working.
I installed raring on my chromebook and unity-support-test reports that it is using hw rendering.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: libnux-4.0-0 4.0.0daily13.
Uname: Linux 3.4.0 armv7l
ApportVersion: 2.8-0ubuntu1
Architecture: armhf
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
Date: Tue Jan 15 22:38:29 2013
DistUpgraded: 2013-01-14 22:05:37,079 DEBUG failed to SystemUnLock() (E:Not locked)
DistroCodename: raring
DistroVariant: ubuntu
GraphicsCard:
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
SHELL=/bin/bash
ProcKernelCmdLine: cros_secure console= console=tty1 debug verbose root=/dev/mmcblk0p7 rootwait rw lsm.module_
Renderer: Software
SourcePackage: nux
UnitySupportTest:
UpgradeStatus: Upgraded to raring on 2013-01-14 (1 days ago)
version.compiz: compiz 1:0.9.9~
version.libdrm2: libdrm2 2.4.40-1
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Tue Jan 15 22:36:36 2013
xserver.configfile: default
xserver.devices:
input gpio-keys.8 KEYBOARD, id 6
input Cypress APA Trackpad (cyapa) TOUCHPAD, id 7
input chromeos-ec KEYBOARD, id 8
xserver.errors:
AIGLX error: dlopen of /usr/lib/
AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output HDMI-1
xserver.version: 2:1.13.
xserver.
Pete Graner (pgraner) wrote : | #1 |
Pete Graner (pgraner) wrote : | #2 |
Pete Graner (pgraner) wrote : | #3 |
Output of glxinfo
Daniel van Vugt (vanvugt) wrote : | #4 |
glxinfo:
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 9.0.1
OpenGL shading language version string: 1.20
This is actually a good thing and we don't want to fall back to LLVMpipe. Because it seems the Software Rasterizer will automatically use LLVMpipe where it needs to. And sticking with it you will still get access to your 2D acceleration provided by the Mali X driver. However forcing LLVMpipe as we do right now is a problem. Because forcing LLVMpipe will not allow you to use the 2D acceleration.
summary: |
- Chromebook uses software rendering when hardware rendering is working + Samsung Chromebook uses software rendering when hardware rendering can + work. Please whitelist Software Rasterizer |
Launchpad Janitor (janitor) wrote : | #5 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in nux (Ubuntu): | |
status: | New → Confirmed |
Tom Townsend (tom-towny) wrote : | #6 |
Is this a similar issue to https:/
Marked it as affecting me as I believe it to be similar.
Changed in chromebook-arm: | |
status: | New → Confirmed |
importance: | Undecided → High |
Oliver Grawert (ogra) wrote : | #7 |
@daniel: you need to use es2_info from the mesa-utils-extra package to have the equivalent of glxinfo on an GLES ARM device...
ogra@chromebook:~$ es2_info
EGL_VERSION = 1.4 Midgard-
EGL_VENDOR = ARM
EGL_EXTENSIONS = EGL_KHR_
EGL_CLIENT_APIS = OpenGL_ES
GL_VERSION: OpenGL ES 2.0
GL_RENDERER: Mali-T604
GL_EXTENSIONS:
GL_ARM_rgba8, GL_ARM_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
cat /proc/maps.txt dump