$ alsactl restore
alsactl: state_lock:125: file /var/lib/alsa/asound.state lock error: File exists alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: File exists alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA Intel HDMI at 0xf3610000 irq 52) alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6 Found hardware: "HDA-Intel" "Intel Haswell HDMI" "HDA:number1,number2,number3" "0x17aa" "0x3978" Hardware is initialized using a generic method alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA Intel PCH at 0xf3614000 irq 51) alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -6 Found hardware: "HDA-Intel" "Realtek ALC233" "HDA:string1,string2,string3" "0x17aa" "0x3978" Hardware is initialized using a generic method alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -2 Found hardware: "USB-Audio" "USB Mixer" "USBstringhere:numberhere" "" "" Hardware is initialized using a generic method
$ cat /proc/asound/cards
0 [HDMI ]: HDA-Intel - HDA Intel HDMI
HDA Intel HDMI at 0xf3610000 irq 52
1 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf3614000 irq 51
2 [Device ]: USB-Audio - USB Audio Device
C-Media Electronics Inc. USB Audio Device at usb-0000:00:14.0-5.4, full speed
so it is weird that HDMI has top priority right? i think device 1 should be top priority (0 or engative number?)
at ALSA - Manjaro i read i need to set device in file /etc/asound.conf but it was empty so i set it like this:
$ cd;echo -e "defaults.pcm.card 1\ndefaults.ctl.card 1" > asound.conf;sudo mv asound.conf /etc/;cd -
(1 is the number under which is shown my primary internal soundcard in above command $ cat /proc/asound/cards )
then i tried to reload:
pulseaudio -k; pulseaudio --start
then i see that the audio started working and VLC player offers selecting from only 2 devices instead of showing bunch of non working pseudo/virual devices) which is correct, maybe developers failed to make it properly detect and set the device before. But it worked before the Christmas kernel upgrade.
Anyone can help debug this so this issue can be fixed?