From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203905] amdgpu:actual_brightness has unreal/wrong value
Date: Thu, 06 May 2021 13:28:34 +0000 [thread overview]
Message-ID: <bug-203905-2300-50ZcN3hIWk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203905-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203905
--- Comment #32 from Filip Hejsek (filip.hejsek@gmail.com) ---
The acpi_video error seems to be
https://github.com/systemd/systemd/issues/15329 - first the ACPI driver creates
acpi_video1 device, then amdgpu removes it in favor of amdgpu_bl1, but systemd
still tries to set brightness on the removed device (which fails). You can
remove the error by masking `systemd-backlight@backlight:acpi_video1.service`.
The amdgpu_bl1 error is probably the bug i linked earlier -
https://bugzilla.kernel.org/show_bug.cgi?id=210263. Do you have silent boot? If
yes, you need to print something to console before setting backlight during
boot. You can use the workaround i posted here:
https://bbs.archlinux.org/viewtopic.php?pid=1971198#p1971198. If you use my
workaround, make sure to remove other workarounds you may have applied for that
error (like another service that runs systemctl start
systemd-backlight@backlight:amdgpu_bl0).
--
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:[~2021-05-06 13:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 20:02 [Bug 203905] New: amdgpu:actual_brightness has unreal/wrong value bugzilla-daemon
2019-06-17 9:44 ` [Bug 203905] " bugzilla-daemon
2019-06-17 10:48 ` bugzilla-daemon
2019-09-26 21:07 ` bugzilla-daemon
2020-02-05 5:34 ` bugzilla-daemon
2020-02-05 5:52 ` bugzilla-daemon
2020-02-09 13:33 ` bugzilla-daemon
2020-02-10 19:16 ` bugzilla-daemon
2020-07-30 6:15 ` bugzilla-daemon
2020-08-01 12:04 ` bugzilla-daemon
2020-08-03 20:13 ` bugzilla-daemon
2020-08-04 20:15 ` bugzilla-daemon
2020-08-17 9:46 ` bugzilla-daemon
2020-08-31 10:46 ` bugzilla-daemon
2020-09-01 19:07 ` bugzilla-daemon
2020-09-08 0:59 ` bugzilla-daemon
2020-09-08 1:00 ` bugzilla-daemon
2020-09-08 1:03 ` bugzilla-daemon
2020-11-23 21:02 ` bugzilla-daemon
2020-12-07 10:17 ` bugzilla-daemon
2021-02-02 14:06 ` bugzilla-daemon
2021-02-07 22:17 ` bugzilla-daemon
2021-02-08 20:47 ` bugzilla-daemon
2021-02-17 17:24 ` bugzilla-daemon
2021-02-17 17:25 ` bugzilla-daemon
2021-03-15 10:58 ` bugzilla-daemon
2021-03-25 13:58 ` bugzilla-daemon
2021-03-25 14:03 ` bugzilla-daemon
2021-03-27 8:45 ` bugzilla-daemon
2021-05-06 10:12 ` bugzilla-daemon
2021-05-06 11:50 ` bugzilla-daemon
2021-05-06 11:56 ` bugzilla-daemon
2021-05-06 13:28 ` bugzilla-daemon [this message]
2021-05-06 14:20 ` 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-203905-2300-50ZcN3hIWk@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.