You are not logged in.
I have issues where my onboard sound isn't recognized for a full minute after the PC boots, and Pipewire defaults to the wrong device every time as a result.
This sound device is recognized as a "00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake-S HD Audio Controller (rev 11)", and after a minute it shows up in pipewire, with the following kernel logs related to this:
[ 3.090832] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[ 3.090899] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[ 3.091367] snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
[ 3.091484] snd_hda_intel 0000:01:00.1: Disabling MSI
[ 3.091492] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[ 4.691706] usbcore: registered new interface driver snd-usb-audio
[ 64.703823] snd_hda_intel 0000:00:1f.3: couldn't bind with audio component
[ 64.715319] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC1220: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[ 64.715322] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 64.715324] snd_hda_codec_realtek hdaudioC0D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 64.715325] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 64.715326] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 64.715326] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18
[ 64.715327] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a
(There is also bizarrely a separate built-in USB audio device for the front headphone jack on the desktop. Really.)
However, it won't actually play sound until I go into the Configuration page in pavucontrol and flip it from "Analog Stereo Output" to "Off" to back to "Analog Stereo Output". Any suggestions on how to cut down on this time and the associated hassles?
Avatar by Ditey: https://twitter.com/phrobitey
Offline
Parallel Windows install? Have you made sure fast boot is disabled there? This sounds like the kind of issue that can happen with a hibernating Windows fucking up firmware state. If Windows isn't there and/or fast-boot is disabled, try a
sudo alsactl init
when the device is available.
Online
Parallel Windows install? Have you made sure fast boot is disabled there? This sounds like the kind of issue that can happen with a hibernating Windows fucking up firmware state. If Windows isn't there and/or fast-boot is disabled, try a
sudo alsactl init
when the device is available.
Arch Linux is the only OS on this machine.
sudo alsactl init
has no effect on the problem.
Last edited by GourdCaptain (2023-05-23 22:59:49)
Avatar by Ditey: https://twitter.com/phrobitey
Offline