[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: XFree86 -configure failure (phase1v19) (4.0.1c)



On Wed, Sep 06, 2000 at 10:10:47AM -0400, Chris Pimlott wrote:
> 	XFree86 -configure fails with the message
> 
> Fatal server error:
> Caught signal 11.  Server aborting
> 
> 	The last module loaded before this is cirrus_alpine (complete
> output is attached).
> 
> 	I was previously running a set of 4.0 binaries and I kept the
> same XF86Config, which I have been using during 4.0.1 testing.  This
> previously XF86Config works fine in v16, v18 and v19 (skipped v17).  This
> is the first time I've actually tried doing a XFree86 -configure in 4.0.1c
> (although it worked fine in 4.0 way back when).
> 
> 	I have tried it under both 2.2.14 and 2.4.0-test6.  Under
> 2.4.0-test6 I also tried it with and without the agpgart kernel module
> installed.  Got the same result in all situations.
> 
> 	My primary video card is a Diamond Stealth II G460 (Intel i740
> chipset) on AGP.  I also have a Canopus Pure3D (3dfx Voodoo 1
> chipset) I'm running Debian Woody.  More details are available on request.


Hmm.

The same thing happened to me - I had been blaming the ATI All In
Wonder 128 in my machine, but it just occurred to me that the Voodoo 2
might actually be at fault.  I'm going to sit down with a remote
debugger and try to isolate this tonight if I have time.

> When reporting a problem related to a server crash, please send
> the full server output, not just the last messages.
> This can be found in the log file "/var/log/XFree86.0.log".
> Please reports problems to branden@debian.org.
> 

Branden, might want to change this to debian-x@lists ?

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/



Reply to: