[nvidia-glx-legacy] ppracer aborts after intro screen on NVidia Riva TNT2

[Pascal De Vuyst]

I'm using dapper 20060502.
planetpenguin-racer 0.3.1-5ubuntu2

Planetpenguin racer aborts after pressing a key in the intro screen that says "press any key to start".

I have Nvidia Riva TNT2 M64 video card and I'm using the nvidia-glx-legacy drivers 1.0.7174+2.6.1.

The former tuxracer did work for me in Breezy which has the same nvidia-glx-legacy driver version.

[Pascal De Vuyst (pascal-devuyst)]

ppracer aborts unexpectedly.

[Pascal De Vuyst (pascal-devuyst)]

I discussed this with _t_ on IRC channel #ubuntu+1. He suggested me to change the following lines in ~/.ppracer/options:

-set warning_level 500
+set warning_level 100

-set write_diagnostic_log true
+set write_diagnostic_log false

This results in the file ~/.ppracer/diagnostic_log.txt in attachment.

[Pascal De Vuyst (pascal-devuyst)]

diagnostic_log as requested by _t_ on IRC.

[Toby Smithe (tsmithe)]

That's weird - it doesn't show any errors or warnings in the log. It just stops. Perhaps I got it wrong and to increase the warning level you've gotta decrease the "warning_level". Doesn't sound right somehow, but you could give it a go. Do you have direct rendering? "glxinfo | grep direct". I don't know if that would affect it though.

[Pascal De Vuyst (pascal-devuyst)]

Changing warning_level doesn't change a lot, the output stays the same.

glxinfo | grep direct returns:
direct rendering: Yes

Perhaps this output from dmesg is usefull which seems to be generated after ppracer aborts (see attachment). I did a sudo dmesg -c first to clear the buffer and then runned ppracer.

[Pascal De Vuyst (pascal-devuyst)]

dmesg messages shown after ppracer aborts

[Toby Smithe (tsmithe)]

Well the dmesg shows that NVRM is doing something (perhaps wrong), and that
it's something to do with the kernel and Xid. NVRM could be something like
nVidia Riva M-something, and Xid might be something to do with X. Are there
any files on your system with Xid (in any shape or form) in them? It may
hold a clue.

On 02/05/06, Pascal De Vuyst <email address hidden> wrote:
>
> Changing warning_level doesn't change a lot, the output stays the same.
>
> glxinfo | grep direct returns:
> direct rendering: Yes
>
> Perhaps this output from dmesg is usefull which seems to be generated
> after ppracer aborts (see attachment). I did a sudo dmesg -c first to clear
> the buffer and then runned ppracer.
>
> ** Attachment added: "dmesg messages shown after ppracer aborts"
> http://librarian.launchpad.net/2448502/dmesg
>
> --
> ppracer aborts after intro screen
> https://launchpad.net/bugs/42478
>

[Joshua Gardner (cellofellow)]

I'd just like to report that I'm getting the same thing here. Intro screen loads, I press any key, and the game dies. The terminal simply says Core Dumped.

I have the nVidia TNT2 and the nvidia-glx-legacy kernel.

Also, when ppracer dies it leaves X at the smaller gaming resolution. Often it disables the mouse and the only way to get X back to normal is to restart it.

Sorry I don't have any real information, but I sure do like this game.

[Martin Günther (launchpad-domain-the-phoenix)]

Yes, same with me. And I also have the nVidia TNT2 and the nvidia-glx-legacy kernel, so this should be the cause.

Actually, there are some more interesting lines in the dmesg output, see attachment.

[Martin Günther (launchpad-domain-the-phoenix)]

... and my diagnostic log.

[Pascal De Vuyst (pascal-devuyst)]

Confirmed by CelloFellow and Martin

[Sitsofe Wheeler (sitsofe)]

NVRM: Xid indicates that this is a bug related to the nvidia binary module - not the user land ppracer program. Punting from ppracer -> linux-restricted-modules-2.6.15 (mention of dapper in this bug report).

Xid's are basically error messages produced by the nvidia binary driver to indicate something unexpected happened. They are only really of use to NVIDIA engineers so your best bet is to talk to NVIDIA about this. There is a forum their folks read over here: http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 .

[papukaija (papukaija)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[papukaija (papukaija)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[papukaija (papukaija)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Please remember that both nv and nvidia's drver for tnt2 don't have 3d acceleration support.