All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207833] Brightness control not working on ASUS TUF FA506IU (AMD Ryzen 7 4800H / Nvidia GTX 1660 Ti)
Date: Fri, 29 May 2020 07:44:14 +0000	[thread overview]
Message-ID: <bug-207833-2300-hOVrKqELE6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207833-2300@https.bugzilla.kernel.org/>

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

--- Comment #2 from julen.pardo@outlook.es ---
(In reply to Mateusz from comment #1)
> Does it work better after closing lid and reopen it? (the system goes
> suspend)
> I have an ASUS Zephyrus G14 with similar specs and this is the case, after
> closing lid and suspending when I wake up the system brightness control
> works good.

Not really, it's the same. Actually I just get a blackscreen and I need to shut
it down :) 

But I've discovered something interesting. If I first boot into the Windows
partition and then reboot into the Linux one, the brightness control works
fine.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-05-29  7:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 17:46 [Bug 207833] New: Brightness control not working on ASUS TUF FA506IU (AMD Ryzen 7 4800H / Nvidia GTX 1660 Ti) bugzilla-daemon
2020-05-29  7:35 ` [Bug 207833] " bugzilla-daemon
2020-05-29  7:44 ` bugzilla-daemon [this message]
2020-05-29 13:10 ` bugzilla-daemon
2021-02-02 14:21 ` bugzilla-daemon
2021-05-06 14:03 ` bugzilla-daemon
2021-05-06 15:10 ` 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-207833-2300-hOVrKqELE6@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.