From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104880] No sound via DP on R9 Fury (4.14 + DC patches)
Date: Wed, 31 Jan 2018 09:43:53 +0000 [thread overview]
Message-ID: <bug-104880-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4474 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104880
Bug ID: 104880
Summary: No sound via DP on R9 Fury (4.14 + DC patches)
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: lakostis@altlinux.org
Created attachment 137079
--> https://bugs.freedesktop.org/attachment.cgi?id=137079&action=edit
dmesg
Greetings!
Trying to make DP sound work on my R9 Fury card.
The problem: no sound caps are detected for monitor via DP
Monitor ASUS PB278 supports DP sound playback (tested with nvidia card and
older R9 2x card), but it's not detected during boot or plug/unplug operations
dmesg:
(did unplug and plugged again)
[ 175.415648] [drm] Rx Caps:
[ 175.549293] [drm] SADs count is: -2, don't need to read it
[ 175.554060] [drm] HBRx4 pass VS=0, PE=0
[ 175.554363] [drm] ASUS PB278: [Block 0]
[ 175.554367] [drm] ASUS PB278: [Block 1]
[ 175.554373] [drm] dc_link_detect: manufacturer_id = 6904, product_id = 27A3,
serial_number = 8C18, manufacture_week = 30, manufacture_year = 26,
display_name = ASUS PB278, speaker_flag = 0, audio_mode_count = 0
[ 175.554978] [drm] {2560x1440, 2720x1481@241500Khz}
[ 175.577625] [drm] HBRx4 pass VS=0, PE=0
[ 293.823823] [drm] Rx Caps:
[ 293.952473] [drm] SADs count is: -2, don't need to read it
[ 293.957217] [drm] HBRx4 pass VS=0, PE=0
[ 293.957516] [drm] ASUS PB278: [Block 0]
[ 293.957520] [drm] ASUS PB278: [Block 1]
[ 293.957526] [drm] dc_link_detect: manufacturer_id = 6904, product_id = 27A3,
serial_number = 8C18, manufacture_week = 30, manufacture_year = 26,
display_name = ASUS PB278, speaker_flag = 0, audio_mode_count = 0
[ 293.958130] [drm] {2560x1440, 2720x1481@241500Khz}
As you see speaker_flag and audio_mode_count all zero and /proc/asound/<*>/eld*
info all empty:
[lakostis@lks HDMI]$ fgrep -r monitor eld*
eld#0.0:monitor_present 0
eld#0.1:monitor_present 0
eld#0.2:monitor_present 0
eld#0.3:monitor_present 0
eld#0.4:monitor_present 0
eld#0.5:monitor_present 0
glxinfo:
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org (0x1002)
Device: AMD Radeon (TM) R9 Fury Series (FIJI / DRM 3.23.0 /
4.14.0-lks-wks-alt10, LLVM 6.0.0) (0x7300)
Version: 17.3.3
Accelerated: yes
Video memory: 4060MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
Memory info (GL_ATI_meminfo):
VBO free memory - total: 4059 MB, largest block: 4059 MB
VBO free aux. memory - total: 4092 MB, largest block: 4092 MB
Texture free memory - total: 4059 MB, largest block: 4059 MB
Texture free aux. memory - total: 4092 MB, largest block: 4092 MB
Renderbuffer free memory - total: 4059 MB, largest block: 4059 MB
Renderbuffer free aux. memory - total: 4092 MB, largest block: 4092 MB
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 4060 MB
Total available memory: 8153 MB
Currently available dedicated video memory: 4059 MB
OpenGL vendor string: X.Org
OpenGL renderer string: AMD Radeon (TM) R9 Fury Series (FIJI / DRM 3.23.0 /
4.14.0-lks-wks-alt10, LLVM 6.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3
(git-80f5f27)
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 3.0 Mesa 17.3.3 (git-80f5f27)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.3.3 (git-80f5f27)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
Mesalib - 17.3.3
Kernel - 4.14.15 + DC patches till end of Oct 2017.
Module params for amdgpu:
$ cat /etc/modprobe.d/amdgpu.conf
# enable DRM extra debugging messages
#options drm debug=0x1e
options amdgpu si_support=0 dc=1 audio=1
options radeon si_support=1
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5888 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:[~2018-01-31 9:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 9:43 bugzilla-daemon [this message]
2018-01-31 9:44 ` [Bug 104880] No sound via DP on R9 Fury (4.14 + DC patches) bugzilla-daemon
2018-01-31 9:51 ` bugzilla-daemon
2018-01-31 15:39 ` bugzilla-daemon
2018-01-31 22:35 ` bugzilla-daemon
2018-01-31 22:45 ` bugzilla-daemon
2018-02-01 0:00 ` bugzilla-daemon
2018-02-01 0:02 ` bugzilla-daemon
2018-02-01 15:02 ` bugzilla-daemon
2018-02-01 15:31 ` [Bug 104880] No sound via DP on R9 Fury (4.15 + amd-staging-4.15 patches) bugzilla-daemon
2018-02-04 22:20 ` bugzilla-daemon
2018-03-21 22:29 ` [Bug 104880] No sound via DP on R9 Fury (4.16 + drm-next-4.17-wip) bugzilla-daemon
2019-11-19 8:29 ` 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-104880-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.