You confirmed that you are using "gdm" as your display manager. That means that gdm is the only properly configured display manager on your system. So, the test you have below for xdm is irrelevant.
Lets step back and have you reboot, do a telinit 3, then do the same thing you did for xdm with gdm instead. Please report the results of that.
I know this may be frustrating, but you are learning a lot of things about generic X administration... you'll be a lot better off after struggling through this and actually getting this fixed than you will be if you get frustrated and give up. So, please, take your time with this if you need to so that you don't give up. Let me know if you want to take a break for a couple of days.
Harold
Woellert, Kirk D. wrote:
Something has changed, after changing run levels and setting debug mode for XDM, telinit 3 xdm -debug 10 -nodaemon I did a reboot and now the Win2K box won't connect anymore (checkboard pattern, no login). I have attached the linux gdm.conf file and included the xdm-config file. Also is a log entry from the /var/log/gdm directory.
Confirmed GDM is the *dm running:
[EMAIL PROTECTED] ~]$ ps -ef |grep gdm root 1056 1 0 09:46 ? 00:00:00 /usr/bin/gdm-binary -nodaemon root 1107 1056 0 09:46 ? 00:00:00 /usr/bin/gdm-binary -nodaemon root 1108 1107 12 09:46 ? 00:58:04 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7 kdw 2480 2458 0 17:38 pts/0 00:00:00 grep gdm [EMAIL PROTECTED] ~]$
----------------------------xdm-config ! $XConsortium: xdm-conf.cpp /main/3 1996/01/15 15:17:26 gildea $ ! $XFree86: xc/programs/xdm/config/xdm-conf.cpp,v 1.6 2000/01/31 19:33:43 dawes Ex DisplayManager.errorLogFile: /var/log/xdm-errors DisplayManager.pidFile: /var/run/xdm-pid DisplayManager.keyFile: /etc/X11/xdm/xdm-keys DisplayManager.servers: /etc/X11/xdm/Xservers DisplayManager.accessFile: /etc/X11/xdm/Xaccess DisplayManager.willing: su nobody -c /etc/X11/xdm/Xwilling ! All displays should use authorization, but we cannot be sure ! X terminals will be configured that way, so by default ! use authorization only for local displays :0, :1, etc. DisplayManager._0.authorize: true DisplayManager._1.authorize: true ! The following three resources set up display :0 as the console. DisplayManager._0.setup: /etc/X11/xdm/Xsetup_0 DisplayManager._0.startup: /etc/X11/xdm/GiveConsole DisplayManager._0.reset: /etc/X11/xdm/TakeConsole ! DisplayManager*resources: /etc/X11/xdm/Xresources DisplayManager*session: /etc/X11/xdm/Xsession DisplayManager*authComplain: false
! SECURITY: do not listen for XDMCP or Chooser requests ! Comment out this line if you want to manage X terminals with xdm !DisplayManager.requestPort: 0
-------------------------------------------------
[EMAIL PROTECTED] gdm]# cat :0.log
XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com
Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-20.9smp ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linu x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Thu Nov 13 17:51:04 2003 (==) Using config file: "/etc/X11/XF86Config"
