View Full Version : Chrome - Can't enable hardware acceleration with Nvidia card and proprietary drivers
chris408
August 26th, 2015, 04:25 AM
Usually I can figure this stuff out by searching other Linux forums but after spending an hour this one has me stumped.
When I go to chrome://gpu/ this is what I see:
Software only, hardware acceleration unavailable
GPU process was unable to boot: GPU access is disabled in chrome://settings.
Disabled Features: all
I have tried enabling the "Override software rendering list" option under chrome://flags but that did not help either.
I am running the 304.88 Xorg Driver for my older 8800GT which I got using the "Driver Manager" tool.
I have tried everything I could find on the web but no luck. Any thoughts? "Use hardware acceleration when available" is checked under advanced options but still no luck.
weatherman2
August 26th, 2015, 04:56 AM
I'm using kernel drivers for my Intel integrated video card, and here's what I get in Chrome:
Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Hardware accelerated
Flash Stage3D: Software only, hardware acceleration unavailable
Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable
Compositing: Hardware accelerated
Multiple Raster Threads: Disabled
Rasterization: Software only, hardware acceleration unavailable
Threaded Rasterization: Enabled
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Hardware accelerated
WebGL: Hardware accelerated
Why does Chrome have hardware acceleration for some features and not others? I don't know - I don't worry about it. It has never been an issue for me. Chrome works fine for me, but the laptop is slow anyway.
Do you see hardware acceleration unavilable for ALL features?
What kinds of issues are you having that you are trying to fix?
Yellow Pasque
August 26th, 2015, 06:31 AM
GPU access is disabled in chrome://settings
Try the simplest fix first. Go into chrome://settings, click on show advanced settings at the bottom, and then scroll down to the bottom again and make sure "use hardware acceleration when available" is checked.
chris408
August 30th, 2015, 01:48 PM
Try the simplest fix first. Go into chrome://settings, click on show advanced settings at the bottom, and then scroll down to the bottom again and make sure "use hardware acceleration when available" is checked.
I checked most of the simple stuff and yes this is selected. Any other thoughts?
chris408
September 9th, 2015, 08:51 PM
Anyone?
Yellow Pasque
September 9th, 2015, 08:59 PM
Google has probably blacklisted your GPU because of some driver bug. Try this and see if it helps:
google-chrome --ignore-gpu-blacklist --enable-webgl
chris408
September 16th, 2015, 02:53 PM
Google has probably blacklisted your GPU because of some driver bug. Try this and see if it helps:
google-chrome --ignore-gpu-blacklist --enable-webgl
I tried this and then went into chrome:gpu and this is what I see. Looks pretty much the same
Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Software only, hardware acceleration unavailable
Flash Stage3D: Software only, hardware acceleration unavailable
Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable
Compositing: Software only, hardware acceleration unavailable
Multiple Raster Threads: Disabled
Rasterization: Software only, hardware acceleration unavailable
Threaded Rasterization: Unavailable
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Software only, hardware acceleration unavailable
WebGL: Unavailable
Driver Bug Workarounds
clear_uniforms_before_first_program_use
init_gl_position_in_vertex_shader
init_vertex_attributes
scalarize_vec_and_mat_constructor_args
use_current_program_after_successful_link
use_virtualized_gl_contexts
Problems Detected
GPU process was unable to boot: GPU access is disabled in chrome://settings.
Disabled Features: all
Always call glUseProgram after a successful link to avoid a driver bug: 349137 (http://crbug.com/349137)
Applied Workarounds: use_current_program_after_successful_link
Program link fails in NVIDIA Linux if gl_Position is not set: 286468 (http://crbug.com/286468)
Applied Workarounds: init_gl_position_in_vertex_shader
Clear uniforms before first program use on all platforms: 124764 (http://crbug.com/124764), 349137 (http://crbug.com/349137)
Applied Workarounds: clear_uniforms_before_first_program_use
Linux NVIDIA drivers don't have the correct defaults for vertex attributes: 351528 (http://crbug.com/351528)
Applied Workarounds: init_vertex_attributes
Always rewrite vec/mat constructors to be consistent: 398694 (http://crbug.com/398694)
Applied Workarounds: scalarize_vec_and_mat_constructor_args
MakeCurrent is slow on Linux
Applied Workarounds: use_virtualized_gl_contexts
Raster is using a single thread.
Disabled Features: multiple_raster_threads
Version Information
Data exported
9/16/2015, 9:50:52 AM
Chrome version
Chrome/44.0.2403.157
Operating system
Linux 3.5.0-17-generic
Software rendering list version
0
Driver bug list version
8.19
ANGLE commit id
709dc46cbd06
2D graphics backend
Skia
Command Line Args
--ignore-gpu-blacklist --enable-webglgoogle-chrome --ignore-gpu-blacklist --enable-webgl --flag-switches-begin --force-gpu-rasterization --ignore-gpu-blacklist --flag-switches-end
Driver Information
Initialization time
0
Sandboxed
false
GPU0
VENDOR = 0x10de, DEVICE= 0x0611
Optimus
false
AMD switchable
false
Driver vendor
NVIDIA
Driver version
304.88
Driver date
Pixel shader version
Vertex shader version
Max. MSAA samples
Machine model name
Machine model version
GL_VENDOR
GL_RENDERER
GL_VERSION
GL_EXTENSIONS
Disabled Extensions
Window system binding vendor
Window system binding version
Window system binding extensions
Window manager
Marco
Compositing manager
No
Direct rendering
Yes
Reset notification strategy
0x0000
GPU process crash count
1
Log Messages
GpuProcessHostUIShim: The GPU process exited with code 32512.
Yellow Pasque
September 16th, 2015, 06:23 PM
This is the best I could google:
https://code.google.com/p/chromium/issues/detail?id=506950
GPU process crash count 1
GpuProcessHostUIShim: The GPU process exited with code 32512.
As the bug report suggests, submit the crash ID (enable crash reporting if not enabled already). http://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug
Powered by vBulletin® Version 4.2.2 Copyright © 2025 vBulletin Solutions, Inc. All rights reserved.