Problems starting X

Problems starting X

Post by Armando L. Caro Jr » Fri, 05 Feb 1999 04:00:00



I have setup Slackware 3.5 (kernel 2.0.34) on a Thinkpad 750Cs by hand.
What I mean by hand is that I moved .tgz files over one by one and
installed them.  I had to do this because I had no CDROM drive.

Everything runs fine except X.  Now I know that there are some tricky
things to get X configured properly on this machine, but I can't even get
the server up.

Typing 'startx' as a user or as root attempts to start X server, but it
crashes before making it.  The output is attached below.  As root, typing
'X' or 'X86_SVGA' seems to startup X, but it doesn't work properly. It
shows the grey background with 2 X mouse pointers!  However, it just sits
there.  If I hit <ctrl> <bkspace> or <ctrl><fn> it just puts up a blank
black screen and I am forced to reboot.

Any ideas?  Please email me your suggestions.

startx output:

_XSERVTransSocketCreateListener: failed to bind listener
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: failed to create listener for local
_X11TransSocketUNIXConnect: Can't connect: errno = 2

XFree86 Version 3.3.2 / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: March 2 1998
        If the server is older than 6-12 months, or if your card is newer
        than the above date, look for a newer version before reporting
        problems.  (see http://www.veryComputer.com/)
Operating System: Linux 2.0.32 i586 [ELF]
Configured drivers:
  SVGA: server for SVGA graphics adaptors (Patchlevel 0):
      NV1, STG2000, RIVA128, ET4000, ET4000W32, ET4000W32i,
      ET4000W32i_rev_b, ET4000W32i_rev_c, ET4000W32p, ET4000W32p_rev_a,
      ET4000W32p_rev_b, ET4000W32p_rev_c, ET4000W32p_rev_d, ET6000, ET6100,
      et3000, pvga1, wd90c00, wd90c10, wd90c30, wd90c24, wd90c31, wd90c33,
      gvga, ati, sis86c201, sis86c202, sis86c205, tvga8200lx, tvga8800cs,
      tvga8900b, tvga8900c, tvga8900cl, tvga8900d, tvga9000, tvga9000i,
      tvga9100b, tvga9200cxr, tgui9400cxi, tgui9420, tgui9420dgi,
      tgui9430dgi, tgui9440agi, *9320, tgui9660, tgui9680, tgui9682,
      tgui9685, *9382, *9385, *9388, *9397, *9520,
      3dimage975, 3dimage985, clgd5420, clgd5422, clgd5424, clgd5426,
      clgd5428, clgd5429, clgd5430, clgd5434, clgd5436, clgd5446, clgd5480,
      clgd5462, clgd5464, clgd5465, clgd6205, clgd6215, clgd6225, clgd6235,
      clgd7541, clgd7542, clgd7543, clgd7548, clgd7555, ncr77c22, ncr77c22e,
      cpq_avga, mga2064w, mga1064sg, mga2164w, mga2164w AGP, oti067, oti077,
      oti087, oti037c, al2101, ali2228, ali2301, ali2302, ali2308, ali2401,
      cl6410, cl6412, cl6420, cl6440, video7, ark1000vl, ark1000pv,
      ark2000pv, ark2000mt, mx, realtek, AP6422, AT24, AT3D, s3_virge,
      s3_svga, ct65520, ct65525, ct65530, ct65535, ct65540, ct65545,
      ct65546, ct65548, ct65550, ct65554, ct65555, ct68554, ct64200,
      ct64300, generic

Fatal server error:
xf86OpenConsole: Server must be running with root permissions
You should be using Xwrapper to start the server or xdm.
We strongly advise against making the server SUID root!

When reporting a problem related to a server crash, please send
the full server output, not just the last messages

_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
giving up.
xinit:  No such file or directory (errno 2):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.

-----------------------------------------------------------------------

University of Delaware                   http://www.veryComputer.com/~acaro      
-----------------------------------------------------------------------

 
 
 

Problems starting X

Post by Vladymyr Iljyc Leni » Sat, 06 Feb 1999 04:00:00


i think, you have improperly konfigured your xserver or xserver have
problem with some option of yours graphic card
you may just edit /etc/XF86Config and remove or comment (hash sign at
begin of row) some option in section for your driver
then you may start x windows again

two mouse pointers indicates you have incorectly set refresh rate or
some problems with graphics card but i don't know exactly where is the
problem, maybe you may say type of your graphics card
--

                                                        = lenin =
a ze ja sem ve~c~nej co?

 
 
 

Problems starting X

Post by Michae » Sat, 06 Feb 1999 04:00:00


Armando,

Instead of transporting the .tgz files by hand, why not do a good old
fashioned floppy install for the X series of diskettes?  Make the diskettes
(from download, or whatever), type setup at your prompt, and specify the
source as your floppy drive, select the X set of diskettes and let'er rip.

Unless I've misunderstood your problem, that is.

Michael


>I have setup Slackware 3.5 (kernel 2.0.34) on a Thinkpad 750Cs by hand.
>What I mean by hand is that I moved .tgz files over one by one and
>installed them.  I had to do this because I had no CDROM drive.

>Everything runs fine except X.  Now I know that there are some tricky
>things to get X configured properly on this machine, but I can't even get
>the server up.

>Typing 'startx' as a user or as root attempts to start X server, but it
>crashes before making it.  The output is attached below.  As root, typing
>'X' or 'X86_SVGA' seems to startup X, but it doesn't work properly. It
>shows the grey background with 2 X mouse pointers!  However, it just sits
>there.  If I hit <ctrl> <bkspace> or <ctrl><fn> it just puts up a blank
>black screen and I am forced to reboot.

>Any ideas?  Please email me your suggestions.

>startx output:

>_XSERVTransSocketCreateListener: failed to bind listener
>_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
>_XSERVTransMakeAllCOTSServerListeners: failed to create listener for local
>_X11TransSocketUNIXConnect: Can't connect: errno = 2

>XFree86 Version 3.3.2 / X Window System
>(protocol Version 11, revision 0, vendor release 6300)
>Release Date: March 2 1998
> If the server is older than 6-12 months, or if your card is newer
> than the above date, look for a newer version before reporting
> problems.  (see http://www.veryComputer.com/)
>Operating System: Linux 2.0.32 i586 [ELF]
>Configured drivers:
>  SVGA: server for SVGA graphics adaptors (Patchlevel 0):
>      NV1, STG2000, RIVA128, ET4000, ET4000W32, ET4000W32i,
>      ET4000W32i_rev_b, ET4000W32i_rev_c, ET4000W32p, ET4000W32p_rev_a,
>      ET4000W32p_rev_b, ET4000W32p_rev_c, ET4000W32p_rev_d, ET6000, ET6100,
>      et3000, pvga1, wd90c00, wd90c10, wd90c30, wd90c24, wd90c31, wd90c33,
>      gvga, ati, sis86c201, sis86c202, sis86c205, tvga8200lx, tvga8800cs,
>      tvga8900b, tvga8900c, tvga8900cl, tvga8900d, tvga9000, tvga9000i,
>      tvga9100b, tvga9200cxr, tgui9400cxi, tgui9420, tgui9420dgi,
>      tgui9430dgi, tgui9440agi, *9320, tgui9660, tgui9680, tgui9682,
>      tgui9685, *9382, *9385, *9388, *9397, *9520,
>      3dimage975, 3dimage985, clgd5420, clgd5422, clgd5424, clgd5426,
>      clgd5428, clgd5429, clgd5430, clgd5434, clgd5436, clgd5446, clgd5480,
>      clgd5462, clgd5464, clgd5465, clgd6205, clgd6215, clgd6225, clgd6235,
>      clgd7541, clgd7542, clgd7543, clgd7548, clgd7555, ncr77c22,
ncr77c22e,
>      cpq_avga, mga2064w, mga1064sg, mga2164w, mga2164w AGP, oti067,
oti077,
>      oti087, oti037c, al2101, ali2228, ali2301, ali2302, ali2308, ali2401,
>      cl6410, cl6412, cl6420, cl6440, video7, ark1000vl, ark1000pv,
>      ark2000pv, ark2000mt, mx, realtek, AP6422, AT24, AT3D, s3_virge,
>      s3_svga, ct65520, ct65525, ct65530, ct65535, ct65540, ct65545,
>      ct65546, ct65548, ct65550, ct65554, ct65555, ct68554, ct64200,
>      ct64300, generic

>Fatal server error:
>xf86OpenConsole: Server must be running with root permissions
>You should be using Xwrapper to start the server or xdm.
>We strongly advise against making the server SUID root!

>When reporting a problem related to a server crash, please send
>the full server output, not just the last messages

>_X11TransSocketUNIXConnect: Can't connect: errno = 2
>_X11TransSocketUNIXConnect: Can't connect: errno = 2
>_X11TransSocketUNIXConnect: Can't connect: errno = 2
>_X11TransSocketUNIXConnect: Can't connect: errno = 2
>_X11TransSocketUNIXConnect: Can't connect: errno = 2
>giving up.
>xinit:  No such file or directory (errno 2):  unable to connect to X server
>xinit:  No such process (errno 3):  Server error.

>-----------------------------------------------------------------------

>University of Delaware                   http://www.veryComputer.com/~acaro
>-----------------------------------------------------------------------