OpenSIM + Raspberry Pi + Rasbian Hard-Float= WORKs!

OpenSim + Raspian hard-float = What was once broken now works!

A while ago we decided to go into a journey of OpenSim. For those who are new to metaverse software; OpenSIM (Or OpenSimulator) is a program that emulates the back-end resources of a commercial metaverse known as “Second Life”. The client or front-end that connect to OpenSIM are third party clients such as firestorm and singularity. We liked working offline from SecondLife and keeping a backup of my stuff. What better way to do this then to keep it on something low-powered like a Raspberry Pi? Read on to learn more.

Video mirrors:

In case you have no-script enabled or for some reason cannot see the title video on this website. I have provided direct links for these videos.

  • WebM – Link – This is the newest video standard, works great on Opera, Firefox, Chrome, and newer android phones, not good for Safari, IE, Apple.
  • MP4 – Link – The most compatible codec but also rather large in file size. Make take a while to download.
  • OGV – Link – the fallback codec for older PC’s and Linux USB stick OS’s. 1st generation web video streaming based on Ogg-Vorbis encoding.


In my past blog about the Raspberry Pi we initially thought we fired out pi due to overclocking but later on found it was just a power issues (USB cables too thin to carry the current). Instead of doing high end gaming we’re going to use it for headless applications like web and OpenSIM. Because I do not know the learning curve of the average Pi or OpenSim User; It should be noted that this guide is going to a bit long. This tutorial covers installing OpenSim as well as compiling all of the sources needed to get OpenSim functioning properly. We broke down compiling this way so that these instructions can work on any ARM processor and not just the Raspberry Pi.


As always, please refer to our FAQ for general questions. We are not responsible for any damages caused from this tutorial either physically, mentally, or financially. This will require a considerable level of time in a Linux shell. If you are not comfortable with that then you may stop right now. I should also note to please PLEASE PLEASE DO NOT bother the OpenSim dev team by submitting a mantis bug report about OpenSim and the Raspberry Pi. The dev team is primarily focused on X86 platform. They simply lack the manpower to chase bugs on other platforms. Everything in this tutorial is bleeding edge beta and subject to change.

Lets begin!.

When you look at the server specs for OpenSim and what they suggest would be a good server for OpenSim. You would be quick to notice that your average spec for a island sim is about 2Ghz of CPU power and 1GB of ram! We later found out that the programming language “MONO” which OpenSim is based around really likes multi-core processors! Suddenly a raspberry Pi 2 becomes a very workable unit. To those which are still rocking the single-core Raspberry Pi A or B+ you’ll find that running OpenSim works. But will be very slow as physics/scripting/assets are all being bounced off of just that one armv6 700Mhz processor.

My Raspberry Pi operating in semi-headless mode.

  When I first tried OpenSim a long time ago. I ran into roadblock after roadblock. Eventually finding out that you cannot install MONO onto a raspberry Pi which is running hard-float from the Debian libraries. You either had to run Wheezy or Pidora in soft-float mode. Which in soft-float everything feels like your running on a 300Mhz Pentium II desktop! It’s painfully slow.

Until now!

But First! Lets do the basics and update your Pi!

sudo apt-get update

sudo apt-get upgrade sudo ldconfig sudo apt-get install libgdiplus

Use MySQL instead of OpenSim SQL-Lite!

After a bit of usage on my Pi We noticed a lot of file not found errors flying on my console just by simply camera panning in and out on my phoenix/firestorm viewer. It seemed like the hyper experimental Mono compile is simply having issues looking up null table references. It didn’t effect moving around the sim. Once again this was an annoyance. So understanding that the build of Mono I have is experimental. The goal is to take as much as you can out of the hands of the Mono development language so that OpenSim runs smooth and stable.

Installing MySQL.

sudo apt-get install mysql-server

It’s going to queue you for the root password for MySQL. This is really important to write this down! We will need it later in the chapter! We’re going to create the initial opensim database for it to use and generate a userid “opensimuser” within MySQL with the password “opensimpassword”. I prey you use something slightly more original then these user/pass.

$ mysql -u root -p
Enter password:
mysql> create database opensim;
Query OK, 1 row affected (0.00 sec)
mysql> use opensim;
Database changed
mysql> create user 'opensimuser'@'localhost' identified by 'opensimpassword';
Query OK, 0 rows affected (0.01 sec)
mysql> grant all on opensim.* to 'opensimuser'@'localhost';
Query OK, 0 rows affected (0.01 sec)
mysql> quit

Mono Language installation onto your Pi.

Pass the following commands to merge the mono-project repositories into your Pi:

 sudo apt-key adv --keyserver hkp:// --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
sudo apt-get update
sudo apt-get upgrade

If you are getting the following errors stating that Mono 4.0 packages are being “held back” if you are using an older linux kernel like debian wheezy. Then WITH EXTREME CAUTION pass the following command. If no errors happen after passing the apt-get upgrade you don’t need to do a full dist-upgrade then.

sudo apt-get dist-upgrade

Pinning/Downloading to a more stable version of Mono for OpenSim

Update 8/19/2016 Since mono development is rather fluid in its upgrades there will be times where downgrading to a more stable version of mono is preferred for OpenSim. At the time of this update Mono version is released and although it takes less memory to run OpenSIM it increases its idle processor to %50 and crashes every few hours. This is not cool. If you have any previous and/or newer versions of MONO then we are going to blow up any previous versions of Mono that exist on our pi.

sudo apt-get remove mono-complete
sudo apt-get purge mono-complete
sudo apt-get autoremove

Next, we will take a earlier snapshot from the repo tree index. We prefer version as it was about the version that was released at the time of this blog but you may try others.

sudo echo "deb main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list

Finally, install mono onto this unit.

sudo apt-get update
sudo apt-get mono-complet

Note: If you are receiving an error as follows:

W: Conflicting distribution: wheezy/snapshots/4.2.3 Release (expected wheezy/snapshots but got wheezy)

You can try the following:

sudo echo "deb wheezy/snapshots/ main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list


sudo echo "deb wheezy/snapshots" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list

It really depends on your flavor of Linux that is running on your Pi. To confirm you have version 4.x or better, type in the following.

mono --version

and it should respond with something like this.

Mono JIT compiler version 4.0.4 (Stable Tue Aug 25 23:45:14 UTC 2015)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors.
        TLS:           __thread
        SIGSEGV:       normal
        Notifications: epoll
        Architecture:  armel,vfp+hard
        Disabled:      none
        Misc:          softdebug
        LLVM:          supported, not enabled.
        GC:            sgen

Congratulations! The mono language is now up to date and setup properly.

Configuring OpenSim.

Continuing on we do the basics such as setup the OpenSim.ini to operate in standalone mode by default. And then we have to modify the StandAlone.ini file to switch database control over to MySQL

sudo tar zxvf ./opensim-0.7.6.tar.gz 
cd opensim-0.7.6
cd bin
cp OpenSim.ini.example OpenSim.ini
nano OpenSim.ini

Now go to cursor position 1064 where it says the following:

  ; Include-Architecture = "config-include/Standalone.ini"

Change to:

  Include-Architecture = "config-include/Standalone.ini"

Ctrl-X and ‘y’ to save changes then:

cd config-include
nano StandaloneCommon.ini

Then Change the following lines so it shows like this.

    ; SQLite
    ;Include-Storage = "config-include/storage/SQLiteStandalone.ini";
    ; MySql
    ; Uncomment these lines if you want to use mysql storage
    ; Change the connection string to your db details
    StorageProvider = "OpenSim.Data.MySQL.dll"
    ConnectionString = "Data Source=localhost;Database=opensim;User ID=opensimuser;Password=opensimpassword;Old Guids=true;"

Effectively, you are turning off the built in SQLite that is handled poorly by the experimental MONO package. By commenting out SQLlite and un-commenting the Storage Provider and Connection String for MySQL. We can then fill out your database name, username and password. Save this file Ctrl-X and “y”

mono OpenSim.exe

Now it’s important that when executing mono files that it is case sensitive. In this case “OpenSim.exe” is the file we need to launch.

Choose your physics engine:

The stock version of OpenSim for Mono is expecting an X86 physics library. This will of course crash your raspberry pi as we are running upon an ARM based architecture. Now if you want to simply test if OpenSim even loads on your Raspberry Pi you may edit the following line 250 in OpenSim.ini:

physics = basicphysics

Un-comment basic physics and add a semi-colon to comment out any of the others and save. Basic physics only pays attention to the land itself and your avatar will clip through all objects. It is however handy to know this in the event you are troubleshooting if it is a physics library that is crashing OpenSim or if there is something major going on.

Click here to learn how to install BulletXNA onto your Pi (This is currently the default physics engine for OpenSim Regions.)


If you want your Pi to run physics natively which means more faster collisions. You may want to choose the legacy ubODE/ODE physics. Click here to learn how to install it onto your Pi.

The LibOpenJpeg module:

This library is responsible for generating map-tiles of your Region so that users can see you on the world map. It may be responsible for other functions within the OpenSim engine.

OpenSim System.DllNotFoundException libopenjpeg errors!

After you’ve installed and configured your estate and parcel for the first time, you’ll see this annoying errors that pop up 3 times every few minutes talking about how it cannot take a snapshot of your terrain because your missing libopenjpeg now! Following the Troubleshooting section it says to do the following:

git clone git:// libopenmetaverse
cd ./libopenmetaverse/openjpeg-dotnet/

I should note that the address on my site and the address in OpenSim troubleshooting is different. OpenMetaverse Foundation changed their file structure without telling anyone! So I updated my link. Before we continue any further! We’re going to pass the command:

nano Makefile

The reason why is we have to strip the -m32 flag out or else when we pass the “Make” command it will get pissed off because we’re not on a X86 processor. go to line 37 where it says the following


and change it to:


save the file and continue to compile the library

cp -p /opensim/bin/lib32/

Finally we have to tell OpenSim where our new library is which mean editing the OpenMetaverse.dll.config in the opensim-0.7.6/bin with nano so “nano OpenMetaverse.dll.config” to get there. This is the original file.

<dllmap os="osx" dll="openjpeg-dotnet.dll" target="lib64/libopenjpeg-dotnet-" />
<dllmap os="!windows,osx" cpu="x86-64,ia64" dll="openjpeg-dotnet.dll" target="lib32/libopenjpeg-dotnet-" />
<dllmap os="!windows,osx" cpu="x86-64,ia64" dll="openjpeg-dotnet-x86_64.dll" target="lib64/libopenjpeg-dotnet-" />
<dllmap os="!windows,osx" cpu="x86" dll="openjpeg-dotnet.dll" target="lib32/libopenjpeg-dotnet-" />
<dllmap os="!windows,osx" cpu="x86" dll="openjpeg-dotnet-x86_64.dll" target="lib64/libopenjpeg-dotnet-" />

And this is what mine is:

<dllmap dll="openjpeg-dotnet.dll" target="lib32/" />

Once again, stripping out the OS detection flag and pointing it to the right folder. save your file and restart OpenSim.exe

Finishing touches on OpenSim configuration files

from the /opensim/installation/directory/bin/ folder wherever you installed it to. We are going to edit “nano /config-include/StandaloneCommon.ini” So that when we configure our viewer it will auto-populate with the correct login information and not give us any crap in terms of connection issues to it.

    WelcomeMessage = "Welcome, Avatar!"
    ;; If you have Gatekeeper set under [Hypergrid], no need to set it here, le$
    ; GatekeeperURI = ""
    SRV_HomeURI = "http://opensimpi:9000"
    SRV_InventoryServerURI = "http://opensimpi:9000"
    SRV_AssetServerURI = "http://opensimpi:9000"
    SRV_ProfileServerURI = "http://opensimpi:9000"
    SRV_FriendsServerURI = "http://opensimpi:9000"
    SRV_IMServerURI = "http://opensimpi:9000"
    ;; For Viewer 2
    MapTileURL = "http://opensimpi:9000/"

You’re going to want to find the [LoginService] in StandaloneCommon.ini around line 110. We are going to change it from localhost to whatever the logical DNS that your Raspberry Pi is. If you have a Domain Name for your Pi web-server that automatically resolves the IP to you that is even better. In this example I am using the unix hostname ‘opensimpi’ that I configured in the advanced options in “sudo raspi-config” this will give the SecondLife client all of the information it needs when connecting to your Pi.

    ; These settings are used to return information on a get_grid_info call.
    ; Client launcher scripts and third-party clients make use of this to
    ; auto-configure the client and to provide a nice user experience. If you
    ; want to facilitate that, you should configure the settings here according
    ; to your grid or standalone setup.
    ; See
    ; login uri: for grid this is the login server URI
    login = http://opensimpi:9000/
    ; long grid name: the long name of your grid
    gridname = "Raspberry Pi OpenSim Default Load"
    ; short grid name: the short name of your grid
    gridnick = "opensimpi"

Next, go to [GridInfoService] and do the same down here which is around line 190 on my configuration. Give it a unique grid-name and gridnick so that you can easily see it when you configure your SecondLife Client.

Configuration of OpenSim complete launch it!

Which after all of this, go back into your /opensim/bin folder and mono OpenSim.exe . it should launch nice and clean like the window below.


Binary download of OpenSim libraries.

All of this compiling libraries and modifying configuration files sucks! Don’t you have binaries for my Pi?

For those who want a snap-shot of the configuration files that I have altered above. you may download this file and unzip it into your /opensim/bin folder to replace the .config files and add the proper .so files into your /opensim/bin/lib/ folder. We will however give you the lecture that most in the linux community will do when it comes to binary files. Which is binary files are typically compiled for a specific environment (in our case that environment is Debian Jessie Raspberry Pi Armv7.) The results may be unstable and unpredictable if you attempt to install these binary libraries onto another Linux kernel. It should also be noted that you are trusting this website to provide the binaries instead of compiling from source yourself which could prove dangerous. Trust no one online and whenever possible always compile your own code.

Client configuration.

In this example I am using an older FireStorm v2 viewer so that I get mesh support and can build within the sim with something I already like on SecondLife. Click on Viewer and Preferences or simply hit Ctrl+P to open the FireStorm preferences menu.

As a note the beta versions of FireStorm do not have the Opensim tab in the preferences section of their client. I really don’t know why! So download the older final release and install it (Installing the final release while using the beta releases on Second Life do not conflict with each other. So you can have one configured for your Pi and the other that logs in normally.) Under Add new grid type in opensimpi:9000 or whatever YOUR hostname that you defined in the StandaloneCommon.ini file. Once you have that typed in, you can hit the Apply button and it will disappear with an entry being added into your Manage Grids second. simply choose your new Pi and click Apply and OK.

The Log into Grid section will change to your Raspberry Pi and from there you simply type your username and password. hit Login and be patient as your OpenSim console on your Pi creates all of the assets of your new user for the first time logging in!


Performance of OpenSim

If you are expecting lightning quick action of OpenSim out of a arm7 processor that only eats a few watts of power. Well, we’re simply not up to the task! You can tell just by how long it takes to make a map-file. On my dual-core Pentium E6300 unit it takes about 5ms, on the Pi 47ms. Perhaps you can run this in something like OSGrid since the amount of people that visit your Sim may be only a handful at a time. But for the person that wants a DIY Metaverse and to work offline peacefully or with just a few people connecting for group projects. Then the Raspberry Pi is a great alternative of making your 24 hour OpenSim station. Building and working with prim’s is fast. Using scripts is average but it really depends on the complexity of your SLscripts. Physics and Terra-forming is SLOW. it’s really better off to modify your sims parcel on a Linux box and then port it over later to your Pi. You click on one section of the land and it takes a second for it to respond. The ODE Physics although it works you could potentially lag out your entire sim by rezzing about 32 cubes and turning physics on to watch them collide with each other. You will not only find it painful to move around, but your console will start to send you warnings about latency issues between server and client.

Performance Update with Banana Pi

Update note 12/24/2014: I have now upgraded to a Banana Pi which is made by LeMaker. It is a dual-core ARMv7 processor which runs at 1Ghz and has a gig of ram. Which falls in line with OpenSim specifications much better then the Raspberry Pi. Terra-forming is almost real-time. Scripts now work as if I was on a low-end dual-core Pentium. Because of the Dual-Core action as well as the DDR3 ram on the Banana Pi which is separate from the On-chip ram of the Raspberry Pi I would say performance is about 4-5 times faster then the Pi. As for power consumption it’s actually better then my classic B pi because it uses a switching power supply similar to the Raspberry Pi B+. Which means during idle it takes 320ma and when I hammer on the Sim with physics you are looking at 420-500ma which is better then the 700ma idle of the old Raspberry Pi. And for $20 extra you simply cannot beat that kind of price. I will be running my OpenSim on a Banana Pi until I can find something else. OpenSim will probably run great on the Raspberry Pi 2/3. Anything with multi-core processing helps out mono and therefore helps out OpenSim for all of it’s physics and processing needs. It should be noted that you realistically only need two cores unless you plan on running multiple regions on one ARM based Pi.

Raspian vs. Pidora in OpenSim

I tried Pidora (Fedora for Raspberry Pi) for this procedure and the experimental mono package got even more unstable! Although it lets me login just fine. If you shift-clicked on a prim to make a clone of a pre-existing prim in OpenSim. It would crash giving null database errors even when switching to MySQL on. Although I love Pidora for it’s firewall features which Raspian does not have. And it DID seem to run a little faster under Pidora.. The stability issues was just too much. I also tried to follow the instructions to hand-compile mono hard-float and it didn’t work.

Screenshot above as to the world that is inside of my Pi upon launch. We have since linked it to OpenSim as you could see my progress in this blog entry.

Some final touches to background OpenSIM so you can log off of your headless server

You probably don’t want to keep an SSH connection going all of the time on another computer. You want to run your Raspberry Pi in a headless state like I am doing. Well, there’s a very old Unix command that can help you with this.

sudo apt-get install screen

The screen command is a great tool allowing you to background processes so that even when you logout the process continues to perpetually run to get this started. type the following:


It will just go back to a blank shell prompt then cd into your OpenSim directory and launch your application:

mono OpenSim.exe

Once that is done simply hit control+A and then control+d to detach this screen session. You can type ‘top’ to verify that mono is still running in the background before you logoff. To restore your detached session simply type in:

screen -r

And your right at your OpenSim console! You may want to have a script that automatically reloads OpenSim in the event of a crash (Since depending on the version of MONO Installed it may happen often) follow this script:

until mono OpenSim.exe ; do
    echo "`date +%Y-%m-%d\ \ %T` # OpenSim crashed with exit code
 $EXIT_CODE. Restart in 10 seconds." >> crash.log
    sleep 10

Save this file as “” and then give it execution permission:

chmod 777 ./

Finally you can run ./ and it will go into a loop if there is an error or gracefully shut down if you tell it to simply shut down.

Related Blogs:

Click here to install the ODE or Open Dynamics physics Engine for your arm processor.

Click here to install bullet physics into OpenSim for your Arm processor.

Want to see what is going on with my Pi on OSGrid? Click here.

Want info on how to install 2.1.x for very early edition Raspberry Pi’s running ARMv6? Click here.

Want the archived instructions for Mono 3.x? Click here.


Final thoughts.

Regardless of what Pi you choose be is Raspberry, Orange, or Banana it’s truly amazing that we live in the age where we can have single-chip devices powerful enough to host our own private virtual realities that people can log into. All without having to suck immense levels of power such as keeping a desktop running 24/7. There’s also educational benefits of the system that Linden Labs have laid down years ago in respects that a lot of the building and design of the world is focused around game design. With running your own personal world, you control said world. To control your information is of the the up-most important to all of us here. Hope this has helped you! Take care and server protect you! END OF LINE+++

50 thoughts on “OpenSIM + Raspberry Pi + Rasbian Hard-Float= WORKs!

    • Not as of yet.. I tried it on my 3 and it’s almost to system spec.. a little slow with bullet. but i’m still on ODE because i like how my avatar moved around similar to old school second life with ODE..

  1. As a matter of curiosity, would it be possible to offload some of the functions to a second Pi? I know that the MySql server could be remotely hosted. How about the physics engine, for example, the tree module, etc. etc.?

    I’m thinking maybe spreading the load for a single estate, multi-region sim across multiple Pis without having to engineer separate estates to line up on separate servers.

    • Although I haven’t messed with such a thing.. There was a demo that IBM put up dealing with hosting several hundred avatars on the same region with distributive computing. Something that not even linden labs could do. talks about it with distributed scene graphing. I never played with it because to be honest i was happy that the mono-project stabilized mono enough to run OpenSim.

      Anyhow. hope that helps answer what you may be looking for.

  2. I’m sorry for so many questions, but on the StandaloneCommon.ini, is the opensimpi in “http://opensimpi:9000” the raspberrypi’s ip address give by my router?

    WelcomeMessage = “Welcome, Avatar!”
    ;; If you have Gatekeeper set under [Hypergrid], no need to set it here, le$
    ; GatekeeperURI = “”

    SRV_HomeURI = “http://opensimpi:9000”
    SRV_InventoryServerURI = “http://opensimpi:9000”
    SRV_AssetServerURI = “http://opensimpi:9000”
    SRV_ProfileServerURI = “http://opensimpi:9000”
    SRV_FriendsServerURI = “http://opensimpi:9000”
    SRV_IMServerURI = “http://opensimpi:9000”

    ;; For Viewer 2
    MapTileURL = “http://opensimpi:9000/”

    • I went with local DNS name so that your pi exists on the router be-it wi-fi DHCP or wired static that it always works. You can go with IP address of router although the best option is to have a domain or sub-domain name pointed to your IP so that it always resolves regardless if you are internally networked to your pi or externally.

  3. I found my problem. I did not have libode-dev installed with the other tools on the video. Also, when you did the ./configure –with-trimesh=opcode –disable-asserts –enable-shared –disable-demos –without-x –disable-threading-intf , I thought we only ran make if it got stuck. I ran it anyways and I was then able to find the .libs directory :)

  4. I’m trying to get opensim working on the raspberry pi 3 using your video. I’m at 16.10 on your video and I’m trying to copy the file to the lib32 directory. When I type the command that you have in the video it tells me that no such file or directory exists. After trying to get to the file, it seems that I don’t have the folder libs. I can only get as far into /ode/src. Can you help me out, thank you in advance. :)

  5. I have a Raspberry PI 3 and I tried following your instructions and things seemed to be going fine until I hit sudo apt-get mono-devel mono-complete
    and got:
    pi@RaspBerryPI3:~ $ sudo apt-get mono-devel mono-complete
    E: Invalid operation mono-devel
    So I guess I didn’t get mono to successfully install. Where to go from here?

    • At the time of this article I think I included mono-devel for those who want to compile the OpenSim environment on their Pi from scratch. Which if you are just downloading OpenSim or OSGrid you don’t need mono-devel.

      as long as mono-complete installs successfully and you’re able to pass the

      mono --version

      command, then you should be good to go.

  6. Aha. Copying to opensim’s root did the trick. Thank you so much :)

    While I never did manage to figure out why Mono v4.2.1 crashes OpenSim so horribly on Ubuntu, I did manage to figure out how to upgrade mono to a not-so-current release; it was simply a matter of telling the package manager what branch to pull from so I told it to pull from (i.e. ‘deb wheezy/snapshots/ main’) and that resolved the teleporting issue for me.

    All seems well now on my little ODROID OS server ^^

  7. It would appear I spoke a bit too soon about mono 3.2.8. In standalone mode; while I can cross over to another region I can’t teleport directly. It gives me a “Could not teleport. Internal error.” popup and the OpenSim console outputs an exception similar to yours before you upgraded to mono 4.0.4. So I followed your procedure to upgrade mono and it installed but gave me mono 4.2.1. OpenSim does not seem to like 4.2.1 at all and crashes upon start up. How might I get specifically 4.0.4 installed? Thank you for your help :)

    • Since the blog posting of mono 4.0.4 I actually did upgrade to 4.2.1 and it’s operational on my OSGrid region banana pi. But perhaps things aren’t well in Ubuntu land. I will load Ubuntu on my Orange Pi to see if I can bring Mono and OpenSim up to speed. The only time I encountered crashing on startup was either the mysql daemon was not running (I use mysql for OpenSim to keep the database away from Mono) Or if I launched OpenSim as root by accident and went back to being just a user only to find out some of my log files were all locked up. Which a “sudo chown -Rf user:user /path/to/opensim” and whatever your “user” name is goes there cleans all of that up.

      As for your OpenJPEG error. System.DllNotFoundException is the big one, but it looks like it IS reading your OpenMetaverse.dll.config or else it would’ve simply said instead of so you are making progress. You can try dropping your into the root of opensim as Mono can look for libraries in its root just for diagnostic reasons.

  8. Ah alright, I have been using OpenSim in standalone mode. Haven’t gotten adventurous enough to try hypergrid yet :)

    The error I got for OpenJPEG:

    15:31:00 – Failed generating terrain map: System.DllNotFoundException:
    at (wrapper managed-to-native) OpenMetaverse.Imaging.OpenJPEG:DotNetAllocDecoded (OpenMetaverse.Imaging.OpenJPEG/MarshalledImage&)
    at OpenMetaverse.Imaging.OpenJPEG.Encode (OpenMetaverse.Imaging.ManagedImage image, Boolean lossless) [0x00000]: in :0
    at OpenMetaverse.Imaging.OpenJPEG.EncodeFromImage (System.Drawing.Bitmap bitmap, Boolean lossless) [0x00000] in :0
    at OpenSim.Region.CoreModules.World.LegacyMap.MapImageModule.WriteJpeg2000Image () [0x00000] in :0

    I know that there is a slight discrepancy in the library name; it’s because I’m using OS 0.8.1 and in that version it was named so I left it named that, copied it over, and changed OpenMetaverse.dll.config to use that name instead of

    My OpenMetaverse.dll.config:

  9. Thank you for this excellent article! It helped me to get OpenSim up and running on an ODROID XU4 (running the default latest Ubuntu distro) without a hitch… mostly :) After fiddling around with it a few days and figuring out how to transfer the operating system to a USB hard drive and run from that instead of the SD card read/write performance had dramatically improved. The 8 core processor and 2 GB of RAM on the XU4 is impressive to me in terms of how well it handles OS; You know just “eyeballing” it and watching how the viewer responds to different tasks but I don’t have any hard numbers to show how much of a measurable difference it would be against a Raspberry Pi 2.

    For the distro I used, mono-complete from the default repositories seems to work fine as it is, no recompile to hard-float was needed or the addition of the 4.x branch repository. Using mono v3.2.8.

    The ODE physics library compile and install went smoothly and is working great!

    I did run into a slight issue with the openjpeg library. It compiled without error and I followed the steps to copy the newly compiled file to the lib32 directory and made the change needed in OpenMetaverse.dll.config to point to the file but… OS still seems to think it’s not “installed correctly” on start up and gives me that red text error. Otherwise it would seem it’s generating map tiles and I can see them in the maptiles directory of OS and also when I open the map in the viewer.

    • Glad to hear it’s working out for you. I too transferred OS off of my SD card on my banana pi and over for my SATA-SSD drive and region reload time decreased by %30.

      As for the differences in Mono . I think it really depends on how you have your OS setup. for me v3.2.8 was very stable when running in standalone mode. However, the moment I activated hypergrid via using the OsGrid region is when I was having lots of issues with teleportation. People teleport in, but they can never teleport out. That’s what forced me to upgrade to 4.x . Then again, Ubuntu’s Mono 3.2.x might be a lot more stable then the Debian (Raspbian) side of things with Pi users.

      Mind copying what the red text is saying for LibOpenJpeg? Not sure if i can help . But I want to see if it’s a file-not-found error or something more serious. LibOpenJpeg does not interfere with region operation it just gets annoying to see in the logs every time it generates a new map-tile.

  10. S-config,
    In the above post, the two 8Gb Sandisk Cards were purchased at Best Buy and I wrote the image to the disk that you posted above from dropbox. Could it be as simple as the Raspberry image won’t work on a Banana pi?

    • That is correct. The Raspberry Pi image I generated for that user in the reply section was a very long time ago when it was still Raspberry Pi A, and B models. Which is compiled for armv6f kernel. That will not boot properly on the banana pi. The reason why I made the pre-load during the start of the Raspberry Pi kickstarter days was compiling mono 2.x on the Pi was really brutal you can’t just get mono from apt-get like we do now.

      I ultimately decided that I had to revise my documentation a few times over the years to lean more on acquiring libraries and compiling it because of the sheer variety of different imbedded units that are out there.

  11. John Summers,
    I like what you did with the Pi and your website, but I cannot find the link to actually buy one of your preloaded SD Cards. I’m working with a banana pi and wish to purchase a 32Gb card. Please advise.

    Also, I’ve done the steps above on my banana pi and I can run mono OpenSim.exe just fine, but I get a message about the not being installed correctly and I can’t log in to the sim on Firestorm. It’s a standalone to be accessible only behind my firewall, until I learn more. What do I need to do?

    I also bought two 8Gb cards from SanDisk and neither one is working. I formatted them in a windows 8.1 machine and the precess reported success, but the pi does nothing with it. It doesn’t recognize it, it doesn’t boot, nothing. Any advice?

    • ? Do you mean If so I did document that error and it not only has to be pointed to the right file so it does not crash but you have to either compile it or download the pre-compiled binary of and of course modify the OpenMetaverse.dll.config file so it can actually find the arm compiled version of

      hope it helps!

      • Awesome! Thanks for getting back to me so soon! I’ll give that a shot as I think it might be pointing to the wrong directory. Also, do you have any ideas on why it won’t allow me to log in? I’m using a Linksys WRT54G router.

        I’d be interested in purchasing an SD card pre-configured and perhaps a whole pi with same and I think others might be as well, either on ebay or a website like this.

        • Okay, when it comes to network troubleshooting. One of the first things you can try the moment OpenSim comes up to the command prompt of your region is open up a web-browser and type in the ip-address along with the default opensim port which is typically 9000. for example, if i type in it responds with the following 404 error:


          The page you requested has been obsconded with by knomes. Find hippos quick!

          If you are trying to log-in, your link parameters should have: "-loginpage http:///?method=login -loginuri http:///" in your link

          If you can get this. Then this means opensim is visible on your network! And the rest may come down to second life client configuration . the OpenSim.ini file is responsible for the UDP port assignment in case you need to change it to something else. I had to change it personally because my banana pi was also running a UPNP server where port 9000 was its interactive web-page. so i modified my opensim.ini to move it up to 9100. since you are running in stand-alone local mode there’s no need to modify anything on your router. Router modification comes when you want to setup hypergrids and have opensim visible to the outside net. Also, your regions have their own UDP ports as stated in the /bin/regions/regions.ini file within opensim. You may want to change those to 9101, 9102 , etc just to keep things organized.

          I’m not sure if I should be doing pre-loadeded images of OpenSim. Part of the problem is the moving target scenario. Where there’s multiple distro’s of bananna pi that are available and each have their own advantage/disadvantages in their own rights. The other issue is because OpenSim is also a moving target in respects that they are slowly evolving and changing to adapt to the newer mono engine and switching physics engines. That it’s better for people to learn how to install it so when the next release comes out they know how to back up their region into .oar files and re-setup the updated software again.

  12. HI, did it as instructed on my new PI, but it stills crashes at the bulletsim point, I used the latest version opensim-0.8.1, any advice you have will be welcome.

    thank you

    • I actually had another blog post dealing with the troubles of compiling bulletsim for ARM on this posting. There is only two solutions can can be offered as a work-around right now until the OpenSim devs update their code to use the libraries directly like how ODE works. One of them is to simply let XNA take over bulletphysics at the penalty of CPU power by modifying your opensim.ini file to include the following statement.

      UseSeparatePhysicsThread = true
      BulletEngine = "bulletxna"

      The BulletSim catagory does not exist in opensim.ini after 0.8.x for some reason. but telling it to run via XNA/mono does work. However, after further testing on OSGrid I’ve been finding out that bullet works with prims great but it kind of sucks at mesh objects with their own collisions defined.

      And of course the fallback is going into opensim.ini and modifying your physics to switch to ODE and compile your own ODE library which is the most efficient physics engine on the Pi and works great with mesh but it’s not great with when it deals with transferring physicals from region to region such as vehicles.

      Anyhow, hope that helps!

      • It worked, thank you very much, I now have to do the jpeg thing, but its is now running on my PI, have yet to try to log in yet, but thanks a lot.

        • Glad to hear it’s working out for you. I’ve revised my blog to include the binaries of and which the only thing you have to do is modify the Ode.NET.dll.config and OpenMetaverse.dll.config to point to the respective files on your Pi.

          My Binaries were originally compiled on the Raspberry Pi v1 running Rasbian and when I upgraded to Banana Pi which runs Armv7 I simply transferred the .so files and it worked from there. Since Pi v2 is Armv7 as well, I don’t think there will be a problem in using the binaries there either.