From owner-freebsd-questions Tue Dec 24 12: 1: 0 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2406437B401 for ; Tue, 24 Dec 2002 12:00:58 -0800 (PST) Received: from elm.phpwebhosting.com (elm.phpwebhosting.com [66.33.90.118]) by mx1.FreeBSD.org (Postfix) with SMTP id 151EF43EB2 for ; Tue, 24 Dec 2002 12:00:57 -0800 (PST) (envelope-from synfin@unixroute.com) Received: (qmail 27685 invoked by uid 508); 24 Dec 2002 20:00:55 -0000 Received: from unknown (HELO u84jfw35cqecx9) (12.250.115.47) by elm.phpwebhosting.com with SMTP; 24 Dec 2002 20:00:55 -0000 Message-ID: <003601c2ab98$50623fb0$6400a8c0@u84jfw35cqecx9> From: "A.Z." To: , "FreeBSD Questions" References: <002d01c2ab88$35df8c20$6400a8c0@u84jfw35cqecx9> <1040753332.58381.195.camel@localhost> <005201c2ab8a$230609b0$6400a8c0@u84jfw35cqecx9> <1040754392.58381.198.camel@localhost> <006101c2ab8d$98063fc0$6400a8c0@u84jfw35cqecx9> <1040755851.58381.201.camel@localhost> <000801c2ab90$738806d0$6400a8c0@u84jfw35cqecx9> <20021224195320.GA52474@sub21-156.member.dsl-only.net> Subject: Re: Prroblem with X Date: Tue, 24 Dec 2002 14:03:38 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Nathan Kinkade" To: "FreeBSD Questions" Sent: Tuesday, December 24, 2002 11:53 AM Subject: Re: Prroblem with X > On Tue, Dec 24, 2002 at 01:07:21PM -0800, A.Z. wrote: > > > Yes, it worked before with other versions just fine. > > > > Here is cut from XFree86 log: > > > > (==) ATI(0): Backing store disabled > > > > (==) ATI(0): Silken mouse enabled > > > > (II) Initializing built-in extension MIT-SHM > > > > (II) Initializing built-in extension XInputExtension > > > > (II) Initializing built-in extension XTEST > > > > (II) Initializing built-in extension XKEYBOARD > > > > (II) Initializing built-in extension LBX > > > > (II) Initializing built-in extension XC-APPGROUP > > > > (II) Initializing built-in extension SECURITY > > > > (II) Initializing built-in extension XINERAMA > > > > (II) Initializing built-in extension XFree86-Bigfont > > > > (II) Initializing built-in extension RENDER > > > > (**) Option "Protocol" "Auto" > > > > (**) Mouse1: Protocol: "Auto" > > > > (**) Option "CorePointer" > > > > (**) Mouse1: Core Pointer > > > > (**) Option "Device" "/dev/sysmouse" > > > > (==) Mouse1: Buttons: 3 > > > > (II) Keyboard "Keyboard1" handled by legacy driver > > > > (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE) > > > > (II) Mouse1: SetupAuto: hw.iftype is 4, hw.model is 0 > > > > (II) Mouse1: SetupAuto: protocol is SysMouse > > > > (**) Option "BaudRate" "1200" > > > > Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing > > from list! > > > I don't think that the fact that X couln't init Speedo fonts would cause > X to fail startup completely. Are there no other informative messages > at the end of /var/log/XFree86.0.log? Why don't you try paring down > your .xinitrc file to only contain something simple like "exec twm". If > that works then start backtracking. Or possibly try setting your X > config for the lowest possible resources, like using a default color > depth of 8 and a Mode of 800x600, just to help eliminate the possiblity that > it might be resource related. > > Nathan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > I have pasted the end of /var/log/XFree86.0.log I have put exec twm Now error message is /kernel: pid 692 (twm), uid 0: exited on signal 11 (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message