Opened 15 years ago
Closed 6 years ago
#5308 closed bug (fixed)
Error at 1680x1050 resolution on Intel GMA 950
Reported by: | xeon3d | Owned by: | kallisti5 |
---|---|---|---|
Priority: | high | Milestone: | R1/beta2 |
Component: | Drivers/Graphics/intel_extreme | Version: | R1/Development |
Keywords: | resolution strech gma950 | Cc: | |
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
Hi.
I have a GMA950 equipped mobo and a LG L204WS Widescreen 20" monitor.
When setting the 1680x1050 resolution (My LCD's native res), the image gets stretched.
According to Pulkomandy (on IRC) this is due to the pixel clock not being as high as it's requested by the monitor. See the attached syslog.
Attachments (1)
Change History (7)
by , 15 years ago
comment:1 by , 13 years ago
Can you please take a photo so that I can have a better understanding of what's going on? I think it's unlikely that the 5 MHz difference cause such problem (or else your monitor is really picky). I would guess it's more likely that we choose wrong multipliers causing the hardware to deliver a different signal.
Also, does your monitor has a menu that shows the input resolution? If so, it would be neat to include that one with your photo. Thanks, and sorry for the delay!
comment:2 by , 13 years ago
So we can continue troubleshooting this issue, please recheck this card with the latest nightlies. Several fixes have gone into the Intel extreme drivers.
If problems still exist, take a picture and grab some syslogs.
comment:3 by , 9 years ago
Could this have been related to https://dev.haiku-os.org/ticket/10271 ? The monitor mentioned is an analogue one so would have shown weird stretching if the PLL wasn't locked - even though the dot clock *says* it's nearly right, the actual generated dot clock would have been way off.
comment:4 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:5 by , 6 years ago
Milestone: | R1 → R1/beta2 |
---|
comment:6 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Probably fixed as #10271, but if it wasn't, there was no reply to the requests for syslogs/pictures from 7 years ago so not much we can do here.
Syslog of the affected machine.