New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 612145 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature



Sign in to add a comment

GPU can't be detected

Reported by wbr...@gmail.com, May 16 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. set strict filesystem permissions
2. 
3. 

What is the expected behavior?
it is possible override gpu vendor and device from command line
--gpu-vendor-id=0x1234 --gpu-device-id=0x1234

What went wrong?
GPU can't be detected properly with Mesa drivers
chrome://gpu/ 
VENDOR = 0x0000, DEVICE= 0x0000

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? N/A 

Chrome version: 50.0.2661.102  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 21.0 r0
 

Comment 1 by wbr...@gmail.com, May 16 2016

It seems glxinfo is able to detect GPU with strict filesystem permissions

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) Sandybridge Desktop  (0x102)
    Version: 11.2.2
    Accelerated: yes
    Video memory: 1536MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 3.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0

Components: Internals>GPU
Cc: j.iso...@samsung.com

Comment 4 by wbr...@gmail.com, Jun 12 2016

I guess it doesn't work because lspci doesn't work for non-root user
$ /usr/sbin/lspci
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.

there are command line options which work
--gpu-testing-vendor-id=0x8086 --gpu-testing-device-id=0x102
Cc: zmo@chromium.org piman@chromium.org
libudev could be used instead of libpci in gpu_info_collector_linux.cc::CollectPCIVideoCardInfo()

Some pointers:
https://cgit.freedesktop.org/wayland/weston/tree/src/compositor-drm.c#n2792
(I guess for the nvidia proprietary driver the subsystem will pci, not drm)
http://man7.org/linux/man-pages/man3/libudev.3.html
http://unix.stackexchange.com/questions/111593/allow-non-root-user-to-read-write-dev-files

Have a go on your configuration by running:
udevadm info --query=all --name=/dev/dri/card0






Comment 6 by wbr...@gmail.com, Nov 11 2016

there is no vendor id or device id in output from udevadm

Comment 7 by wbr...@gmail.com, Nov 11 2016

GLX_MESA_query_renderer extension or possibly libudev can detect GPU 
cat /sys/devices/pci0000:00/0000:00:02.0/drm/card0/device/vendor
0x8086
cat /sys/devices/pci0000:00/0000:00:02.0/drm/card0/device/device 
0x0102

Cc: sunn...@chromium.org
Components: -Internals>GPU Internals>GPU>Internals
Labels: -Type-Compat Needs-Feedback Type-Feature
To override device/vendor id, you need to use the --gpu-testing-device-id=0xabcd and --gpu-testing-vendor-id=0xffff flags. Note that the "testing" is important. If that works, this bug should be closed as WontFix as it's unlikely that we'll ever implement any other workarounds for this.

Comment 9 by wbr...@gmail.com, Apr 4 2017

it works
Project Member

Comment 10 by sheriffbot@chromium.org, Apr 4 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sunnyps@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)

Sign in to add a comment