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: Fri, 19 Dec 2025 22:55:22 +0000 [thread overview]
Message-ID: <bug-219904-215701-qEU7yW8mCe@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 #19 from KeyofBlueS (keyofblues@gmail.com) ---
ASUS has recently released new official BIOS versions:
- ROG STRIX Z790-F GAMING WIFI - BIOS 3107 (2025/12/15)
- ROG STRIX B660-F GAMING WIFI - BIOS 3811 (2025/11/21)
Unfortunately, after installing these updates on both motherboards, I can
confirm that the beeper issue is still present and behaves exactly as before.
The fix works correctly only with the test BIOS versions that ASUS previously
provided to me through technical support.
I've already informed my ASUS contact and asked them to pass this information
to the technical team, in case the fix has not yet been fully merged into the
official BIOS releases.
I'll keep the community updated as soon as there are any further developments.
Thanks to everyone for the continued feedback and collaboration.
--
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 prev parent reply other threads:[~2025-12-19 22:55 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 [this message]
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-qEU7yW8mCe@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