From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 219904] New: pc speaker not working (just pop's/click's) on intel chipsets gen 6, 7 and probably more
Date: Fri, 21 Mar 2025 15:09:16 +0000 [thread overview]
Message-ID: <bug-219904-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219904
Bug ID: 219904
Summary: pc speaker not working (just pop's/click's) on intel
chipsets gen 6, 7 and probably more
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: tobias.diendorfer@gmail.com
Regression: No
The internal pc speaker just pop's/click's when ill try to play sound, with ex.
beep command. It does'nt matter which frequency or duration, the issue is
always here.
* The pcspkr module is loaded.
* The issue occurs on Unraid v7+ (slackware with kernel 6.6.78) and also
ubuntu 24.04.
* The issue is also present in windows.
The issue goes away when you put the device to standby and wake it from
standby.
That's really weird!
Here are some links:
https://forums.unraid.net/topic/168324-biosinternal-speaker-issues-clicking-rather-than-beeping/
https://www.reddit.com/r/linuxquestions/comments/10jg9ip/pc_speaker_makes_clicking_sound_instead_of_beep/?embed_host_url=https://forums.unraid.net/index.php
Affected (confirmed) boards are:
* Asus PRIME B760M-A D4-CSM
* Gigabyte H610I
* ASRock B660
So affected chipsets seems gen 6, 7 and probably more.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2025-03-21 15:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 15:09 bugzilla-daemon [this message]
2025-03-21 17:11 ` [Bug 219904] pc speaker not working (just pop's/click's) on intel chipsets gen 6, 7 and probably more bugzilla-daemon
2025-03-21 17:14 ` bugzilla-daemon
2025-03-21 17:34 ` bugzilla-daemon
2025-03-22 7:31 ` bugzilla-daemon
2025-03-22 10:03 ` bugzilla-daemon
2025-03-22 12:51 ` bugzilla-daemon
2025-03-22 17:47 ` bugzilla-daemon
2025-11-01 9:23 ` bugzilla-daemon
2025-11-01 16:29 ` bugzilla-daemon
2025-11-01 16:58 ` bugzilla-daemon
2025-11-01 17:51 ` bugzilla-daemon
2025-11-05 20:00 ` bugzilla-daemon
2025-11-28 18:41 ` bugzilla-daemon
2025-11-28 18:55 ` bugzilla-daemon
2025-11-28 18:58 ` bugzilla-daemon
2025-11-28 19:47 ` bugzilla-daemon
2025-11-28 21:44 ` bugzilla-daemon
2025-11-29 10:17 ` bugzilla-daemon
2025-12-01 11:38 ` bugzilla-daemon
2025-12-19 22:55 ` bugzilla-daemon
2026-04-09 13:40 ` bugzilla-daemon
2026-04-09 15:16 ` bugzilla-daemon
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=bug-219904-215701@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.