-
Notifications
You must be signed in to change notification settings - Fork 513
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
[rpi4] Limited RGB range #12476
Comments
Not a bug. You're trying to run a command to control an Intel GPU-specific parameter on an xorg display, while rpi4 uses a VideoCore GPU on Wayland. The correct way to adjust such parameters on rpi4 is in Try setting For more info see https://elinux.org/RPiconfig |
@n2qz |
You tested it with |
I tested |
Install the build from this drive: https://drive.google.com/drive/folders/1OaxfQoMTO08jVlKbaMM-iGpo1sXnIj4P?usp=drive_link Put your modetest commands in Here's what I tested with, I can observe that the values are changed but I don't notice any change in the way the display appears on my system:
|
Thanks, modetest works, it switches to full mode. But in this build there is a problem not related to modetest. For some reason the whole interface does not work smoothly, as if in 20-25fps (although according to the frame counter more). Compared with version 40 and there everything is fine. |
Thanks for the confirmation. I'll get the modetest binary included in either v41 or v42, depending on when our next buildroot bump occurs. The other issue is completely separate, and was already reported. You may want to chime in on the relevant report. |
This is relevant not only for raspberry pi 4, but for all models running on kms driver. At least |
Batocera build version
40
Your architecture
raspberry pi 4
Your Graphic Processor Unit(s) (GPU)
raspberry pi 4
Issue description
When I connect to my raspberry pi 4 monitor via hdmi I get a limited rgb range, in other distributions I can force switch to full rgb range with xrandr.
xrandr --output HDMI-1 --set "Broadcast RGB" "Full"
It seems to be possible to do it with other utilities such as modetest and kmstest, but batocera for raspberry pi 4 doesn't have anything like that, so I can't fix this problem.
The text was updated successfully, but these errors were encountered: