[SOLVED] SLES 10 Desktop help

vindsen · 12-03-2010, 10:48 AM

When my new server arrived(SLES 10) desktop part of it was working fine.Then i wanted to configure VNC from YaSt.While testing it my desktop crashed.Its not coming up it gives me following error msg when i type in startx command:

Quote:

xauth: creating new authority file /root/.serverauth.12014
/usr/X11R6/bin/xauth: (stdin):2: unknown command "e88ea0fcd36417897bad590f2f4c5a78"

X Window System Version 6.9.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 6.9
Build Operating System: SuSE Linux [ELF] SuSE
Current Operating System: Linux2.6.16.60-0.54.5-smp #1 SMP Fri Sep 4 01:28:03 UTC 2009 x86_64
Build Date: 05 September 2009
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
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/Xorg.0.log", Time: Fri Dec 3 16:30:33 2010
(==) Using config file: "/etc/X11/xorg.conf"
ACPI: OSPMOpen called
ACPI: Opening device
(EE) Failed to load module "rfbkeyb" (module does not exist, 0)
(EE) Failed to load module "rfbmouse" (module does not exist, 0)
(WW) MGA(0): Failed to set up write-combining range (0x96600000,0x1f0000)
(WW) MGA(0): Failed to set up write-combining range (0x96400000,0x3f0000)
(WW) MGA(0): Failed to set up write-combining range (0x96000000,0x7f0000)
(WW) MGA(0): Failed to set up write-combining range (0x96600000,0x1f0000)
(WW) MGA(0): Failed to set up write-combining range (0x96400000,0x3f0000)
(WW) MGA(0): Failed to set up write-combining range (0x96000000,0x7f0000)
(EE) MGA(0): [drm] Direct rendering only supported with G200/G400/G450/G550.
ListenOnTCPPort: Address already in use
Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from list!

*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.

Backtrace:
0: X(xf86SigHandler+0x7e) [0x44895e]
1: /lib64/libc.so.6 [0x2b487461afc0]
2: /usr/X11R6/lib64/modules/vnc.so(httpCheckFds+0x7c) [0x2b4874aeba9c]
3: /usr/X11R6/lib64/modules/vnc.so [0x2b4874adafe2]
4: X(WakeupHandler+0x8a) [0x48904a]
5: X(WaitForSomething+0x197) [0x4a7267]
6: X(Dispatch+0x85) [0x4886d5]
7: X(main+0x3fe) [0x49597e]
8: /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b4874608304]
9: X [0x430e89]

Fatal server error:
Caught signal 7. Server aborting

Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

ACPI: Closing device
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.

Pls help me solve this problem with ur expertise

thanks
vindsen

TB0ne · 12-03-2010, 11:17 AM

Quote:

Originally Posted by vindsen

When my new server arrived(SLES 10) desktop part of it was working fine.Then i wanted to configure VNC from YaSt.While testing it my desktop crashed.Its not coming up it gives me following error msg when i type in startx command:

Pls help me solve this problem with ur expertise

Spell your words out...that text-speak garbage is against LQ rules.

First place to check is /etc/X11, and look for any xorg.conf files. There should be one there now, and may be a backup file, if there were changes made. Something like xorg.conf.install, or the like. Move/rename the xorg.conf file that's there now, to something, and COPY the backup file to xorg.conf, and try to start X then. If that doesn't work, make a backup of the xorg.conf file to some other directory (like your home directory), and remove it from /etc/X11. Then try to run sax2 from the command-prompt, so you can set up a basic X configuration again.

If you're using SLES, you've got support...you can call Novell.

jschiwal · 12-03-2010, 12:00 PM

Could you run a live distro and see if you have video. I'm wondering if there might be a problem with your graphic device, which caused the initial crash.

The error message from xauth doesn't seem to make sense to me. Xauth is used to create & share cookies allowing access to the display.
It seems, from searches on Google, that different problems result in the same message.

Please post the permissions for the X server. E.G. on OpenSuSE
ls -l /usr/bin/X*
lrwxrwxrwx 1 root root 14 2010-09-06 02:52 /usr/bin/X -> /var/lib/X11/X
lrwxrwxrwx 1 root root 1 2010-08-20 16:12 /usr/bin/X11 -> .
-rwxr-xr-x 1 root root 1709352 2010-08-19 10:37 /usr/bin/Xdmx
-rwxr-xr-x 1 root root 2071496 2010-08-19 10:37 /usr/bin/Xephyr
-rwxr-xr-x 1 root root 1665024 2010-08-19 10:37 /usr/bin/Xnest
-rws--x--x 1 root root 1946536 2010-08-19 10:37 /usr/bin/Xorg
-rwxr-xr-x 1 root root 1877472 2010-08-19 10:37 /usr/bin/Xvfb
-rwxr-xr-x 1 root root 1914288 2010-08-19 10:37 /usr/bin/Xvnc
-rwxr-xr-x 1 root root 849 2010-11-26 00:54 /usr/bin/X.x11-video-nvidiaG02

Check if you have space on your partitions. A run away file, filling up a partition can cause X to not start. This could cause a failure replacing the .Xauthority file.

vindsen · 12-06-2010, 12:35 PM

Quote:

Originally Posted by TB0ne

Spell your words out...that text-speak garbage is against LQ rules.

First place to check is /etc/X11, and look for any xorg.conf files. There should be one there now, and may be a backup file, if there were changes made. Something like xorg.conf.install, or the like. Move/rename the xorg.conf file that's there now, to something, and COPY the backup file to xorg.conf, and try to start X then. If that doesn't work, make a backup of the xorg.conf file to some other directory (like your home directory), and remove it from /etc/X11. Then try to run sax2 from the command-prompt, so you can set up a basic X configuration again.

If you're using SLES, you've got support...you can call Novell.

Many thanks for ur response
I moved the xorg.conf file to my home directory and removed the existing one after taking back-up.I tired reconfiguring through sax2 command and it works.I can get into my desktop!!! so When i restarted I am able to see desktop login for SUSE Linux and im able to enter username only.I dont know for some reason im not able to enter the password.The characters are not getting recognised.So starngely when i remove my mouse im able to enter the password and login to desktop.Again through Failsafe Startx command works im getting my desktop and not through ordinary boot.

So Guru's please help

vindsen

(P.S I tried different mouse devices and in different USB port still the problem remains)

TB0ne · 12-06-2010, 12:49 PM

Quote:

Originally Posted by vindsen

Many thanks for ur response
I moved the xorg.conf file to my home directory and removed the existing one after taking back-up.I tired reconfiguring through sax2 command and it works.I can get into my desktop!!! so When i restarted I am able to see desktop login for SUSE Linux and im able to enter username only.I dont know for some reason im not able to enter the password.The characters are not getting recognised.So starngely when i remove my mouse im able to enter the password and login to desktop.Again through Failsafe Startx command works im getting my desktop and not through ordinary boot.
(P.S I tried different mouse devices and in different USB port still the problem remains)

Again, SPELL OUT YOUR WORDS. It's "your", not "ur".

If you've tried with different mice, that is indeed very puzzling. Have you tried a different desktop environment to see if the problem persists? And are you using GDM or KDM? Running the kdm-config (or gdm-config), may let you set things up. And again, you can call Novell for support...you are PAYING for it with your SLES....they can help you.

vindsen · 12-07-2010, 07:11 AM

Quote:

Originally Posted by TB0ne

Again, SPELL OUT YOUR WORDS. It's "your", not "ur".

If you've tried with different mice, that is indeed very puzzling. Have you tried a different desktop environment to see if the problem persists? And are you using GDM or KDM? Running the kdm-config (or gdm-config), may let you set things up. And again, you can call Novell for support...you are PAYING for it with your SLES....they can help you.

Thanks for YOUR response

For some strange reason one more shutdown did the trick.Now my SLES is up and running and also configured my VNC.It's been such a good learning experience.

cheers
vindsen