From: LinArcX <LinArcX@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: awkward sound in boot up(just seen in recent versions of linux kernel)
Date: Sat, 12 Aug 2023 15:46:33 +0200 [thread overview]
Message-ID: <20230812134633.6TTCQcRGGE3fJ7x_jja-cM6C3QxBbyL3rIqbb7AQz9U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45029@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]
New comment by LinArcX on void-packages repository
https://github.com/void-linux/void-packages/issues/45029#issuecomment-1675923381
Comment:
ok, I found the issue. by disabling this kernel module: ` sudo modprobe -r snd_hda_intel` i can log in successfully but without no sound for sure. if I try to enable it again, I'll hear the same harsh sound again.
I think one of my audio devices has some problems with newer versions of Linux kernel.
This is the information about them:
```
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
DeviceName: Onboard Audio
Subsystem: ASUSTeK Computer Inc. Device 1ac3
Flags: bus master, fast devsel, latency 0, IRQ 30
Memory at df600000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1)
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at dd080000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
```
next prev parent reply other threads:[~2023-08-12 13:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 8:54 [ISSUE] " LinArcX
2023-07-14 8:56 ` LinArcX
2023-08-12 13:20 ` LinArcX
2023-08-12 13:21 ` LinArcX
2023-08-12 13:21 ` LinArcX
2023-08-12 13:45 ` LinArcX
2023-08-12 13:46 ` LinArcX [this message]
2023-08-17 3:01 ` tornaria
2023-08-17 6:07 ` LinArcX
2023-08-17 7:03 ` LinArcX
2023-08-17 14:33 ` tornaria
2023-08-17 15:41 ` LinArcX
2023-08-22 20:39 ` LinArcX
2023-10-05 16:58 ` namgo
2023-10-05 17:35 ` LinArcX
2023-11-01 12:18 ` LinArcX
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=20230812134633.6TTCQcRGGE3fJ7x_jja-cM6C3QxBbyL3rIqbb7AQz9U@z \
--to=linarcx@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).