Samsung Chromebook uses software rendering when hardware rendering can work. Please whitelist Software Rasterizer

Bug #1100067 reported by Pete Graner on 2013-01-15
24
This bug affects 5 people
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.01.11-0ubuntu1
Uname: Linux 3.4.0 armv7l
ApportVersion: 2.8-0ubuntu1
Architecture: armhf
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
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_DIR=<set>
 SHELL=/bin/bash
ProcKernelCmdLine: cros_secure console= console=tty1 debug verbose root=/dev/mmcblk0p7 rootwait rw lsm.module_locking=0
Renderer: Software
SourcePackage: nux
UnitySupportTest:

UpgradeStatus: Upgraded to raring on 2013-01-14 (1 days ago)
version.compiz: compiz 1:0.9.9~daily13.01.14-0ubuntu1
version.libdrm2: libdrm2 2.4.40-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1
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/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)
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output HDMI-1
xserver.version: 2:1.13.1.901-0ubuntu1
xserver.video_driver: armsoc

Pete Graner (pgraner) wrote :
Pete Graner (pgraner) wrote :

cat /proc/maps.txt dump

Pete Graner (pgraner) wrote :

Output of glxinfo

Daniel van Vugt (vanvugt) wrote :

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 :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nux (Ubuntu):
status: New → Confirmed
Tom Townsend (tom-towny) wrote :

Is this a similar issue to https://bugs.launchpad.net/chromebook-arm/+bug/1085596 ?

Marked it as affecting me as I believe it to be similar.

Yuri Pole (x3qt-dev) on 2013-02-06
Changed in chromebook-arm:
status: New → Confirmed
importance: Undecided → High
Oliver Grawert (ogra) wrote :

@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-"r1p2-00bet0"
EGL_VENDOR = ARM
EGL_EXTENSIONS = EGL_KHR_config_attribs EGL_KHR_image EGL_KHR_image_base EGL_KHR_fence_sync EGL_ARM_wait_sync EGL_KHR_gl_texture_2D_image EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image_pixmap
EGL_CLIENT_APIS = OpenGL_ES
GL_VERSION: OpenGL ES 2.0
GL_RENDERER: Mali-T604
GL_EXTENSIONS:
    GL_ARM_rgba8, GL_ARM_mali_shader_binary,
    GL_ARM_texture_format_rgba16_la16, GL_OES_depth24, GL_OES_depth_texture,
    GL_OES_packed_depth_stencil, GL_OES_rgb8_rgba8, GL_EXT_read_format_bgra,
    GL_OES_compressed_paletted_texture, GL_OES_compressed_ETC1_RGB8_texture,
    GL_OES_standard_derivatives, GL_OES_EGL_image, GL_OES_EGL_image_external,
    GL_OES_texture_npot, GL_OES_vertex_half_float,
    GL_OES_required_internalformat, GL_OES_vertex_array_object,
    GL_OES_mapbuffer, GL_EXT_texture_format_BGRA8888, GL_EXT_texture_rg,
    GL_EXT_texture_type_2_10_10_10_REV, GL_OES_fbo_render_mipmap,
    GL_OES_element_index_uint, GL_EXT_occlusion_query_boolean,
    GL_EXT_blend_minmax, GL_EXT_discard_framebuffer,
    GL_OES_get_program_binary, GL_ARM_mali_program_binary, GL_OES_texture_3D,
    GL_EXT_texture_storage, GL_EXT_multisampled_render_to_texture

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers