I am getting this alsa error. I think it is not perfectly compatible with my sound chip, Realtek ALC 1220. Fedora 35
garberw@electron> uname -a
Linux electron 5.15.4-201.fc35.x86_64 #1 SMP Tue Nov 23 18:54:50 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
alsactl: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA Intel PCH at 0x380ffff20000 irq 85)
alsactl: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6
alsactl: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA ATI HDMI at 0xd8e60000 irq 87)
alsactl: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -6
Not sure if it would fix it but might help determine something for you by elimination if nothing else. If it doesn’t change the results then it likely isn’t the issue or related so you can then ignore it and move onto other possibilities.
Looking at your original post it looks like it is a configuration error, did you try the solution that you reference? If so, then I take it your asking to have this solution referenced in the documentation. There is a bug here about this, maybe go there and comment
What is alsa needed for if I have pipewire? Would I lose any functionality if I disabled alsa? I expect it is used for some packages which require compatibility with the previous version. I forgot why I installed alsa, but somewhere it was recommended.
If there is no sacrifice, could you please explain how to shut down alsa if it is not too hard.
That would definitely cure this. Thanks (I read the previous post and link; it is a new system; alc1220 is relatively new).
On Fedora? With systemd? That’s definitely not right. /etc/rc.d/ is a vestigial directory tree, see /etc/rc.d/init.d/README. Nobody should be doing anything in /etc/rc.d in any release of Fedora since around Fedora 21(?)!
To adjust the commands in the alsa-state.service unit, you can run sudo systemctl edit --full alsa-state.service and edit the ExecStart and ExecStop command strings accordingly.
Ah, sorry, I didn’t realize that was just a copy-paste from that page. You may want to enclose the quoted bits in [quote] markers so it’s clearer. Anyway, the systemctl edit command I mentioned would be the modern-day equivalent, if I’m understanding those ancient-history suggestions correctly.
# Note that two different ALSA card state management schemes exist and they
# can be switched using a file exist check - /etc/alsa/state-daemon.conf .
Description=Manage Sound Card State (restore and store)
ExecStart=-/usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf --initfile=/lib/alsa/init/00main rdaemon
ExecStop=-/usr/sbin/alsactl -s kill save_and_quit
I do have the error to. Quite confusing the whole sotry ?!
Alsa was needed in the beginning of adoption of Pipewire as there were some missing functionality that was desired but not available yet on Pipewire. You manipulate Pipewire with pw-cli and other commands. Or you use Wireplumber for patching use, but there is still session management incompleteness. Alsa provides low level sound card/chip drivers, so maybe will be around for a bit. Another thing to keep in mind about your boot up being untidy which is largely the bulk of the issue, is that when systemd is starting things up, it starts a lot of concurrent tasks which in turn often need some other task going to continue. While those pre-requisite tasks are missing, said started task will complain to systemd which in turn tells you about it. Eventually things get caught up and it disappears (the annoying message). The boot continues as you note.
Btw you could remove alsa-ucm with $ sudo dnf remove alsa-ucm. It will remove three files: alsa-ucm, alsa-utils, and libsamplerate. After that reboot. Your error messages about alsa-ucm will gone and your audio will still working.
If something goes wrong, you could reinstall it with $ sudo dnf install alsa-ucm alsa-utils libsamplerate.