Bug 125866

I need an X server log from while you're using the s3virge driver
in order to get the specific PCI ID and implement this change
properly.  Please attach using the link below.

Thanks in advance.

ping

We need an X server log, or "lspci -vn" to get the PCI ID, or we
can't make this change.

Thanks in advance.

Created attachment 101796 [details]
lspci -vn

output from lspci -vn

Created attachment 101797 [details]
XFree86 log file

This is /var/log/XFree86.0.log from a FC1 system.

Created attachment 103118 [details]
lspci -vn

Created attachment 103119 [details]
Xorg.0.log

The driver for this video hardware was changed from the "s3virge"
driver to the "vesa" driver in 2002, due to a bug report from IBM
stating the s3virge driver gave corrupted video.

Please review bug #59956 to confirm the problem experienced by
that person does not occur for you at all.  I'll update that
bug to request the reporter of that bug test against rawhide also.

Thanks in advance.

New entry added to "pcitable" which specifies this card exactly,
including subvendor/subdevice fields, so this specific chip can
have the driver assigned individually.  I added a new entry
to the "Cards" file named "S3 Trio64 3D" which this pcitable
entry now maps to (the previous mapping was to the "S3 Trio3D"
entry).

I also changed both the old entry and the new entry to the "s3virge"
driver, so all hardware reporting device ID 0x8903 and 0x8904 will
now map to the same "s3virge" driver.  Under the new mapping scheme,
should anyone out there encounter problems now under the current
"s3virge" driver, we can reassign individual devices or subdevices
to a particular driver, rather than an all or nothing assignment.

Since there aren't a lot of people usually testing the S3 drivers
nowadays, I urge all S3 Trio users to test the new assignements
in rawhide as soon as possible, because it is very likely the
Fedora Core 3 release will ship with the new assignments as-is,
and if there are problems with this, we'll need to know far
in advance of the FC3 final release in order to have time to try
and fix the driver assignments.

Also, please report any actual "s3virge" driver bugs directly
to X.Org bugzilla, in order that the driver maintainers are
aware of any problems and may fix them.  We do not directly
maintain the driver, and our support for this hardware will mostly
be limited to driver reassignments and similar workarounds.

Thanks in advance for testing!

The new package is hwdata-0.124-1

The "bug" is still there.

I installed FC3-test2 and still got "vesa" instead of "s3virge".
(FC3-test2 has hwdata-0.131-1).

Here are the current hardware database entries for this hardware
in hwdata CVS head:

[pcitable]
0x5333  0x8904  "Card:S3 Trio3D"
0x5333  0x8904  0x1014  0x00db  "Card:S3 Trio64 3D"
0x5333  0x8904  0x1014  0x305c  "Card:S3 Trio64 3D"

I just added the entry for the specific subvendor/subdevice you guys
have, however it would have defaulted to the master entry previously,
and both of them are pointing to the same driver currently, so my recent
addition shouldn't change anything.


[Cards]
# Changed default driver for S3 Trio3D from "s3virge" to "vesa" driver as per
# bug #59956 in bugzilla.  The bug reporter of the above report should be
# consulted before changing this back to a native driver in the future.  This
# is changed for 4.2.0 post RHL 7.3.  --  July 26, 2002 - Mike A. Harris
# Update:  Bug #125866 has requested the driver for this hardware be changed
# to use the "s3virge" driver.  I've investigated the original bug #59956 and
# the PCI IDs are identical for all 3 users in those 2 bug reports, so I
# assume the "s3virge" driver works now in X.Org X11 6.7.99.903 et al.  I'm
# changing the default back from "vesa" to "s3virge" for the "S3 Trio3D" entry
# here, but I've added a new one named "S3 Trio64 3D" as well, which also
# defaults to the "s3virge" driver.  I've left the pcitable->Cards mapping
# alone for the 0x8904 and 0x8903 entries so that they can be changed in the
# future if a problem is discovered, however the new entry added to pcitable
# is for the specific card referenced in these above bug reports, specified
# including the subvendor/subdevice fields, so that we can assign drivers for
# these card ranges in a more finely grained manner.
NAME S3 Trio3D
CHIPSET S3 Trio3D
NOCLOCKPROBE
DRIVER s3virge
# See above comment for "S3 Trio3D" as it applies to this one as well.
# This "S3 Trio64 3D" entry is specifically for:
#       01:01.0 Class 0300: 5333:8904 (rev 01) Subsystem: 1014:00db
NAME S3 Trio64 3D
CHIPSET S3 Trio3D
NOCLOCKPROBE
DRIVER s3virge


It's possible the previous updates might have gotten the chip ID wrong,
but I've now manually confirmed this is correct in hwdata in rawhide,
so I'm closing this as "RAWHIDE" now.

If there are further problems, please reopen.

Thanks guys.

it works in FC3 (final).

Thanks.