[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Suddenly no X-window

On Friday 26 March 2004 01:57 pm, David Mosberger wrote:
> >>>>> On Fri, 26 Mar 2004 19:36:55 +1100, Duraid Madina
> >>>>> <duraid@octopus.com.au> said:
>   Duraid> You'll probably want to use a newer nvidia driver (from
>   Duraid> nvidia.com) or move libc back down. I don't think you have
>   Duraid> any other choices.
> A word of warning with the nvidia driver: it's important to use the
> driver with a "matching" XFree86 server.  AFAIK, the current nvidia
> drivers work with all version of XFree86 v4.3.x, but NOT with v4.4.x.
> Apparently, there is some version-checking support in the X server
> which could detect such mismatches, but the nvidia driver doesn't seem
> to do that and as a result, it will load into XFree86 v4.4.xx just
> fine, except that it will then sooner or later crash with a segfault.
> 	--david

Well, I went to a newer nvidia driver, 1.0-5336
(NVIDIA-Linux-ia64-1.0-5336-pkg1.run  there was also a "pkg0"
version in the ftp archive, but I guess that was an oops)

Now X starts but KDE will not run

(II) Initializing extension GLX
startkde: Starting up...
/usr/X11R6/bin/kde: line 143: 14986 Segmentation fault    kreadconfig --file
    kpersonalizerrc --group General --key FirstLogin --default true --type         
_X11TransOpen: Unable to find transport for local
ksplash: cannot connect to X server :0
Warning: connect() failed:  : No such file or directory
ksmserver:  cannot connect to X server :0
startkde: Shutting down...
Warning: connect() failed:  : No such file or directory
Error: Can't contact kdeinit!
startkde: Running shutdown scripts...
startkde: Done.

I think that the _X11TransOpen failure is the key one but I
don't understand what it means precisely.  There were
messages during boot up about "no response from
localhost" Does that mean that some demon is not running??
I can ping localhost and a lot of others. Also, ftp to nvidia and
apt-get to debian have worked fine.

Richard Harke

Reply to: