From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ALSA Development <alsa-devel@alsa-project.org>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Oder Chiou <oder_chiou@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
aguertin <aguertin+kbz@aguertin.net>
Subject: Fwd: No sound from monitor speakers unless snd_hda_codec_realtek is inserted before snd_hda_intel
Date: Thu, 26 Oct 2023 15:10:17 +0700 [thread overview]
Message-ID: <d6e886d4-9084-4d56-a544-36d9ba526dcd@gmail.com> (raw)
Hi,
I notice a bug report on Bugzilla [1]. Quoting from it:
> I have an Asus Pro B550M-C/CSM motherboard, which uses a Realtek ALC887-VD, and a monitor (with speakers) plugged in via DisplayPort. On booting normally, I get no sound from the monitor speakers (other sound outputs like USB or bluetooth headphones work fine).
>
> I have found two workarounds for getting the monitor sound working:
> 1. rmmod snd_hda_intel && modprobe snd_hda_intel
> 2. ensure that snd_hda_codec_realtek is inserted before snd_hda_intel (e.g. by adding `softdep snd_hda_intel pre: snd_hda_codec_realtek` in modprobe.d)
>
> Notably, timing does not seem to be an issue: even if snd_hda_intel is blacklisted from loading at boot, it will not work when it is loaded unless is is unloaded and loaded again or snd_hda_codec_realtek is loaded first.
>
> This is not a recent regression - it has been happening as long as I have had the hardware (since at least late 2021).
>
> Since it's not clear which is more useful, I am attaching two runs of alsa-info.sh - one is from a normal boot with sound not working, and the other is after running rmmod snd_hda_intel && modprobe snd_hda_intel with sound working.
See Bugzilla for the full thread and alsa-input output on both working
and buggy cases.
AFAIK, it looks like module dependency issue.
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=218027
--
An old man doll... just what I always wanted! - Clara
reply other threads:[~2023-10-26 8:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d6e886d4-9084-4d56-a544-36d9ba526dcd@gmail.com \
--to=bagasdotme@gmail.com \
--cc=aguertin+kbz@aguertin.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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
all inboxes | Powered by JetHome®