Date: Thu, 17 Jul 2008 10:42:24 -0700 From: Rem P Roberti <remegius@comcast.net> To: Roland Smith <rsmith@xs4all.nl> Cc: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: X won't play Message-ID: <20080717174224.GA794@remdog.net> In-Reply-To: <20080717172849.GA33118@slackbox.xs4all.nl> References: <20080717164609.GA1010@remdog.net> <20080717172849.GA33118@slackbox.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2008.07.17 19:28:49 +0000, Roland Smith wrote:
> On Thu, Jul 17, 2008 at 09:46:09AM -0700, Rem P Roberti wrote:
> > > > I'm kind of new to this, so would appreciate a hand. I just got through
> > > > configuring a custom kernel. Both makebuild and installbuild take place
> > > > with no problems and the kernel boots just like it's supposed to. But
> > > > when I try to bring up X I get this error message:
> > > >
> > > > _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
> > > > _XSERVTransMakeAllCOTSServerListeners: server already running
> > >
> > > Maybe you forgot something netowrking related. Please show a diff(1) of
> > > you kernel configurations, see below.
> > >
> > > > Fatal server error:
> > > > Cannot establish any listening sockets - Make sure an X server isn't
> > > > already running
> > > >
> > > > I rebooted with the old kernel and everything is back to normal.
> > > > Obviously I removed something from the kernel configuration file that I
> > > > shouldn't have. Can someone give me a heads up on just what that might
> > > > be?
> > >
> > > Please post the output of 'diff -u oldconfig newconfig', where oldconfig
> > > and newconfig are replaced by the paths of the old and new kernel
> > > configuration files.
> > >
>
> Hmm. Nothing suspicious as far as I can see.
>
> Since it says "server already running" in the original error message, was
> there perhaps a stray hidden lockfile or socket in /tmp/?
>
I cleaned up the /tmp directory, but the new kernel still refuses to
allow X to boot. In my original post I failed to include this part of
the error message, which comes at the end:
XIO: fatal IO error 54 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
As I said earlier, when I unload the new kernel and boot the old one I
have no problem bringing up X.
Rem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080717174224.GA794>