dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98146] DRI_PRIME=1 and fullscreen issues
Date: Tue, 11 Oct 2016 07:32:36 +0000	[thread overview]
Message-ID: <bug-98146-502-lFReSN0q6x@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98146-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1660 bytes --]

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

--- Comment #11 from Darek Deoniziak <darekdeoniziak@gmail.com> ---
DRI_PRIME=1 LIBGL_DEBUG=verbose glxinfo >/dev/null:
libGL: screen 0 does not appear to be DRI3 capable
libGL: pci id for fd 4: 1002:6604, driver radeonsi
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/radeonsi_dri.so
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
libGL: Can't open configuration file /home/darek/.drirc: No such file or
directory.
libGL: Can't open configuration file /home/darek/.drirc: No such file or
directory.

LIBGL_DEBUG=verbose glxinfo >/dev/null:
libGL: screen 0 does not appear to be DRI3 capable
libGL: pci id for fd 4: 8086:1616, driver i965
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/i965_dri.so
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
libGL: Can't open configuration file /home/darek/.drirc: No such file or
directory.
libGL: Using DRI2 for screen 0
libGL: Can't open configuration file /home/darek/.drirc: No such file or
directory.
libGL: Can't open configuration file /home/darek/.drirc: No such file or
directory.
libGL: Can't open configuration file /home/darek/.drirc: No such file or
directory.

It seems that I'm still using DRI2, how can I change that, am I missing some
libraries?

I am also using git version of mesa drivers, could closing fullscreen freezing
stop after recent updates? I couldn't reproduce freezing (4) and hdmi issues
while pressing fn button to change display (5) for last few days.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2424 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-10-11  7:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 15:02 [Bug 98146] DRI_PRIME=1 and fullscreen issues bugzilla-daemon
2016-10-07 15:29 ` bugzilla-daemon
2016-10-07 16:33 ` bugzilla-daemon
2016-10-07 16:34 ` bugzilla-daemon
2016-10-07 16:55 ` bugzilla-daemon
2016-10-07 18:27 ` bugzilla-daemon
2016-10-07 18:46 ` bugzilla-daemon
2016-10-07 19:51 ` bugzilla-daemon
2016-10-07 19:53 ` bugzilla-daemon
2016-10-10  9:12 ` bugzilla-daemon
2016-10-11  7:21 ` bugzilla-daemon
2016-10-11  7:32 ` bugzilla-daemon [this message]
2016-10-11  7:41 ` bugzilla-daemon
2016-10-20 19:51 ` bugzilla-daemon
2016-10-20 20:27 ` bugzilla-daemon
2016-10-21  5:33 ` bugzilla-daemon
2016-10-22 16:24 ` bugzilla-daemon
2016-10-22 17:40 ` bugzilla-daemon
2016-10-22 20:52 ` bugzilla-daemon
2016-10-25  6:35 ` bugzilla-daemon
2017-06-25  6:42 ` bugzilla-daemon
2017-06-25 13:35 ` bugzilla-daemon
2017-07-25 12:33 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-98146-502-lFReSN0q6x@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).