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