Re: x-crash (please decipher my log file)

[Kent West]

Niels L. Ellegaard wrote:

I recently updated my xfree from 4.0 to 4.3 (sarge). Suddenly my x
stopped working. I would be grateful if someone could help me decipher
my log file. 

My XF86Conf-4 is almost directly created by dpkg-reconfigure. However
I removed the part about the generic mouse because I got a complaint
that I did not have the device /dev/input/mice (I don't know how to
create it... I make a symbolic link, and it get's deleted)
 

I believe this device node is automagically created when a USB mouse is 
inserted. Alternatively, you might try switching to the /dev directory 
and running "./MAKEDEV mouse" or maybe even just "./MAKEDEV". (This is 
from hazy understanding, so you might want to do some research along 
these lines.)

When I write dpkg-reconfigure xserver-xfree86 I get an error saying
"open_sock() No such device". Afterwards I get errors saying that the
configlets ofxserver-common and timezoneconf are bad.
In dmesg I have a lot of messages like the following
atkdb.c: Unknown key released (tanslated set 2, code 0x7 on isa0060/serio0)
atkbd.c: This is an XFREE86 bug. It shouldn't access hardware directly
Would it help if I started XFree86 in gdb to create a log?

                     Thanks in advance

                             Niels

Here is the log: 

(--) PCI:*(1:0:0) nVidia Corporation NV11 [GeForce2 MX/MX 400] rev 178, Mem @ 0xce000000/24, 0xc0000000/27, BIOS 

My first suspicion is that the new version of X has changed in its 
support for your nVidia chipset.
My second suspicion is that in your old system you had a third-party 
(directly from nVidia?) driver which was wiped out with this upgrade, 
and you'll need to go back to nVidia to get their driver.

(WW) NV(0): config file vrefresh range 50-75Hz not within DDC vrefresh range 55-75Hz
 

It appears your digital device controller (?) has a different vertical 
refresh than what is specified in your XF86Config-4 file; you can reset 
this by running "dpkg-reconfigure xserver-xfree86" and choosing 
"Advanced" (I think) at the point you're asked how you want to set the 
monitor timings.

Fatal server error:
Caught signal 11.  Server aborting
 

I don't recall if this error number occurs with other non-X-related 
errors, so I'll ask the question: Are you sure it's X that is dying and 
not the failure of X to find a window manager/client which causes X to die?

In other words, is this happening from "startx" or from a login manager 
like kdm? Is it happening from at least two different wm's?

--
Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]