new install opensuse 13.2, can not start x server

I have just installed opensuse 13.2 64 bit os. It does not boot to desktop. I used curses yast to install nvidia drivers with no luck. Here is the error message:
fatal server error:
(EE) xf86openconsole: can not open /dev/tty0 (no such file or directory)
(EE) please also check log file at ‘/home/jeffrey/.local/share/xorg/xorg.0.log’ for additional information
vga arbitration: can not restore default device
(EE) server terminating with error (1). closing log file
giving up

xinit: unable to connect to x server: connection refused
xinit: server error

xinit failed. /usre/bin/xorg is not setuid, may be that is the reason
if so, either use a display manager or adjust /etc/permissions.local and run 'chkstat --system --set ’ afterwords

I checked and /dev/tty0 does exist along with many other terminals. Do I need to add myself to a user group in yast?

Did you get to a terminal at boot and did you install NVIDIA and did you install the right version and is this a notebook that has Optimus??? ie what video do you have exactly

Little confused at which point you get the tty error?

Did you check the check sum of the downloaded ISO and if using a DVD did you do a media check before the install??

It is a desktop amd 64 bit processor, 2gig ram and nvidia geforce 6 series video card. I can log in as user and root user at the command prompt. The tty0 error is listed when I type startx as root. I have a functioning linux install without a gui desktop. The install disk is fine. I used it to do an update on another box.

And which nvidia driver did you install?
Your card is only supported by the G02 variant.

Enter YaST again (in text mode) and make sure those three packages are installed (and none others with nvidia in the name):
nvidia-gfxG02-kmp-desktop, x11-video-nvidiaG02, nvidia-computeG02

If they are installed, re-install them (Upgrade Unconditionally, not sure at the moment how this would be selected in text mode, press SPACE I suppose until the packages are marked with ‘>’).

And, does Recovery Mode work? (“Advanced Options” in the boot menu)

I updated the 3 packages. I ran startx and I had a cursor arrow and a small box with message:
call to lnvsertemp failed. Temp. dir full? Check your installation.

It almost looks like it is at the desktop.

I also have other drivers:
xf86-video-neuveau
xf86-video-nv
lldrm_nouveau2
lldrm_nouveau2-32bit

Should they be deleted?

That’s totally unrelated to the graphics driver.
That means that KDE cannot create necessary temporary directories during startup.
See the error message.
Is your /tmp or /var/tmp full or unwriteable?

df -h
ls -la /tmp /var/tmp

I also have other drivers:
xf86-video-neuveau
xf86-video-nv
lldrm_nouveau2
lldrm_nouveau2-32bit

Should they be deleted?

No.

It says that /tmp has a total of 20
/var/tmp has a total of 0
after running the commands

How can I tell what condition the folders are in (full/not writable)?

ls -l /tmp
ls -l /var/tmp

Which command said that?
The “ls -l …”?
And what about “df -h”?

How can I tell what condition the folders are in (full/not writable)?

The commands should tell you/us.

df -h shows the free space, ls -l shows (among other things) the permissions.
Or run “ls -ld /var/tmp /var/tmp/kde*” and post the output (maybe a picture of the screen).

Here is the output from ls -ld /var/tmp /var/tmp/kde*

drwxrwxrwt 1 root root 58 nov 11 12:53 /var/tmp
drwx------ 1 jeffrey users 0 nov 11 09:17 /var/tmp/kdecache-jeffrey
drwx------ 1 root root 0 nov 11 12:53 /var/tmp/kdecache-root

Here is the output from ls -ld /var/tmp /var/tmp/kde*

drwxrwxrwt 1 root root 58 nov 11 12:53 /var/tmp
drwx------ 1 jeffrey users 0 nov 11 09:17 /var/tmp/kdecache-jeffrey
drwx------ 1 root root 0 nov 11 12:53 /var/tmp/kdecache-root

the output from df -h is 14% used space

output from ls -la /tmp /var/tmp
/tmp total 20
/var/tmp total 0

output from ls -la /tmp
/tmp total 20
drwxrwxrwt 1 root root 266 nov 11 13:30 .
drwxr-xr-x 1 root root 184 nov 11 13:25 …
drwx----- 1 kdm kdm 0 nov 11 09:28 0185821108
drwx----- 1 kdm kdm 0 nov 11 12:56 0413755701
lines repeat 0591911561
0591911561
1210829937
1460519076
drwxrwxrwt 1 root root 0 nov 11 09:16 .font-unix
drwxrwxrwt 1 root root 0 nov 11 09:16 .ICE-unix
drwx------ 1 jeffrey users 0 nov 11 09:17 kde-jeffrey
drwx------ 1 root root 0 nov 11 12:53 kde-root
drwxrwxrwt 1 root root 0 nov 11 09:16 .text-unix
drwxrwxrwt 1 root root 0 nov 11 13:25 .X11-unix
drwxrwxrwt 1 root root 0 nov 11 09:16 .XIM-unix
-rw------- 1 root root 6 nov 11 04:15 y2yamldataewGw7u

Ok, this all looks fine.

Can you create files in /tmp and /var/tmp? (as user)

touch /tmp/xxx
touch /var/tmp/xxx

Maybe there’s a problem with you home directory then?
“lnusertmp” creates links to /var/tmp in /home/$USER/.kde4, that message states that this failed.

ls -la ~/.kde4

The touch /tmp/test and touch /var/tmp/test did not produce any errors.

Output from command 'ls -la ~/.kde4
total 4
drwx------ 3 jeffrey users 90 nov 11 09:17
drwxr-----19 jeffrey users 4096 nov 12 08:43
lrwxrwxrwx 1 jeffrey users 25 nov 11 09:17 cache-linux-k1qc → /var/tmp/kdecache-jeffrey
drwx------ 4 jeffrey users 32 nov 11 09:17 share
lrwxrwxrwx 1 jeffrey users 30 nov 11 09:17 socket-linux-k1qc → /run/user/1000/ksocket-jeffrey
lrwxrwxrwx 1 jeffrey users 16 nov 11 09:17 tmp-linux-k1qc → /tmp/kde-jeffrey

This seems to be the culprit then:

socket-linux-k1q points to /run/user/1000/ksocket-jeffrey, which doesn’t exist I suppose. (/run/user/XXXX/ normally only contains mount points for disks/partitions mounted via udisks2, i.e. dolphin or the device notifier).
So KDE cannot create any sockets and fails to start.

The easiest way to solve that problem would be to remove that symlink. KDE should recreate it on next startup, correctly pointing to /tmp/.

rm ~/.kde4/socket-linux-k1qc

I was able to remove the link as user and rebooted. It paused at the splash screen showing the first icon, the hard drive, then back to the command prompt. I tried to run startx and received the call to lnusertmp failed. I also tried removing the link as root, but could not find it, unless it it just a user specific link?

Yes, it is a user specific link.

Did you try startx as root?
It won’t work as user.

Did that link maybe get recreated incorrectly again?

I am able to delete the link as user. I became root and ran startx and received the call to lnvsertemp failed message. Back at tty screen I see:
hostname: name or service not known
xauth: file /root/.serverauth.1883 does not exist
Error: cannot create directory ‘/run/user/0/ksocket-root’:
no such file or directory

Ok, the same problem.
It tries to create the folder in /run/user/0/ (0 is root’s userid) instead of /tmp.

Hm.
I looked at the source code, and lnusertmp seems to take the directory from the environment variables $KDETMP or $TMPDIR if they are set, and fall back to /tmp otherwise.

So IMHO, the only reason for using /run/user/$UID can be that one of those variables is set wrong.
What does the following print?

echo $KDETMP
echo $TMPDIR

nothing is echoed back to the screen when I type the commands echo $TMPDIR AND echo $KDETMP