DSM-G600, DNS-3xx and NSA-220 Hack Forum

The upnp/av server that runs with the default DSM-G600 firmware does not support localized strings and does not provide that many features. Looking for a replacement I fell for the MediaTomb project and have successfully installed it on my DSM-G600. It is working quite well with the DSM-520 mediaplayer that now displays Swedish titles correctly.

Some notes on what I did:

** Install Gentoo on the device using chroot

** Dowload MediaTomb

Grab the latest source code from the MediaTomb(http://mediatomb.cc/pages/download) website.

** Emerge packages to make mediatomb compile

libiconv is not masked for ppc arcitecture so we have to unmask it before we can emerge it:

echo "dev-libs/libiconv" /etc/portage/package.unmask
emerge dev-libs/libiconv
emerge dev-db/sqlite

now you can do ./configure, however you might want to emerge some other packages in order to parse metadata and do scripting:

** emerge packages for dealing with metadata in audio and photo files

emerge media-libs/id3lib
emerge media-libs/libexif
[emerge media-libs/taglib]
[emerge media-libs/libextractor]

The "taglib" and "libextractor" is disabled by default configuration.

The libextractor depends on "dev-libs/glib" that is "profile" masked. The libextractor shows up as
disabled even if not emerged. Perhaps some other app creates the required files. Have not dug any deeper into this.

** package to enable scripting in mediatomb

emerge dev-lang/spidermonkey

** configure, compile and install
./configure

should now produce the following output at the end

CONFIGURATION SUMMARY ----

sqlite3       : yes
mysql         : missing
libjs         : yes
libmagic      : yes
inotify       : missing
libexif       : yes
id3lib        : yes
taglib        : disabled
libextractor  : disabled

make
make install

** Startup MediaTomb

Startup using RJ45
/usr/local/bin/mediatomb -e br0

Startup using WiFi
/usr/local/bin/mediatomb -e br0:0

** Mount root filesystem

If you have installed Gentoo in a subfolder of your HD_a2 drive you have to mount it again in order to access the files on the root.
After you have chroot:ed into Gentoo do the following:

mkdir /mnt/root
mount /dev/sda2 /mnt/root

** Let MediaTomb start on boot

Place the following lines in the "fun_plug" file:

-----
# Mount Gentoo devices
mount -o bind /dev /mnt/HD_a2/gentoo/dev
mount -t proc none /mnt/HD_a2/gentoo/proc
/mnt/HD_a2/chroot /mnt/HD_a2/gentoo mount /dev/sda2 /mnt/root

# Start MediaTomb
/mnt/HD_a2/chroot /mnt/HD_a2/gentoo /usr/local/bin/mediatomb -e br0 > /var/log/mediatomb.log 2>&1 &
-----

Note: I had some trouble when letting the MediaTomb start as a daemon process using the "-d" switch(Getting defuct processes for some reason). That is why the last line starts MediaTomb in the background using the ampesand instead of "-d" switch. The root mediatomb process still gets parent pid set to 1 and does not die when the fun_plug script exits.

** Stop MediaTomb

Send the kill signal to the MediaTomb process identified by doing a "ps -ef | grep mediatomb". The process that has "ppid" set to 1 should be killed with the "kill <pid>" command.

** Configure UI port

In order to let the MediaTomb UI bind to the same port on each startup you have to add the following line to the config.xml file:
-----
...
<server>
  ...
  <port>8080</port>
...
-----

** Configure MediaTomb to run as non root

TODO! - my mediatomb process runs as root which is bad, I know :-(

** Error - startup

-----
terminate called after throwing an instance of 'StorageException'
terminate called recursively
-----

Solution: Create the database manually

-----
cd /usr/local/share/mediatomb/
cat sqlite3.sql | sqlite3 mediatomb.db
mv mediatomb.db /.mediatomb
-----

See http://wl500g.info/archive/index.php/t-8456.html

** Error - importing dirs

Getting lots of "could not be converted to new encoding: invalid character sequence!" when adding directories using he web UI

Modify the file/meta encoding in config.xml file:

-----
...
  <import ...>
    <filesystem-charset>ISO-8859-1</filesystem-charset>
    <metadata-charset>ISO-8859-1</metadata-charset>
...
-----