You are not logged in.

#1 2018-12-14 22:00:00

digitalone
Member
Registered: 2011-08-19
Posts: 328

dri mesa config won't apply

Chromium-vaapi needs 'allow_rgb10_configs' to be disabled.

Adding the following configuration to '/etc/drirc' or '$HOME/.drirc':

<driconf>
   <device screen="0" driver="radeonsi">
      <application name="Chromium" executable="chromium">
         <option name="allow_rgb10_configs" value="false" />
      </application>
   </device>
</driconf>

won't work, so that seems mesa configuration is not applied. Is that really a bug or there's something wrong in the config? Should be reported?

Last edited by digitalone (2018-12-14 22:00:26)

Offline

#2 2018-12-15 12:22:51

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: dri mesa config won't apply

https://wiki.archlinux.org/index.php/Ch … celeration

allow_rgb10_configs is not a mesa option.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2018-12-15 13:09:02

digitalone
Member
Registered: 2011-08-19
Posts: 328

Offline

#4 2018-12-15 14:46:06

digitalone
Member
Registered: 2011-08-19
Posts: 328

Re: dri mesa config won't apply

Did many attempts and it works in this way:

<driconf>
    <device driver="radeonsi">
        <option name="allow_rgb10_configs" value="false" />
    </device>
</driconf>

So why won't work specifying the application?

Tried also

<driconf>
   <device screen="0" driver="radeonsi">
      <application name="Chromium" executable="/usr/bin/chromium">
         <option name="allow_rgb10_configs" value="false" />
      </application>
   </device>
</driconf>

won't work either.

Offline

#5 2018-12-15 22:49:16

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: dri mesa config won't apply

The correct executable to use might be "/usr/lib/chromium/chromium". I tried checking this by running "xprop" and then looking for the "_NET_WM_PID" entry, then running "ps -f -p ..." with that PID.

Offline

#6 2018-12-15 23:07:18

digitalone
Member
Registered: 2011-08-19
Posts: 328

Re: dri mesa config won't apply

Ropid wrote:

The correct executable to use might be "/usr/lib/chromium/chromium". I tried checking this by running "xprop" and then looking for the "_NET_WM_PID" entry, then running "ps -f -p ..." with that PID.

Used that also. After many attempts, it worked only two times, the rest is the same. Maybe there's something wrong with the many threads that chromium generates.

With only one tab active after the start, I see about 10 Chromium entries in KSysGuard.

Tried also to add chrome-sandbox executable, it's useless.

One thing interesting: the only two times that it worked, I started from command line (but I tried many other times from command line and it didn't work).

If one won't disable it globally, it's better to declare the variable before the executable command in ~/.locale/share/applications/chromium.desktop entry. That works.

Offline

#7 2018-12-16 13:15:59

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: dri mesa config won't apply

Seems I interpreted that wiki part wrong and allow_rgb10_configs is indeed a mesa option.


digitalone wrote:

If one won't disable it globally, it's better to declare the variable before the executable command in ~/.locale/share/applications/chromium.desktop entry. That works.

Good idea, maybe you could add it to the wiki as an alternative for setting rgb10 systemwide ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#8 2018-12-16 21:47:02

digitalone
Member
Registered: 2011-08-19
Posts: 328

Re: dri mesa config won't apply

Lone_Wolf wrote:

Seems I interpreted that wiki part wrong and allow_rgb10_configs is indeed a mesa option.


digitalone wrote:

If one won't disable it globally, it's better to declare the variable before the executable command in ~/.locale/share/applications/chromium.desktop entry. That works.

Good idea, maybe you could add it to the wiki as an alternative for setting rgb10 systemwide ?

Sure.

If my English is bad, you can fix or improve it.

Offline

Board footer

Powered by FluxBB