This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: xwin on cygwin - cannot connect
- From: "Andrew Leung" <andrew dot leung at utoronto dot ca>
- To: <cygwin-xfree at cygwin dot com>
- Date: Sun, 30 Nov 2003 21:01:06 -0500
- Subject: RE: xwin on cygwin - cannot connect
- Reply-to: cygwin-xfree at cygwin dot com
I thought this could be a network issue, but ping signs don't show info
on packet loss:
drew@SCV ~
$ ping -t 192.168.0.4
Pinging 192.168.0.4 with 32 bytes of data:
Reply from 192.168.0.4: bytes=32 time=2ms TTL=64
Reply from 192.168.0.4: bytes=32 time=2ms TTL=64
Reply from 192.168.0.4: bytes=32 time=2ms TTL=64
Reply from 192.168.0.4: bytes=32 time=2ms TTL=64
Reply from 192.168.0.4: bytes=32 time=2ms TTL=64
Reply from 192.168.0.4: bytes=32 time=2ms TTL=64
Reply from 192.168.0.4: bytes=32 time=2ms TTL=64
Ping statistics for 192.168.0.4:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms
Control-C
drew@SCV ~
is xdcmp being flaky? I'm going to try rebooting to box and try an
initial connection again.
-----Original Message-----
From: cygwin-xfree-owner@cygwin.com
[mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Harold L Hunt II
Sent: Sunday, November 30, 2003 8:09 PM
To: cygwin-xfree@cygwin.com
Subject: Re: xwin on cygwin - cannot connect
What are the exact flags you are passing to XWin.exe? Please copy and
paste them so that there are no transcription errors.
Harold
Andrew Leung wrote:
> K actually the flag was enabled already - I must have forgotten to
> restart it after making those changes. After doing that, here's some
> changes in the logs - the IP you see there is ip of the linux box.
> Also, I was watching top closely during the connection attempt, and
> found kdmgreeter process popon for maybe 5 seconds, and then disappear
> off the list.. is that indicative of anything?
>
>
> ddxProcessArgument - Initializing default screens
> winInitializeDefaultScreens - w 1024 h 768
> winInitializeDefaultScreens - Returning
> OsVendorInit - Creating bogus screen 0
> _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
> (EE) Unable to locate/open config file
> InitOutput - Error reading config file
> winDetectSupportedEngines - Windows NT/2000/XP
> winDetectSupportedEngines - DirectDraw installed
> winDetectSupportedEngines - Allowing PrimaryDD
> winDetectSupportedEngines - DirectDraw4 installed
> winDetectSupportedEngines - Returning, supported engines 0000001f
> InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
> winSetEngine - Using Shadow DirectDraw NonLocking
> winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits
> per pixel
> winCreateBoundingWindowWindowed - User w: 1024 h: 768
> winCreateBoundingWindowWindowed - Current w: 1024 h: 768
> winAdjustForAutoHide - Original WorkArea: 0 100 718 1024
> winAdjustForAutoHide - Adjusted WorkArea: 0 100 718 1024
> winCreateBoundingWindowWindowed - WindowClient w 918 h 693 r 918 l 0 b
> 693 t 0
> winCreateBoundingWindowWindowed - Returning
> winCreatePrimarySurfaceShadowDDNL - Creating primary surface
> winCreatePrimarySurfaceShadowDDNL - Created primary surface
> winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary
surface
> winAllocateFBShadowDDNL - lPitch: 3672
> winAllocateFBShadowDDNL - Created shadow pitch: 3672
> winAllocateFBShadowDDNL - Created shadow stride: 918
> winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
> winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d
24
> bpp 32
> winCreateDefColormap - Deferring to fbCreateDefColormap ()
> winFinishScreenInitFB - returning
> winScreenInit - returning
> InitOutput - Returning.
> MIT-SHM extension disabled due to lack of kernel support
> XFree86-Bigfont extension local-client optimization disabled due to
lack
> of shared memory support in the kernel
> (==) winConfigKeyboard - Layout: "00000409" (00000409)
> (EE) No primary keyboard configured
> (==) Using compiletime defaults for keyboard
> Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)"
> Options = "(null)"
> winPointerWarpCursor - Discarding first warp: 459 346
> winBlockHandler - Releasing pmServerStarted
> winBlockHandler - pthread_mutex_unlock () returned
>
> AUDIT: Sun Nov 30 19:59:45 2003: 2708 XWin: client 6 rejected from IP
> 192.168.0.4 port 1024
> Auth name: MIT-MAGIC-COOKIE-1 ID: -1
> AUDIT: Sun Nov 30 19:59:46 2003: 2708 XWin: client 6 rejected from IP
> 192.168.0.4 port 1025
> Auth name: MIT-MAGIC-COOKIE-1 ID: -1
> AUDIT: Sun Nov 30 19:59:50 2003: 2708 XWin: client 6 rejected from IP
> 192.168.0.4 port 1026
> Auth name: MIT-MAGIC-COOKIE-1 ID: -1
> AUDIT: Sun Nov 30 19:59:55 2003: 2708 XWin: client 6 rejected from IP
> 192.168.0.4 port 1027
> Auth name: MIT-MAGIC-COOKIE-1 ID: -1
> AUDIT: Sun Nov 30 20:00:02 2003: 2708 XWin: client 6 rejected from IP
> 192.168.0.4 port 1028
> Auth name: MIT-MAGIC-COOKIE-1 ID: -1
> AUDIT: Sun Nov 30 20:00:11 2003: 2708 XWin: client 6 rejected from IP
> 192.168.0.4 port 1029
> Auth name: MIT-MAGIC-COOKIE-1 ID: -1
> AUDIT: Sun Nov 30 20:00:22 2003: 2708 XWin: client 6 rejected from IP
> 192.168.0.4 port 1030
> Auth name: MIT-MAGIC-COOKIE-1 ID: -1
>
>
>
> -----Original Message-----
> From: cygwin-xfree-owner@cygwin.com
> [mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Harold L Hunt II
> Sent: Sunday, November 30, 2003 7:06 PM
> To: cygwin-xfree@cygwin.com
> Subject: Re: xwin on cygwin - cannot connect
>
> Andrew,
>
> Oops, forgot to check the basics. XDMCP is not enabled by default on
> most Linux distributions these days. See below for information on how
> to enable it:
>
>
http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-mandrake-8.1-
> xdmcp
>
> Make sure that you either restart gdm (drop to runlevel 3, then go
back
> to runlevel 5) or just restart the Linux machine to make sure that the
> XDMCP enable flag is read. Then do your test again.
>
> Harold
>
> Andrew Leung wrote:
>
>
>>Harold,
>>
>>Yes that's the latest XWin.log off the cygwin installation. Then I
>>suppose it's something on the linux box. Are there logs on there that
>>would shed some light? I see that gdm is running from top command:
>>
>> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU
>>COMMAND
>> 2089 root 14 0 936 900 752 R 2.1 3.0 0:02 0 top
>> 2092 root 11 0 10372 5276 1500 S 1.3 17.9 0:16 0 X
>> 2060 root 11 0 896 740 660 S 0.7 2.5 0:00 0 sshd
>> 6 root 10 0 0 0 0 SW 0.1 0.0 0:15 0
>>kupdated
>> 2101 gdm 9 0 10968 10M 6736 S 0.1 37.3 0:26 0
>>gdmgreeter
>> 1 root 9 0 80 52 44 S 0.0 0.1 0:04 0 init
>> 2 root 9 0 0 0 0 SW 0.0 0.0 0:00 0
>>keventd
>> 3 root 19 19 0 0 0 SWN 0.0 0.0 0:00 0
>>ksoftirqd_CPU
>> 4 root 9 0 0 0 0 SW 0.0 0.0 0:33 0
>
> kswapd
>
>>Login screen prompt is on the box. Am I in the right direction or
>>something missing?
>>
>>-----Original Message-----
>>From: cygwin-xfree-owner@cygwin.com
>>[mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Harold L Hunt II
>>Sent: Sunday, November 30, 2003 1:27 AM
>>To: cygwin-xfree@cygwin.com
>>Subject: Re: xwin on cygwin - cannot connect
>>
>>Andrew,
>>
>>Hmm... the log file looks okay, you did try a failed connection, then
>>send in that XWin.log, right?
>>
>>I'm going to bed. Maybe someone else can help.
>>
>>Harold
>>
>>Andrew Leung wrote:
>>
>>
>>
>>>Thanks for the reply, here it is, This was my latest attempt, but
>>
>>now
>>
>>
>>>it seems the checkered screen stays.. but with no change. It does
not
>>>disappear on me at this point.
>>>
>>>ddxProcessArgument - Initializing default screens
>>>winInitializeDefaultScreens - w 1024 h 768
>>>winInitializeDefaultScreens - Returning
>>>OsVendorInit - Creating bogus screen 0
>>>_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
>>>(EE) Unable to locate/open config file
>>>InitOutput - Error reading config file
>>>winDetectSupportedEngines - Windows NT/2000/XP
>>>winDetectSupportedEngines - DirectDraw installed
>>>winDetectSupportedEngines - Allowing PrimaryDD
>>>winDetectSupportedEngines - DirectDraw4 installed
>>>winDetectSupportedEngines - Returning, supported engines 0000001f
>>>InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
>>>winSetEngine - Using Shadow DirectDraw NonLocking
>>>winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits
>>>per pixel
>>>winCreateBoundingWindowWindowed - User w: 1024 h: 768
>>>winCreateBoundingWindowWindowed - Current w: 1024 h: 768
>>>winAdjustForAutoHide - Original WorkArea: 0 100 718 1024
>>>winAdjustForAutoHide - Adjusted WorkArea: 0 100 718 1024
>>>winCreateBoundingWindowWindowed - WindowClient w 918 h 693 r 918 l 0
b
>>>693 t 0
>>>winCreateBoundingWindowWindowed - Returning
>>>winCreatePrimarySurfaceShadowDDNL - Creating primary surface
>>>winCreatePrimarySurfaceShadowDDNL - Created primary surface
>>>winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary
>>
>>surface
>>
>>
>>>winAllocateFBShadowDDNL - lPitch: 3672
>>>winAllocateFBShadowDDNL - Created shadow pitch: 3672
>>>winAllocateFBShadowDDNL - Created shadow stride: 918
>>>winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
>>>winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d
>>
>>24
>>
>>
>>>bpp 32
>>>winCreateDefColormap - Deferring to fbCreateDefColormap ()
>>>winFinishScreenInitFB - returning
>>>winScreenInit - returning
>>>InitOutput - Returning.
>>>MIT-SHM extension disabled due to lack of kernel support
>>>XFree86-Bigfont extension local-client optimization disabled due to
>>
>>lack
>>
>>
>>>of shared memory support in the kernel
>>>(==) winConfigKeyboard - Layout: "00000409" (00000409)
>>>(EE) No primary keyboard configured
>>>(==) Using compiletime defaults for keyboard
>>>Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)"
>>>Options = "(null)"
>>>winPointerWarpCursor - Discarding first warp: 459 346
>>>winBlockHandler - Releasing pmServerStarted
>>>winBlockHandler - pthread_mutex_unlock () returned
>>>
>>>
>>>-----Original Message-----
>>>From: cygwin-xfree-owner@cygwin.com
>>>[mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Harold L Hunt II
>>>Sent: Sunday, November 30, 2003 1:09 AM
>>>To: cygwin-xfree@cygwin.com
>>>Subject: Re: xwin on cygwin - cannot connect
>>>
>>>Andrew,
>>>
>>>Andrew Leung wrote:
>>>
>>>
>>>
>>>>I've got cygwin on winxp machine - can't connect to the X server.
>>>
>>>When
>>>
>>>
>>>
>>>>using xwin.exe :0 -query <host> the checkered screen quickly comes
up
>>>>and then disappears.. Anyone know whats happening? Also I remember
>>>>someone mentioning that X shouldn't be running on the linux box when
>>>>trying to connect. How do I stop this as the login screen loads up
>>>>everytime I boot up? The machine is running slackware. I'm pretty
>>>
>>>sure
>>>
>>>
>>>
>>>>there's communication since tcpdumps show some responsive port 117
>>>>traffic.. Any help is appreciated, I'm new to linux so I'm not sure
>>>>what to look for.. Thanks in advance.
>>>
>>>
>>>Sounds like you have a font problem on your Windows machine. Please
>>>send in the contents of /tmp/XWin.log after a failed attempt to
>>
>>connect.
>>
>>
>>>Harold
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>