Created attachment 1789853 [details]
alsa-info_v1.2.5-2.txt

The upstream bug: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1269

Same laptop model. Same problem.

my logs look different:

❯ journalctl  -b | grep -i pipewire
jun 10 16:52:45 lenovo-lumi systemd[4159]: Listening on PipeWire PulseAudio.
jun 10 16:52:52 lenovo-lumi systemd[4215]: Listening on PipeWire PulseAudio.
jun 10 16:52:55 lenovo-lumi systemd[4215]: Started PipeWire PulseAudio.
jun 10 16:52:55 lenovo-lumi rtkit-daemon[2877]: Successfully made thread 5194 of process 5194 (/usr/bin/pipewire-pulse) owned by '1000' high priority at nice level -11.
jun 10 16:52:55 lenovo-lumi rtkit-daemon[2877]: Successfully made thread 5193 of process 5193 (/usr/bin/pipewire) owned by '1000' high priority at nice level -11.
jun 10 16:52:55 lenovo-lumi rtkit-daemon[2877]: Successfully made thread 5196 of process 5194 (/usr/bin/pipewire-pulse) owned by '1000' RT at priority 20.
jun 10 16:52:55 lenovo-lumi rtkit-daemon[2877]: Successfully made thread 5195 of process 5193 (/usr/bin/pipewire) owned by '1000' RT at priority 20.
jun 10 16:52:55 lenovo-lumi rtkit-daemon[2877]: Successfully made thread 5202 of process 5202 (/usr/bin/pipewire-media-session) owned by '1000' high priority at nice level -11.
jun 10 16:52:55 lenovo-lumi rtkit-daemon[2877]: Successfully made thread 5204 of process 5202 (/usr/bin/pipewire-media-session) owned by '1000' RT at priority 20.
jun 10 16:52:55 lenovo-lumi pipewire-media-session[5202]: can't make factory instance: No such file or directory
jun 10 16:52:55 lenovo-lumi pipewire[5193]: '_ucm0003.hw:Generic_1': playback open failed: No such device
jun 10 16:52:55 lenovo-lumi pipewire[5193]: adapter 0x55f50e7a2fb0: can't get format: No such device
jun 10 16:52:55 lenovo-lumi pipewire[5193]: usage: node.name=<string>
jun 10 16:52:55 lenovo-lumi pipewire-media-session[5202]: error id:39 seq:357 res:-22 (Invalid argument): usage: node.name=<string>
jun 10 16:53:02 lenovo-lumi systemd[4159]: pipewire-pulse.socket: Deactivated successfully.
jun 10 16:53:02 lenovo-lumi systemd[4159]: Closed PipeWire PulseAudio.
jun 10 16:53:02 lenovo-lumi systemd[4159]: pipewire.socket: Deactivated successfully.

Obvious workaround:

# dnf install alsa-lib-1.2.4-5.fc34.x86_64 alsa-ucm-1.2.4-5.fc34.noarch alsa-utils-1.2.4-2.fc34.x86_64

Please, wait for the pipewire update.

A workaround for 1.2.5 (comment one line in /usr/share/alsa/ucm2/ucm.conf):

  # diff -u  /usr/share/alsa/ucm2/ucm-orig.conf /usr/share/alsa/ucm2/ucm.conf
  --- /usr/share/alsa/ucm2/ucm-orig.conf	2021-06-10 18:00:26.711251962 +0200
  +++ /usr/share/alsa/ucm2/ucm.conf	2021-06-10 18:00:33.155257230 +0200
  @@ -18,7 +18,7 @@
   Define.V2Module yes	# non-empty string to enable module name lookups (obsolete)
   Define.V2Name yes	# non-empty string to enable driver & card name lookups (obsolete)
 
  -Include.libgen.File "/lib/generic.conf"  # private alsa-lib configuration
  +#Include.libgen.File "/lib/generic.conf"  # private alsa-lib configuration
 
   If.driver {
 	Condition {

FEDORA-2021-642e1eef81 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-642e1eef81

New pipewire-0.3.30-2.fc3 is not yet in updates-testing repo so I download it from koji with following command:
$ koji download-build --arch=x86_64 pipewire-0.3.30-2.fc34

After pipewire update to newest version I have now audio fully functional on my T14s AMD.

Many thanks for so quick resolution.

FEDORA-2021-642e1eef81 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-642e1eef81`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-642e1eef81

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

*** Bug 1970729 has been marked as a duplicate of this bug. ***

FEDORA-2021-642e1eef81 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.