Some further details on my testing: I have now compiled the current CVS driver for 4.1 (required just changing one line in sis_driver.c to get rid of xf86ReadDomainMemory() (if i recall correctly) and replacing it with (old) xf86ReadBIOS(). I don't know whether or not this is proper - but the driver does not complain about any unresolved symbols and comes up fine. I still see the following issues:
1) Disabling the VESA framebuffer for console mode did not change anything. The driver still makes the computer freeze every second or third time after switching to VTs and back (actually, the problem is switching back to X). I see green vertical lines of about 30 (?) pixels in height on top of the - otherwise correctly displayed - screen; mouse and keyboard dead, machine otherwise alive. (It seems what I see there is the text screen displayed in gfx mode.) I know when lockup it going to happen because the X screen shows up slightly quicker after pressing ALT-F7 than when it works. 2) APM: This works - sometimes. Resuming locks up the box about every second or third time. This seems to lock the machine hard, ie no network available any more. 3) I included Stuart Young's VesaFBHack patch and this makes the driver run correctly. I switched to VTs and suspended/resumed for about twenty times each now, flawlessly. I have not taken a closer look at the driver's current code yet, but I somewhat doubt that it's just are hardware problem. Even if the display doesn't get initialized correctly - and this is exactly what Stuart's patch skips - , this shouldn't cause a lock-up, am I right? Well, I'll keep testing. Thomas PS: Rene, the driver I mailed to you is the one I am talking about here, ie for 4.1 _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
