Red Hat Bugzilla – Bug 51934
XFree86-4.1.0 fails to read S3 Prosavage KM133 video bios
Last modified: 2007-04-18 12:35:59 EDT
Description of Problem:
I am using XFree86-4.1.0 with S3 Prosavage KM133 integrated video.
The driver is the 1.1.18 version from
When I run "X -xf86config XF86Config" I get this error messages in the
/var/log/XFree86.0.log file ->
(EE) SAVAGE(0): Cannot read V_BIOS
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run X
X doesnot start and quits after error messages
Created attachment 28233 [details]
Created attachment 28234 [details]
This is like buying a Ford truck, and then calling GM and telling
them "something is wrong with my truck."
Report the bug to the driver author please, we have not shipped
The reason I am using this savage driver is given in Bug 47768, caused by savage driver
shipped with X-4.1.0 (from redhat/rawhide RPMS). Tim Roberts' current savage driver has solved
that problem. I had the understanding that Tim Roberts' savage driver is referenced by redhat developers, as is evident from ur comments in bug 37467. In fact, it was bug 37467 that gave
me the idea of using Tim's savage driver.
That is ok to use the driver, yes. Red Hat XFree86 does not currently
include that driver, and might not in the future either, especially
if there are known flaws and regressions in that driver.
Sure, i may point out a driver on the web somewhere in a goodwill effort
to help someone solve their problem by providing information, but that
doesn't mean that because I provide a URL or info to someone that
we support bug reports for external source code not contained in Red
Hat Linux. Bugzilla is for tracking bugs in Red Hat Linux and related
products, including rawhide, etc. Not for bug general bug reports.
Sorry if I have mislead you. If I do update the driver to the latest
one 1.1.18, and you continue to have this problem however, by all means,
please come back here and reopen this bugreport so that we can track it.
One thing to note, is that the 1.1.18 driver was released with a bug, and
Tim fixed it, and repackaged the new package as 1.1.18 again for whatever
reason instead of calling it 1.1.19. It is possible that yours is the
older one. Sorry I can't be more help right now.