Bug 25183 - XF86 4.0.2 crash with S3 Inc. ViRGE/DX
XF86 4.0.2 crash with S3 Inc. ViRGE/DX
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
7.1
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-01-29 08:58 EST by Tim Waugh
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-06 15:55:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
XFree86.0.log (29.66 KB, text/plain)
2001-01-29 08:58 EST, Tim Waugh
no flags Details
My config file. (1.40 KB, text/plain)
2001-01-29 09:01 EST, Tim Waugh
no flags Details

  None (edit)
Description Tim Waugh 2001-01-29 08:58:15 EST
XF86 3.3.6 works fine, but XF86 4.0.2 crashes when logging in via kdm.
Comment 1 Tim Waugh 2001-01-29 08:58:39 EST
Created attachment 8419 [details]
XFree86.0.log
Comment 2 Tim Waugh 2001-01-29 08:59:51 EST
00:0e.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01) (prog-if 
00 [VGA])
        Subsystem: S3 Inc. ViRGE/DX
        Flags: bus master, medium devsel, latency 40, IRQ 11
        Memory at f8000000 (32-bit, non-prefetchable) [size=64M]
        Expansion ROM at <unassigned> [disabled] [size=64K]

or in numbers:

00:0e.0 Class 0300: 5333:8a01 (rev 01)
        Subsystem: 5333:8a01
        Flags: bus master, medium devsel, latency 40, IRQ 11
        Memory at f8000000 (32-bit, non-prefetchable) [size=64M]
        Expansion ROM at <unassigned> [disabled] [size=64K]

Comment 3 Tim Waugh 2001-01-29 09:01:09 EST
Created attachment 8420 [details]
My config file.
Comment 4 Tim Waugh 2001-01-29 09:08:51 EST
This also happens without my weirdo modeline in XF86Config-4.
Comment 5 Tim Waugh 2001-02-09 07:25:06 EST
This looks like it's fixed now (4.0.2-7).

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