Opened 3 years ago
Closed 16 months ago
#16413 closed bug (fixed)
Unable to change refresh rate setting (Hz) under "Screen", under preferences.
|Reported by:||mpxlbs||Owned by:||nobody|
Description (last modified by )
Carefully submitting this ticket. I don't know if it's a Vesa/Framebuffer limitation/invalid ticket.
Trying to select a new refresh rate under screen other than 60hz results in
"The screen mode could not be set: Invalid argument"
My display supports up to 144hz and uses displayport 1.2 to and from the GPU.
Change History (7)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
by , 3 years ago
Syslog July 17th
comment:3 by , 2 years ago
I can reproduce this problem. In fact refresh setting is the only parameter that I can change as there are only 2 modes detected for my display: resolution and color modes are constant (1920x1080x32) and I have 2 refresh rates available.
I've managed to debug that it's a status code returned from BScreen API. I want to look closer as my first task.
comment:4 by , 2 years ago
After studying how it all works, my understanding is that I'm using UEFI and Haiku basically is using fixed screen mode set by bootloader and there are no services in UEFI that would allow to change it after OS boots, so a dedicated graphics driver would be required to change mode.
I confirmed that B_BAD_VALUE is returned in my case here: https://git.haiku-os.org/haiku/tree/src/add-ons/accelerants/vesa/mode.cpp#n201
- Change return code here to B_UNSUPPORTED, so that error message shown to user makes more sense.
- Investigate why
screenmode -lshows 2 supported modes - I would expect only 1 if I can't change it.
- Modify Screen preferences app to show just 1 refresh rate - currently it shows multiple refresh rates available to choose.
comment:5 by , 2 years ago
Great work guys, the option to set HZ has been removed when using the vesa driver! No more confusion :)
Edit: Although, it is still present when using "Framebuffer", instead of "Vesa", under "Screen", it now reports as "Operation not supported". Good work!
comment:6 by , 16 months ago
|Milestone:||Unscheduled → R1/beta4|
|Status:||new → closed|
Seems to be fixed then.
Please attach a syslog.