From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221430] nvidia_wmi_ec_backlight: brightness writes silently dropped on HP OMEN 16 (2025)
Date: Tue, 05 May 2026 12:23:41 +0000 [thread overview]
Message-ID: <bug-221430-215701-lgKHZzqwmZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221430-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221430
Hans de Goede (hansg@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hansg@kernel.org
--- Comment #4 from Hans de Goede (hansg@kernel.org) ---
Hi, thank you for your bug report.
Problems like this with nvidia_wmi_ec backlight control are a known issue. I've
had a plan to properly fix this for a while now, but I don't have the time to
implement this.
I've taken the time to write this down, see:
https://lore.kernel.org/dri-devel/f10c039b-e9ef-4aae-8291-8f1e71074586@oss.qualcomm.com/
In the mean time as a workaround can you try adding "acpi_backlight=native" to
your kernel commandline I suspect/hope that that will help.
--
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:[~2026-05-05 12:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 21:23 [Bug 221430] New: nvidia_wmi_ec_backlight: brightness writes silently dropped on HP OMEN 16 (2025) bugzilla-daemon
2026-04-28 21:25 ` [Bug 221430] " bugzilla-daemon
2026-04-28 21:25 ` bugzilla-daemon
2026-04-28 21:25 ` bugzilla-daemon
2026-05-05 12:23 ` bugzilla-daemon [this message]
2026-05-10 10:16 ` bugzilla-daemon
2026-05-10 15:20 ` bugzilla-daemon
2026-05-11 22:29 ` bugzilla-daemon
2026-05-12 9:47 ` bugzilla-daemon
2026-05-12 20:22 ` bugzilla-daemon
2026-05-12 20:23 ` bugzilla-daemon
2026-05-12 20:25 ` bugzilla-daemon
2026-05-12 20:25 ` bugzilla-daemon
2026-05-15 10:01 ` bugzilla-daemon
2026-06-08 11:31 ` 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-221430-215701-lgKHZzqwmZ@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