From: medanisjbara <medanisjbara@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Sound is not working because CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM is not set
Date: Thu, 18 Aug 2022 12:45:22 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38755@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
New issue by medanisjbara on void-packages repository
https://github.com/void-linux/void-packages/issues/38755
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.17_1 x86_64 AuthenticAMD uptodate rFF
### Package(s) Affected
linux5.18-5.18.17_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Sound should work out of the box.
### Actual behaviour
`alsamixer` didn't detect my sound card.
But when using another kernel (e.g. [arch's zen kernel](https://archlinux.org/packages/extra/x86_64/linux-zen/) ) and everything was working fine.
After checking the differences in `lsmod` and looking through both configs. I was able to find the module `snd_hda_intel_hdmi` present in the kernel that had sound working. And void's kernel config contained this.
```
# CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM is not set
```
I tried rebuilding the kernel with void linux's config file (from `/proc/config.gz`) with that option both enabled and disabled. And I can confirm that enabling it does solve my problem.
### Steps to reproduce
* Buy a computer with the same hardware as mine.
* Install void linux (I installed void for the first time only a couple of days ago).
* Use `alsamixer` or try to get sound working in any way (using the default kernel that comes with void.
PS: Thank you for this amazing distribution!!!!
next reply other threads:[~2022-08-18 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 10:45 medanisjbara [this message]
2022-08-18 14:49 ` icp1994
2022-08-19 8:38 ` medanisjbara
2022-08-19 8:39 ` medanisjbara
2022-08-26 18:43 ` mvf
2022-08-27 15:55 ` sgn
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38755@inbox.vuxu.org \
--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).