Github messages for voidlinux
 help / color / mirror / Atom feed
From: medanisjbara <medanisjbara@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Sound is not working because CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM is not set
Date: Fri, 19 Aug 2022 10:39:04 +0200	[thread overview]
Message-ID: <20220819083904.O81V3wTWrZq3z-Xo_Y_w_KesFv4-3NunDfvqS3kt1nw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38755@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 6290 bytes --]

New comment by medanisjbara on void-packages repository

https://github.com/void-linux/void-packages/issues/38755#issuecomment-1220406957

Comment:
@icp1994 Unfortunately, I just tried installing that, and it didn't work. I even went through the trouble of booting archlinux from a usb using voidlinux's kernel and installing `linux-firmware` and `alsa-firmware` (I didn't know about the packages you just provided. But I knew something else that might've worked so I tried it).  
I had no luck with both firmwares. Yet enabling that single option in the kernel configuration just solves my issue (at least temporarily).

So I believe this is a kernel problem. Not a firmware problem.

I booted void linux with the default void kernel (To gather some information about this) and sound didn't work even when I rebooted to the custom kernel. It just died. Looking at `dmesg`. There was this section that appeared at boot (and every time I try to `rmmod snd_hda_intel && modprobe snd_hda_intel`.)
```
[  396.917687] pcieport 0000:00:01.1: Data Link Layer Link Active not set in 1000 msec
[  396.917756] snd_hda_intel 0000:01:00.1: can't change power state from D3cold to D0 (config space inaccessible)
[  396.917885] snd_hda_intel 0000:01:00.1: Disabling MSI
[  396.917900] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[  396.917915] snd_hda_intel 0000:01:00.1: VGA controller is disabled
[  396.917917] snd_hda_intel 0000:01:00.1: Delaying initialization
[  396.929024] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC285: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[  396.929028] snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[  396.929030] snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[  396.929031] snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
[  396.929032] snd_hda_codec_realtek hdaudioC1D0:    inputs:
[  396.929032] snd_hda_codec_realtek hdaudioC1D0:      Mic=0x19
[  396.929033] snd_hda_codec_realtek hdaudioC1D0:      Internal Mic=0x12
[  397.589500] input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:08.1/0000:05:00.6/sound/card1/input18
[  397.589720] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:05:00.6/sound/card1/input19
```
And then booting voidlinux with arch's `linux-zen` just fixed the problem again.

My assumption is that voidlinux's default kernel saves some faulty value somewhere which my custom kernel (void's config with `CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM` enabled) is enable to overwrite. Hens the `can't change power state from D3cold to D0` in dmesg.  
My assumption is based on the existence of a [bug](https://wiki.archlinux.org/title/Backlight#Backlight_is_always_at_full_brightness_after_a_reboot_with_amdgpu_driver) where a value is not saved correctly which might cause problems but I am no expert.  
For all I know, enabling the option mentioned in the title fixes the problem as long as the last booted kernel is not the defaut kernel (the one who has that option not set).

Before I finish. I believe I should provide some hardware specifications. So here is the output of `lspci`
```
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] (rev ff)
01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev ff)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16)
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter
04:00.0 Non-Volatile memory controller: Solid State Storage Technology Corporation Device 9100 (rev 03)
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev c7)
05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
05:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 01)
05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller
06:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
06:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
```


  parent reply	other threads:[~2022-08-19  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 10:45 [ISSUE] " medanisjbara
2022-08-18 14:49 ` icp1994
2022-08-19  8:38 ` medanisjbara
2022-08-19  8:39 ` medanisjbara [this message]
2022-08-26 18:43 ` mvf
2022-08-27 15:55 ` sgn
2024-06-14  6:11 ` [ISSUE] [CLOSED] " classabbyamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220819083904.O81V3wTWrZq3z-Xo_Y_w_KesFv4-3NunDfvqS3kt1nw@z \
    --to=medanisjbara@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).