#15036: Prevent auto defaulting to screen resolutions higher than monitor
display
capability.
--------------------------------+----------------------------
Reporter: cocobean | Owner: nobody
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: Drivers/Graphics | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking: 15037
Has a Patch: 0 | Platform: All
--------------------------------+----------------------------
Comment (by pulkomandy):
We read the EDID data of the display and use the resolutions that are
advertised there. We try to use the native resolution because that looks
better.
If your display is telling us it supports a resolution but it in fact
doesn't, we can't do anything about it. Blame your display manufacturer.
If on the other hand it supports that resolution, but we end up using the
wrong timings, that's a problem in our video drivers and we could fix it.
It is unclear from your message if the problem is during boot (when the
VESA driver is used) or later (when app_server is started and the "real"
driver is loaded). You also did not include any info on your hardware:
video card, and EDID data (a syslog would include both), as well as the
specs for the display if possible (so we know which resolution it is
supposed to use).
We already use VESA compliant GTF modelines.
As it is, this bugreport is unusable because you do not give us enough
information to know what your problem really is.
--
Ticket URL: <https://dev.haiku-os.org/ticket/15036#comment:5>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
