{"id":128,"date":"2008-09-03T21:48:55","date_gmt":"2008-09-04T02:48:55","guid":{"rendered":"https:\/\/lowtek.ca\/roo\/?p=128"},"modified":"2022-05-31T12:24:41","modified_gmt":"2022-05-31T16:24:41","slug":"installing-and-using-slimrio","status":"publish","type":"post","link":"https:\/\/lowtek.ca\/roo\/2008\/installing-and-using-slimrio\/","title":{"rendered":"Installing and Using SlimRIO"},"content":{"rendered":"

I’ve previously talked<\/a> about the SlimRIO<\/a> project, but I finally got around to actually getting it properly setup and installed in the playroom downstairs.\u00a0 I figure I should give back to the community and write up a short How-To article.<\/p>\n

\"\"<\/a><\/p>\n

<\/p>\n

I run a Linux based music server, but SlimRIO will also work if you wanted to use Windows to serve up music.\u00a0 I will focus on Linux issues here, more specifically Ubuntu (Debian) configuration.\u00a0 There will also be some amount of hand waving that occurs, I’m going to assume you can figure out some of the details yourself.\u00a0 The SlimRIO website does cover Linux installation<\/a> and configuration.\u00a0 I’m actually using SlimServer<\/a> still as I haven’t upgraded to SqueezeCenter<\/a> yet.<\/p>\n

The first hurdle you might stumble on is getting the DHCP server to offer up an IP address.\u00a0 This will vary depending on your setup, but in my case my DHCP server is handled by my Linksys WRTGL<\/a> router running DD-WRT<\/a>.\u00a0 If you’ve got a compatible router, I strongly recommend considering using DD-WRT.\u00a0 Under the Adminstration->Services tab you can define a list of static leases that map MAC addresses to names and IPs.\u00a0 It’s really nice to talk to all of the devices on the home network by name – instead of trying to remember the IP address.\u00a0 [ok, so this probably wasn’t terribly helpful but there are lots of how-to documents on Linux DHCP servers<\/a>]<\/p>\n

Initially just run the Python based SSDP<\/a> server.\u00a0 I found that on Linux the auto-detection of the host machines IP address didn’t work, so to be safe I recommend passing the numeric IP address (ie: 192.168.1.12) of your NFS file server.\u00a0 Later I’ll talk about using the C version and growing an \/etc\/init.d script for Debian based systems.<\/p>\n

The next tricky part will be getting an NFS server configured.\u00a0 This is where the name (or IP) address you’ve assigned to the RIO will matter.\u00a0 I ended up using WireShark<\/a> to sniff traffic to determine what was going wrong, it may be something you want to consider available to help diagnose problems.\u00a0 When the device boots it first gets an IP, the DHCP server tells the RIO what its hostname will be.\u00a0 The SSDP “response” tells it where the NFS server lives.\u00a0 The boot firmware then tries to mount via NFS the \/tftpboot\/<rio hostname> directory to get the rest of the firmware.\u00a0 Jeff Mock hosts the original investigation<\/a> into the RIO boot sequence.<\/p>\n

Assuming all things are configured correctly, it will just work.\u00a0 Of course you’ll have problems, but that’s where WireShark will be a life saver in pointing out what you did wrong.\u00a0 Another good place to look is the system logs on your Linux machine.<\/p>\n

Now let’s make it slick and build an init.d script to start the SSDP server.\u00a0 This was the first time I had created one of these, so my solution may be naive – and I know that I took the long road to the solution I ended up with.\u00a0 The Debian policy manual<\/a> covers init.d scripts in section 9.3, I initially found 9.3.5<\/a> that talked about the provided skeleton implementation.\u00a0 I then hacked this up to build my own init.d script for SSDP<\/a>.\u00a0 The man page for the start-stop-daemon<\/a> was very helpful in doing this.<\/p>\n

Most of the implementation should be obvious as it is primarily directly from the skeleton.\u00a0 The only real work is in the start function:<\/p>\n

#
\n#\u00a0\u00a0\u00a0 Function that starts the daemon\/service.
\n#
\nd_start() {
\nstart-stop-daemon –start –quiet –pidfile $PIDFILE \\
\n–exec $DAEMON –background –make-pidfile \\
\n— 192.168.1.12 \\
\n|| echo -n ” already running”
\n}<\/span><\/p>\n

I’ve added the –background flag as the C version of SSDP is not a daemon and would never return control to the calling program.\u00a0 The –make-pidfile instructs the start-stop-daemon to manage the pidfile for us instead of assuming the ssdp program will do so.\u00a0 The final — followed by the IP address of the NFS server is an argument to be passed to the ssdp executable.\u00a0 This script was installed as \/etc\/init.d\/ssdp and now works as expected providing start, stop and restart.<\/p>\n

The ssdp program was compiled from the C source available from the SlimRIO site<\/a>. I installed it in \/usr\/local\/bin and used chown to assign it to the slimserver user and group, then chmod +s to run the program setuid<\/a> as a nod towards security (this causes it to run as the slimserver user).<\/p>\n

Have the SSDP server automatically started at boot time is trivial.\u00a0 I originally found an article<\/a> on how to do it in Ubuntu, but it was also<\/a> in the Debian policy manual had I read it more carefully. (sometimes search engines make you stupid)<\/p>\n

The SlimRIO firmware emulates a SliMP3<\/a> device which isn’t capable of some of the fancy (now standard) screen savers and visualizers, this isn’t a big deal for me.\u00a0 Also, in my setup it seemed that my MP3s were stored in a higher bitrate than it could easily handle without pauses. This is easily solved through a simple configuration in Slimserver under Player Settings->Audio – you can configure the bitrate limiting (default is no limit) which causes the music to be re-encoded on the fly, I found 128kbps to work fine.<\/p>\n

As always, I get a kick out of “hacking” consumer electronics.\u00a0 Its is also nice to take something that was gathering dust and put it to good use.<\/p>\n","protected":false},"excerpt":{"rendered":"

I’ve previously talked about the SlimRIO project, but I finally got around to actually getting it properly setup and installed in the playroom downstairs.\u00a0 I figure I should give back to the community and write up a short How-To article.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,11,12],"tags":[],"class_list":["post-128","post","type-post","status-publish","format-standard","hentry","category-computing","category-gadgets","category-how-to"],"_links":{"self":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/128","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/comments?post=128"}],"version-history":[{"count":3,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/128\/revisions"}],"predecessor-version":[{"id":2050,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/128\/revisions\/2050"}],"wp:attachment":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/media?parent=128"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/categories?post=128"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/tags?post=128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}