From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98146] DRI_PRIME=1 and fullscreen issues
Date: Fri, 07 Oct 2016 15:02:41 +0000 [thread overview]
Message-ID: <bug-98146-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1856 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98146
Bug ID: 98146
Summary: DRI_PRIME=1 and fullscreen issues
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: darekdeoniziak@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
I have multiple issues while using DRI_PRIME=1 (radeon):
1. Few windowed mode applications don't draw content until window is resized.
Also right-click context menu doesn't always appear
2. I have screen tearing for fullscreen apps running in , screen is cutted from
screen corner to corner, crossing at the centre of the screen.
3. tearing and flickering when running programs.
4. fullscreen games often freeze screen when minimized or closed (tested on
multiple games like Talos Principle, Dota, Tomb Raider, 0.ad, etc). After
freeze i usualy go to tty and restart lightdm. Maybe it is also intel gpu
related?
---
I am using DRI_PRIME=1 for multiple programs after updating drivers using oibaf
ppa: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers on Ubuntu
16.04.
I have Dell Inspirion 7548 with Radeon Opal R7 M265 and Broadwell G2, lshw -c
video output: http://pastebin.com/kdJzaXNk
DRI_PRIME=1 glxinfo OpenGL renderer: Gallium 0.4 on AMD OLAND (DRM 2.43.0 /
4.4.0-36-generic, LLVM 3.9.0)
DRI_PRIME=1 glxinfo OpenGL version: OpenGL version string: 3.0 Mesa
12.1.0-devel
4.4.0-38-generic Ubuntu 16.04
---
The issues easly can be reproduced, let me know which logs should I submit to
help.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3333 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
next reply other threads:[~2016-10-07 15:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 15:02 bugzilla-daemon [this message]
2016-10-07 15:29 ` [Bug 98146] DRI_PRIME=1 and fullscreen issues 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
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.