[Bug 237340] Unable to make HDMI sound works with HD630

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237340

alfredoFALK <alfredovogel at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alfredovogel at gmail.com

--- Comment #9 from alfredoFALK <alfredovogel at gmail.com> ---
Hi,
I also have this problem/bug on my ASUS H110T. I run 4 operating systems on
different hdd/sdd on this machine: Manjaro,Win10,macOS and freeBSD as
TridentOS.
All OS have a working HDMI sound connection except freeBSD.
Here are the two outputs from the standard commands requested by other websites
or forums :
--------------------------------------------------------
cat /dev/sndstat:trident-3675% cat /dev/sndstat
Installed devices:
pcm0: <Realtek ALC887 (Analog)> (play/rec)
pcm1: <Realtek ALC887 (Analog)> (play/rec)
pcm2: <Intel Kaby Lake (HDMI/DP 8ch)> (play) default
No devices installed from userspace.
-----------------------------------------------------------------------------
sysctl -a | grep snd.default: hw.snd.default_unit: 2
hw.snd.default_auto: 0
------------------------------------------------------------------------------
mixer
Mixer vol      is currently set to 100:100
Mixer pcm      is currently set to 100:100
Mixer speaker  is currently set to  74:74
Mixer line     is currently set to   1:1
Mixer mic      is currently set to  67:67
Mixer mix      is currently set to  74:74
Mixer rec      is currently set to  35:35
Mixer igain    is currently set to   0:0
----------------------------------------------------------------------------


  To get to this situation I did exactly the devices.hints line mentioned by
@Emrion on this bug report.
Nobody has a solution and it looks to me that the BSD community of developers
has no intention to find a solution! openBSD has definitely stated they are not
developing HDMI and freeBSD seems to feel the same!
Maybe somebody can prove me wrong! 
This bug has been dormant since May 2019, so my feeling is nobody is dealing
with it.
Thanks to anybody who can give some help with this issue!

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