Alex asks: > 1. If it's possible that the Linux SiS driver has > somehow "programmed" the monitor to respond with > a changed ID string and/or different timings, etc. > which could confuse the Windows driver startup-query. > > 2. If the above MAY have happened (under ANY circumstances, Linux > or not), whether there exists a way (utility, etc.) to "reset" > the monitor to its original values. Thomas Winischhofer replies: The SiS driver does not "program the monitor". It only reads its DDC info. There is no way the monitor reports different data after this (at least not that I know of). The only issue could be that the Windows driver reads DDC1 data which is not available after booting Linux since the DDC specification says that as soon as a device is being switched to DDC2 (which the SiS Linux/XF86 driver does), it has to remain in this state until it is switched off. But I can hardly imagine that the SiS Windows driver depends on DDC1. (But then again, this is SiS... you never know... Anyway, if switching off and on the monitor doesn't help, I suggest you switch off the monitor detection in Windows and use a fixed rate there). ------------------------------------------------------- Thomas, Thank you very much for your prompt comments and help. For the record ? The monitor is always fully shut off, whether between a switch from Linux to Windows or just before a boot up on Windows. This eliminates the possibility that the monitor (if OK) might not present the proper DDC1 info to Windows. As I mentioned, the only time the problem doesn?t show up is when I leave the monitor off until after Windows has been fully up (thus ?simulating? the ?switching off of monitor detection in Windows? the hard way.) This raises a few new questions: 1. Is it possible that the Linux driver, once it gets (and maybe stores) the correct info from the monitor on first install, it no longer cares what happens afterwards, while Windows keeps inquiring the now wrong DDC1 data on any boot up? In other words, is it possible that the monitor is now defective (DDC1-wise) with Linux not noticing anything? 2. I do not know a way to ?switch off the monitor detection in Windows and use a fixed rate there?. I?d appreciate a pointer from you here (even if it might include messing up with system registry). 3. When you say ?But then again, this is SiS... you never know...?, I detect a certain unhappiness with SiS651 on your part. Do you think my spending some money on a video card (with a different chip, of course) would fix this annoying problem for sure? Again, many thanks, -- Alex _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
