Bug 2027280

Summary: Internal audio card not detected (Everest ESSX8336 / AMD Renoir 4800H)
Product: [Fedora] Fedora Reporter: Raj R <dutiful.monday586>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 35CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 16:00:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journalctl --no-hostname -k
none
hwinfo --sound
none
lspci -nnk
none
lsmod | grep -i snd
none
details of /proc/asound
none
screenshots of Sound settings and pavucontrol (no external display)
none
screenshots of Sound settings and pavucontrol (external display connected) none

Description Raj R 2021-11-29 10:07:34 UTC 
Created attachment 1843985 [details]
journalctl --no-hostname -k

1. Please describe the problem:

The laptop's internal audio card is not detected. So, the stereo jack also doesn't work.
Audio via Bluetooth and external HDMI port works fine.

Under Windows, they work fine.

There are other users using other distros (LTS and latest kernels) facing the same issue letting me believe that a kernel fix is possibly needed. I, personally, have tried almost 5-6 different live environments ranging from kernels 5.10 to 5.16. None of them detect the internal sound card or show Dummy Output.

Device details on linux-hardware.org -> https://linux-hardware.org/?id=pci:1002-1637-1e83-3e33

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

Linux 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

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 :

No.

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

Boot your laptop. Check SOUND in Gnome Settings or pavucontrol. Internal speakers/audio card is not detected.

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``:

It doesn't work on a live environment of Rawhide (with Kernel 5.16rc2)

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

I don't think so.

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 Raj R 2021-11-29 10:08:46 UTC 
Created attachment 1843986 [details]
hwinfo --sound
Comment 2 Raj R 2021-11-29 10:09:42 UTC 
Created attachment 1843987 [details]
lspci -nnk
Comment 3 Raj R 2021-11-29 10:11:00 UTC 
Created attachment 1843989 [details]
lsmod | grep -i snd
Comment 4 Raj R 2021-11-29 10:13:58 UTC 
Created attachment 1843992 [details]
details of /proc/asound
Comment 5 Raj R 2021-11-29 10:20:11 UTC 
Created attachment 1843993 [details]
screenshots of Sound settings and pavucontrol (no external display)
Comment 6 Raj R 2021-11-29 10:21:00 UTC 
Created attachment 1843994 [details]
screenshots of Sound settings and pavucontrol (external display connected)
Comment 7 Raj R 2021-12-01 16:09:04 UTC 
I booted into Windows today to make sure everything was up to date and noticed that the audio chip used is "Everest ESSX8336 I2S".

I googled that and found that support was added to the kernel 5.16 about a month ago and some fixes were added about a week ago. However, skimming through the commits/related issues, it seems that the fixes are applicable to Intel systems only.

This is the related issue for AMD (no progress so far) -> https://github.com/thesofproject/linux/issues/3249
Comment 8 Raj R 2021-12-03 14:24:54 UTC 
I have returned the laptop so I would be unable to help out with this issue but it still needs fix/support.
Comment 9 Ben Cotton 2022-11-29 17:24:55 UTC 
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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
'version' of '35'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 10 Ben Cotton 2022-12-13 16:00:32 UTC 
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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