Bug 11581

Summary: Neomagic 128XD ( 2160 )
Product: [Retired] Red Hat Linux Reporter: Michael Bohde <m_bohde>
Component: XFree86Assignee: Mike A. Harris <mharris>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 6.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-04-24 16:27:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Bohde 2000-05-22 18:02:29 UTC 
Computer Specs:
EZBOOK 700E Series
K6-2 300Mhz
32MB RAM ( Upgraded to 96MB )
2.01GB Hard Disk
LCD panel capable to 800x600x24bpp common state 800x600x16bpp

Earlier versions of Redhat and other Linux OSes have enabled this setup to
use 800x600x16bpp resolutions while Redhat 6.2 doesn't

Symptoms
* only able to use 1MB video RAM card is 2MB
* not able to use over 8bpp capable of 24bpp
* use at 640x480 or 600x400... can't recall  produces horizontal stripes
across the screen while booting into the graphical login

This problem did not surface until I used Redhat 6.2 Deluxe so I believe
the problem lies there I was also informed XFree86 was updated to 3.3.6

Workarounds that have been suggested to me:
* Downgrade XFree86 to version 3.3.3
Comment 1 Michael Bohde 2000-05-23 13:14:59 UTC 
RedHat Linux 5.2 Worked at 800x600x16bpp stable with this setup
Comment 2 Mike A. Harris 2001-03-10 04:14:31 UTC 
Please try the latest version of XFree86 from:

ftp://people.redhat.com/mharris/xfree86

If it works for you, please update the bug report to let me know, if it doesn't
work, please send me a copy of your Xserver logs and your config file as a
file attachment to the bug report.
Comment 3 Mike A. Harris 2001-05-20 22:27:01 UTC 
Please upgrade to the latest release of Red Hat Linux.
Closing bug due to lack of feedback.  The current release should solve
your problem.