I'm running a
. business line Fujitsu Siemens S7010 notebook
. with the GM855(=i82855) graphics chipset
. connected to Samsung SyncMaster 204B 1600x1200 display via DVI
. OS WindowsXP
That worked fine with the most recent GMA drivers v14.19.50 dated 2/8/2006:
Then I bought an HP w2408 Display capable of 1920x1200. I recognized that regardless what I do, I could not get beyond the 1600x1200 resolution for this new display. After googling I figured the intel IEGD drivers should provide a solution:
Yes, indeed I got 1920x1200 running with both IEGD 5.0 and IEGD 7.0 (7/4/2007). It uses the DVO-B Port of the chipset to use the DVI. Still this windows driver has two very annoying shortfalls (besides some others that don't bother as much), which prevent me from considering the IEGD driver a serious way to go:
1. I switch between mobile and docking station usage. The Fn + CRT/LCD/CLONE keyboard switches are not supported in the IEGD driver and you are stuck with a black display if you hibernate while having an external display connected and wake up with nothing else than the internal LVDS display. You would expect a reboot and new display detection would fix the problem since you installed the driver with
HKR, ALL1General , DisplayDetect, %REG_DWORD%, 1
HKR, ALL1General , PortOrder, %REG_SZ%, "42500"
and for each port something like:
HKR, ALL1Port2General , Edid, %REG_DWORD%, 1
HKR, ALL1Port2General , EdidAvail, %REG_DWORD%, 3
HKR, ALL1Port2General , EdidNotAvail, %REG_DWORD%, 1
But that's not sufficient. YOU ARE STUCK! To walk around this problem I use IEGDGUI.exe switching to LVDS single display prior hibernating/rebooting if there is the chance that the next usage will be mobile without an external display. But I know ... some day I will forget. This problem seems to be recognized already:
2. Performance in 2D: This driver sometimes sucks 100% of CPU time and slows down screen updates dramatically. Switching tabs in Firefox 18.104.22.168 may last once in a while for 1 - 15 seconds. That's simply not acceptable. I found at least one other guy with a different chipset (Intel GMA945) who suffers from the same problem with that driver:
There are other applications as well that seriously suffer like TexnicCenter, Opera, ...
I assume some of the currentl
y non-visible but allocated VRam gets invalidated by the driver too early and upon reactivation of the VRam by some application, the application get's the notification that the Vram is not available and it has to reallocate and render again. This is a Windows specific feature - other applications e.g. Java2D library have specific strategies two walk round that problem by caching ... (I stop here, because I get OffTopic).
Okay, both problems really, really prevent serious usage! If there is no magic registry key that I'm missing here, then intel really has to do something, since this chipset is not at the end of it's lifecycle!
These are the solutions I can think of beginning with the one with the smallest implementation effort:
Get you EDID reading correct in the Windows GMA driver (not the IEGD)! Both of my monitors supply correct EDID information, which I can read by means of MonInfo
Only the relevant part here:
Samsung SyncMaster 204B:
Display type and signal..... Digital
Timing recommendation #1.... 1600x1200 at 60Hz
Modeline................ "1600x1200" 162,000 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
Display type and signal..... Digital
Timing recommendation #1.... 1920x1200 at 60Hz
Modeline................ "1920x1200" 154,000 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync
I can't get past 1600x1200 with this driver. It's not a VBIOS fault - MonInfo reads the EDID correct.
Enhance the Windows GMA driver (not IEGD) with a facility to provide custom resolutions - at least by a registry key. For later Chipsets (e.g. 915GM, 945GM, ...) this has been implemented in v14.25.50 such that custom resolutions can be used:
And actually even work with PowerStrip:
Fix the above two problems in IEGD >7.0. I do not expect this to be a solution, since embedded requirements are completely different (e.g. no requirement for CRT/LVDS/CLONE keyboard switch).