This is a read-only archive of the Mumble forums.

This website archives and makes accessible historical state. It receives no updates or corrections. It is provided only to keep the information accessible as-is, under their old address.

For up-to-date information please refer to the Mumble website and its linked documentation and other resources. For support please refer to one of our other community/support channels.

Jump to content

Mumble on the SheevaPlug


chasophias
 Share

Recommended Posts

Hi,


Ok.. i'm running Mumble 1.2.2-5 on Debian using the Sheevaplug.

Details:


Hardware: Sheevaplug (1,2Ghz ARM CPU)

OS: Debian Sid Armel

Kernel: 2.6.33.1

Tested Server-Version: 1.2.2-5

Clients: WinXP SP3 x86, Win7 x64

Tested Client-Version: 1.2.2 and 1.2.3


Basicly it runs quite good!

However, it still has an interesting bug.

When people connect there is a chance that others don't see the newcomer.

This is also the case when people change channels..

To fix: Those that did not see should reconnect.


The chance of occurence increases seemingly lineair with the amount of clients connected.

3 members.. zero problems.. 8 - 11 members.. frequent problem.

In the beginning i had the problem also with 3-4 members..

Then i configured my router to give all mumble communications the highest priority.

That decreased the chance of occurence a lot.


Today i'm running uMurMur.. the problem does not occur.

I would rather run the full featured mumble-serve because it has a nice integration with my phpbb forum.


I'm really looking forward to the 1.2.3 server but its not in the debian repository yet.

So perhaps i should turn to the git repository.. did not do that yet.


I also downloaded the sources (1.2.2-5) but i don't have a clue where to look for the code that might be responsible for this bug.

The plug i have is a Developers plug allowing me to have sufficient space to put in all compiler and dev-libs to compile.

I thought ill take a crack at it. Any suggestions?

Link to comment
Share on other sites

  • Moderators

I guess the problem is not fixed in 1.2.3 but we don't have the hardware to debug it as it seems to happen on ARM only and I don't know what could be the problem... maybe byteorder (but many ARMs use LE mode) or something else the arm compiler does different...

Link to comment
Share on other sites

Ok Debuggin C++ Code.. is not really my thing.. but i can give it a try.

Here is my architecture dump (dpkg-architecture):


DEB_BUILD_ARCH=armel

DEB_BUILD_ARCH_OS=linux

DEB_BUILD_ARCH_CPU=arm

DEB_BUILD_ARCH_BITS=32

DEB_BUILD_ARCH_ENDIAN=little

DEB_BUILD_GNU_CPU=arm

DEB_BUILD_GNU_SYSTEM=linux-gnueabi

DEB_BUILD_GNU_TYPE=arm-linux-gnueabi

DEB_HOST_ARCH=armel

DEB_HOST_ARCH_OS=linux

DEB_HOST_ARCH_CPU=arm

DEB_HOST_ARCH_BITS=32

DEB_HOST_ARCH_ENDIAN=little

DEB_HOST_GNU_CPU=arm

DEB_HOST_GNU_SYSTEM=linux-gnueabi

DEB_HOST_GNU_TYPE=arm-linux-gnueabi


So yes.. its little endian.

Ill try to find some nice C++ Debugging tooling and stuff.. it will take me a while to set it all up.

Link to comment
Share on other sites

 Share

×
×
  • Create New...