public inbox for platform-driver-x86@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 219904] pc speaker not working (just pop's/click's) on intel chipsets gen 6, 7 and probably more
Date: Thu, 09 Apr 2026 13:40:54 +0000	[thread overview]
Message-ID: <bug-219904-215701-2gfDpQXLLk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219904-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219904

--- Comment #20 from KeyofBlueS (keyofblues@gmail.com) ---
Good news, the issue is now officially resolved by ASUS.

ASUS released new BIOS versions for the motherboards I had reported to them:

- ROG STRIX Z790-F GAMING WIFI: BIOS 3201
- ROG STRIX B660-F GAMING WIFI: BIOS 4001

ASUS support clarified that the feature is present but not enabled by default.

To make the PC Speaker work correctly, you need to enable the following option
in the BIOS:

"BIOS" > "Advanced Mode" > "Advanced" > "Onboard Devices Configuration" > "8254
timer clock in OS"

After enabling this option on the Z790-F with BIOS 3201, I can confirm that the
PC Speaker works correctly again.

Unfortunately, I cannot test the B660-F at the moment, but since the same
change was reported for its BIOS as well, it should behave the same.

It's currently not clear whether this fix will be released for other
motherboards too. If you are affected, it's worth checking whether a BIOS
update is available for your motherboard and then looking in the BIOS for the
option "8254 timer clock in OS" (or something similar).

If you can't find it, I recommend contacting your motherboard vendor's support
and mentioning the issue, as well as the fact that ASUS solved it by
introducing this BIOS option. That may help them reproduce the fix on their
side.

Huge thanks to ASUS support and their technical team for actually investigating
the issue and implementing a fix. The support experience was genuinely
impressive.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-04-09 13:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21 15:09 [Bug 219904] New: pc speaker not working (just pop's/click's) on intel chipsets gen 6, 7 and probably more bugzilla-daemon
2025-03-21 17:11 ` [Bug 219904] " 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 [this message]
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-2gfDpQXLLk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox