Bug 5280 - SIS 6326 and XFree-3.3.5 cant display fonts( get black boxes)
SIS 6326 and XFree-3.3.5 cant display fonts( get black boxes)
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-09-21 14:04 EDT by hawaii5o
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-09-21 14:12:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description hawaii5o 1999-09-21 14:04:28 EDT
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 3.3.3.1 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 Xfree.org 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 3.3.3.1   to    Xfree 3.3.5
XFree SVGA 3.3.3.1   to    XFree SVGA 3.3.5
XFree 75dpi fonts 3.3.3.1   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-3.3.3.1  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
peoblems.
Thanks
Umesh
Comment 1 Preston Brown 1999-09-21 14:12:59 EDT
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.