X86 platform drivers
 help / color / mirror / Atom feed
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, 12 May 2026 09:47:54 +0000	[thread overview]
Message-ID: <bug-221430-215701-XgVEFYba4T@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221430-215701@https.bugzilla.kernel.org/>

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

--- Comment #8 from Hans de Goede (hansg@kernel.org) ---
(In reply to floquimaurice from comment #7)
> Hi Hans,
> 
> I added acpi_backlight=native nvidia_wmi_ec_backlight.force=1 (and
> nvidia.NVreg_EnableBacklightHandler=0) to my kernel command line.
> 
> Here are the folders that appeared in /sys/class/backlight/:
> 
>     intel_backlight (max_brightness: 192000)
> 
>     nvidia_0 (max_brightness: 100)
> 
>     nvidia_wmi_ec_backlight (max_brightness: 100)
> 
> I tried echoing different values into the brightness file for each of these
> three folders. The commands were accepted without any errors, but the
> physical screen brightness did not change at all.
> 
> I am just reporting the facts here. Let me know if you need me to run any
> other specific commands or tests!

Ok, so this is not a classic "which backlight driver should we use" problem.
But rather some issue with one of the backlight drivers.

The 192000 max-brightness for the intel_backlight looks suspicious.

Assuming that the LCD panel is indeed being driven by the Intel GPU and not
muxed to the nvidia GPU then I would start with filing a bug against the i915
driver:

https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html

What value did you select in the BIOS for the hybrid-GPU config ? If you
selected discrete only instead of one of the hybrid options then this more
likely is an nvidia driver issue...

-- 
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-05-12  9:47 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
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 [this message]
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-XgVEFYba4T@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