Category Archives: Sonstiges

Komg Mod – DLNA Media Server Setup

I’m going to explain in a few simple steps how to setup a Streaming Media Server using my dd-wrt build with integrated MiniDLNA.

1. Enabling USB Storage Support

usb.png

click to enlarge

There is not much to say here except. In my case I choose /jffs as mountpoint. JFFS is the prefered moint in case you want to make use of the jffs filesystem which is used to prevent excessive wear from flash cells. The mountpoint /opt is used whenever you want to use optware packages. Optware packages include a install script that usually install „optware“packages in the directory /opt, dd-wrt checks the location /opt for apps, scripts etc, that’s how optware basically works.

With the latest builds usb media will also be automatically mounted to the mointpoint /mnt. So if you leave everything empty you should find the contents of your drives partitions under /mnt/disc<x>_part<y> where x is the disc number and y is the partition number. Thus if you have  a single drives with 2 partitions attached. They will be automatically mounted to:

/mnt/disc0_part1

/mnt/disc0_part2

2. Enable DLNA Server

minidlna.png

click to enlarge

No it is time to enable the DLNA Server. Fill in the neccessary information for minidlna by specifying  the Server Identification. This is the string that will later be displayed by your media clients.

Now enter the directories. As noted earlier  I told dd-wrt to moint my partition, that contains the videos, to /jffs. I placed my videos in a directory share/video, since the partition was mounted to /jffs the full path to my videos is /jffs/share/video. If you remove this drive and attach it to windows  you would find the files for example under  D:\share\video. Same applies to pictures etc.

Now you can specify an update intervall. In my case I set it to 240s. So when I copy a new video to the router e.g. via samba share it will take up 240s until this new files is added to minidlnas database, and until the client sees it. Normally you can leave this field empty, since the default value should be fine.

A more important setting is the DB Path . The db path is the place where minidlna stores the index database. The default is to store it in /tmp directory which means it is purely inside the routers ram. Now if you have lots of media files this db can get very big and consume several megabytes, the consequence of that is that you run out of ram on the router and the router will be slowed down. In extreme cases the router will not be able to handle new connections etc. My advice, if you have more then 500 files in those directories store the db somewhere on the external media.

3. Start your client and check it is working. E.g. Windows 7 Media Player

FAQ:

1) How do I know minidlna is running?

Check „Status->Sysinfo“ under Services you will find the status of minidlna

2) How long does it take to index the directories

This depends on the amount of files. A rough guess 1min for 500 files.

3) How can I debug minidlna

Logon to the router e.g ssh and make sure minidlna is stopped, e.g. killall minidlna. Now start minidlna in debug mode:   /usr/sbin/minidlna -R -d -f /tmp/minidlna.conf

e.location.getItemLocation(e.id) has no properties – nach Firefox Update

Nach Aktualisierung auf Firefox 2.0.8 musste ich heute feststellen, dass sämtliche Extensions inaktiv waren. Ein Versuch eine der Extensions via Extension Manager zu löschen schlug fehl.

Letztendlich konnte ich den Fehler lokalisieren. Es lag an einem Extension Eintrag der auf eine nicht mehr vorhandene Extension zeigte. Zum Entfernen dieses Eintrags habe ich einfach die entsprechende Zeile in extensions.cache und localstore.rdf entfernt. Anschließend wurden sämtliche Extensions wieder geladen.

[Update]

Dieses Problem könnte evtl mit folgenden Bug zusammenhängen.

Blog Start

Ab sofort kann man hier Tips & Tricks aus meiner täglichen Arbeit nachlesen:-)