From: James Cloos <cloos@jhcloos.com>
To: dri-devel@lists.freedesktop.org
Subject: HDMI Audio screwed up w/ recent kernels
Date: Thu, 22 Dec 2016 19:49:57 -0500 [thread overview]
Message-ID: <m3d1gj8o5m.fsf@jhcloos.com> (raw)
I haven't paid as close attention to Xorg issues sine the stroke last
year, and I hadn't needed to reboot the box in the living room in
several months.
When I did need to, I found that hdmi audio was unlistenable. It
sounded like it was mixed witht white noise.
If I boot vmlinuz-3.19.0 is works fine. I had compiled 4.1.0 and 4.5.0,
as well as its current default kernel, 4.9.0 (all from Linus' git). All
of those 4. kernels show the crappy audio.
In 4.9 I then tried switching to amdgpu. That did not help.
The box has a Kaveri apu (ChipID 0x1313).
Firmware is from linux-firmware.git and is compiled into the kernel via
CONFIG_EXTRA_FIRMWARE.
With radeon the kernel command line has: radeon.modeset=1 radeon.audio=1
With amdgpu I switched to: amdgpu.audio=1 amdgpu.exp_hw_support=1
Any thoughs on where to look?
I find it hard to believe that a bug like this could persist for so
long.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-12-23 0:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 0:49 James Cloos [this message]
2016-12-27 9:47 ` HDMI Audio screwed up w/ recent kernels Daniel Vetter
2016-12-27 17:17 ` James Cloos
2016-12-27 18:20 ` Daniel Vetter
2016-12-27 18:32 ` Bridgman, John
2016-12-28 19:43 ` James Cloos
2016-12-31 5:36 ` Alex Deucher
2016-12-31 7:55 ` James Cloos
2017-01-02 16:04 ` Alex Deucher
2017-01-02 17:11 ` James Cloos
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=m3d1gj8o5m.fsf@jhcloos.com \
--to=cloos@jhcloos.com \
--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.