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.
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.
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
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.
On 7/4/25 2:18 AM, J.O. Aho wrote:
On 04/07/2025 03.58, bad sector wrote:
This is my guestimation:
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? >>
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: nothingthe board Line-Out = no sound. I do get a noise when partly
Playback tab:
System Sounds
I put the headset cable from the front panel, plug it into
On Sat, 7/5/2025 8:32 PM, bad sector wrote:
On 7/4/25 2:18 AM, J.O. Aho wrote:the board Line-Out = no sound. I do get a noise when partly
On 04/07/2025 03.58, bad sector wrote:
This is my guestimation:
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? >>>
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
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"
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:the board Line-Out = no sound. I do get a noise when partly
On 04/07/2025 03.58, bad sector wrote:
This is my guestimation:
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? >>>>
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
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.
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:the board Line-Out = no sound. I do get a noise when partly
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
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
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).
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
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
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.
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 1,064 |
Nodes: | 10 (0 / 10) |
Uptime: | 146:24:15 |
Calls: | 13,691 |
Calls today: | 1 |
Files: | 186,935 |
D/L today: |
23 files (2,078K bytes) |
Messages: | 2,410,869 |