SuSE 10.2, IBM R50e working

Hi guys and gals,

Wanted to let you all know that the client (SecondLife_i686_1_13_1_6) worked pretty well for me, right out of the box. And I have to say, really not a bad job! I'm really impressed. Thanks for making this available on Linux.

Specs:

SuSE 10.2
Linux 2.6.18.2-34-default i686
KDE 3.5.5

IBM R50e Laptop
1.24 Gb RAM
1.4 Ghz Celeron
Intel 855GM / i810 Graphics

Hi,

I also installed the latest alpha on my SuSE 10.2 box. It has a Core 2 Duo processor, gobs of RAM and a nVidia GeForce 7300 card.

Things seem to be working well with one major exception: When I walk or fly, there's a kind of stuttering effect--you move forward a few steps and then slip backward followed by more forward movement. It's kind of a "four steps forward, one back" thing, and it persists thoughout all walking and flying.

I've also noticed that lots of objects take a long time, sometimes apparently forever to come up to full resolution.

I have an Intel iMac 20", too, and things work fine there using the same network connection...Actually the iMac's on a household wireless network while the Linux box is directly wired to the DSL line. The connection is 6000 kbps (6 mbps) inbound and 768 kbps outbound, so I don't think it's a matter of network throughput.

I'm very new to SL, so there may be settings I should change, but it does seem like something's slightly amiss with the Linux version.

RS

Stuttering movement and rez delays are usually caused by packet loss, i. e. faulty network connection. Please make sure the cabling used to connect the box to the net is good and check your networking settings in the SL client (bandwidth slider should be a tad lower than your actual DSL line speed).

I have had "packet loss" showing up on my system, when Suse does its indexing - i.e. the system is loaded.

I have of course also had packet loss when I got flaky packets - and when I was downloading stuff from a fast site while running the SL Linux client.

All else being equal, I have also had bad packets which were a bug known to LL

I do agree with Zi's analysis, though - I have had stuttering, overflying my destination, keyboard not responding, you name it, all from bad packets.

Ctrl Shift 1 brings up a monitor window that enables you to see bad packet rate, if "client" is visible on the top of the Window Frame as a menu option.

If not, Ctrl Shift D (or Ctrl <windows> D, I think) enables the Client and Server Debug Menu entries.

That machine is used for other purposes and none of them suggest a problem with network hardware or connections. The bandwidth setting is the same as on the Mac installation where it works fine (using the same DSL line). Both machines traverse the same router and switch to connect to the DSL modem. The Mac connects wirelessly to the router, the Linux box is wired. And, of course, I've not tried using both at once. ... (What does SL do if you try to log in from multiple machines? Reject the latter attempt? Bump the former one?)


RS

If you have multiple accounts and do one-per-machine you're fine.

To use more than one machine with the same "real IP", SL has a command line option "-port (number)", where (number) is between 13000 and 13010, I think. I have used this on one machine, with two SL sessions, using "-port 13000" and on the other session "-port 13002" and aside from being DEAD slow, it seems to run OK.

Using the clients simultaneously without this option, causes SL to go weird The second client hangs...

The need to reassing port numbers is natural, if you do any network programming.

I wasn't thinking of using a single machine, actaully, but rather wondering what would happen if I logged in on the two machines I have that both run SL (iMac and Linux) concurrently and using the same ID. As it turns out, that would make them appear at the SL server end as originating from two different IP addresses, since I have four static IP addresses here.

Actually, it's not that I have any real interest in trying to run two sessions concurrently, I was just curious about what would happen if one tried.

RS

Do you actually see packet loss? Watch the network bar on the top right of the client window if it shows any or check the stats on CTRL SHIFT 1 like Angel suggested. If you indeed see packet loss, check the network settings on the Linux box, traceroute to the Linden servers and lower your MTU settings to prevent packet fragmentation.

Good luck!