All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bug 210263] New: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
@ 2020-11-18 22:33 bugzilla-daemon
  2021-02-02 11:32 ` [Bug 210263] " bugzilla-daemon
                   ` (7 more replies)
  0 siblings, 8 replies; 9+ messages in thread
From: bugzilla-daemon @ 2020-11-18 22:33 UTC (permalink / raw)
  To: dri-devel

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

            Bug ID: 210263
           Summary: brightness device returns ENXIO (?) on brightness
                    restore at boot, with bootoption "quiet"
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.9.8
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: plusfabi@gmail.com
        Regression: No

Created attachment 293729
  --> https://bugzilla.kernel.org/attachment.cgi?id=293729&action=edit
dmesg

Following: https://github.com/systemd/systemd/issues/17645

If I set kernel boot option "quiet", systemd fails to restore brightness level
with error

Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0.

At boot.

full journal output is: 

journalctl -b -1 -u systemd-backlight@backlight:amdgpu_bl0.service
-- Logs begin at Thu 2020-09-17 08:15:00 CEST, end at Tue 2020-11-17 14:19:18
CET. --
Nov 17 14:15:15 frigg systemd[1]: Starting Load/Save Screen Backlight
Brightness of backlight:amdgpu_bl0...
Nov 17 14:15:15 frigg systemd-backlight[325]: amdgpu_bl0: Failed to write
system 'brightness' attribute: No such device or address
Nov 17 14:15:15 frigg systemd[1]:
systemd-backlight@backlight:amdgpu_bl0.service: Main process exited,
code=exited, status=1/FAILURE
Nov 17 14:15:15 frigg systemd[1]:
systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'.
Nov 17 14:15:15 frigg systemd[1]: Failed to start Load/Save Screen Backlight
Brightness of backlight:amdgpu_bl0.


This is an AMD Renoir system, with AMD Ryzen 5 4500U APU,

This happens only, if I set 'quiet' as boot option. If I remove it, brightness
restore works fine.

If I boot with quiet set, after login I can do 

systemctl start systemd-backlight@backlight:amdgpu_bl0.service

And it will successfully restore my brightness level.

-- 
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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug 210263] brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
  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 ` bugzilla-daemon
  2021-02-10 11:19 ` bugzilla-daemon
                   ` (6 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2021-02-02 11:32 UTC (permalink / raw)
  To: dri-devel

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

--- Comment #1 from ninelore@protonmail.com ---
Can confirm this with a Ryzen 7 4800H. Any news on this?

-- 
You may reply to this email to add a comment.

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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug 210263] brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
  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
                   ` (5 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2021-02-10 11:19 UTC (permalink / raw)
  To: dri-devel

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

--- Comment #2 from ninelore@protonmail.com ---
I just found out that this Issue does NOT occur when you additionally add the
fbcon=nodefer kernel parameter.

-- 
You may reply to this email to add a comment.

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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug 210263] brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
  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
                   ` (4 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2021-02-10 16:10 UTC (permalink / raw)
  To: dri-devel

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

--- Comment #3 from Fabian (plusfabi@gmail.com) ---
(In reply to ninelore from comment #2)
> I just found out that this Issue does NOT occur when you additionally add
> the fbcon=nodefer kernel parameter.

This workaround works for me too.

-- 
You may reply to this email to add a comment.

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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug 210263] brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
  2020-11-18 22:33 [Bug 210263] New: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet" bugzilla-daemon
                   ` (2 preceding siblings ...)
  2021-02-10 16:10 ` bugzilla-daemon
@ 2021-07-29 13:23 ` bugzilla-daemon
  2021-12-02  8:35 ` bugzilla-daemon
                   ` (3 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2021-07-29 13:23 UTC (permalink / raw)
  To: dri-devel

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

Jonas Platte (jplatte+linux@posteo.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jplatte+linux@posteo.de

--- Comment #4 from Jonas Platte (jplatte+linux@posteo.de) ---
Workaround works for me too, on a Lenovo Ideapad 530S-14ARR with an AMD Ryzen
2500U. I also set acpi_backlight=vendor to fix the same error message for
backlight:acpi_video1. (No idea why it tries to restore backlight brightness
twice)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug 210263] brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
  2020-11-18 22:33 [Bug 210263] New: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet" bugzilla-daemon
                   ` (3 preceding siblings ...)
  2021-07-29 13:23 ` bugzilla-daemon
@ 2021-12-02  8:35 ` bugzilla-daemon
  2022-01-05 21:25 ` bugzilla-daemon
                   ` (2 subsequent siblings)
  7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2021-12-02  8:35 UTC (permalink / raw)
  To: dri-devel

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

--- Comment #5 from Fabian (fabiscafe@mailbox.org) ---
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?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug 210263] brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
  2020-11-18 22:33 [Bug 210263] New: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet" bugzilla-daemon
                   ` (4 preceding siblings ...)
  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
  7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2022-01-05 21:25 UTC (permalink / raw)
  To: dri-devel

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

jaromir.obr@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jaromir.obr@gmail.com

--- Comment #6 from jaromir.obr@gmail.com ---
@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.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug 210263] brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
  2020-11-18 22:33 [Bug 210263] New: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet" bugzilla-daemon
                   ` (5 preceding siblings ...)
  2022-01-05 21:25 ` bugzilla-daemon
@ 2022-01-08 13:05 ` bugzilla-daemon
  2022-01-12 15:08 ` bugzilla-daemon
  7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2022-01-08 13:05 UTC (permalink / raw)
  To: dri-devel

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

--- Comment #7 from jaromir.obr@gmail.com ---
Related fix for resume from suspend in kernel 5.15 explained here:
https://www.phoronix.com/scan.php?page=news_item&px=AMD-S2idle-Fix-Linux-5.15
The say it could also fix an issue with brightness.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug 210263] brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
  2020-11-18 22:33 [Bug 210263] New: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet" bugzilla-daemon
                   ` (6 preceding siblings ...)
  2022-01-08 13:05 ` bugzilla-daemon
@ 2022-01-12 15:08 ` bugzilla-daemon
  7 siblings, 0 replies; 9+ messages in thread
From: bugzilla-daemon @ 2022-01-12 15:08 UTC (permalink / raw)
  To: dri-devel

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.

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2022-01-12 15:08 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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.