[Xid] Found temporary solution

[Cimi]

I've found a stupid solution (temporary) for the famous Xid crash.

Just to avoid total freeze
Run X.
Run nvidia-settings and enable FSAA.
Download and unpack this file (found in this forum): http://visualisation.tudelft.nl/~cpb...ash-x86.tar.gz
Run the program 2 or three times (one is sufficient for 90% cases) just to make Xid error compare (tail -f /var/log/kern.log).

Now, when you'll play ut2004 the system doesn't crash, at least it will crash ONLY the game.

My Xid error, it appears only the first time I run the Cone3-nvcrash:

just4fun:/home/cimi# tail -f /var/log/kern.log
Jan  5 03:19:47 just4fun kernel: NVRM: Xid: 27,  L1 -> L0
Jan  5 03:19:48 just4fun kernel: NVRM: Xid: 12, COCOD 00000002 beef3901 00000039 00000400 0d080300
Jan  5 03:19:48 just4fun kernel: NVRM: Xid: 27,  L1 -> L0
Jan  5 03:19:48 just4fun kernel: NVRM: Xid: 6, PE0002 0f54 f000ff53 00110578 f000ef57 00000000
Jan  5 03:19:48 just4fun kernel: NVRM: Xid: 27,  L1 -> L0
Jan  5 03:19:48 just4fun kernel: NVRM: Xid: 12, COCOD 00000002 beef3901 00000039 00000400 00e3e3e3
Jan  5 03:19:48 just4fun kernel: NVRM: Xid: 27,  L1 -> L0
Jan  5 03:19:48 just4fun kernel: NVRM: Xid: 6, PE0002 0f54 f000ff53 00110578 f000ff53 00000000
Jan  5 03:19:48 just4fun kernel: NVRM: Xid: 27,  L1 -> L0
Jan  5 03:19:48 just4fun kernel: NVRM: Xid: 12, COCOD 00000002 beef3901 00000039 00000400 009f9f9f

I'm hoping nvidia developer will continue their great job fixing the most common bug of all!
After this will be fixed nvidia linux driver will be absolutely perfect!
Thanks in advantages.

Andrea (Cimi).

[JaXXoN]

Interessting observation! I was about to post a similar one, but for
me it's actually the opposite: after running Cone3-nvcrash (BTW.:
no immediate system freeze any more with 8178) i also see
a number of XIDs in the kernel log and then the system easily
freezes when switching from X to text console. This "bad mood"
even persists after power cycling (power off for five seconds) -
means after reboot, the system still easily crashes when switching VTs.
It is necessary to power down the machine for at least 30
seconds to get the driver behaving well, again. Other then
that, 8178 works pretty good for me, so far (i'm having some
troubles with UT2004, but i think that's a different issue, not
related to the nvidia driver).

regards

Bernhard

[Cimi]

It was only a case... ut2004 crashed again, without Xid this time!

[evilghost]

I have no issues with UT2004 on two boxes running 8178, have you applied the recent 3369.1 UT2004 patch, not vanilla 3369. 3369.1 addresses some memory leaks/etc that are known to cause crashes. When I was running 3369 I was crashing almost constantly and sporadically (without Xid errors). 3369.1 resolved the issue and I did not have crash issues prior to applying vanilla 3369.

[Cimi]

I've installed the game and patched it only with http://liflg.org/?catid=6&gameid=17
3369.2. I was right? Or I had to patch with other patches and then repatch with this one?

[evilghost]

Hmm, I've not tried 3369.2, to be honest, I didn't even realize 3369.2 was out. Perhaps could you try using 3369.1 and see if you have the same problem with 3369.2? I know without question vanilla 3369 was bad producing high-memory utilization and almost constant crashes.

Let me know if you would.

[evilghost]

Thinking more about it, I think 3369.2 was just a hotfix and was did not include all of 3369. I think you need to install 3369 and then install 3369.2 (or 3369.1).

[JaXXoN]

Originally Posted by evilghost

I have no issues with UT2004 on two boxes running 8178, have you applied the recent 3369.1 UT2004 patch, not vanilla 3369.

I'm using version 3369.2, but the bug also apeared in earlier versions:

Sometime, the screen freezes or goes black, but you can still hear the
sound (i.e. when you go/fly around or shoot). I then need to commit
suicide (i.e. AvRIL into floor) or wait until i get killed - this brings the
screen back. Pretty annoying, especially when you carry the flag around!

This happens rarely and i have the "impression" the problem only occurs
under the following circumstances:

1. From server browers, select some server (join)
2. Screen goes black with white letters "Connecting ..."
3. This screen is typically only shown for a few seconds, but
sometimes it can take a long time until the connection
is established (although the server is for sure up and running).
4. In this cases, it typically helps to abort the connection with the
escape-key and return to the server browser to click "Join" again.
(then the connection typically works out immediatly)
5. Sometimes, it happens that connection proceeds (load screen
shows up) before you actually can click the Join button in the
server browser. I think this causes the effect decribed above,
but i didn't yet checked if it is 100% reproducable.

regards

Bernhard

[Cimi]

done patching and repatching and nothing changes. I can't play any games!!

[evilghost]

Tried 3369.1?

[Cimi]

Originally Posted by evilghost

Tried 3369.1?

yes, 3369, 3369.1, 3369.2.
It's an nvidia bug. Under windows NO crash. Under linux ut2004 and enemy territory crashed in the same way... image frozen, music for 10 seconds with hard disk working (red led on the computer case), then all freeze.
And I must do an hardreboot.

[netllama]

Please post a bug report.

Thanks,
Lonni