From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67550] New: Radeon+Intel GPU with HDMI audio on Intel
Date: Tue, 30 Jul 2013 16:58:11 +0000 [thread overview]
Message-ID: <bug-67550-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2991 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67550
Priority: medium
Bug ID: 67550
Assignee: dri-devel@lists.freedesktop.org
Summary: Radeon+Intel GPU with HDMI audio on Intel
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: a.heider@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: DRI CVS
Component: General
Product: DRI
I have multiple, but related, issues with a dual GPU setup:
1) cursor flickering
2) no HDMI audio on secondary GPU without extending X11 for that output
3) xrandr broken with xorg.conf describing the dual setup
4) driQueryOptioni() not multi GPU aware (crash in mesa)
Setup:
Radeon 6850 PCIe as primary device, connected to a TFT over DVI
HD4000 on Ivybridge as secondary device, connected to a receiver over HDMI
(plus a projector connected to my receiver via HDMI)
Pretty much the latest and greatest of everything in the graphics stack.
Why the secondary connection? It's used to get multichannel audio to my
receiver, which isn't possible with the additional radeon HDMI head.
If I extend my desktop via:
xrandr --output $intel_hdmi --right-of $radeon_dvi --mode 1280x720 --refresh 60
It properly extends the display to the secondary GPU. I get a picture on the
projector, as well as HDMI audio on the receiver.
#1, without xorg.conf
Now with both outputs enabled there is a mouse cursor issue with apps on the
primary output:
* mplayer (without using vdpau), dvb-t viewer or firefox+flash: when moving the
cursor over the video output, there's a rectangle of garbage around the cursor.
Looks like a rect of a prior frame on a broken alpha mask. The issue with
mplayer vanishes when using vdpau.
* The cursor in full screen GL games flickers. One frame it's there, then
vanishes some later, but mostly its gone, making GUIs a real pita.
If I disable the $intel_hdmi output again the problem goes away. But that
brings us to the second problem:
#2, without xorg.conf
The receiver sends its own EDID block, so I can extend via xrandr without
turning on the projector.
But the projector is turned off in most cases, so is there a way to disable a
display output but keep the HDMI audio output? (as a workaround for #1)
I found:
xrandr --output $intel_hdmi --set audio force-dvi|off|auto|on
but it seems that only works if the display output is enabled (or I'm too
stupid to properly use xrandr)...
#3 with xorg.conf
xrandr thinks HDMI isn't connected to the Intel GPU, and hence doesn't allow to
toggle it, yet HDMI audio over it just works. While that would probably work
around #1 I cannot tell because then I run into:
#4 with xorg.conf
All GL apps crash with:
glxinfo: /home/andre/devel/mesa/src/mesa/drivers/dri/common/xmlconfig.c:1030:
driQueryOptioni: Assertion `cache->info[i].name != ((void *)0)' failed.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4291 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-07-30 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 16:58 bugzilla-daemon [this message]
2013-07-30 16:58 ` [Bug 67550] Radeon+Intel GPU with HDMI audio on Intel bugzilla-daemon
2013-07-30 16:59 ` bugzilla-daemon
2013-07-30 17:00 ` bugzilla-daemon
2013-07-30 17:27 ` bugzilla-daemon
2013-07-31 10:30 ` bugzilla-daemon
2013-07-31 11:54 ` bugzilla-daemon
2013-07-31 12:05 ` bugzilla-daemon
2013-08-04 4:40 ` bugzilla-daemon
2013-08-05 9:21 ` 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-67550-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 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).