From Newsgroup: alt.os.linux


I'm trying to find out why I'm getting no sound out the board's own
backpanel 1/8" audio Line-Out (green) port. AFAIK this port should
ALWAYS work! Also AFAIK there had been some driver delays but the 3
sound systems all seem to be driven now. BIOS just saus HD Audio and is 'Enabled' & in Suse Tumbleweed Yast reports:

Navi 31 HDMI/DP Audio
Drivers
Active: yes
modprobe: Yes
modules
modprobe snd_hda-intel

Rembrandt Radeon HD audio controller
Drivers
Active: yes
modprobe: Yes
modules
modprobe snd_hda-intel

Family 17h/19h/1ah HD Audio Controller
Drivers
Active: yes
modprobe: Yes
modules
modprobe snd_hda-intel


I don't even know what these all are, I mean which one does what
exactly? In linux plugging the headset into the rear port just gives me scratchy static blasts when I move the headset plug. So maybe the
(always shitty at best) mini receptacle is broken or desoldered?

The front panel (extension headers) headset port works fine.




--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 04/07/2025 03.58, bad sector wrote:

I'm trying to find out why I'm getting no sound out the board's own backpanel 1/8" audio Line-Out (green) port. AFAIK this port should
ALWAYS work! Also AFAIK there had been some driver delays but the 3
sound systems all seem to be driven now. BIOS just saus HD Audio and is 'Enabled' & in Suse Tumbleweed Yast reports:

Navi 31 HDMI/DP Audio
 Drivers
  Active: yes
  modprobe: Yes
 modules
  modprobe snd_hda-intel

Rembrandt Radeon HD audio controller
 Drivers
  Active: yes
  modprobe: Yes
 modules
  modprobe snd_hda-intel

Family 17h/19h/1ah HD Audio Controller
 Drivers
  Active: yes
  modprobe: Yes
 modules
  modprobe snd_hda-intel

I don't even know what these all are, I mean which one does what
exactly?

This is my guestimation:
Navi is your RDNA based Radeon card.
Family is your motherboards built in audio card
Rembrandt I guess is the audio in the Graphics provided by your CPU.

In linux plugging the headset into the rear port just gives me
scratchy static blasts when I move the headset plug. So maybe the
(always shitty at best) mini receptacle is broken or desoldered?

The front panel (extension headers) headset port works fine.

Some setups have had the issue that you either can use the ports in the
back or the front, not both at the same time, not sure if that is the
case for you.

Also things depends on what are you using in the pipewire/pulseaudio Analog/Digital vs Pro Audio profile. You should go with the Pro Audio nowadays.
--
//Aho

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Thu, 7/3/2025 9:58 PM, bad sector wrote:

I'm trying to find out why I'm getting no sound out the board's own backpanel 1/8" audio Line-Out (green) port. AFAIK this port should ALWAYS work! Also AFAIK there had been some driver delays but the 3 sound systems all seem to be driven now. BIOS just saus HD Audio and is 'Enabled' & in Suse Tumbleweed Yast reports:

Navi 31 HDMI/DP Audio
 Drivers
  Active: yes
  modprobe: Yes
 modules
  modprobe snd_hda-intel

Rembrandt Radeon HD audio controller
 Drivers
  Active: yes
  modprobe: Yes
 modules
  modprobe snd_hda-intel

Family 17h/19h/1ah HD Audio Controller
 Drivers
  Active: yes
  modprobe: Yes
 modules
  modprobe snd_hda-intel

I don't even know what these all are, I mean which one does what exactly?  In linux plugging the headset into the rear port just gives me scratchy static blasts when I move the headset plug. So maybe the (always shitty at best) mini receptacle is broken or desoldered?

The front panel (extension headers) headset port works fine.

some-serial-bus Bit-stuffed-audio-carriage
GPU Radeon HD audio controller -------------------- HDMI/DP Audio

HDAudio-serial (serial buses at low-megabit rates)
PCH-HDaudio (snd_hda-intel) -------------------- Realtek 1220


There seems to be some confusion with all the snd-hda-intel instances.
It should have been fixed in whatever kernel you are running. Details at bottom.

https://bugzilla.kernel.org/show_bug.cgi?id=218409

*******

The ALC 1220 is pretty weird. It has a bilingual interface.
It supports HDAUdio, but it also support an AMD SOC digital
interface (which might be why it is on your board).

The chip seems to have more pins than a conventional HDAUdio
CODEC. At powerup, a strap pin indicates whether the SOC interface
(System On A Chip) is to be used, or the conventional Intel HDAudio
is to be used.

https://www.igorslab.de/wp-content/uploads/2022/06/ALC1220_VB-DataSheet_0.3.pdf

It seems to have about the same resources inside. There should be a total
of eight stereo jacks of capability. Four are used for 7.1 audio.
The other four are used for front panel header interfaces and
whatever weirdness they want to package this week. Your manual shows five jacks, and some clever sharing.

A channel map has to be passed, via the driver or some other means.
Maybe there is an ACPI table with the info. I don't know how that
works. Usually the jacks are re-taskable (a FP Mic can drive Headphones).

And the presence detect of a connector, is via a side contact. Modern computer cases, by now, should have a FP mode where the side contacts work,
they are resistor encoded. Four front panel channels, the plugs cause
one of sixteen voltages to appear on a pin. An ADC inside the chip converts that to a four bit code, and from that, the chip knows which switch closures are present. A newly detected plug, can result in a "what did you just
plug in" response. This saved pins on the old 48 pin design.

Analog Devices had a scheme, where they measured the AC impedance of a
pin widget, and if it measured 32 ohms, they used the "headphone" determination.
If it measured 10K, maybe it was "computer speakers". RealTek doesn't
generally do that. They have to use whatever means they can think of, such
as asking you. In the past, an admission they were not Analog Devices,
would appear around page 150 of the datasheet :-) They can detect a plug
has been inserted, but they are unlikely to know what the plug is.

The Analog Devices documentation, declared that the impedance measurement of
a just-inserted jack, took three milliseconds or so (or some relatively short time).
I measured it. The "tone" placed on the jack, was present for a bit more than one second.
You cat would have been scared out of its socks, by the noise, if
your amp went up to 25 KHz.

The chip isn't too much of a squirrel, but in times past, the amount
of metadata to make this stuff work is just staggering. When it doesn't
work, where is my surprised face ? It needs a lot of tables, to code
up all the variations. And mistakes can be made.

The above kernel.org, seems to indicate one driver is getting
loaded, and there is some confusion after that happens about
what each driver instance uses for settings.

As for your feeling "I'm not very lucky on this audio issue", be
aware there are *multiple* busted audio solutions since your
last motherboard purchase. Including the laptops with the
"digital amp" inside it, where you get a notation on your
screen "speakers not ready". That's how you know you're screwed.
Analog speakers just work :-) That's how you know they're analog.
It's because they work.

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 2025-07-04 at 08:18 J.O. Aho wrote:

I'm trying to find out why I'm getting no sound out the board's own
backpanel 1/8" audio Line-Out (green) port. AFAIK this port should ALWAYS
work! […]
The front panel (extension headers) headset port works fine.

Some setups have had the issue that you either can use the ports in the back or the front, not both at the same time

Got one of these, running PulseAudio on openSUSE 15.4. Have to switch
between front and back ports using 'pacmd'.

First had to find the names to use:

$ pactl get-default-sink
alsa_output.pci-0000_00_1f.3.analog-stereo
$ pactl list sinks ## showing only relevant parts of the output ##
Sink #0
    […]
    Name: alsa_output.pci-0000_00_1f.3.analog-stereo
    […]
    Ports:
        analog-output-lineout: Line Out (type: Line, […])         analog-output-headphones: Headphones (type: Headphones, […])     Active Port: analog-output-headphones
    […]
$

Then wrote a script which checks the active port and switches to the other using command:

pacmd set-sink-port alsa_output.pci-0000_00_1f.3.analog-stereo analog-output-lineout

Have it sitting in the tray on XFCE's panel to be able toggle the output
with a single mouse click.

HTH


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 7/4/25 2:18 AM, J.O. Aho wrote:

On 04/07/2025 03.58, bad sector wrote:

I'm trying to find out why I'm getting no sound out the board's own
backpanel 1/8" audio Line-Out (green) port. AFAIK this port should
ALWAYS work! Also AFAIK there had been some driver delays but the 3
sound systems all seem to be driven now. BIOS just saus HD Audio and
is 'Enabled' & in Suse Tumbleweed Yast reports:

Navi 31 HDMI/DP Audio
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel

Rembrandt Radeon HD audio controller
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel

Family 17h/19h/1ah HD Audio Controller
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel


I don't even know what these all are, I mean which one does what exactly?

This is my guestimation:
Navi is your RDNA based Radeon card.
Family is your motherboards built in audio card
Rembrandt I guess is the audio in the Graphics provided by your CPU.

In linux plugging the headset into the rear port just gives me
scratchy static blasts when I move the headset plug. So maybe the
(always shitty at best) mini receptacle is broken or desoldered?

The front panel (extension headers) headset port works fine.

Some setups have had the issue that you either can use the ports in the
back or the front, not both at the same time, not sure if that is the
case for you.

I use the same mini stereo cable to feed my headset so either it's in
the front panel 'headset' receptacle OR the rear motherboard panel
Line-Out one. Would there be any point in disconnectiong the front panel completely from the board audio pinout? Wouldn't make much sense having
to to do that, I rather suspect the board panel Line-Out receptackle is
dead, it's the most plausible cause.

Also things depends on what are you using in the pipewire/pulseaudio Analog/Digital vs Pro Audio profile. You should go with the Pro Audio nowadays.

I have Proaudio as selection for all 3 in PAVU Configuration tab

Configuration:
Nav31: Proaudio
Rembrandt: Proaudio
Family17: Proaudio

(doing the dialog backward because Config setup affectrs the previous tabs)

Input devices:
Family 17 Pro
Family 17 Pro2

Output devices: (all enabled)
Rembrandt Radeon HD Audio Controler Pro
Rembrandt Radeon HD Audio Controler Pro7
Rembrandt Radeon HD Audio Controler Pro8
Family17 HD Audio Controler Pro
Navi31 HDMI/DP Audio Pro
Navi31 HDMI/DP Audio Pro7
Navi31 HDMI/DP Audio Pro8
Navi31 HDMI/DP Audio Pro9


Recording tab: nothing

Playback tab:
System Sounds

I put the headset cable from the fromt panel, plug it into ther bopard Liner-Out = no sound. I do get a noise when partly insetred, goes silent
when fully in.



--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Sat, 7/5/2025 8:32 PM, bad sector wrote:

On 7/4/25 2:18 AM, J.O. Aho wrote:

On 04/07/2025 03.58, bad sector wrote:

I'm trying to find out why I'm getting no sound out the board's own backpanel 1/8" audio Line-Out (green) port. AFAIK this port should ALWAYS work! Also AFAIK there had been some driver delays but the 3 sound systems all seem to be driven now. BIOS just saus HD Audio and is 'Enabled' & in Suse Tumbleweed Yast reports:

Navi 31 HDMI/DP Audio
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel

Rembrandt Radeon HD audio controller
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel

Family 17h/19h/1ah HD Audio Controller
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel


I don't even know what these all are, I mean which one does what exactly? >>

This is my guestimation:
Navi is your RDNA based Radeon card.
Family is your motherboards built in audio card
Rembrandt I guess is the audio in the Graphics provided by your CPU.

In linux plugging the headset into the rear port just gives me scratchy static blasts when I move the headset plug. So maybe the (always shitty at best) mini receptacle is broken or desoldered?

The front panel (extension headers) headset port works fine.

Some setups have had the issue that you either can use the ports in the back or the front, not both at the same time, not sure if that is the case for you.

I use the same mini stereo cable to feed my headset so either it's in the front panel 'headset' receptacle OR the rear motherboard panel Line-Out one. Would there be any point in disconnectiong the front panel completely from the board audio pinout? Wouldn't make much sense having to to do that, I rather suspect the board panel Line-Out receptackle is dead, it's the most plausible cause.

Also things depends on what are you using in the pipewire/pulseaudio Analog/Digital vs Pro Audio profile. You should go with the Pro Audio nowadays.

I have Proaudio as selection for all 3 in PAVU Configuration tab

Configuration:
 Nav31: Proaudio
 Rembrandt: Proaudio
 Family17: Proaudio

(doing the dialog backward because Config setup affectrs the previous tabs)

Input devices:
 Family 17 Pro
 Family 17 Pro2

Output devices: (all enabled)
 Rembrandt Radeon HD Audio Controler Pro
 Rembrandt Radeon HD Audio Controler Pro7
 Rembrandt Radeon HD Audio Controler Pro8
 Family17 HD Audio Controler Pro
 Navi31 HDMI/DP Audio Pro
 Navi31 HDMI/DP Audio Pro7
 Navi31 HDMI/DP Audio Pro8
 Navi31 HDMI/DP Audio Pro9

Recording tab: nothing

Playback tab:
 System Sounds

I put the headset cable from the front panel, plug it into

the board Line-Out = no sound. I do get a noise when partly
inserted, goes silent when fully in.


That might be similar to plugging TRRS male into TRS female,
but looking at the manual, I did not get any sense whatsoever,
of any Creative Audio shenanigans. Some equipment use stupid mixtures
of TRS and TRRS, just to annoy people.

I don't expect it's anything like that, and it is some sort of
software issue.

I would try an "alternate test environment", evaluate the hardware,
hear that it all works, then go back to trying to figure out
the sound config details on the current setup.

I don't think the fine details of the ALC 1220 are the root cause here.
But you need to try any sort of alternate driver-bringup to evaluate
whether it can ever be made to work.

The FP header on the board, and the computer case, they have "modes".
The case FP can be "AC'97 era with looped Line_out wiring" or
it can be declared as having "HDaudio jacks with side-contact
presence detect". Sometimes this is implemented as two separate case
looms for AC'97 or HDAudio usage.

The total of eight stereo channels on the chip, drive two encoder-trees
of four jacks each, into the two presence detect signals on the side
of the chip. In the HDaudio era, there is independence between Line_out
on the back and FP Headphone and FP Microphone. Only the usage of some
AC'97 setup could short something together, and there are likely
instructions in the manual for "not doing certain things to
aggravate the situation". For example, the two blue shorting jumpers
for an AC'97 header would be missing on a modern machine, to prevent
a user from getting themselves into trouble.

To do a good job, a builder has to read both the motherboard
manual, and the instructions that come with the case (such as
they are). Not all the manuals are of equal value to a builder.

Phantek - no manual entry for audio, FP cable is (marked) HDAudio only (Presence# grounded)

Asus Mobo - FP wiring indicated as HDAudio format, and wiring matches
my memory of the signal purpose.

which is different than some older computer cases, which have a AC'97 loom
for FP in the case, as well as an HDAudio loom for FP, and you only
connect the "right one" for the vintage of motherboard. A really old motherboard, you would use the AC'97 loom after removing the two
blue shorting plugs from the AC'97 motherboard.

Your setup is new enough, it should be HDAudio on both ends and
pretty hard to foul up unless the header was shifted. And you can't
shift the header, because it has a keying pin!

Some motherboards, when you flip them over, they have white paper
"arrows" adhered to the PCB, marking "places of potential short circuit".
You are supposed to pay attention to the arrows, and remove the case
tray standoffs that correspond to the trouble-arrow indicator.

On the A7N8X Deluxe, of the nine standoffs on the tray, one must
be removed, or it shorts out the Left channel of LineOut :-)
This is not marked on the PCB. the usage of the paper-arrows is
a new thing.

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 7/6/25 4:49 AM, Paul wrote:

On Sat, 7/5/2025 8:32 PM, bad sector wrote:

On 7/4/25 2:18 AM, J.O. Aho wrote:

On 04/07/2025 03.58, bad sector wrote:

I'm trying to find out why I'm getting no sound out the board's own backpanel 1/8" audio Line-Out (green) port. AFAIK this port should ALWAYS work! Also AFAIK there had been some driver delays but the 3 sound systems all seem to be driven now. BIOS just saus HD Audio and is 'Enabled' & in Suse Tumbleweed Yast reports:

Navi 31 HDMI/DP Audio
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel

Rembrandt Radeon HD audio controller
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel

Family 17h/19h/1ah HD Audio Controller
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel


I don't even know what these all are, I mean which one does what exactly? >>>

This is my guestimation:
Navi is your RDNA based Radeon card.
Family is your motherboards built in audio card
Rembrandt I guess is the audio in the Graphics provided by your CPU.

In linux plugging the headset into the rear port just gives me scratchy static blasts when I move the headset plug. So maybe the (always shitty at best) mini receptacle is broken or desoldered?

The front panel (extension headers) headset port works fine.

Some setups have had the issue that you either can use the ports in the back or the front, not both at the same time, not sure if that is the case for you.

I use the same mini stereo cable to feed my headset so either it's in the front panel 'headset' receptacle OR the rear motherboard panel Line-Out one. Would there be any point in disconnectiong the front panel completely from the board audio pinout? Wouldn't make much sense having to to do that, I rather suspect the board panel Line-Out receptackle is dead, it's the most plausible cause.

Also things depends on what are you using in the pipewire/pulseaudio Analog/Digital vs Pro Audio profile. You should go with the Pro Audio nowadays.

I have Proaudio as selection for all 3 in PAVU Configuration tab

Configuration:
 Nav31: Proaudio
 Rembrandt: Proaudio
 Family17: Proaudio

(doing the dialog backward because Config setup affectrs the previous tabs) >>
Input devices:
 Family 17 Pro
 Family 17 Pro2

Output devices: (all enabled)
 Rembrandt Radeon HD Audio Controler Pro
 Rembrandt Radeon HD Audio Controler Pro7
 Rembrandt Radeon HD Audio Controler Pro8
 Family17 HD Audio Controler Pro
 Navi31 HDMI/DP Audio Pro
 Navi31 HDMI/DP Audio Pro7
 Navi31 HDMI/DP Audio Pro8
 Navi31 HDMI/DP Audio Pro9


Recording tab: nothing

Playback tab:
 System Sounds

I put the headset cable from the front panel, plug it into

the board Line-Out = no sound. I do get a noise when partly
inserted, goes silent when fully in.

That might be similar to plugging TRRS male into TRS female,
but looking at the manual, I did not get any sense whatsoever,
of any Creative Audio shenanigans. Some equipment use stupid mixtures
of TRS and TRRS, just to annoy people.

I don't expect it's anything like that, and it is some sort of
software issue.

I would try an "alternate test environment"

That's a huge field! :-)

I spent two freakin' hours pissing around with it and composing a
response which thunderbird then just LOST so I won't repeat it all. I
*think* it boils down to that elusive note I once read but cannot find
anymore which said something like 'when using the Adv-Audio header
adv-audio will not b e available' (presumably elsewhere). Anyone who can
find that note AND is expert enough to reveal its secrets is welcome to
do so. In addition as far as VLC goes I had to set audio prefs to ALSA
and Pipewire to make VLC produce sound. If I reconnect the panel header
I lose the Line-Out sound again.

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Sun, 7/6/2025 8:09 PM, bad sector wrote:

On 7/6/25 4:49 AM, Paul wrote:

On Sat, 7/5/2025 8:32 PM, bad sector wrote:

On 7/4/25 2:18 AM, J.O. Aho wrote:

On 04/07/2025 03.58, bad sector wrote:

I'm trying to find out why I'm getting no sound out the board's own backpanel 1/8" audio Line-Out (green) port. AFAIK this port should ALWAYS work! Also AFAIK there had been some driver delays but the 3 sound systems all seem to be driven now. BIOS just saus HD Audio and is 'Enabled' & in Suse Tumbleweed Yast reports:

Navi 31 HDMI/DP Audio
   Drivers
    Active: yes
    modprobe: Yes
   modules
    modprobe snd_hda-intel

Rembrandt Radeon HD audio controller
   Drivers
    Active: yes
    modprobe: Yes
   modules
    modprobe snd_hda-intel

Family 17h/19h/1ah HD Audio Controller
   Drivers
    Active: yes
    modprobe: Yes
   modules
    modprobe snd_hda-intel


I don't even know what these all are, I mean which one does what exactly? >>>>

This is my guestimation:
Navi is your RDNA based Radeon card.
Family is your motherboards built in audio card
Rembrandt I guess is the audio in the Graphics provided by your CPU.

In linux plugging the headset into the rear port just gives me scratchy static blasts when I move the headset plug. So maybe the (always shitty at best) mini receptacle is broken or desoldered?

The front panel (extension headers) headset port works fine.

Some setups have had the issue that you either can use the ports in the back or the front, not both at the same time, not sure if that is the case for you.

I use the same mini stereo cable to feed my headset so either it's in the front panel 'headset' receptacle OR the rear motherboard panel Line-Out one. Would there be any point in disconnectiong the front panel completely from the board audio pinout? Wouldn't make much sense having to to do that, I rather suspect the board panel Line-Out receptackle is dead, it's the most plausible cause.

Also things depends on what are you using in the pipewire/pulseaudio Analog/Digital vs Pro Audio profile. You should go with the Pro Audio nowadays.

I have Proaudio as selection for all 3 in PAVU Configuration tab

Configuration:
  Nav31: Proaudio
  Rembrandt: Proaudio
  Family17: Proaudio

(doing the dialog backward because Config setup affectrs the previous tabs) >>>
Input devices:
  Family 17 Pro
  Family 17 Pro2

Output devices: (all enabled)
  Rembrandt Radeon HD Audio Controler Pro
  Rembrandt Radeon HD Audio Controler Pro7
  Rembrandt Radeon HD Audio Controler Pro8
  Family17 HD Audio Controler Pro
  Navi31 HDMI/DP Audio Pro
  Navi31 HDMI/DP Audio Pro7
  Navi31 HDMI/DP Audio Pro8
  Navi31 HDMI/DP Audio Pro9


Recording tab: nothing

Playback tab:
  System Sounds

I put the headset cable from the front panel, plug it into

   the board Line-Out = no sound. I do get a noise when partly
   inserted, goes silent when fully in.

That might be similar to plugging TRRS male into TRS female,
but looking at the manual, I did not get any sense whatsoever,
of any Creative Audio shenanigans. Some equipment use stupid mixtures
of TRS and TRRS, just to annoy people.

I don't expect it's anything like that, and it is some sort of
software issue.

I would try an "alternate test environment"

That's a huge field!  :-)

I spent two freakin' hours pissing around with it and composing a response which thunderbird then just LOST so I won't repeat it all. I *think* it boils down to that elusive note I once read but cannot find anymore which said something like 'when using the Adv-Audio header adv-audio will not b e available' (presumably elsewhere). Anyone who can find that note AND is expert enough to reveal its secrets is welcome to do so. In addition as far as VLC goes I had to set audio prefs to ALSA and Pipewire to make VLC produce sound. If I reconnect the panel header I lose the Line-Out sound again.

OK, maybe the Headphone on the case, when the FP cable is
connected, is always asserting the side contact for Headphones,
causing the driver to stop driving Line-Out on the IO plate.

https://www.eevblog.com/forum/projects/ac97-vs-hd-audio-computer-case-frontpanel-audio-i-feel-clueless/

Down near the end of this document, is the resistor tree for
the two encoded side contact signals on the HDAudio. The HDAudio has
a total of eight jacks possible, built as two resistor trees.

https://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/high-definition-audio-specification.pdf

Here is my summary picture:

[Picture]

https://i.postimg.cc/HWJGdpP4/HDAudio-standard-front-panel-summary.gif

One port is for Headphone. One port is for Microphone.

Some devices use a single jack, a TRRS, which is headphones+mono-mike as
one of those annoyance things. But motherboards don't do that. Mobile
devices might.

Some laptops do coaxial TOSLink and LineOut on the same jack, and
you learn this when you stare into the Headphone jack and you can
see red colored light :-) Again, while motherboards have gained
a separate TOSLink hole (with the red light), no attempt has been
made to squeeze the function into one jack-hole.

The Windows driver, likely supports both Line-Out as well as HeadPhone,
running in 32 ohm mode at the same time. I don't know if the Linux
driver includes that, as there may be a need to have a GUI selector
of some sort to enable it.

Paul
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 7/6/25 11:33 PM, Paul wrote:

On Sun, 7/6/2025 8:09 PM, bad sector wrote:

On 7/6/25 4:49 AM, Paul wrote:

On Sat, 7/5/2025 8:32 PM, bad sector wrote:

On 7/4/25 2:18 AM, J.O. Aho wrote:

On 04/07/2025 03.58, bad sector wrote:

I'm trying to find out why I'm getting no sound out the board's own backpanel 1/8" audio Line-Out (green) port. AFAIK this port should ALWAYS work! Also AFAIK there had been some driver delays but the 3 sound systems all seem to be driven now. BIOS just saus HD Audio and is 'Enabled' & in Suse Tumbleweed Yast reports:

Navi 31 HDMI/DP Audio
   Drivers
    Active: yes
    modprobe: Yes
   modules
    modprobe snd_hda-intel

Rembrandt Radeon HD audio controller
   Drivers
    Active: yes
    modprobe: Yes
   modules
    modprobe snd_hda-intel

Family 17h/19h/1ah HD Audio Controller
   Drivers
    Active: yes
    modprobe: Yes
   modules
    modprobe snd_hda-intel


I don't even know what these all are, I mean which one does what exactly?

This is my guestimation:
Navi is your RDNA based Radeon card.
Family is your motherboards built in audio card
Rembrandt I guess is the audio in the Graphics provided by your CPU. >>>>>

In linux plugging the headset into the rear port just gives me scratchy static blasts when I move the headset plug. So maybe the (always shitty at best) mini receptacle is broken or desoldered?

The front panel (extension headers) headset port works fine.

Some setups have had the issue that you either can use the ports in the back or the front, not both at the same time, not sure if that is the case for you.

I use the same mini stereo cable to feed my headset so either it's in the front panel 'headset' receptacle OR the rear motherboard panel Line-Out one. Would there be any point in disconnectiong the front panel completely from the board audio pinout? Wouldn't make much sense having to to do that, I rather suspect the board panel Line-Out receptackle is dead, it's the most plausible cause.

Also things depends on what are you using in the pipewire/pulseaudio Analog/Digital vs Pro Audio profile. You should go with the Pro Audio nowadays.

I have Proaudio as selection for all 3 in PAVU Configuration tab

Configuration:
  Nav31: Proaudio
  Rembrandt: Proaudio
  Family17: Proaudio

(doing the dialog backward because Config setup affectrs the previous tabs)

Input devices:
  Family 17 Pro
  Family 17 Pro2

Output devices: (all enabled)
  Rembrandt Radeon HD Audio Controler Pro
  Rembrandt Radeon HD Audio Controler Pro7
  Rembrandt Radeon HD Audio Controler Pro8
  Family17 HD Audio Controler Pro
  Navi31 HDMI/DP Audio Pro
  Navi31 HDMI/DP Audio Pro7
  Navi31 HDMI/DP Audio Pro8
  Navi31 HDMI/DP Audio Pro9


Recording tab: nothing

Playback tab:
  System Sounds

I put the headset cable from the front panel, plug it into

   the board Line-Out = no sound. I do get a noise when partly
   inserted, goes silent when fully in.

That might be similar to plugging TRRS male into TRS female,
but looking at the manual, I did not get any sense whatsoever,
of any Creative Audio shenanigans. Some equipment use stupid mixtures
of TRS and TRRS, just to annoy people.

I don't expect it's anything like that, and it is some sort of
software issue.

I would try an "alternate test environment"

That's a huge field!  :-)

I spent two freakin' hours pissing around with it and composing a response which thunderbird then just LOST so I won't repeat it all. I *think* it boils down to that elusive note I once read but cannot find anymore which said something like 'when using the Adv-Audio header adv-audio will not b e available' (presumably elsewhere). Anyone who can find that note AND is expert enough to reveal its secrets is welcome to do so. In addition as far as VLC goes I had to set audio prefs to ALSA and Pipewire to make VLC produce sound. If I reconnect the panel header I lose the Line-Out sound again.

OK, maybe the Headphone on the case, when the FP cable is
connected, is always asserting the side contact for Headphones,
causing the driver to stop driving Line-Out on the IO plate.

https://www.eevblog.com/forum/projects/ac97-vs-hd-audio-computer-case-frontpanel-audio-i-feel-clueless/

Down near the end of this document, is the resistor tree for
the two encoded side contact signals on the HDAudio. The HDAudio has
a total of eight jacks possible, built as two resistor trees.

https://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/high-definition-audio-specification.pdf

Here is my summary picture:

[Picture]

https://i.postimg.cc/HWJGdpP4/HDAudio-standard-front-panel-summary.gif

Thanks, as usual you come up with the 'expert enough' explanation. But
why would Asus do something this stupid? I mean there are times when I
might want to hear an overwhelming guitar track in the headphone (remote panel) while ALSO feeding the speakers (board Line-Out) at reduced
radiation to let everyone know 'don't fucking bother me!'. Sometimes I
wonder where their designers got their diplomas if any (and not just
Asus either).

One port is for Headphone. One port is for Microphone.

Some devices use a single jack, a TRRS, which is headphones+mono-mike as
one of those annoyance things. But motherboards don't do that. Mobile
devices might.

Some laptops do coaxial TOSLink and LineOut on the same jack, and
you learn this when you stare into the Headphone jack and you can
see red colored light :-) Again, while motherboards have gained
a separate TOSLink hole (with the red light), no attempt has been
made to squeeze the function into one jack-hole.

The Windows driver, likely supports both Line-Out as well as HeadPhone, running in 32 ohm mode at the same time. I don't know if the Linux
driver includes that, as there may be a need to have a GUI selector
of some sort to enable it.

Paul

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Mon, 7/7/2025 7:38 AM, bad sector wrote:

Here is my summary picture:

    [Picture]

     https://i.postimg.cc/HWJGdpP4/HDAudio-standard-front-panel-summary.gif

Thanks, as usual you come up with the 'expert enough' explanation. But why would Asus do something this stupid? I mean there are times when I might want to hear an overwhelming guitar track in the headphone (remote panel) while ALSO feeding the speakers (board Line-Out) at reduced radiation to let everyone know 'don't fucking bother me!'. Sometimes I wonder where their designers got their diplomas if any (and not  just Asus either).

It's not on Asus this time.

The design is an Intel specification. The PDF comes from Intel.
Asus just follows it. The purpose of having Intel act as a pseudo
PC97 controller, is to make all the hardware companies do things
that are compatible with one another.

For example, HDAudio Codecs were footprint compatible. If you
were in the factory, and you ran out of Realtek 48 pin QFP, you
could look around and find something that solders in the same spot.
And have multi-sourcing.

In AC'97 days, the Line-Out signal did double-duty. If could
drive Line-Out. It could drive Headphones front panel jack.
It did not tend to drive both, because the *standard* of the
time, steered the output. If you plugged in the Headphone jack,
that actually (via switches), disconnected the Line-Out on the
back I/O plate. This is why, by default, a new AC'97 motherboard
came with two blue jumpers to take the place of the FP cable
in the case. It provided continuity so the Line-Out at least
worked by default. When you removed the two blue jumpers
and plugged in the AC'97 FP cable, then the either-or behavior
was in place, and plugging in front HeadPhones, disabled Line-Out.

When Intel was thinking about the HDAudio era, their initial
thought was

"We will implement this feature in software"

In other words, when the jack sense detected HeadPhones in the front,
the driver would disable Line-Out. That was their initial thought.
This got rid of the need for special jacks to mute the Line-Out.

Then later, someone else said:

"Wouldn't it be cool if we could drive Line-Out and HeadPhones
separately, with no Mute feature implied"

With an ASIO driver, in principle you could drive separate signals
to the two jacks. This would allow, say, driving a set of speakers
in the next room, for someone.

I've not seen a GUI selector or driving software which gets
the best out of the hardware. All I can tell you, is the spec
sheets started carrying information about how many boost channels
(32 ohms) could be operated at the same time. It seems to be
an artificial limitation, and more about aligning with the
concept of two separate music sessions, than anything else.

The Zalman 5.1 headphones (three transducers in each ear cup),
it really wanted three 32-ohn stereo channels, to drive the
transducers. But we never got there, as no HDAudio will
drive three of the 32 ohm jack outputs at the same time.
Ports without boost, only drive 600 ohm loads and
cannot drive "speaker cones" directly (the tiny transducers
in the ear cups). Thus the Zalman always needed an external
buffer amp, to get enough drive to run all the cones. The
hardware industry did not feel obliged to fix that.

Paul

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 7/7/25 9:15 PM, Paul wrote:

On Mon, 7/7/2025 7:38 AM, bad sector wrote:

Here is my summary picture:

    [Picture]

     https://i.postimg.cc/HWJGdpP4/HDAudio-standard-front-panel-summary.gif

Thanks, as usual you come up with the 'expert enough' explanation. But why would Asus do something this stupid? I mean there are times when I might want to hear an overwhelming guitar track in the headphone (remote panel) while ALSO feeding the speakers (board Line-Out) at reduced radiation to let everyone know 'don't fucking bother me!'. Sometimes I wonder where their designers got their diplomas if any (and not  just Asus either).

It's not on Asus this time.

The design is an Intel specification. The PDF comes from Intel.
Asus just follows it. The purpose of having Intel act as a pseudo
PC97 controller, is to make all the hardware companies do things
that are compatible with one another.

For example, HDAudio Codecs were footprint compatible. If you
were in the factory, and you ran out of Realtek 48 pin QFP, you
could look around and find something that solders in the same spot.
And have multi-sourcing.

In AC'97 days, the Line-Out signal did double-duty. If could
drive Line-Out. It could drive Headphones front panel jack.
It did not tend to drive both, because the *standard* of the
time, steered the output. If you plugged in the Headphone jack,
that actually (via switches), disconnected the Line-Out on the
back I/O plate. This is why, by default, a new AC'97 motherboard
came with two blue jumpers to take the place of the FP cable
in the case. It provided continuity so the Line-Out at least
worked by default. When you removed the two blue jumpers
and plugged in the AC'97 FP cable, then the either-or behavior
was in place, and plugging in front HeadPhones, disabled Line-Out.

When Intel was thinking about the HDAudio era, their initial
thought was

"We will implement this feature in software"

In other words, when the jack sense detected HeadPhones in the front,
the driver would disable Line-Out. That was their initial thought.
This got rid of the need for special jacks to mute the Line-Out.

Then later, someone else said:

"Wouldn't it be cool if we could drive Line-Out and HeadPhones
separately, with no Mute feature implied"

With an ASIO driver, in principle you could drive separate signals
to the two jacks. This would allow, say, driving a set of speakers
in the next room, for someone.

I've not seen a GUI selector or driving software which gets
the best out of the hardware. All I can tell you, is the spec
sheets started carrying information about how many boost channels
(32 ohms) could be operated at the same time. It seems to be
an artificial limitation, and more about aligning with the
concept of two separate music sessions, than anything else.

The Zalman 5.1 headphones (three transducers in each ear cup),
it really wanted three 32-ohn stereo channels, to drive the
transducers. But we never got there, as no HDAudio will
drive three of the 32 ohm jack outputs at the same time.
Ports without boost, only drive 600 ohm loads and
cannot drive "speaker cones" directly (the tiny transducers
in the ear cups). Thus the Zalman always needed an external
buffer amp, to get enough drive to run all the cones. The
hardware industry did not feel obliged to fix that.

Paul

In the two wifi headphones I use this may not be an issue... with my
wired earbuds, yes. Ask me how come I'm not surprised that no designer,
Intel or othertel, ever sat down with RealWorld musicians and such to
find out what the RealWorld needs might be. One communication-arts
lecture I attended covered the topic of composing in the globalized multilingual, multi-cultural, auto-translated ether and how those
guiding principles also applied to interface design and by extension all design. For brevity I'll cover only the interfacing challenges which
apply to documentation as well. You sit down with test subjects and run
them through the hoops that be ...UNTIL you get no more questions from
them anymore. THAT's when your design or composition is ready for
release and not before. That was circa 1964 for crissake, it seems like
fewer people are aware of it today than were then.

About those Zalmans, I suppose the 3 speaker design was a way to bring surroundsound to headphones? I've been using $ennhei$er wirele$$ ever
since a very lengthy and very productive exchange with one of their
former research engineers, the products themselves have probably been 'orientalized' a lot since the old days but they still give excellent
tone spectrum and even more importantly no 'doctored' bass (their
Achilles' heel being interference with my router, they keep stepping on
each other at times).



--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 7/4/25 7:52 AM, marrgol wrote:

On 2025-07-04 at 08:18 J.O. Aho wrote:

I'm trying to find out why I'm getting no sound out the board's own
backpanel 1/8" audio Line-Out (green) port. AFAIK this port should ALWAYS >>> work! […]
The front panel (extension headers) headset port works fine.

Some setups have had the issue that you either can use the ports in the back >> or the front, not both at the same time

Got one of these, running PulseAudio on openSUSE 15.4. Have to switch between front and back ports using 'pacmd'.

First had to find the names to use:

$ pactl get-default-sink
alsa_output.pci-0000_00_1f.3.analog-stereo
$ pactl list sinks ## showing only relevant parts of the output ##
Sink #0
    […]
    Name: alsa_output.pci-0000_00_1f.3.analog-stereo
    […]
    Ports:
        analog-output-lineout: Line Out (type: Line, […])
        analog-output-headphones: Headphones (type: Headphones, […])
    Active Port: analog-output-headphones
    […]
$

Then wrote a script which checks the active port and switches to the other using command:

pacmd set-sink-port alsa_output.pci-0000_00_1f.3.analog-stereo analog-output-lineout

Have it sitting in the tray on XFCE's panel to be able toggle the output
with a single mouse click.

HTH

Eventually it will help but I gotta be 'out of ground' first! I do
things like 1-click scripts in the panel in KDE & XFCE but I first need
to tame this audio whorehouse: find out which and how to kill off.


Right now I have pipewire in charge I think and using the board's
backpanel audio prts (onboard [adv] audio header not connected to remote panel).



~ pactl get-default-sink

alsa_output.pci-0000_79_00.6.pro-output-0



~ pactl list sinks

Sink #809
State: IDLE
Name: alsa_output.pci-0000_79_00.6.pro-output-0
Description: Family 17h/19h/1ah HD Audio Controller Pro
Driver: PipeWire
Sample Specification: s32le 2ch 48000Hz
Channel Map: aux0,aux1
Owner Module: 4294967295
Mute: no
Volume: aux0: 65536 / 100% / 0.00 dB,
aux1: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-0000_79_00.6.pro-output-0.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY
Properties:
alsa.card = "2"
alsa.card_name = "HD-Audio Generic"
alsa.class = "generic"
alsa.components = "HDA:10ec1168,1043886b,00100101"
alsa.device = "0"
alsa.driver_name = "snd_hda_intel"
alsa.id = "ALC1220 Analog"
alsa.long_card_name = "HD-Audio Generic at 0xdcf80000
irq 129"
alsa.mixer_name = "Realtek ALC1220"
alsa.name = "ALC1220 Analog"
alsa.resolution_bits = "32"
alsa.subclass = "generic-mix"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.sync.id = "00000000:00000000:00000000:00000000"
api.alsa.card.longname = "HD-Audio Generic at
0xdcf80000 irq 129"
api.alsa.card.name = "HD-Audio Generic"
api.alsa.path = "hw:2,0"
api.alsa.pcm.card = "2"
api.alsa.pcm.stream = "playback"
audio.channels = "2"
audio.position = "AUX0,AUX1"
card.profile.device = "1"
clock.name = "api.alsa.2"
device.api = "alsa"
device.class = "sound"
device.icon_name = "audio-card-analog"
device.id = "43"
device.profile.description = "Pro"
device.profile.name = "pro-output-0"
device.profile.pro = "true"
device.routes = "0"
factory.name = "api.alsa.pcm.sink"
media.class = "Audio/Sink"
device.description = "Family 17h/19h/1ah HD Audio
Controller"
node.name = "alsa_output.pci-0000_79_00.6.pro-output-0"
node.nick = "ALC1220 Analog"
node.pause-on-idle = "false"
object.path = "alsa:acp:Generic_1:1:playback"
port.group = "playback"
priority.driver = "1500"
priority.session = "1500"
factory.id = "19"
clock.quantum-limit = "8192"
client.id = "40"
node.driver = "true"
node.loop.name = "data-loop.0"
library.name = "audioconvert/libspa-audioconvert"
object.id = "116"
object.serial = "809"
node.max-latency = "16384/48000"
api.alsa.period-size = "1024"
api.alsa.period-num = "32"
api.alsa.headroom = "0"
api.acp.auto-port = "false"
api.acp.auto-profile = "false"
api.alsa.card = "2"
api.alsa.split-enable = "true"
api.alsa.use-acp = "true"
api.dbus.ReserveDevice1 = "Audio2"
api.dbus.ReserveDevice1.Priority = "-20"
device.bus = "pci"
device.bus_path = "pci-0000:79:00.6"
device.enum.api = "udev"
device.name = "alsa_card.pci-0000_79_00.6"
device.nick = "HD-Audio Generic"
device.plugged.usec = "14780236"
device.product.id = "0x15e3"
device.product.name = "Family 17h/19h/1ah HD Audio Controller"
device.subsystem = "sound"
sysfs.path = "/devices/pci0000:00/0000:00:08.1/0000:79:00.6/sound/card2"
device.vendor.id = "0x1022"
device.vendor.name = "Advanced Micro Devices, Inc. [AMD]"
spa.object.id = "6"
device.string = "2"
Formats:
pcm

Sink #928
State: IDLE
Name: alsa_output.pci-0000_03_00.1.pro-output-3
Description: Navi 31 HDMI/DP Audio Pro
Driver: PipeWire
Sample Specification: s32le 2ch 48000Hz
Channel Map: aux0,aux1
Owner Module: 4294967295
Mute: no
Volume: aux0: 65536 / 100% / 0.00 dB,
aux1: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-0000_03_00.1.pro-output-3.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY
Properties:
alsa.card = "0"
alsa.card_name = "HDA ATI HDMI"
alsa.class = "generic"
alsa.components = "HDA:1002aa01,00aa0100,00100800"
alsa.device = "3"
alsa.driver_name = "snd_hda_intel"
alsa.id = "HDMI 0"
alsa.long_card_name = "HDA ATI HDMI at 0xdd720000 irq 127"
alsa.mixer_name = "ATI R6xx HDMI"
alsa.name = "BenQ EX321UX"
alsa.resolution_bits = "32"
alsa.subclass = "generic-mix"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.sync.id = "00000000:00000000:00000000:00000000"
api.alsa.card.longname = "HDA ATI HDMI at 0xdd720000
irq 127"
api.alsa.card.name = "HDA ATI HDMI"
api.alsa.path = "hw:0,3"
api.alsa.pcm.card = "0"
api.alsa.pcm.stream = "playback"
audio.channels = "2"
audio.position = "AUX0,AUX1"
card.profile.device = "0"
clock.name = "api.alsa.0"
device.api = "alsa"
device.class = "sound"
device.icon_name = "audio-card-analog"
device.id = "41"
device.profile.description = "Pro"
device.profile.name = "pro-output-3"
device.profile.pro = "true"
device.routes = "0"
factory.name = "api.alsa.pcm.sink"
media.class = "Audio/Sink"
device.description = "Navi 31 HDMI/DP Audio"
node.name = "alsa_output.pci-0000_03_00.1.pro-output-3"
node.nick = "BenQ EX321UX"
node.pause-on-idle = "false"
object.path = "alsa:acp:HDMI:0:playback"
port.group = "playback"
priority.driver = "1196"
priority.session = "1196"
factory.id = "19"
clock.quantum-limit = "8192"
client.id = "40"
node.driver = "true"
node.loop.name = "data-loop.0"
library.name = "audioconvert/libspa-audioconvert"
object.id = "193"
object.serial = "928"
node.max-latency = "16384/48000"
api.alsa.period-size = "1024"
api.alsa.period-num = "32"
api.alsa.headroom = "0"
api.acp.auto-port = "false"
api.acp.auto-profile = "false"
api.alsa.card = "0"
api.alsa.split-enable = "true"
api.alsa.use-acp = "true"
api.dbus.ReserveDevice1 = "Audio0"
api.dbus.ReserveDevice1.Priority = "-20"
device.bus = "pci"
device.bus_path = "pci-0000:03:00.1"
device.enum.api = "udev"
device.name = "alsa_card.pci-0000_03_00.1"
device.nick = "HDA ATI HDMI"
device.plugged.usec = "14763259"
device.product.id = "0xab30"
device.product.name = "Navi 31 HDMI/DP Audio"
device.subsystem = "sound"
sysfs.path = "/devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card0"
device.vendor.id = "0x1002"
device.vendor.name = "Advanced Micro Devices, Inc.
[AMD/ATI]"
spa.object.id = "2"
device.string = "0"
Formats:
pcm

Sink #929
State: IDLE
Name: alsa_output.pci-0000_03_00.1.pro-output-7
Description: Navi 31 HDMI/DP Audio Pro 7
Driver: PipeWire
Sample Specification: s32le 8ch 48000Hz
Channel Map: aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7
Owner Module: 4294967295
Mute: no
Volume: aux0: 65536 / 100% / 0.00 dB,
aux1: 65536 / 100% / 0.00 dB,
aux2: 65536 / 100% / 0.00 dB,
aux3: 65536 / 100% / 0.00 dB,
aux4: 65536 / 100% / 0.00 dB,
aux5: 65536 / 100% / 0.00 dB,
aux6: 65536 / 100% / 0.00 dB,
aux7: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-0000_03_00.1.pro-output-7.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY
Properties:
alsa.card = "0"
alsa.card_name = "HDA ATI HDMI"
alsa.class = "generic"
alsa.components = "HDA:1002aa01,00aa0100,00100800"
alsa.device = "7"
alsa.driver_name = "snd_hda_intel"
alsa.id = "HDMI 1"
alsa.long_card_name = "HDA ATI HDMI at 0xdd720000 irq 127"
alsa.mixer_name = "ATI R6xx HDMI"
alsa.name = "HDMI 1"
alsa.resolution_bits = "32"
alsa.subclass = "generic-mix"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.sync.id = "00000000:00000000:00000000:00000000"
api.alsa.card.longname = "HDA ATI HDMI at 0xdd720000
irq 127"
api.alsa.card.name = "HDA ATI HDMI"
api.alsa.path = "hw:0,7"
api.alsa.pcm.card = "0"
api.alsa.pcm.stream = "playback"
audio.channels = "8"
audio.position = "AUX0,AUX1,AUX2,AUX3,AUX4,AUX5,AUX6,AUX7"
card.profile.device = "1"
clock.name = "api.alsa.0"
device.api = "alsa"
device.class = "sound"
device.icon_name = "audio-card-analog"
device.id = "41"
device.profile.description = "Pro 7"
device.profile.name = "pro-output-7"
device.profile.pro = "true"
device.routes = "0"
factory.name = "api.alsa.pcm.sink"
media.class = "Audio/Sink"
device.description = "Navi 31 HDMI/DP Audio"
node.name = "alsa_output.pci-0000_03_00.1.pro-output-7"
node.nick = "HDMI 1"
node.pause-on-idle = "false"
object.path = "alsa:acp:HDMI:1:playback"
port.group = "playback"
priority.driver = "1132"
priority.session = "1132"
factory.id = "19"
clock.quantum-limit = "8192"
client.id = "40"
node.driver = "true"
node.loop.name = "data-loop.0"
library.name = "audioconvert/libspa-audioconvert"
object.id = "57"
object.serial = "929"
node.max-latency = "16384/48000"
api.alsa.period-size = "1024"
api.alsa.period-num = "32"
api.alsa.headroom = "0"
api.acp.auto-port = "false"
api.acp.auto-profile = "false"
api.alsa.card = "0"
api.alsa.split-enable = "true"
api.alsa.use-acp = "true"
api.dbus.ReserveDevice1 = "Audio0"
api.dbus.ReserveDevice1.Priority = "-20"
device.bus = "pci"
device.bus_path = "pci-0000:03:00.1"
device.enum.api = "udev"
device.name = "alsa_card.pci-0000_03_00.1"
device.nick = "HDA ATI HDMI"
device.plugged.usec = "14763259"
device.product.id = "0xab30"
device.product.name = "Navi 31 HDMI/DP Audio"
device.subsystem = "sound"
sysfs.path = "/devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card0"
device.vendor.id = "0x1002"
device.vendor.name = "Advanced Micro Devices, Inc.
[AMD/ATI]"
spa.object.id = "2"
device.string = "0"
Formats:
pcm

Sink #930
State: IDLE
Name: alsa_output.pci-0000_03_00.1.pro-output-8
Description: Navi 31 HDMI/DP Audio Pro 8
Driver: PipeWire
Sample Specification: s32le 8ch 48000Hz
Channel Map: aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7
Owner Module: 4294967295
Mute: no
Volume: aux0: 65536 / 100% / 0.00 dB,
aux1: 65536 / 100% / 0.00 dB,
aux2: 65536 / 100% / 0.00 dB,
aux3: 65536 / 100% / 0.00 dB,
aux4: 65536 / 100% / 0.00 dB,
aux5: 65536 / 100% / 0.00 dB,
aux6: 65536 / 100% / 0.00 dB,
aux7: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-0000_03_00.1.pro-output-8.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY
Properties:
alsa.card = "0"
alsa.card_name = "HDA ATI HDMI"
alsa.class = "generic"
alsa.components = "HDA:1002aa01,00aa0100,00100800"
alsa.device = "8"
alsa.driver_name = "snd_hda_intel"
alsa.id = "HDMI 2"
alsa.long_card_name = "HDA ATI HDMI at 0xdd720000 irq 127"
alsa.mixer_name = "ATI R6xx HDMI"
alsa.name = "HDMI 2"
alsa.resolution_bits = "32"
alsa.subclass = "generic-mix"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.sync.id = "00000000:00000000:00000000:00000000"
api.alsa.card.longname = "HDA ATI HDMI at 0xdd720000
irq 127"
api.alsa.card.name = "HDA ATI HDMI"
api.alsa.path = "hw:0,8"
api.alsa.pcm.card = "0"
api.alsa.pcm.stream = "playback"
audio.channels = "8"
audio.position = "AUX0,AUX1,AUX2,AUX3,AUX4,AUX5,AUX6,AUX7"
card.profile.device = "2"
clock.name = "api.alsa.0"
device.api = "alsa"
device.class = "sound"
device.icon_name = "audio-card-analog"
device.id = "41"
device.profile.description = "Pro 8"
device.profile.name = "pro-output-8"
device.profile.pro = "true"
device.routes = "0"
factory.name = "api.alsa.pcm.sink"
media.class = "Audio/Sink"
device.description = "Navi 31 HDMI/DP Audio"
node.name = "alsa_output.pci-0000_03_00.1.pro-output-8"
node.nick = "HDMI 2"
node.pause-on-idle = "false"
object.path = "alsa:acp:HDMI:2:playback"
port.group = "playback"
priority.driver = "1116"
priority.session = "1116"
factory.id = "19"
clock.quantum-limit = "8192"
client.id = "40"
node.driver = "true"
node.loop.name = "data-loop.0"
library.name = "audioconvert/libspa-audioconvert"
object.id = "236"
object.serial = "930"
node.max-latency = "16384/48000"
api.alsa.period-size = "1024"
api.alsa.period-num = "32"
api.alsa.headroom = "0"
api.acp.auto-port = "false"
api.acp.auto-profile = "false"
api.alsa.card = "0"
api.alsa.split-enable = "true"
api.alsa.use-acp = "true"
api.dbus.ReserveDevice1 = "Audio0"
api.dbus.ReserveDevice1.Priority = "-20"
device.bus = "pci"
device.bus_path = "pci-0000:03:00.1"
device.enum.api = "udev"
device.name = "alsa_card.pci-0000_03_00.1"
device.nick = "HDA ATI HDMI"
device.plugged.usec = "14763259"
device.product.id = "0xab30"
device.product.name = "Navi 31 HDMI/DP Audio"
device.subsystem = "sound"
sysfs.path = "/devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card0"
device.vendor.id = "0x1002"
device.vendor.name = "Advanced Micro Devices, Inc.
[AMD/ATI]"
spa.object.id = "2"
device.string = "0"
Formats:
pcm

Sink #931
State: IDLE
Name: alsa_output.pci-0000_03_00.1.pro-output-9
Description: Navi 31 HDMI/DP Audio Pro 9
Driver: PipeWire
Sample Specification: s32le 8ch 48000Hz
Channel Map: aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7
Owner Module: 4294967295
Mute: no
Volume: aux0: 65536 / 100% / 0.00 dB,
aux1: 65536 / 100% / 0.00 dB,
aux2: 65536 / 100% / 0.00 dB,
aux3: 65536 / 100% / 0.00 dB,
aux4: 65536 / 100% / 0.00 dB,
aux5: 65536 / 100% / 0.00 dB,
aux6: 65536 / 100% / 0.00 dB,
aux7: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-0000_03_00.1.pro-output-9.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY
Properties:
alsa.card = "0"
alsa.card_name = "HDA ATI HDMI"
alsa.class = "generic"
alsa.components = "HDA:1002aa01,00aa0100,00100800"
alsa.device = "9"
alsa.driver_name = "snd_hda_intel"
alsa.id = "HDMI 3"
alsa.long_card_name = "HDA ATI HDMI at 0xdd720000 irq 127"
alsa.mixer_name = "ATI R6xx HDMI"
alsa.name = "HDMI 3"
alsa.resolution_bits = "32"
alsa.subclass = "generic-mix"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.sync.id = "00000000:00000000:00000000:00000000"
api.alsa.card.longname = "HDA ATI HDMI at 0xdd720000
irq 127"
api.alsa.card.name = "HDA ATI HDMI"
api.alsa.path = "hw:0,9"
api.alsa.pcm.card = "0"
api.alsa.pcm.stream = "playback"
audio.channels = "8"
audio.position = "AUX0,AUX1,AUX2,AUX3,AUX4,AUX5,AUX6,AUX7"
card.profile.device = "3"
clock.name = "api.alsa.0"
device.api = "alsa"
device.class = "sound"
device.icon_name = "audio-card-analog"
device.id = "41"
device.profile.description = "Pro 9"
device.profile.name = "pro-output-9"
device.profile.pro = "true"
device.routes = "0"
factory.name = "api.alsa.pcm.sink"
media.class = "Audio/Sink"
device.description = "Navi 31 HDMI/DP Audio"
node.name = "alsa_output.pci-0000_03_00.1.pro-output-9"
node.nick = "HDMI 3"
node.pause-on-idle = "false"
object.path = "alsa:acp:HDMI:3:playback"
port.group = "playback"
priority.driver = "1100"
priority.session = "1100"
factory.id = "19"
clock.quantum-limit = "8192"
client.id = "40"
node.driver = "true"
node.loop.name = "data-loop.0"
library.name = "audioconvert/libspa-audioconvert"
object.id = "250"
object.serial = "931"
node.max-latency = "16384/48000"
api.alsa.period-size = "1024"
api.alsa.period-num = "32"
api.alsa.headroom = "0"
api.acp.auto-port = "false"
api.acp.auto-profile = "false"
api.alsa.card = "0"
api.alsa.split-enable = "true"
api.alsa.use-acp = "true"
api.dbus.ReserveDevice1 = "Audio0"
api.dbus.ReserveDevice1.Priority = "-20"
device.bus = "pci"
device.bus_path = "pci-0000:03:00.1"
device.enum.api = "udev"
device.name = "alsa_card.pci-0000_03_00.1"
device.nick = "HDA ATI HDMI"
device.plugged.usec = "14763259"
device.product.id = "0xab30"
device.product.name = "Navi 31 HDMI/DP Audio"
device.subsystem = "sound"
sysfs.path = "/devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card0"
device.vendor.id = "0x1002"
device.vendor.name = "Advanced Micro Devices, Inc.
[AMD/ATI]"
spa.object.id = "2"
device.string = "0"
Formats:
pcm

Sink #1012
State: IDLE
Name: alsa_output.pci-0000_79_00.1.pro-output-3
Description: Rembrandt Radeon High Definition Audio Controller Pro
Driver: PipeWire
Sample Specification: s32le 8ch 48000Hz
Channel Map: aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7
Owner Module: 4294967295
Mute: no
Volume: aux0: 65536 / 100% / 0.00 dB,
aux1: 65536 / 100% / 0.00 dB,
aux2: 65536 / 100% / 0.00 dB,
aux3: 65536 / 100% / 0.00 dB,
aux4: 65536 / 100% / 0.00 dB,
aux5: 65536 / 100% / 0.00 dB,
aux6: 65536 / 100% / 0.00 dB,
aux7: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-0000_79_00.1.pro-output-3.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY
Properties:
alsa.card = "1"
alsa.card_name = "HD-Audio Generic"
alsa.class = "generic"
alsa.components = "HDA:1002aa01,00aa0100,00100800"
alsa.device = "3"
alsa.driver_name = "snd_hda_intel"
alsa.id = "HDMI 0"
alsa.long_card_name = "HD-Audio Generic at 0xdcf88000
irq 128"
alsa.mixer_name = "ATI R6xx HDMI"
alsa.name = "HDMI 0"
alsa.resolution_bits = "32"
alsa.subclass = "generic-mix"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.sync.id = "00000000:00000000:00000000:00000000"
api.alsa.card.longname = "HD-Audio Generic at
0xdcf88000 irq 128"
api.alsa.card.name = "HD-Audio Generic"
api.alsa.path = "hw:1,3"
api.alsa.pcm.card = "1"
api.alsa.pcm.stream = "playback"
audio.channels = "8"
audio.position = "AUX0,AUX1,AUX2,AUX3,AUX4,AUX5,AUX6,AUX7"
card.profile.device = "0"
clock.name = "api.alsa.1"
device.api = "alsa"
device.class = "sound"
device.icon_name = "audio-card-analog"
device.id = "42"
device.profile.description = "Pro"
device.profile.name = "pro-output-3"
device.profile.pro = "true"
device.routes = "0"
factory.name = "api.alsa.pcm.sink"
media.class = "Audio/Sink"
device.description = "Rembrandt Radeon High Definition
Audio Controller"
node.name = "alsa_output.pci-0000_79_00.1.pro-output-3"
node.nick = "HDMI 0"
node.pause-on-idle = "false"
object.path = "alsa:acp:Generic:0:playback"
port.group = "playback"
priority.driver = "1196"
priority.session = "1196"
factory.id = "19"
clock.quantum-limit = "8192"
client.id = "40"
node.driver = "true"
node.loop.name = "data-loop.0"
library.name = "audioconvert/libspa-audioconvert"
object.id = "53"
object.serial = "1012"
node.max-latency = "16384/48000"
api.alsa.period-size = "1024"
api.alsa.period-num = "32"
api.alsa.headroom = "0"
api.acp.auto-port = "false"
api.acp.auto-profile = "false"
api.alsa.card = "1"
api.alsa.split-enable = "true"
api.alsa.use-acp = "true"
api.dbus.ReserveDevice1 = "Audio1"
api.dbus.ReserveDevice1.Priority = "-20"
device.bus = "pci"
device.bus_path = "pci-0000:79:00.1"
device.enum.api = "udev"
device.name = "alsa_card.pci-0000_79_00.1"
device.nick = "HD-Audio Generic"
device.plugged.usec = "14763316"
device.product.id = "0x1640"
device.product.name = "Rembrandt Radeon High Definition
Audio Controller"
device.subsystem = "sound"
sysfs.path = "/devices/pci0000:00/0000:00:08.1/0000:79:00.1/sound/card1"
device.vendor.id = "0x1002"
device.vendor.name = "Advanced Micro Devices, Inc.
[AMD/ATI]"
spa.object.id = "4"
device.string = "1"
Formats:
pcm

Sink #1013
State: IDLE
Name: alsa_output.pci-0000_79_00.1.pro-output-7
Description: Rembrandt Radeon High Definition Audio Controller
Pro 7
Driver: PipeWire
Sample Specification: s32le 8ch 48000Hz
Channel Map: aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7
Owner Module: 4294967295
Mute: no
Volume: aux0: 65536 / 100% / 0.00 dB,
aux1: 65536 / 100% / 0.00 dB,
aux2: 65536 / 100% / 0.00 dB,
aux3: 65536 / 100% / 0.00 dB,
aux4: 65536 / 100% / 0.00 dB,
aux5: 65536 / 100% / 0.00 dB,
aux6: 65536 / 100% / 0.00 dB,
aux7: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-0000_79_00.1.pro-output-7.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY
Properties:
alsa.card = "1"
alsa.card_name = "HD-Audio Generic"
alsa.class = "generic"
alsa.components = "HDA:1002aa01,00aa0100,00100800"
alsa.device = "7"
alsa.driver_name = "snd_hda_intel"
alsa.id = "HDMI 1"
alsa.long_card_name = "HD-Audio Generic at 0xdcf88000
irq 128"
alsa.mixer_name = "ATI R6xx HDMI"
alsa.name = "HDMI 1"
alsa.resolution_bits = "32"
alsa.subclass = "generic-mix"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.sync.id = "00000000:00000000:00000000:00000000"
api.alsa.card.longname = "HD-Audio Generic at
0xdcf88000 irq 128"
api.alsa.card.name = "HD-Audio Generic"
api.alsa.path = "hw:1,7"
api.alsa.pcm.card = "1"
api.alsa.pcm.stream = "playback"
audio.channels = "8"
audio.position = "AUX0,AUX1,AUX2,AUX3,AUX4,AUX5,AUX6,AUX7"
card.profile.device = "1"
clock.name = "api.alsa.1"
device.api = "alsa"
device.class = "sound"
device.icon_name = "audio-card-analog"
device.id = "42"
device.profile.description = "Pro 7"
device.profile.name = "pro-output-7"
device.profile.pro = "true"
device.routes = "0"
factory.name = "api.alsa.pcm.sink"
media.class = "Audio/Sink"
device.description = "Rembrandt Radeon High Definition
Audio Controller"
node.name = "alsa_output.pci-0000_79_00.1.pro-output-7"
node.nick = "HDMI 1"
node.pause-on-idle = "false"
object.path = "alsa:acp:Generic:1:playback"
port.group = "playback"
priority.driver = "1132"
priority.session = "1132"
factory.id = "19"
clock.quantum-limit = "8192"
client.id = "40"
node.driver = "true"
node.loop.name = "data-loop.0"
library.name = "audioconvert/libspa-audioconvert"
object.id = "148"
object.serial = "1013"
node.max-latency = "16384/48000"
api.alsa.period-size = "1024"
api.alsa.period-num = "32"
api.alsa.headroom = "0"
api.acp.auto-port = "false"
api.acp.auto-profile = "false"
api.alsa.card = "1"
api.alsa.split-enable = "true"
api.alsa.use-acp = "true"
api.dbus.ReserveDevice1 = "Audio1"
api.dbus.ReserveDevice1.Priority = "-20"
device.bus = "pci"
device.bus_path = "pci-0000:79:00.1"
device.enum.api = "udev"
device.name = "alsa_card.pci-0000_79_00.1"
device.nick = "HD-Audio Generic"
device.plugged.usec = "14763316"
device.product.id = "0x1640"
device.product.name = "Rembrandt Radeon High Definition
Audio Controller"
device.subsystem = "sound"
sysfs.path = "/devices/pci0000:00/0000:00:08.1/0000:79:00.1/sound/card1"
device.vendor.id = "0x1002"
device.vendor.name = "Advanced Micro Devices, Inc.
[AMD/ATI]"
spa.object.id = "4"
device.string = "1"
Formats:
pcm

Sink #1014
State: IDLE
Name: alsa_output.pci-0000_79_00.1.pro-output-8
Description: Rembrandt Radeon High Definition Audio Controller
Pro 8
Driver: PipeWire
Sample Specification: s32le 8ch 48000Hz
Channel Map: aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7
Owner Module: 4294967295
Mute: no
Volume: aux0: 65536 / 100% / 0.00 dB,
aux1: 65536 / 100% / 0.00 dB,
aux2: 65536 / 100% / 0.00 dB,
aux3: 65536 / 100% / 0.00 dB,
aux4: 65536 / 100% / 0.00 dB,
aux5: 65536 / 100% / 0.00 dB,
aux6: 65536 / 100% / 0.00 dB,
aux7: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-0000_79_00.1.pro-output-8.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY
Properties:
alsa.card = "1"
alsa.card_name = "HD-Audio Generic"
alsa.class = "generic"
alsa.components = "HDA:1002aa01,00aa0100,00100800"
alsa.device = "8"
alsa.driver_name = "snd_hda_intel"
alsa.id = "HDMI 2"
alsa.long_card_name = "HD-Audio Generic at 0xdcf88000
irq 128"
alsa.mixer_name = "ATI R6xx HDMI"
alsa.name = "HDMI 2"
alsa.resolution_bits = "32"
alsa.subclass = "generic-mix"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.sync.id = "00000000:00000000:00000000:00000000"
api.alsa.card.longname = "HD-Audio Generic at
0xdcf88000 irq 128"
api.alsa.card.name = "HD-Audio Generic"
api.alsa.path = "hw:1,8"
api.alsa.pcm.card = "1"
api.alsa.pcm.stream = "playback"
audio.channels = "8"
audio.position = "AUX0,AUX1,AUX2,AUX3,AUX4,AUX5,AUX6,AUX7"
card.profile.device = "2"
clock.name = "api.alsa.1"
device.api = "alsa"
device.class = "sound"
device.icon_name = "audio-card-analog"
device.id = "42"
device.profile.description = "Pro 8"
device.profile.name = "pro-output-8"
device.profile.pro = "true"
device.routes = "0"
factory.name = "api.alsa.pcm.sink"
media.class = "Audio/Sink"
device.description = "Rembrandt Radeon High Definition
Audio Controller"
node.name = "alsa_output.pci-0000_79_00.1.pro-output-8"
node.nick = "HDMI 2"
node.pause-on-idle = "false"
object.path = "alsa:acp:Generic:2:playback"
port.group = "playback"
priority.driver = "1116"
priority.session = "1116"
factory.id = "19"
clock.quantum-limit = "8192"
client.id = "40"
node.driver = "true"
node.loop.name = "data-loop.0"
library.name = "audioconvert/libspa-audioconvert"
object.id = "194"
object.serial = "1014"
node.max-latency = "16384/48000"
api.alsa.period-size = "1024"
api.alsa.period-num = "32"
api.alsa.headroom = "0"
api.acp.auto-port = "false"
api.acp.auto-profile = "false"
api.alsa.card = "1"
api.alsa.split-enable = "true"
api.alsa.use-acp = "true"
api.dbus.ReserveDevice1 = "Audio1"
api.dbus.ReserveDevice1.Priority = "-20"
device.bus = "pci"
device.bus_path = "pci-0000:79:00.1"
device.enum.api = "udev"
device.name = "alsa_card.pci-0000_79_00.1"
device.nick = "HD-Audio Generic"
device.plugged.usec = "14763316"
device.product.id = "0x1640"
device.product.name = "Rembrandt Radeon High Definition
Audio Controller"
device.subsystem = "sound"
sysfs.path = "/devices/pci0000:00/0000:00:08.1/0000:79:00.1/sound/card1"
device.vendor.id = "0x1002"
device.vendor.name = "Advanced Micro Devices, Inc.
[AMD/ATI]"
spa.object.id = "4"
device.string = "1"
Formats:
pcm














--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 7/4/25 2:18 AM, J.O. Aho wrote:

On 04/07/2025 03.58, bad sector wrote:

I'm trying to find out why I'm getting no sound out the board's own
backpanel 1/8" audio Line-Out (green) port. AFAIK this port should
ALWAYS work! Also AFAIK there had been some driver delays but the 3
sound systems all seem to be driven now. BIOS just saus HD Audio and
is 'Enabled' & in Suse Tumbleweed Yast reports:

Navi 31 HDMI/DP Audio
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel

Rembrandt Radeon HD audio controller
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel

Family 17h/19h/1ah HD Audio Controller
  Drivers
   Active: yes
   modprobe: Yes
  modules
   modprobe snd_hda-intel


I don't even know what these all are, I mean which one does what exactly?

This is my guestimation:
Navi is your RDNA based Radeon card.
Family is your motherboards built in audio card
Rembrandt I guess is the audio in the Graphics provided by your CPU.

Thanks, way over my head and I've never seen this much sound not working
right :-)

The BIOS lets me kill 'Family' adv-audio but that's the only one I want
to keep. I might be able to nix the integrated CPU-gpu including the
sound it produces but I have no idea how to disable the Radeon GPU 'HDMI
audio only' which I think gets sent to the monitor. Once I'm down to
onboard advanced audio it might become more manageble.


see my response to marrgol about sinks

In linux plugging the headset into the rear port just gives me
scratchy static blasts when I move the headset plug. So maybe the
(always shitty at best) mini receptacle is broken or desoldered?

The front panel (extension headers) headset port works fine.

Some setups have had the issue that you either can use the ports in the
back or the front, not both at the same time, not sure if that is the
case for you.

Also things depends on what are you using in the pipewire/pulseaudio Analog/Digital vs Pro Audio profile. You should go with the Pro Audio nowadays.

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Tue, 8 Jul 2025 06:57:42 -0400, bad sector wrote:

You sit down with test subjects and run them through the hoops that
be ...UNTIL you get no more questions from them anymore. THAT's when
your design or composition is ready for release and not before.

Presumably you sit down with a new, different group of subjects for
each iteration. Otherwise you’re just habituating them to the quirks
of your particular design.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 10/1/25 2:04 AM, Lawrence D’Oliveiro wrote:

On Tue, 8 Jul 2025 06:57:42 -0400, bad sector wrote:

You sit down with test subjects and run them through the hoops that
be ...UNTIL you get no more questions from them anymore. THAT's when
your design or composition is ready for release and not before.

Presumably you sit down with a new, different group of subjects for
each iteration. Otherwise you’re just habituating them to the quirks
of your particular design.

Good idea! But we could be jumping the gun a little. The industry (most industries) seems to be drifting in the opposite direction, that of the coke-machine 'business-model' as zookerbooger would say. In this model
the supply-side produces and packs into a 'dispenser' where you take
what's offered, period. We've come a long way since my childhood days
when the farmer produced an all around A1 quality product so when he
stacked up the water melons at the market people could get a taste of
one before buying it.


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Wed, 1 Oct 2025 08:44:06 -0400, bad sector wrote:

On 10/1/25 2:04 AM, Lawrence D’Oliveiro wrote:

On Tue, 8 Jul 2025 06:57:42 -0400, bad sector wrote:

You sit down with test subjects and run them through the hoops that be
...UNTIL you get no more questions from them anymore. THAT's when your
design or composition is ready for release and not before.

Presumably you sit down with a new, different group of subjects for
each iteration. Otherwise you’re just habituating them to the quirks of
your particular design.

Good idea! But we could be jumping the gun a little. The industry (most industries) seems to be drifting in the opposite direction, that of the coke-machine 'business-model' as zookerbooger would say. In this model
the supply-side produces and packs into a 'dispenser' where you take
what's offered, period.

The proprietary companies have certainly long been like that. I can
remember when folks at Apple (like Bruce “Tog” Tognazzini), for example, prided themselves on conducting proper user-interface testing. Tog even
wrote a book on it, which I have.

Nowadays the only ones really offering a choice of UI are the open-source people.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 10/10/25 8:13 PM, Lawrence D’Oliveiro wrote:

On Wed, 1 Oct 2025 08:44:06 -0400, bad sector wrote:

On 10/1/25 2:04 AM, Lawrence D’Oliveiro wrote:

On Tue, 8 Jul 2025 06:57:42 -0400, bad sector wrote:

You sit down with test subjects and run them through the hoops that be >>>> ...UNTIL you get no more questions from them anymore. THAT's when your >>>> design or composition is ready for release and not before.

Presumably you sit down with a new, different group of subjects for
each iteration. Otherwise you’re just habituating them to the quirks of >>> your particular design.

Good idea! But we could be jumping the gun a little. The industry (most
industries) seems to be drifting in the opposite direction, that of the
coke-machine 'business-model' as zookerbooger would say. In this model
the supply-side produces and packs into a 'dispenser' where you take
what's offered, period.

The proprietary companies have certainly long been like that. I can
remember when folks at Apple (like Bruce “Tog” Tognazzini), for example, prided themselves on conducting proper user-interface testing. Tog even
wrote a book on it, which I have.

Nowadays the only ones really offering a choice of UI are the open-source people.

I once wrote a little prog in Perl using html as the GUI (Perl at that
time was very good for that). Optional argument or 'switch' buttons were
not is short supply but I thought that the 1920x1200 monitor was being under-employed so I decided to print the actual command line including
all switches including the change executed by that last button with the
active buttons highlighted, the last button used AND the last cLi change
also highlighted in another color at the bottom of the dialog window
(the command line sometimes taking up 2-3 lines). In all humility that
was by far the best dammned GUI that I have ever seen. Nowadays I see
password prompts that do not state WHICH password is being solicited,
only 'authentication required'... puke, puke, puke.

--- Synchronet 3.21a-Linux NewsLink 1.2