Reply To: Problems with Firefly on Diskstation 207+ – for Soundbridge

FireFly Media Server Firefly Media Server Forums Firefly Media Server Setup Issues Problems with Firefly on Diskstation 207+ – for Soundbridge Reply To: Problems with Firefly on Diskstation 207+ – for Soundbridge

#17049
ul206585
Guest

When we put it on the wiki, might be good to show all the threads:

1 RSP/Roku/Pinnacle Discussion and installation (Pinnacle does not support rsp)
http://forums.fireflymediaserver.org/viewtopic.php?t=7768&start=0&postdays=0&postorder=asc&highlight=

2 Nightly/1586 discussion on NSLU2 (arm, too) (Arm version supporting RSP)
http://www.nslu2-linux.org/wiki/Optware/Mt-daapd?from=Unslung.Mt-daapd

3 Firefly installation on Synology in General (using ipkg)
http://www.synology.com/wiki/index.php/Compiled_programs_for_Power_PC_CPU_based_Synology_Products

4 Firefly installation on arm-based synology (using tar)
http://www.synology.com/wiki/index.php/Compiled_programs_for_Marvell_mv5281_ARM-based_Synology_Products#Firefly.2FMt-daapd_by_Mike

5 Firefly on Synology DS-207+ (using tar too, very similar to 4)
http://forums.fireflymediaserver.org/viewtopic.php?t=7793&start=0&postdays=0&postorder=asc&highlight=

I found that both routes above lead to the same result (i.e. use 3 with an arm package, and use 4 or 5 – 5 is a much more detailed and clear version of 4), I find the route 3 a bit leaner.

In rjcris posting in 5, there are a few typos, might be helpful to point out!

– in step 13, I did not have to remove the mt-daapd files, these we untarred into the correct location

– in step 17, the script is called firefly, not S99… so the copy command is
cp /opt/local/mt-daapd/mt-daapd/etc/firefly /usr/syno/etc/rc.d/S99firerfly.sh
.. and purists might also call the final file S99firefly.sh (without r …)

My currently installed version is
– use the process of 3 with the file proposed in 2. Yet, I still have to resolve the RSP issue, i.e. my pinnacle M1001 does not talk to the synology firefly (“incpompatible music servers found”). This should not be an issue with the Roku branded version, which should run just by using route 3 with the latest arm 16xx build.

– with approach 4 and 5, telnet was deactivated after the reboot, but this can be fixed with the telnet disable/enable patch on
http://www.synology.com/enu/support/download.php#DS207+
You have to first disable and then enable telnet to get it back to work.

Happy fireflying!

And any tips on how to cope with the rsp issue are highly welcome!