64 bit Ubuntu starting but not working.

Ok, I know I should move to 32 bit.

Having said that, I stubbornly ignore it and ask.

I have a Ubuntu 8.10- the Intrepid Ibex - and my SL (I've tried so many different viewers that I can't remember them all) does always the same: starts, connects, then I'm usually stuck at the lower sim corner with no objects rezzing. Blue and water and it's all.

Netstat shows one connection established (on a mac with a healthy SL I have four)

Seems to be a net problem, but exchanging machine and keeping the same IP won't change. Anyone had experienced this (and possibly solved it?)

Thanks for any comment!







-----------my "about second life"-------

Second Life 1.22.11 (113976)
Release Notes

CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Memory: 2008 MB
OS Version: Linux 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8800 GS/PCI/SSE2
OpenGL Version: 2.1.2 NVIDIA 177.82

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.23073 (Mozilla GRE version 1.8.1.13_0000000000)
Packets Lost: 5953/19012 (31.3%)

1.st your packet lost dont looks good, its aboove 30%...as far i now i comes to problems (when my isp has problems as example) when packet losts goes over 5% sometimes even with 1%.

2.nd if you dont having a huge database or intensive graphics work running (3d, huge pictures etc) you really dont need to be on 64Bit...not yet.

3rd. I know many are saying 64Bit, i underwrite that..but not for now...maybe for the future.
Now allmost for SL 64Bit(Linux) is pain in the ass...my 2 cents to it.

4rd. 64bit isnt real 64bit, cpu is still a 32bit one, with some 64bit extensions, like sse, mmx etc.

5th. back to your problem, it's the high packetlost in my eyes.

Thanks Hawk!

I agree it must be the net, but why? The machine is perfectly functional with normal network connectivity. So it's the way SL uses network access?

Just an idea: SL is known to have (had(?)) problems with some (not all) WLAN setups. So if you've been using WLAN, try with wired LAN, instead.

The login process is mostly HTTP-based, but transfer of world-content is UDP-based. Possibly you are using some sort of firewall which understands and permits the HTTP requests but not the UDP requests. If this is a Linux-specific problem, possibly your distribution has iptables (or similar) enabled by default - if so, please try again with the software firewall disabled. That's my first thought.

Try to deinstall apparmor/apparmor-utils and libapparmor1. In many circunstances, this utility block net trafic.

SaludOS/2

Thank you all for trying to think this out. Both suggestions sounded very reasonable and I've tried them immediately. Sadly, no change.

-@Tofu:--

I've stopped firewalling through firecracker; iptables says

sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

-@Damien:---

I've tried with apparmor (both stopping it and actually removing it) but to no avail.

-----------------

Also, I've tried to connect on UDP (the nc trick: nc -l -u -p 53000, nc -u target 53000), from a remote machine - and it works. So, I guess it IS udp - but somehow from the SL side, not from the system side.

By the way my packet loss went up to 106%
And when I tp, I get strange coordinates (ex. x 10000)

Well, I guess it's just my bad luck.. thanks again guys!