[Mesa-dev] [Bug 102682] vblank_mode ignored from ~/.drirc

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=102682

GitLab Migration User  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEW |RESOLVED

--- Comment #6 from GitLab Migration User  ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1018.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 102682] vblank_mode ignored from ~/.drirc

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=102682

--- Comment #5 from Niklas Haas  ---
At the very least, it's a bug in driconf that it doesn't show up in the GUI.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 102682] vblank_mode ignored from ~/.drirc

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=102682

--- Comment #4 from Nicolai Hähnle  ---
IMHO, while there is a certain internal logic to it, having to put
driver="dri2" here is surprising and bad usability. I'd say this is a valid
bug, and should be fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 102682] vblank_mode ignored from ~/.drirc

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=102682

--- Comment #3 from Gustaw Smolarczyk  ---
Was too fast. The passed driver name is not "loader" but "dri2". And I think
it's intentional, since vblank_mode is not an option of a device driver but of
the dri infrastructure.

I will let the more experienced developers judge this bug report, but I would
say it's NOTABUG.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 102682] vblank_mode ignored from ~/.drirc

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=102682

--- Comment #2 from Niklas Haas  ---
Verifying that your work-around does, indeed, work around the issue.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 102682] vblank_mode ignored from ~/.drirc

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=102682

--- Comment #1 from Gustaw Smolarczyk  ---
Hi,

The problem seems to be with the `driver="radeonsi"' part (the screen attribute
is not used when driver is present). It seems that there is a bug and an
incorrect driver name "loader" is passed to the xmlconfig machinery.

For a quick work-around, just remove both screen and driver attributes, unless
you want to restrict your setting to a specific driver/screen.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 102682] vblank_mode ignored from ~/.drirc

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=102682

Bug ID: 102682
   Summary: vblank_mode ignored from ~/.drirc
   Product: Mesa
   Version: 17.2
  Hardware: Other
OS: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: Mesa core
  Assignee: mesa-dev@lists.freedesktop.org
  Reporter: bugs.freedesk...@haasn.xyz
QA Contact: mesa-dev@lists.freedesktop.org

Various sources (e.g. IRC) have led me to believe that `vblank_mode` should be
a settable option via ~/.drirc; however, it doesn't seem like this is the case
to me. A demonstration:









I made this from the ~/.drirc skeleton created by `driconf`. Curiously, the
`vblank_mode` setting was also absent from that skeleton, but I added it
manually. (It's also absent from the GUI - although a friend of mine says he
has the option in his driconf interface!) As expected, this option seems to
have no effect - I still get vsync in all tested applications (e.g. glxgears).

I can override it manually by using the environment variable vblank_mode, e.g.
`vblank_mode=0 glxgears`. This *does* work, although it doesn't explain why
this option is seemingly ignored from ~/.drirc. More worrying is the fact that
the actual source code (dri3_set_swap_interval) uses configQuery("vblank_mode")
to get this value, so it should pull it from both XML and the environment,
right?

If this is not expected behavior, I can try stepping through the `configQuery`
function in gdb; but I thought I'd ask first in case this is a known or easily
explained issue.

Mesa version is 17.2.0, kernel version is 4.12.4, device is a Sapphire RX 560.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev