Chrome/Chromium: NVIDIA: could not open the device file /dev/nvidia0

Sadface · 2013-05-12 01:16:15

I wasn't sure whether this belongs to Applications/Desktop Environments or here, since I'm not exactly sure which one it is. Pardon if I chose poorly.

Ever since Chrome/Chromium v26 (or v25) came along, I've been having massive problems with anything CSS 2D/CSS 3D/Hardware Accelleration.
For a long time I've searched google and many a bug tracker with no results that help me in any way, so it appears I am the only one who has this problem
and it might not be a bug in Chromium. I tried every major release since the broken one, up to the current dev version, they are all affected.

The problem is as follows: Anything that makes Chromium use my GPU (CSS transformations for example) works fine for a second before
completely stopping the browser while simultaneously driving my GPU to full speed. When doing this, it outputs three lines into the shell:

NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted).
NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted).
NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted).

"dmesg" does not mention this.

On to my setup, the most relevant parts of it:

Software:
DE: KDE 4.10.2
Kernel: 3.8.11-1
Driver: NVIDIA Proprietary, Version 313.30 (Driving two monitors)
Hardware:
GPU: GF GTX 560 Ti

While hunting down bug trackers and forum posts, I've tried every possible fix they recommended and I can exclude
* Driver problem: 3D gaming works *very* well with no problems whatsoever, as does Firefox.
* User permissions: I'm in all the standard groups, including "video"
* Hardware changes: I've been using this card since 2011

There appears to be, however, light at the end of the tunnel: If I run Chromium as root, via

$ kdesu chromium --user-data-dir=~/.config/chromium
# or
$ kdesu google-chrome --user-data-dir=~/.config/google-chrome

It works *perfectly*, buttery smooth and without any warning in my console. I do not think it's a permission error, since
other applications work perfectly well without root, and this has not happened with Chromium v25 (or 24, I'm not sure anymore).
Also if I downgrade Chromium it'll work perfectly again as well.

Does anyone have *any* idea what can be done?

Thank you very much for reading!

Last edited by Sadface (2013-05-12 01:22:43)

cepe · 2013-05-26 20:47:27

Hi!

When I am using Chromium I get following message in it's console log:

NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted).

Does anybody know what does it mean?

Last edited by cepe (2013-05-26 20:52:02)

foutrelis · 2013-05-26 21:08:25

Same topic with more information (no answers or solution though):

https://bbs.archlinux.org/viewtopic.php?id=163158

karol · 2013-05-26 21:08:38

Have you tried https://wiki.archlinux.org/index.php/Nv … tput_error ?

cepe · 2013-05-26 21:33:02

foutrelis wrote:

Same topic with more information (no answers or solution though) (...)

Yea, It seems that we have the same problem.

karol wrote:

Have you tried (...)?

No, I haven't because I believe that this is a quite different problem than mine.

jasonwryan · 2013-05-26 21:46:57

foutrelis wrote:

Same topic with more information (no answers or solution though):
https://bbs.archlinux.org/viewtopic.php?id=163158

Merging...

sobota · 2013-05-27 09:43:35

I have this same a issue. In my case solution is change group from root to video. In my opinion the best solution is udev rule.

But rule doesn't work. How solve this?

KERNEL=="nvidia[0-9]", GROUP="video", MODE="0666"

Thorsten Reinbold · 2013-06-07 10:29:32

sobota wrote:

I have this same a issue. In my case solution is change group from root to video. In my opinion the best solution is udev rule.
But rule doesn't work. How solve this?
KERNEL=="nvidia[0-9]", GROUP="video", MODE="0666"

What I found, was a discussion in the debian mailing list:

> The patch to create these devices in udev is included in debian's non-free
> source. Perhaps you were missing the appropriate udev rules to actually
> create the device files.
>
> Put the following in a file (whose name ends in .rules) in
> /etc/udev/rules.d
>
> KERNEL="nvidia[0-9]*", NAME="%k"
> KERNEL="nvidiactl", NAME="%k"

That doesn't do anything out of the ordinary, since by default, udev
will create the nodes with the kernel names, if no rules exists. You
have here basically created a rule that names the nodes to be the kernel
names.

If the nvidia modules have been ported to sysfs, then udev should pick
up the device, and create the nodes automatically.

I hope this is helpful.

Edit: maybe this is also useful.

Last edited by Thorsten Reinbold (2013-06-07 10:38:18)

Arch Linux

#1 2013-05-12 01:16:15

Chrome/Chromium: NVIDIA: could not open the device file /dev/nvidia0

#2 2013-05-26 20:47:27

Re: Chrome/Chromium: NVIDIA: could not open the device file /dev/nvidia0

#3 2013-05-26 21:08:25

Re: Chrome/Chromium: NVIDIA: could not open the device file /dev/nvidia0

#4 2013-05-26 21:08:38

Re: Chrome/Chromium: NVIDIA: could not open the device file /dev/nvidia0

#5 2013-05-26 21:33:02

Re: Chrome/Chromium: NVIDIA: could not open the device file /dev/nvidia0

#6 2013-05-26 21:46:57

Re: Chrome/Chromium: NVIDIA: could not open the device file /dev/nvidia0

#7 2013-05-27 09:43:35

Re: Chrome/Chromium: NVIDIA: could not open the device file /dev/nvidia0

#8 2013-06-07 10:29:32

Re: Chrome/Chromium: NVIDIA: could not open the device file /dev/nvidia0

Board footer