### System details

Intel core 325,16GB DDR5, Intel integrated graphics, latest omarchy

### What's wrong?

Hey, first i wanna say that i really love Omarchy. 
i did bought a new laptop and it came with windows 11
everything worked, so i installed omarchy and i instantly recognized that the internal speakers arent working. but my microphone worked fine right after the installation. 
after some troubleshooting and some more troubleshooting i came to the conclusion that i cant fix it myself, i really tried. so i decided to open a bug report on bugzilla because i think its a kernel issue with the newer Panther lake laptops. 

omponent: Sound
Product: Drivers

Subject: [Panther Lake / ThinkPad E16 Gen 4] Internal speakers non-functional (speaker_outs=0), microphone regression after driver troubleshooting

## System Information
- Machine: Lenovo ThinkPad E16 Gen 4 (Intel)
- Model: 21YC0008GE
- CPU/Platform: Intel Panther Lake
- Kernel version: 7.0.10-arch1-1
- Distribution: Arch Linux (Omarchy, Hyprland-based)
- BIOS/UEFI version: R3AET28W(1.02 )
- BIOS release date: 03/13/2026

## Audio Hardware
00:1f.3 Multimedia audio controller: Intel Corporation Device e428 (rev 01)
        Subsystem: Lenovo Device 513e
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_sof_pci_intel_ptl, snd_hda_intel

Codec: Conexant SN6140 (hdaudioC0D0)

## Problem Description
The internal speakers on this laptop produce no audio output. dmesg shows
the Conexant codec auto-probing during boot and picking a fixup for PCI
SSID 17aa:0000, but the resulting autoconfig reports:

    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
    hp_outs=1 (0x16/0x0/0x0/0x0/0x0)

I.e. no speaker output pin is being reported/configured at all, while the
headphone pin is correctly detected. This strongly suggests the pin
configuration provided by the platform (via ACPI/BIOS) is missing or
incorrect for the speaker outputs, rather than a driver-side codec support
gap.

Extensive driver-level troubleshooting has been performed (kernel module
parameters, ALSA/PipeWire configuration, firmware/quirk attempts) without
restoring speaker output.

During this troubleshooting process, a regression occurred: the internal
microphone (Internal Mic=0x1a, per codec inputs below) stopped working,
despite the pin still being reported by the codec. This suggests one of
the applied workarounds/quirks negatively affected the microphone codec
path rather than the pin config itself.

## Codec Pin Configuration (from dmesg)
[   62.196006] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [xe])
[   62.222274] snd_hda_codec_conexant hdaudioC0D0: SN6140: BIOS auto-probing.
[   62.222594] snd_hda_codec_conexant hdaudioC0D0: SN6140: picked fixup for PCI SSID 17aa:0000
[   62.222718] snd_hda_codec_conexant hdaudioC0D0: autoconfig for SN6140: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[   62.222720] snd_hda_codec_conexant hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   62.222721] snd_hda_codec_conexant hdaudioC0D0:    hp_outs=1 (0x16/0x0/0x0/0x0/0x0)
[   62.222722] snd_hda_codec_conexant hdaudioC0D0:    mono: mono_out=0x0
[   62.222723] snd_hda_codec_conexant hdaudioC0D0:    inputs:
[   62.222724] snd_hda_codec_conexant hdaudioC0D0:        Mic=0x19
[   62.222725] snd_hda_codec_conexant hdaudioC0D0:        Internal Mic=0x1a

## Steps Already Taken
- Tested various HDA kernel module parameters/quirks
- Adjusted ALSA/PipeWire configuration
- Checked/updated firmware packages (linux-firmware)
- No BIOS update currently available from Lenovo addressing this issue

## Expected Behavior
Internal speakers and microphone should function via the standard
ALSA/HDA audio pipeline, with speaker_outs correctly populated by the
codec autoconfig.

## Actual Behavior
- Internal speakers: speaker_outs=0, no output, no ALSA errors
- Internal microphone: previously working, now non-functional after
  troubleshooting steps above

## Additional Information
alsa-info.sh failed to run (404 fetching the script itself, not the
upload step) - can provide on request if a working script URL is
available.

the bug report is about 3 weeks old, nobody even answered on it. so i try my luck here.
i really dont wanna go back to windows ...