Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 5280 - SIS 6326 and XFree-3.3.5 cant display fonts( get black boxes)
Summary: SIS 6326 and XFree-3.3.5 cant display fonts( get black boxes)
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-09-21 18:04 UTC by hawaii5o
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-09-21 18:12:37 UTC

Attachments (Terms of Use)

Description hawaii5o 1999-09-21 18:04:28 UTC
I have a builtin sis 6236 graphics chip, NEC C500 monitor
and trying to run RH 6.0 on it. The RH 6.0 came with the
Xfree in it and I could not get the graphics chip to
use the full screen, the screen is either horizontally or
vertically squeezed. XF86Setup and xvidtune were not able to
help either. I read in the site that the 3.3.5 has
improved support for the sis and tried to install the update
that redhat had posted. I updated the following packages

XFree   to    Xfree 3.3.5
XFree SVGA   to    XFree SVGA 3.3.5
XFree 75dpi fonts   to   XFree 75drpi fonts 3.3.5

Thre were no error messages and X started nomally but every
where letters appeard there were black boxes. The cursor
sometimes appeard as a large white box.
I had to reinstall the old XFree-SVGA-  to get the
fonts back to nomal but still stuck with a small screen.

I know of another person who is running the Mandeake 6.2(
Kerne 2.9 and XFree 3.3.5) on the same setup and has no

Comment 1 Preston Brown 1999-09-21 18:12:59 UTC
Please get the LATEST errata packages.  We released a fix which
addressed SiS 6326 problems.

Note You need to log in before you can comment on or make changes to this bug.