Audio on 14-CURRENT

mnd999 · May 22, 2023

What is the state of audio on 14-current? I've got a couple of sound devices, but no luck. I get the impression audio had a bit of an overhaul in 14 - can't remember where I read that.

The first is 'CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus]' which snd_hda detects, and creates devices but no sound ever comes out despite the bars moving in pavucontrol. If I max the volume, I get a hiss in the speakers sometimes but that's about it.

Perhaps its the audio selector - it looks like nid20 is the connected output, but nid36 seem to think it's disabled. I'm not sure how to fix that:

Code:

dev.hdaa.0.nid36: audio selector
     Widget cap: 0x00300101 STEREO
    Association: 1 (0x0001)
            OSS: speaker, mic, mix
    Connections: 12
          + <- nid=24 [pin: Mic (Pink Jack)] (selected)
          + [DISABLED] <- nid=25 [pin: Mic (Pink Jack)]
          + [DISABLED] <- nid=26 [pin: Line-in (Blue Jack)]
          + [DISABLED] <- nid=27 [pin: Headphones (Green Jack)]
          + [DISABLED] <- nid=28 [pin: Speaker (None)] [DISABLED]
          + <- nid=29 [beep widget]
          + [DISABLED] <- nid=20 [pin: Line-out (Green Jack)]
          + [DISABLED] <- nid=21 [pin: Line-out (Black Jack)]
          + [DISABLED] <- nid=22 [pin: Line-out (Orange Jack)]
          + [DISABLED] <- nid=23 [pin: Line-out (None)] [DISABLED]
          + <- nid=11 [audio mixer]
          + [DISABLED] <- nid=18 [pin: Speaker (None)] [DISABLED]


hdaa0: Dumping AFG pins:
hdaa0: nid   0x    as seq device       conn  jack    loc        color   misc
hdaa0: 17 40130000 0  0  Speaker       None  ATAPI   0x00       Unknown 0 DISA
hdaa0:     Caps:    OUT
hdaa0: 18 411111f0 15 0  Speaker       None  1/8     Rear       Black   1 DISA
hdaa0:     Caps: IN
hdaa0: 20 01014010 1  0  Line-out      Jack  1/8     Rear       Green   0
hdaa0:     Caps: IN OUT HP EAPD      Sense: 0x80000000 (connected)
hdaa0: 21 01011012 1  2  Line-out      Jack  1/8     Rear       Black   0
hdaa0:     Caps: IN OUT HP           Sense: 0x00000000 (disconnected)
hdaa0: 22 01016011 1  1  Line-out      Jack  1/8     Rear       Orange  0
hdaa0:     Caps: IN OUT HP           Sense: 0x00000000 (disconnected)
hdaa0: 23 41012014 1  4  Line-out      None  1/8     Rear       Grey    0 DISA
hdaa0:     Caps: IN OUT HP           Sense: 0x00000000 (disconnected)
hdaa0: 24 01a19040 4  0  Mic           Jack  1/8     Rear       Pink    0
hdaa0:     Caps: IN OUT HP      VREF Sense: 0x00000000 (disconnected)
hdaa0: 25 02a19050 5  0  Mic           Jack  1/8     Front      Pink    0
hdaa0:     Caps: IN OUT HP      VREF Sense: 0x00000000 (disconnected)
hdaa0: 26 01813060 6  0  Line-in       Jack  1/8     Rear       Blue    0
hdaa0:     Caps: IN OUT HP      VREF Sense: 0x00000000 (disconnected)
hdaa0: 27 0221401f 1  15 Headphones    Jack  1/8     Front      Green   0
hdaa0:     Caps: IN OUT HP EAPD VREF Sense: 0x00000000 (disconnected)
hdaa0: 28 411111f0 15 0  Speaker       None  1/8     Rear       Black   1 DISA
hdaa0:     Caps: IN                  Sense: 0x00000000 (disconnected)
hdaa0: 30 41441130 3  0  SPDIF-out     None  RCA     Rear       Black   1 DISA
hdaa0:     Caps:    OUT
hdaa0: 31 41c46170 7  0  SPDIF-in      None  RCA     Rear       Orange  1 DISA
hdaa0:     Caps: IN
hdaa0: NumGPIO=2 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1

I also have a Logitech USB headset which when connected spams the following to dmesg and then generates ear-splitting feedback and not much else.

Code:

uaudio1 numa-domain 1 on uhub4
uaudio1: <Logitech USB Headset> on usbus2
uaudio1: Play[0]: 48000 Hz, 2 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Play[0]: 44100 Hz, 2 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Play[0]: 32000 Hz, 2 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Play[0]: 22050 Hz, 2 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Play[0]: 16000 Hz, 2 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Play[0]: 11025 Hz, 2 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Play[0]: 8000 Hz, 2 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Record[0]: 48000 Hz, 1 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Record[0]: 44100 Hz, 1 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Record[0]: 32000 Hz, 1 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Record[0]: 22050 Hz, 1 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Record[0]: 16000 Hz, 1 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Record[0]: 11025 Hz, 1 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: Record[0]: 8000 Hz, 1 ch, 16-bit S-LE PCM format, 2x2ms buffer.
uaudio1: No MIDI sequencer.
pcm9: <USB audio> numa-domain 1 on uaudio1
uaudio1: HID volume keys found.

Is anyone having more success than me. I need to use 14-current for the amdgpu support.

zirias@ · May 22, 2023

mnd999 said:
I get the impression audio had a bit of an overhaul in 14 - can't remember where I read that.

So, did you try a RELEASE version and it works?

In case it's really an issue only with -CURRENT, please address your questions to the freebsd-current mailinglist.

mnd999 · May 22, 2023

No I did not try a release version much because, as I said in my original message, the GPU doesn’t work there, so no display.

The instant earsplitting feedback was definitely present on release, that’s all I can say.

zirias@ · May 22, 2023

Hm! GPU support was exactly the reason why I started my FreeBSD journey on 11-CURRENT instead of the recommended 10.x-RELEASE back then ... (but since 11.0 was finally released, I only use -CURRENT for testing ports now).

So, that's certainly a valid reason to (temporarily!) use -CURRENT. But still, it should be possible to get SOME display on -RELEASE as well (after all, simple framebuffer/vesa drivers should always work, although not performing well). It will help with further analysis to know whether the problem is "new" in -CURRENT.

And then, if the problem is really specific to -CURRENT, the mailing list is the better place. That's because -CURRENT is a moving target, and few people here on the forums use it, and even fewer are (base) developers with some insight what's currently going on ....

patmaddox · May 25, 2023

I'm afraid I don't have an answer to your question. Just responding to this bit:

mnd999 said:
What is the state of audio on 14-current? I've got a couple of sound devices, but no luck. I get the impression audio had a bit of an overhaul in 14 - can't remember where I read that.

Possibly you're referring to sound mixer improvements, included in July 2021 report. The most current info I can find is in the mixer section on wiki.

nomoo · Jun 29, 2023

Just checked, Sound BlasterX AE-5 Plus successfully works with 13.2-RELEASE. No tuning needed, just selected default output.

mnd999 · Jul 8, 2023

Yeah, the audio on the displayport output (AMD Navi) works alright as well on -CURRENT. I think it's just a quirk of this card.

Alexander88207 · Jul 8, 2023

mnd999 said:
I need to use 14-current for the amdgpu support.

I do currently use 14-CURRENT aswell for amdgpu support, but i do use only the kernel part from that so that i keep the stable 13 userland with its libs and tools. (Works with releases aswell ofc)

Code:

freebsd-version -kru
14.0-CURRENT
14.0-CURRENT
13.2-STABLE

Audio on 14-CURRENT

Enthusiast