With my G35 Asus P5E-VM running Ubuntu 8.04 pre-rel x86-64 with Intel driver 2.2.1, I am seeing two symptoms, using the HDMI port w/ HDMI->DVI adapter:
- dual-link DVI cable to projector
-> unable to lock, so blank screen
- single-link DVI cable to Belinea 1600x1200 LCD
-> consistent off-by-2 Y size
It seems entirely conceivable that my projector doesn't accept resolutions that aren't expected and untested via the DVI-D connection; I can readily see this happening on HDMI/DVI TVs which support only particular resolutions and possibly on particular digital monitors.
Observations which make me tie the bug to the Intel driver:
- during BIOS init and before Linux takes over, we see:
- 640x480
- during Ubuntu's booting and VESA framebuffer use:
- 640x480
- in X, testing various resolutions, the monitor reports:
- 1600x1198
- 1280x1022
- 1280x958
- 1152x862
- 1024x766
- 800x598
- 640x478
All output in /var/log/Xorg.0.log, xrandr etc, points the correct resolution being used, so it seems like a chip configuration/register setup issue.
Let me know of useful information I can get and contribute!
With my G35 Asus P5E-VM running Ubuntu 8.04 pre-rel x86-64 with Intel driver 2.2.1, I am seeing two symptoms, using the HDMI port w/ HDMI->DVI adapter:
- dual-link DVI cable to projector
-> unable to lock, so blank screen
- single-link DVI cable to Belinea 1600x1200 LCD
-> consistent off-by-2 Y size
It seems entirely conceivable that my projector doesn't accept resolutions that aren't expected and untested via the DVI-D connection; I can readily see this happening on HDMI/DVI TVs which support only particular resolutions and possibly on particular digital monitors.
Observations which make me tie the bug to the Intel driver:
- during BIOS init and before Linux takes over, we see:
- 640x480
- during Ubuntu's booting and VESA framebuffer use:
- 640x480
- in X, testing various resolutions, the monitor reports:
- 1600x1198
- 1280x1022
- 1280x958
- 1152x862
- 1024x766
- 800x598
- 640x478
All output in /var/log/ Xorg.0. log, xrandr etc, points the correct resolution being used, so it seems like a chip configuration/ register setup issue.
Let me know of useful information I can get and contribute!