Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 74458 - ATI Rage 128 mobility video card crashes X server
ATI Rage 128 mobility video card crashes X server
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
Depends On:
Blocks: 82779
  Show dependency treegraph
Reported: 2002-09-24 14:27 EDT by Chris L. Gray
Modified: 2005-10-31 17:00 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-24 13:40:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
XFree86 Log (56.62 KB, text/plain)
2002-09-24 14:28 EDT, Chris L. Gray
no flags Details
XF86Config (3.55 KB, application/octet-stream)
2002-12-13 20:32 EST, Chris L. Gray
no flags Details

  None (edit)
Description Chris L. Gray 2002-09-24 14:27:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
ATI Rage 128 mobility video card crashes X server. The video card is on a Compaq
Presario 1800 laptop. This began on first boot after install. I am having to use
the 'vesa' drivers to use X at all.

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

How reproducible:

Steps to Reproduce:
1.Use 'redhat-confic-xfree86 --reconfigure' to add 'r128' back as the default
driver for my card.
2.Use 'startx' from the command line.
3.X attempts to start, screen flickers, server crashes and gives output,  'no
screens were found'

Actual Results:  X attempts to start, screen flickers, server crashes and gives
output,  'no screens were found'.

Expected Results:  X server should have launched.

Additional info:
Comment 1 Chris L. Gray 2002-09-24 14:28:24 EDT
Created attachment 77064 [details]
XFree86 Log
Comment 2 Alexander Larsson 2002-10-02 02:44:54 EDT
The logs look ok to me at least. Can you attach the /etc/X11/XF86Config file too?

mharris: This looks like yours.
Comment 3 Chris L. Gray 2002-12-02 14:20:52 EST
Where do we stand on this? I am new to Bugzilla, what can I do to help things 

Chris Gray
Comment 4 Mike A. Harris 2002-12-02 14:34:54 EST
The current status is: Waiting for the file attachment requested by alexl
Comment 5 Brent Fox 2002-12-13 17:17:55 EST
Chris, are you still seeing the problem?  If so, can you please attach the
/etc/X11/XF86Config file?  Otherwise, we're kind of stuck on this issue.
Comment 6 Chris L. Gray 2002-12-13 20:32:34 EST
Created attachment 88717 [details]
Comment 7 Brent Fox 2002-12-20 04:14:30 EST
mharris: can you look at this now that the config file has been attached?
Comment 8 Brent Fox 2003-01-20 17:54:51 EST
I'm changing the component to XFree86 since it looks like the config file is
valid.  Maybe the driver is at fault.
Comment 9 rodrigo 2003-08-04 20:43:59 EDT
I am new in Linux running RedHat 8.0 and last thing I did is running up2date 
from command line and when I wanted to startx it won't start. Screen flickers 
and will give this error:
XIO: fatal IO error 104 (connextion reset by peer) on X server "0:0" after 0 
requests (0 known processed) with 0 events remaining.
any idea?
Comment 10 Mike A. Harris 2004-09-24 13:40:51 EDT
We believe this issue to be resolved in our currently shipping
OS releases.  Please upgrade to Fedora Core 2 or later, and if this
issue turns out to still be reproduceable, please file a bug report
in the X.Org bugzilla located at http://bugs.freedesktop.org in the
"xorg" component.

Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes
that become available for consideration in future updates.

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