ubuntu + SL works 5 mn

I can use SL but after 2 or 3 minutes it is slower and slower. And after 5 mn all my computer is freezed.

I have Ubuntu 8.04 LTS

maxed out RAM?

This sounds like an overheating issue. Is this a laptop?

Also, knowing your system specifications would help: Computer model, type processor, type/model graphics card/chip, graphics driver being used, amount of installed RAM, and so on.

Same here: Ubuntu 9.10 64, AMD Quad Core processor, 4 GB RAM, NVIDIA GeForce 9500 GT with propietary drivers. All worked well for me with Ubuntu 9.04 on the same computer before new installation. ¿Any help?

Edit: no laptop.

It seems that the only viewer that is working fine for me right now is Snowglobe, with every other I tried (SL, Hippo, Omviewer) I have the same problem.

I have a ASUS EEE 1000H Netbook. 2 gig ram, 1.6 Atom processor with a 160gig hd. Intel UMA video
Exact specs can be found here: http://benchmarkreviews.com/index.php?option=com_content&task=view&id=231&Itemid=1&limit=1&limitstart=4 However, I have updated the ram from the base model.
O/S Linux Mint Gloria 7

I have just installed the stable omvviewer from byteme.org

The viewer shows up in the Games menu after a successful install. My experience has been that I can log in just fine. I agree to the autostreaming popup. I then find my character on a bridge on Help Island. Movement is very stuttering and delayed and then after about 5 minutes my computer freezes up solid.

Omvviewer is my second atttempt at getting a functional viewer. I initially downloaded the secondlife viewer from the secondlife website, expanded the archive file and ran the secondlife exe file from within the folder created. I had the same experience that way too.

Any suggestions on something to try?

Do UI and atmospheric sounds continue to work after the freezing occurs?.

Reason I ask, or maybe its a completely unrelated issue, but I have recently been testing Ubuntu 9.10 32bit, seems like the voice vs pulseaudio fight is back, with my system in particular I notice, after say 5 minutes, the viewer becomes VERY slow, and appears to be running at a very low framerate. Music still streams, and voice seems to keep working (although garbled), but all UI and other sounds, become muted.

Voice quality on my system under 9.10, sounds like a garbled mess, even before the pulseaudio crash. Only cure I have so far is to kill pulseaudio and prevent it from auto spawning, without pulseaudio almost everything works great, including slvoice.

Closing the viewer results in it freezing, killing pulseaudio completes the closing of the viewer.

I wonder if this is happening to others?.

Second Life 1.23.4 (12390 Jun 11 2009 15:37:14 (Second Life Release)
Release Notes

Built with GCC version 40102

CPU: AMD Athlon(TM) XP 1800+
Memory: 503 MB
OS Version: Linux 2.6.24-24-386 #1 Sat Aug 22 00:32:28 UTC 2009 i686
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce2 GTS/AGP/SSE/3DNOW!
OpenGL Version: 1.5.3 NVIDIA 71.86.04

libcurl Version: libcurl/7.16.4 OpenSSL/0.9.7c zlib/1.2.3.3 c-ares/1.4.0
J2C Decoder Version: KDU
Audio Driver Version: OpenAL, version 1.1 / OpenAL Community / OpenAL Soft: ALSA Software on default
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.27235 (Mozilla GRE version 1.8.1.18_0000000000)

---

Thats Ubuntu 8.04 (latest, all upgrades)

Desktop tiny tower. 1024x768 tube.

No Voice. No Streams.

Graphics: Full screen or in window, both good. Set Prefs \ Graphics to low, draw 64, avatar imposters on, no bump or shiny, sun and moon, terrain low, disable VBO and it will toddle along at between 10 and 30fps most places for hours without falling over. Even with only 503MB RAM available.

It runs if I bump up stuff but... yeah! kinda depending how far I push it.

Its the VBO in Hardware Options, I think that trashes most low-end configs. The official viewer enables this by default on this config. It runs enabled but is woeful. Disable and whoosh. So I recommend this as the first thing to look at when tuning.

---

Snowglobe run as well on this config. The only 3rd party viewer that works is Meerkat. None of the others even start. No idea why.

---

PS. I do have another box, this is just my whats the least one that will run SL and not fall over because of problems on my end.

Before I go any further, I note that the 1.23 viewer has very definite framerate issues. Even on my setup, I find that my framerate starts slowing to a crawl even in places where I used to get 30+ FPS with older viewers. There is something unkosher with the 1.23 code. I'm kinda curious to know if Compiz might be stepping in the way. Can someone running the 1.23 viewer without Compiz enabled confirm if there's a gradual framerate drop or not?

You're trying to run SL on a netbook. Netbooks are generally not designed for 3D game performance, and it is unlikely that your netbook's graphics chip even has proper 3D support in Linux. If you can get SL to run at all, let alone with usable framerates, consider yourself very fortunate.Sounds like a scheduling problem in Pulseaudio. I fought this issue with 8.10 Intrepid. The way I fixed it there was to edit /etc/pulse/default.pa, looking for the line "load-module module-hal-detect tsched=1". If the line has "tsched=1" or no tsched setting at all, then edit the line so that it ends with tsched=0. This should fix your sound issues with OpenAL.

Out of curiosity, what version of Pulseaudio and ALSA are you running?
You got SL to run on that? And a Windlight viewer, no less? I am *very* impressed!

I recall getting 1.18 working on a system quite like this. I had 768MB memory though. It ran.., well maybe ran was a bit optimistic, oozed would be a better way of putting it. It worked for about two weeks, long enough to let me get out of help island and start setting up things, and then my internet started throwing up obstacles. I ended up losing that avi before I got back on when I forgot the password.

I recall getting about 6-8 fps on a lightly loaded sim, and about 3-5 on a moderately loaded one. The heavy ones essentially locked the viewer up. I did get sound though.

Pulseaudio 0.9.18, and ALSA 1.0.20.

In this version there seems to be no "load-module module-hal-detect tsched=1" option, and I just tried out pulseaudio again to be sure, and pulseaudio faded faster than the viewer rezzed my avatar. No UI sounds on load basically, and voice was using 51% CPU.

Ick! Well, I'm glad you posted this now before Karmic came out. Looks like I'll be hanging on to Jaunty a while longer while I try to hammer away at the problem on my testbed laptop.

Edit: There's no "load-module module-hal-detect" line in /etc/pulse/default.pa at all?

I have switched to Kubuntu, would that make a difference?, I should have mentioned, as Ubuntu Karmic 'forces' pulseaudio use now, and I don't think its stable enough to be forced as an integrated feature in Ubuntu, for one the volume control seems to work with pulseaudio only now, so, for me to un-install pulseaudio, or even disable it, prevents the volume control in Karmic 'Ubuntu' from loading, selecting the sounds option in the menu after disabling, brings up an error something about pulseaudio not loaded, and the sound tray icon no longer appears. I did try the alsa mixer and another volume control from the repos, but they have limited functionality, most importantly for me, is having volume controls working from my multimedia keyboard at least. Kubuntu has not forced this yet and uses the original, and imo, the most configurable volume control, I almost feel like Ubuntu is trying to ruin their own product with this, as so many have pulseaudio problems, the few who claim its working 'perfect' need to run a wider variety of applications imo before claiming its 'perfect' working order, it works good if you just use rhythmbox and watch youtube videos, but any more than that, even using skype, as with my system sound mutes at random intervals and I need to restart skype to give me back the sounds.

OK, now thats off my chest, lol, I ran a search in kate for "load-module module-hal-detect" within 'default.pa', obviously without the quotes, lol. and it gave me no results found, so I dont know what is going on there?, really seems like a rushed release this one tbh. Although......I was told in the Karmic testers section of the Ubuntu forums, pulseaudio is a totally new product, and is NOT in any way comparable to pulseaudio in Jaunty. Although in Jaunty pulseaudio worked well for me, it did crash on rare occasion, but it was pretty much reliable........more importantly it worked with the intention it was created for, and not doing the exact reverse, like previous versions, and now with this new version.

Okay, you're using Kubuntu, which uses Phonon, if I'm not mistaken, at least since Intrepid. I have heard of Pulseaudio installations on KDE-based distros, but not very often. I honestly don't know the KDE side of the house well enough to know what's going on in your case. I can't tell if Phonon is a sound server like Pulseaudio is (and aRts was), or if is a backend like gstreamer and xine, or is a mixture of both; and I don't know if Phonon and Pulseaudio work together or not. KDE is, to me, a really strange creature.

On the GTK side, it doesn't surprise me too much that Ubuntu is "forcing" Pulseaudio. It's the way most of the Gnome-based distros are going. Honestly, I like Pulseaudio. I like the ability to tailor volume levels per application, to use another computer as a virtual sound card, and the ability to see all of the sinks in use (and in the case of gstreamer streams, see the title and artist of songs that are playing - comes in handy in SL clubs). It has had its issues, to be sure; but it has usually been with applications that either weren't Pulseaudio-aware or attempted to access the ALSA device directly. Pulseaudio 0.9.10, which came with Hardy and Intrepid, was prone to crashes with SL due to the way OpenAL abuses the API. 0.9.14 (Jaunty) is far more stable. I haven't had it crash yet, though sound has occasionally glitched under high CPU load. OpenAL still wreaks havoc with it, but at least it doesn't crash anymore. Setting TSCHED to 0 seems to take that beast pretty well, at the expense of a few more CPU cycles. But, love it or hate it, Pulseaudio is becoming a Linux (at least Gnome-based distros) fact of life, becoming more integrated into the desktop environment.

It sounds like I'm going to have to play around with 0.9.20 when Karmic comes out, and see what's different with it. I do note, however, that 0.9.20 is not yet a stable release (latest stable is 0.9.19, according to the Pulseaudio website, so things might change by the time it's released as a stable release)