37 replies to this topic

[fabio]

freedom2, on Oct 26 2010, 01:22 AM, said:

Is there [...] a way to run it windowed so I can access desktop and kill the process?

Create ~/.config/0ad/config/local.cfg andput in:

windowed = true

Also see /usr/share/games/0ad/config/default.cfg for other options.

[Random-Dude]

Hi,

I've updated my previous code with an updated script :-). This fixes the "bug" you mentioned. and a few other things. See Changelog at the bottom for all changes.

I would recommend using reverse on previous script, and running the new one :-)

I believe 0-AD has a "alt+enter" key-combo which switches it from windowed to non-windowed on the fly. The above poster is also correct if you want a permanent solution :-)

As for the 100% CPU, does this happen when in Login screen, or only after login? A re-install of drivers may/may not fix this.

The All option on the previous script only installed these extra packages:
nvidia-glx (now included by default on new script)
nvidia-185-libvdpau
nvidia-current-dev
nvidia-185-modaliases (now included by default on new script)
nvidia-glx-185-dev
nvidia-current-dev

As for 0AD still not starting, are you still getting the same segfault message?

[freedom2]

Thank you for the windowed config, fabio!


....


Hi - not a seg fault .

Now it stalls when I hover over the Single Player and gives this output in the window..

0x7f3b80914916) /usr/lib/games/0ad/libmozjs-ps-release.so(+0x70916) [0x7f3b80914916]
(0x7f3b8091e6ed) /usr/lib/games/0ad/libmozjs-ps-release.so(js_Invoke+0x8dd) [0x7f3b8091e6ed]
(0x7f3b8091efc8) /usr/lib/games/0ad/libmozjs-ps-release.so(+0x7afc8) [0x7f3b8091efc8]
(0x7f3b808c545a) /usr/lib/games/0ad/libmozjs-ps-release.so(JS_CallFunctionValue+0x1a) [0x7f3b808c545a]
(0x5be6e9) /usr/games/pyrogenesis() [0x5be6e9]

errno = 0 (?)
OS error = ?


©ontinue, (S)uppress, (B)reak, Launch (D)ebugger, or (E)xit?
©ontinue, (S)uppress, (B)reak, Launch (D)ebugger, or (E)xit?
D
Sleeping until debugger attaches.
Please wait.

and it crashes.



I will try the as soon as placate wife....

Edited by freedom2, 27 October 2010 - 12:57 AM.

[freedom2]

Random-Dude, on Oct 26 2010, 04:48 AM, said:

As for the 100% CPU, does this happen when in Login screen, or only after login? A re-install of drivers may/may not fix this.

This went away after reboot, and was typical of my earlier experience with beta 10.10 ubuntu.


I was excited to see update to 0AD dev pa 8469 in my Update Manager.

Still have same new error as I posted above . I will play with this a bit more tonight.

[freedom2]

Now have 0AD alpha running on Ubuntu 10.10 64 bit!

1. Downgraded my Nvidia drivers with the script in this post.

2. deleted the game cache

rm -rf ~/.cache/0ad

3. upgraded to the October 30 ppa-dev


Thanks for all of your help! (Fabio, Philip`, RandomDude )

Is a beautiful game!

[Random-Dude]

freedom2, on Oct 31 2010, 05:51 PM, said:

Now have 0AD alpha running on Ubuntu 10.10 64 bit!

1. Downgraded my Nvidia drivers with the script in this post.

2. deleted the game cache

rm -rf ~/.cache/0ad

3. upgraded to the October 30 ppa-dev


Thanks for all of your help! (Fabio, Philip`, RandomDude )

Is a beautiful game!

That's great news! :-). Glad you got it working. :-).

[Ykkrosh]

Is this fixed by the 260.19.21 drivers?

They say:

Quote

Fixed a race condition in OpenGL that could cause crashes with multithreaded applications.

which sounds relevant.

[Random-Dude]

Ykkrosh, on Nov 11 2010, 08:02 PM, said:

Is this fixed by the 260.19.21 drivers?

They say:
which sounds relevant.

Hi, Just gave it a test run on my main (fc12) box. Everything seems ok so far. Only gave it a test run though (start-up (fullscreen), flick through menus, start game, default selection, play, enter game.. move units, exit back to menu, switch to windowed, start new game, play with camera, screenshot :-) ) I've added the screenshot below, it's rather large though (1440x900) so I've only linked it :-) It merely demonstrates 0AD running with newest drivers :-)

http://img526.images...reenshot1sg.png

So, from what I can tell, the new drivers appear to be fixed.

[fcxSanya]

Hooray! Good news, Random-Dude, thanks for testing

[freedom2]

Ykkrosh, on Nov 11 2010, 02:02 PM, said:

Is this fixed by the 260.19.21 drivers?

They say:
which sounds relevant.

Confirmed on Ubuntu 10.10 ; I upgraded my x86_64 drivers and game now works.

Thank you for posting this!


installation notes that may help others:

had to do a

sudo modprobe -R nvidia

after running the nvidia .run installer to overcome an 'api mismatch: nvidia kernal module ... ' error I was getting.

*off to play around with game now...*

[Ykkrosh]

Could someone with NVIDIA drivers (either the broken ones or upgraded/downgraded ones) post the output of running "glxinfo", and the content of ~/.config/0ad/logs/system_info.txt ? (Hopefully that'll include enough information to let the game detect these broken drivers, so in the next release we can give an informative error message to users.)

[freedom2]

Ykkrosh, on Nov 19 2010, 12:31 PM, said:

Could someone with NVIDIA drivers (either the broken ones or upgraded/downgraded ones) post the output of running "glxinfo", and the content of ~/.config/0ad/logs/system_info.txt ? (Hopefully that'll include enough information to let the game detect these broken drivers, so in the next release we can give an informative error message to users.)

My glxinfo

http://paste.ubuntu.com/534445/

and my ~/.config/0ad/logs/system_info.txt

http://paste.ubuntu.com/534447/


nvidia version 260.19.21

[Ykkrosh]

Thanks - I've added some stuff in r8663 so it should detect the broken driver versions and tell people to upgrade.

[freedom2]

glad to be of help! thanks for addressing this issue.

[steronius]

Finally after months of being unable to launch 0ad, here is a "Fix" for Ubuntu 10.04 & 10.10 to update to newest nvidia drivers.

sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
sudo apt-get update
sudo apt-get upgrade

reference: http://www.ubuntuupd...a/ubuntu-x-swat

Edited by steronius, 26 November 2010 - 09:18 PM.

[yepland]

As a fedora 13 user, I too can confirm that the new nvidia driver 260.19.21 works with 0ad-r08413-alpha. The new nvidia driver 260.19.21 hotness isn't in the mainstream repos, but it is in the testing. in short, all you need to do is create a testing repo, enable it, then update nvidia.

the repo /etc/yum.repos.d/rpmfusion-nonfree-testing.repo

[testing]
baseurl=http://download1.rpmfusion.org/nonfree/fedora/updates/testing/13/i386
enabled=1
gpgcheck=0

then update with # yum update akmod-nvidia

you might want to disable the enable flag above after your nvidia update is complete so that way your normal updates don't get mixed in with the testing repo.

great job on the game!!!
-dp

[lucinos]

steronius, on Nov 26 2010, 09:43 PM, said:

Finally after months of being unable to launch 0ad, here is a "Fix" for Ubuntu 10.04 & 10.10 to update to newest nvidia drivers.

sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
sudo apt-get update
sudo apt-get upgrade

reference: http://www.ubuntuupd...a/ubuntu-x-swat

I had exactly the same problem I did exactly this and 0AD now plays fine.

Now Trigger (a racing game) plays in an unacceptable way (the ground is not visible). I tried some other games and they seem fine. I do not mind that I "lost" Trigger, but I wonder if anything else bad happened. (Trigger before was playing flawlessly)

Thanks

editGood News everybody, after a restart Trigger is ok. So it seems that the upgrade did no harm at all.

Edited by lucinos, 07 December 2010 - 07:01 PM.

[taccoboss]

Tried 0ad alpha 3 and now is working good with Nvidia 260.19.26 driver on Ubuntu 10.10. No more seg fault issues! Very good!