FW: Problems starting XFree86 => Problem Solved

["Harold Hunt" <huntharo at msu dot edu>]

Naveen forgot to cc the list.

-----Original Message-----
From: Naveen Kansara [mailto:nkansara@primus.com.au]
Sent: Monday, April 01, 2002 2:44 AM
To: Harold Hunt
Subject: Re: Problems starting XFree86 => Problem Solved


Thanks Harold. After readig the XWin.log from /tmp I found out that it was
the 'classical' error 'Can't find default font 'fixed''. After a revisit to
mail acrhives again, I realised that I had to remount cygwin root into
binary mode(which was in text mode initially), then reinstall and wow it
worked. I still can't start X from bash but works fine from dos(good enough
for me :-).

Great work guys. Keep up the good work. Many thanks to everyone associated
in developing XFree86 and Cygwin.

Naveen

----- Original Message -----
From: "Harold Hunt" <huntharo@msu.edu>
To: "Naveen Kansara" <nkansara@primus.com.au>; <cygwin-xfree@cygwin.com>
Sent: Monday, April 01, 2002 5:22 AM
Subject: RE: Problems starting XFree86


> First off, look in the log file:
>
>
http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-log-file-location
>
> Then, send in that log file to the mailing list if you can't figure out
what
> to do.
>
> I suspect that you may need to update DirectX, since it sounds like the
> server is having a problem allocating memory for drawing the graphics.
>
> Harold
>
> > -----Original Message-----
> > From: cygwin-xfree-owner@cygwin.com
> > [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Naveen Kansara
> > Sent: Sunday, March 31, 2002 8:04 AM
> > To: cygwin-xfree@cygwin.com
> > Subject: Problems starting XFree86
> >
> >
> > Hi
> >
> > I have recently installed XFree86 4.2 on my PC which has WIN 98 and
cygwin
> > version 2.194.2.21. I have read the mail archives and have tried all the
> > available options but nothing seems to work. I am giving the results
when
> > startx is envoked under bash or startxwin under dos. Both startx and
> > startxwin.bat are as supplied by the installation(which was
troublefree).
> >
> > The output when running startxwin.bat from dos command prompt
> > >>startxwin.bat - Starting on Windows 95/98/Me
> > X connection to 127.0.0.1:0.0 broken (explicit kill or server shutdown)
> >
> > The output when running startx from bash prompt
> > >>startx
> > waiting for X server to begin accepting connections .
> > ..
> > giving up.
> > xinit:  Connection refused (errno 111):  unable to connect to X server
> > xinit:  No such process (errno 3):  Server error.
> >
> > $ XWin -query 127.0.0.1:0.0
> > opens up the Cygwin/XFree86 window but closes it after a few secs
without
> > any error messages. Trying to run Xwin -query to a remote host (which is
a
> > Solaris machine) has the same effect.
> >
> > Trying xterm on it's own gives the can't open display error.
> > $ xterm
> > xterm Xt error: Can't open display: 127.0.0.1
> >
> >
> > In both instances the Cygwin/XFree86 window opens but is completely
> > blank(white background), remains for few seconds and then closes.
However
> > running XWin has the same response but no error message is printed.
> >
> > I have a PPP and a Realtek RTL8029(AS) Ethernet adapter.
> > Below is the output of ipconfig /all
> >
> > Windows 98 IP Configuration
> >
> >  Host Name . . . . . . . . . : NKANSARA
> >  DNS Servers . . . . . . . . : 203.134.24.70
> >                                        203.134.26.70
> >  Node Type . . . . . . . . . : Broadcast
> >  NetBIOS Scope ID. . . . . . :
> >  IP Routing Enabled. . . . . : No
> >  WINS Proxy Enabled. . . . . : No
> >  NetBIOS Resolution Uses DNS : No
> >
> > 0 Ethernet adapter :
> >
> >  Description . . . . . . . . : PPP Adapter.
> >  Physical Address. . . . . . : 44-45-53-54-00-00
> >  DHCP Enabled. . . . . . . . : Yes
> >  IP Address. . . . . . . . . : 210.50.202.191
> >  Subnet Mask . . . . . . . . : 255.255.255.0
> >  Default Gateway . . . . . . : 210.50.202.191
> >  DHCP Server . . . . . . . . : 255.255.255.255
> >  Primary WINS Server . . . . :
> >  Secondary WINS Server . . . :
> >  Lease Obtained. . . . . . . : 01 01 80 12:00:00
> >  Lease Expires . . . . . . . : 01 01 80 12:00:00
> >
> > 1 Ethernet adapter :
> >  Description . . . . . . . . : Realtek RTL8029(AS) Ethernet Adapt
> >  Physical Address. . . . . . : 00-4F-49-00-73-37
> >  DHCP Enabled. . . . . . . . : Yes
> >  IP Address. . . . . . . . . : 169.254.14.92
> >  Subnet Mask . . . . . . . . : 255.255.0.0
> >  Default Gateway . . . . . . :
> >  DHCP Server . . . . . . . . : 255.255.255.255
> >  Primary WINS Server . . . . :
> >  Secondary WINS Server . . . :
> >  Lease Obtained. . . . . . . : 03 30 02 10:50:46
> >  Lease Expires . . . . . . . :
> >
> > Below is the output of netstat -a
> > $ netstat -a
> >
> > Active Connections
> >
> >   Proto  Local Address          Foreign Address        State
> >   TCP    nkansara:1088          NKANSARA:0             LISTENING
> >   TCP    nkansara:137           NKANSARA:0             LISTENING
> >   TCP    nkansara:138           NKANSARA:0             LISTENING
> >   TCP    nkansara:nbsession     NKANSARA:0             LISTENING
> >   TCP    nkansara:137           NKANSARA:0             LISTENING
> >   TCP    nkansara:138           NKANSARA:0             LISTENING
> >   TCP    nkansara:nbsession     NKANSARA:0             LISTENING
> >   UDP    nkansara:1088          *:*
> >   UDP    nkansara:nbname        *:*
> >   UDP    nkansara:nbdatagram    *:*
> >   UDP    nkansara:nbname        *:*
> >   UDP    nkansara:nbdatagram    *:*
> >
> > Though the ping works well  on 127.0.0.1
> > $ ping 127.0.0.1
> >
> > Pinging 127.0.0.1 with 32 bytes of data:
> >
> > Reply from 127.0.0.1: bytes=32 time=1ms TTL=128
> > Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
> > Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
> > Reply from 127.0.0.1: bytes=32 time=1ms TTL=128
> >
> > Ping statistics for 127.0.0.1:
> >     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > Approximate round trip times in milli-seconds:
> >     Minimum = 0ms, Maximum =  1ms, Average =  0ms
> >
> > Some of the solutions tried by me are:
> > 1)setting the ecvironment valiable OS and DISPLAY
> > 2)trying various sets of ip address such as 0.0.0.0
> >
> > It seems to me that either it cannot connect to 127.0.0.1 or the
> > connection
> > can't be maintained. Any suggestions/pointers/references would be highly
> > appreciated.
> >
> > Thanks
> >
> > Naveen
> >
> >
>