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: Sat, 01 Nov 2025 16:29:37 +0000	[thread overview]
Message-ID: <bug-219904-215701-i4UBt0JdOn@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 #9 from popy (tobias.diendorfer@gmail.com) ---
@KeyofBlueS my first ticket to gigabyte #1818413 was just receiving an standard
answer...

Since there is only one comment about the issue on Reddit without any other
information, please provide more info(screenshot or video) about the issue.

Please also clear CMOS, install latest BIOS, install another SSD with no data
stored, install OS, APP Center, drivers, and check again.

... had not time to test any further so i went with the workaround (after boot
trigger standby and wakup in 5 seconds :-) )

But after i read your post, i am not giving up on this.

Have created an new ticket on gigabyte eSupport platform with link to your
comment.

Hope they take this now serious and just trying to reproduce the issue!

Otherwise i will go the ASUS route for my next system (NAS, PC, ...)

Will keep you updated.

-- 
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:[~2025-11-01 16:29 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 [this message]
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-i4UBt0JdOn@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