Bug 102119 - Fuzzy X Graphics with Neomagic Chipset (RH9)
Summary: Fuzzy X Graphics with Neomagic Chipset (RH9)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 9
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-11 15:39 UTC by Christos P. Sotiriou
Modified: 2007-04-18 16:56 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-09-24 08:58:21 UTC
Embargoed:

Attachments (Terms of Use)

Description Christos P. Sotiriou 2003-08-11 15:39:26 UTC 
Description of problem:
neomagic Chipset driver (/usr/X11R6/lib/modules/drivers/neomagic_drv.o)
produces fuzzy X display and does not support the 1024x768 video mode.

(tested on an IBM Thinkpad 600E)

Version-Release number of selected component (if applicable):
RedHat 9

How reproducible:
The problem appears right from the installation CD.

Steps to Reproduce:
1. Try installing RH9 on Thinkpad 600E
2.
3.
    
Actual results:
Fuzzy/distorted screen on X ONLY! Text mode looks fine.

Expected results:
Clear Graphics

Additional info:

Solution : use VESA driver instead, vesa_drv.o
Comment 1 Mike A. Harris 2003-08-23 03:32:39 UTC 
Please report this problem to XFree86.org bugzilla, so that the neomagic
upstream maintainer is aware of the problem and can investigate the matter.
Attach your X server log file and config file to the bug report also, so
the maintainer has a bit more detail to start with.

I've no neomagic hardware available to me unfortunately, and no knowledge
of the neomagic hardware or specifications.  However, if you provide a URL
to your upstream bug report, I'll track the bug upstream and try to backport
any fixes if possible.

Thanks.
Comment 2 Mike A. Harris 2003-09-24 08:58:21 UTC 
No upstream bug URL provided, can't track upstream investigation/resolution,
setting resolution to "WONTFIX".
Note You need to log in before you can comment on or make changes to this bug.