On Mon, Feb 13, 2006 at 02:55:17PM +0100, Richard Zidlicky wrote: > On Sun, Feb 05, 2006 at 03:32:59PM -0600, Lance Tagliapietra wrote: > > Hello, > > > > I've done a bit more investigating since I made this post, and observe > > in the log files referenced below that the X server is aborting with a > > Signal 7. From my research, this could indicate a hardware issue, but > > I don't think so here. > > > > The log file shows the following: > > > > Fatal server error: > > Caught signal 7. Server aborting > > isn't that the old module loading problem again? Does not > work because of caching on 68060 and perhaps 68040. > > Richard
I appreciate your suggestion. The system referred to above is a 68030 (GVP accelerator with scsi and 16M RAM). I can properly start X from the command prompt, both root and non-root users with the startx command, now. I am thinking that the issue is that the X log in program is not starting properly on the console screen, and hence X aborts. I say this because I get the same signal 7 message in my XFree86.0.log when I exit my X session that I started with the startx command. This is where I plan to look next barring better ideas from the group. --Lance -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
