From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0) distributed savage_drv.o driver module hangs (do not pass go, do not write any output anywhere, just die) machine on K7VMA motherboard w/ VIA S3 ProSavage KM133 video chipset Reproducible: Always Steps to Reproduce: 1. Install (on a machine w/K7VMA MB) through to X Configuration 2. Select any of the S3 drivers, & continue to mode selection 3. Test any video mode Actual Results: Screen goes blank -- no response from machine. I also tried finishing the install & booting to text mode, then running X while redirecting the output to a file, but the crash was so quick that the output file was not present after the subsequent fsck. Expected Results: valid X test. I installed the linux binary of savage_drv.o from the generic XFree86 4.0.3 update distro & was able to get X working with that. Has been up for the past 24+ hours.
I believe that's what was fixed in Mike's 4.0.3-9 at ftp://people.redhat.com/mharris/xfree86/
I tried the most recent savage driver (1.1.15) from <http://www.probo.com/timr/savage40.html> and the server from Mike's 4.0.3-9. Both hung the machine in the same way (requiring a hard reboot.)
Our 4.0.3-9 driver *is* the 1.1.15 driver from the URL you supplied. It is the most stable Savage driver all around for now until the maintainer finds solutions for the open bugs with it I'm afraid. I've looked around and can't find anything. I do not have any hardware with which to test with myself unfortunately.
Are you using Xconfigurator --preferxf4 to configure? Please attach your X logs and configs below.
Created attachment 16491 [details] XF86Config-4
Created attachment 16492 [details] XFree86.0.log
Created attachment 16493 [details] XFree86.0.log from working savage_drv.o 1.1.13 (from xfree86.org's upgrade release of 4.0.3)
I notice that the working version (1.1.13) INCORRECTLY identifies the video chipset as a PM133. I am very confident that the K7VMA in fact has the KM133.
I am currently using 4.1.0 with K7VMA motherboard (S3 ProSavage video) and facing the same problem of hung server when testing with Xconfigurator.
Please attach the output of "lspci -v" and also "lspci -vn" so I can analize the PCI info to corelate with what XFree86 is doing.
Please supply the requested information.
XFree86 4.1.0-5 contains the latest Savage driver, which includes fixes for this chipset. Others have reported that it solves problems they were having. Please try this, and give feedback of wether it fixes the problem for you or not. If not, then please supply the information I have requested above.
Oops, I left out the URL: ftp://people.redhat.com/mharris/testing/bleeding-edge
Bug has remained in MODIFIED state with no problem report for over 6 months. Closing bug as fixed in latest Savage driver in CURRENTRELEASE of Red Hat Linux 7.3.