On Sat, 23 Dec 2000, lee wrote:

>
> i've read /var/log /messages but myself can't tell whats up......;(..i can't
> attach it as its 461k long :)
>
>
> i tried running:
> xdm
> and it hung as well........it tried to load then just hangs with no image at all
> on screen.........
> there is no *.error file in /root
>
>


I've taken a quick look at the copy of the file that you sent to me and this
is what i saw so far (sorry if I had any major mistake, but my eyes are
starting to get blurry after a looong day).

First, you seem to be running Red Hat Linux 7.  It may make a difference
in certain cases, and I didn't install that particular version yet.  I did
play with pinstripe (the beta release) for a while, but never installed the
final version.

Second, you also seem to be experiencing some problems with the filesystems.
For example:

Dec 23 19:24:07 localhost rc.sysinit: Mounting local filesystems:  failed
...
Dec 23 19:24:29 localhost Waiting[510]: Write_pid: write failed - No space left on 
device

Take a look into that issue.  Boot into the system again, and run the 'df'
command to see how you're doing as far as disk space is concerned.  Then,
also take a look at the "/etc/fstab" file to make sure it's correctly
configured.

Third, you also seem to have a lot of services enabled by default and you
may not want to do that.  Log in as root from the console after you
initialize in runlevel 3 and run 'ntsysv' to turn off many of those
services that you may not need.  Even if you plan to use them later,
simply disabling them now will help troubleshoot the problem.  To give you
an example, you seem to have NFS enabled by default.

Other interesting things I found out:

o You also seem to be experiencing problems while loading modules (check
        all those errors regarding this issue).

o Verify that your "/etc/fstab" is correctly configured:
Dec 23 11:22:00 localhost mount: mount: fs type shm not supported by kernel
Dec 23 11:22:00 localhost mount: mount: the kernel does not recognize /dev/sda4 as a 
block device

o  Here is the biggie, the actual problem regarding gdm:
Dec 23 11:22:40 localhost gdm[828]: gdm_slave_windows_kill_ioerror_handler: Fatal X 
error - Restarting :0
Dec 23 11:22:43 localhost gdm[831]: gdm_slave_windows_kill_ioerror_handler: Fatal X 
error - Restarting :0
Dec 23 11:22:46 localhost gdm[834]: gdm_slave_windows_kill_ioerror_handler: Fatal X 
error - Restarting :0
Dec 23 11:22:49 localhost gdm[837]: gdm_slave_windows_kill_ioerror_handler: Fatal X 
error - Restarting :0
Dec 23 11:22:49 localhost gdm[824]: Failed to start X server several times in a short 
time period; disabling display :0
...
...

o I also see this other message related to Gnome:
Dec 17 12:30:01 localhost gnome-name-server[884]: input condition is: 0x11, exiting



Make sure you clean up the "/tmp" directory and doublecheck all the errors
regarding the filesystems and "/etc/fstab".  I have a feeling this is a
disk problem, perhaps because one of the partitions is full or something
like that.

Let me know what happens.









------------------------------------------------------
Nitebirdz
------------------------------------------------------
Thus spake the master programmer:
"You can demonstrate a program for a corporate
executive, but you can't make him computer literate."



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to