BF>Can you start X from the console? No. No X from console. What I get after startx is: There is no link /var/X11R6/bin/X to the correct X server binary. Please configure the correct X server with SaX/SaX2, which will create the missing link. I'm aborting now. BF>Type in '/usr/X11R6/bin/X' The X is a symbolic link to /var/X11R6/bin/X which is connected to the /usr/X11R6/bin/X86???? BF>That will start the server. You will see nothing but a BF>series of dots on the BF>screen, but it shows that your X server is working. To BF>stop it, log in at BF>another console and kill the process. No dots. BF>Then try 'startx > startlog' at the console. This BF>should fire up X and KDE. BF>if it doesn't, startlog will contain valuable clues. Gives the same result as '/usr/X11R6/bin/X' Finally the monitor stops receiving data and starts a sleeping phase. Using Sax2 also ends in a sleeping monitor after telling me: Initializing Please wait... startup No further action. So I think I have to do some editing but where? BF>On Friday 13 Jun 2003 14:07, Constant Brouerius van BF>Nidek wrote: BF>> Sorry for the repost but I did not get an answer so BF>here it BF>> goes. My video card, a Matrox G 200 went down and a BF>> replacement S3, Savage 4 was the replacement. BF>> During booting the new hardware was with the 8.1 BF>version BF>> recognised correctly and the XF86Config was changed BF>> accordingly with Yast2 in console. BF>> BF>> After reboot I ended up in console. The grafic login BF>did BF>> not work. Console works okay but X and KDE are out of BF>> reach. BF>> What should I do to get X back? -- " Every little BYTE helps " NTReader v0.36w(P)/Beta (Registered) in conjunction with Net-Tamer.