Bug 1893813 - Lenove ThinkPad T495s Ryzen 7 Pro 3700U microphone and speaker do not work
Summary: Lenove ThinkPad T495s Ryzen 7 Pro 3700U microphone and speaker do not work
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-02 17:02 UTC by Bernhard Schuster
Modified: 2021-11-30 16:32 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 16:32:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lsmod output (6.60 KB, text/plain)
2020-11-02 17:02 UTC, Bernhard Schuster
no flags Details
audio source list (16.07 KB, text/plain)
2020-11-02 17:04 UTC, Bernhard Schuster
no flags Details
journalctl --no... > dmesg.txt (113.95 KB, text/plain)
2020-11-02 17:05 UTC, Bernhard Schuster
no flags Details
screenshot showing that there is activity in pavucontrol, but not in gnome-settings (200.83 KB, image/png)
2020-11-03 07:51 UTC, Bernhard Schuster
no flags Details

Description Bernhard Schuster 2020-11-02 17:02:46 UTC
Created attachment 1725909 [details]
lsmod output

Created attachment 1725909 [details]
lsmod output

1. Please describe the problem:

Microphone does not record anything from gnome.
No speaker sound, except for when used with hotkeys <Fn><Speaker+> or <Fn><Speaker+>

In dmesg one can see 

Nov 02 17:28:04 kernel: acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517

followed by 

Nov 02 17:28:03 kernel: snd_pci_acp3x 0000:06:00.5: enabling device (0000 -> 0002)
Nov 02 17:28:03 kernel: snd_pci_acp3x 0000:06:00.5: Invalid ACP audio mode : 2



Issues: which have partial overlap:

https://bugzilla.redhat.com/show_bug.cgi?id=1850122
https://www.udoo.org/forum/threads/acp-invalid-audio-mode.32523/

It might be a race between different modules for one and the same device, two drivers support the PCI ID

https://linux-hardware.org/index.php?id=pci:1022-15e2-103c-8433


``
06:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor
	Subsystem: Lenovo Device 5127
	Flags: bus master, fast devsel, latency 0, IRQ 80
	Memory at d0580000 (32-bit, non-prefetchable) [size=256K]
	Capabilities: <access denied>
	Kernel driver in use: snd_rn_pci_acp3x
	Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x
```

https://bugzilla.kernel.org/show_bug.cgi?id=208699 states that mode 2 is not supported.

Audio with a blutooth headphone works flawlessly though.

2. What is the Version-Release number of the kernel:

5.8.17-300.fc33.x86_64 #1 SMP Thu Oct 29 15:55:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Fedora 32 with all updates worked fine.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Yes, every boot.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Does not appear on rawhide, 5.10-rc1, but fails with a different error message.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

Not that I am aware of.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Bernhard Schuster 2020-11-02 17:04:36 UTC
Created attachment 1725910 [details]
audio source list

Comment 2 Bernhard Schuster 2020-11-02 17:05:34 UTC
Created attachment 1725911 [details]
journalctl --no... > dmesg.txt

Comment 3 Bernhard Schuster 2020-11-03 07:51:17 UTC
Created attachment 1726116 [details]
screenshot showing that there is activity in pavucontrol, but not in gnome-settings

Comment 4 Bernhard Schuster 2020-11-03 08:25:26 UTC
Adding blacklists for the Renoir (Ryzen 4xxxU) variant to /etc/modprobe.d/yada-blacklist.conf with content

blacklist snd_rn_pci_acp3x
blacklist snd_acp3x_rn

makes the microphone show up properly (no more unplugged tag) and the audio input also shows up in gnome-settings

Comment 5 Ben Cotton 2021-11-04 17:24:38 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2021-11-30 16:32:53 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.