From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 210263] brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
Date: Wed, 12 Jan 2022 15:08:49 +0000 [thread overview]
Message-ID: <bug-210263-2300-UEadgH0kBO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210263-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210263
--- Comment #8 from ninelore@protonmail.com ---
(In reply to Fabian from comment #5)
> As of Kernel 5.15, I don't need fbcon=nodefer anymore. By default the
> backlight works and is set on start. I still get from time to time an
> boot-error by systemd, but that can be also worked around by loading amdgpu
> early.
>
> Can someone confirm this?
(In reply to jaromir.obr from comment #6)
> @Fabian
> I have the same experience. I was running kernel 5.13 on Ubuntu 21.10 and
> when I upgraded to mainline kernel 5.15.13 (using
> https://github.com/pimlie/ubuntu-mainline-kernel.sh), the service
> "systemd-backlight@backlight:amdgpu_bl0.service" starts as expected and
> backlight seems to be restored.
>
> With kernel 5.13 it failed: "Failed to start Load/Save Screen Backlight
> Brightness of backlight:amdgpu_bl0" and I was not able to start it manually.
Can confirm this bug is fixed with 5.15
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2022-01-12 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 22:33 [Bug 210263] New: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet" bugzilla-daemon
2021-02-02 11:32 ` [Bug 210263] " bugzilla-daemon
2021-02-10 11:19 ` bugzilla-daemon
2021-02-10 16:10 ` bugzilla-daemon
2021-07-29 13:23 ` bugzilla-daemon
2021-12-02 8:35 ` bugzilla-daemon
2022-01-05 21:25 ` bugzilla-daemon
2022-01-08 13:05 ` bugzilla-daemon
2022-01-12 15:08 ` bugzilla-daemon [this message]
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-210263-2300-UEadgH0kBO@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).