Bug 28206 - Xfree86 hangs with neomagic
Summary: Xfree86 hangs with neomagic
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-02-18 05:03 UTC by sethbc1980
Modified: 2007-04-18 16:31 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2001-02-18 05:03:48 UTC

Attachments (Terms of Use)

Description sethbc1980 2001-02-18 05:03:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

I have a gateway 2500 laptop, i have edited all of the config scripts and 
they are all correct.  I used Xconfigurator to set it up, and checked 
against old XF86Config's that i have.  when i do a 'startx' command, it 
simply hangs at a blank black screen.  to solve i have changed back to 
XF86_SVGA, (3.3.6)  now, i have used XFree86 4.0.1 before, and 4.0 worked 
fine as well, 4.0.2 just doesn't work.

Reproducible: Always
Steps to Reproduce:
1.Xconfigurator for a laptop with a neomagic
2.type 'startx'

Actual Results:  XFree86 locks up

Expected Results:  XFree86 probably should start up right

(the reason i label it a high priority is that after install the computer 
simply hangs when it tries to load X, this would be a problem if i didn't 
have old config files laying around and have XF86_SVGA installed)

Comment 1 Mike A. Harris 2001-02-18 05:37:03 UTC
I've changed the default X configuration to use 3.3.6 by default instead
of XFree 4 since a number of people are reporting this.  Preston, changes
are checked into CVS for "Cards" file.  Next release of X & Xconfigurator
should default to 3.3.6.

Neomagic doesn't make graphics hardware anymore and they don't release their
specs either.  Thus, support for this chip is likely to stay broken unless
someone can talk Neomagic into releasing specs, or someone who has one of
these chipsets can hack code into 4 from the 3.3.x source.

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