From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203905] amdgpu:actual_brightness has unreal/wrong value
Date: Mon, 15 Mar 2021 10:58:03 +0000 [thread overview]
Message-ID: <bug-203905-2300-cU6PeieArB@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 #25 from m11.1l1.f64@gmail.com ---
I found another workaround and it's easier than EVER and it's done via
mkinitcpio😁
First, what's mkinitcpio(https://wiki.archlinux.org/index.php/Mkinitcpio)?
The initial ramdisk is in essence a very small environment (early userspace)
which loads various kernel modules and sets up necessary things before handing
over control to init. This makes it possible to have, for example, encrypted
root file systems and root file systems on a software RAID array. mkinitcpio
allows for easy extension with custom hooks, has autodetection at runtime, and
many other features.
So go ahead and edit with `sudo nano /etc/mkinitcpio.conf`
Then add the "amdgpu" in the modules section like this:
`MODULES=(amdgpu)`
After that, simply run `sudo mkinitcpio -P` so that it regenerates mkinitcpio
for all kernels
This solved my issue, I hope it works for others 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
next prev parent reply other threads:[~2021-03-15 10:58 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 [this message]
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
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-cU6PeieArB@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).