-
-
Notifications
You must be signed in to change notification settings - Fork 857
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Brightness control on Raven is broken #236
Comments
What is the display type? |
Where can I see this in macOS? |
I meant LCD, OLED, ... if it has HDR, etc. |
It seems like this issue is specific to Raven (DCN 1). I have not seen the issue occur on Renoir (DCN 2). It is possible that AMDRadeonX6000Framebuffer has a bug with the DMCU control. I will investigate how to solve this without removing the newly added Catalina support for brightness control and etc. |
Okay. I look forward to your fix. And yes, thanks for such a great project, you made it possible for me not to buy a macbook for overprice. :) |
An idea:maybe we can design a command for users to add boot-args to disable Catalina brightness control code, or delete Catalina brightness control code, because Catalina is outdated. |
I improved the situation a little bit. |
macOS Version
Ventura
What is your CPU's model?
AMD Ryzen 5 PRO 3500U
Please describe the behaviour in detail.
After upgrading to the latest version of NootedRed: https://github.com/ChefKissInc/NootedRed/actions/runs/8277805359 (commit [274ba77])
The brightness control stopped working properly, the brightness reduction via the native "Brightness Slider" from macOS only goes down one point from the maximum brightness value, the brightness does not go any lower after moving the slider.
In the previous version of Nootedred:
https://github.com/ChefKissInc/NootedRed/actions/runs/7765787829 (Commit [eff598f])
The brightness control was working properly. Via the native "Brightness Slider" from macOS.
Videos demonstrating the problem are attached in two files.
Before:
https://github.com/ChefKissInc/NootedRed/assets/116596455/5e0ec249-8dbe-4360-8178-868efe9eb4d6
After:
https://github.com/ChefKissInc/NootedRed/assets/116596455/285fd8c8-38a0-4218-a8a4-97404bcb6f7d
What should've happened instead?
Brightness control, well, what else is there? :D
If applicable, attach the .gpuRestart, .panic, etc file related to this issue.
Pointless, the problem is inside Nootedred, apparently this problem appeared after commit d6554a3: https://github.com/ChefKissInc/NootedRed/actions/runs/8253163850
Bug report submission terms
The text was updated successfully, but these errors were encountered: