NSLU2-Linux
view · edit · print · history

Applications.SlimServer History

Hide minor edits - Show changes to markup

October 26, 2008, at 03:26 PM by Paul Brandt --
Changed lines 50-51 from:
  • Issue found: the SqueezeBox? spontaneously reboots itself very frequently. This issue has nothing to do with the NSLU and is resolved by downgrading the firmware of the SqueezeBox? to version 64; versions above 64 seem to introduce this issue. Refer to the slimserver fora, especially the one describing the issue: http://forums.slimdevices.com/showthread.php?t=35054
to:
  • Issue found: the SqueezeBox? spontaneously reboots itself very frequently. This issue has nothing to do with the NSLU and is resolved by downgrading the firmware of the SqueezeBox? to version 64; versions above 64 seem to introduce this issue. Refer to the slimserver fora, especially the one describing the issue: http://forums.slimdevices.com/showthread.php?t=35054 . Firmware version 64 seems to work fine with slimserver release 6.5.4
October 26, 2008, at 03:24 PM by Paul Brandt -- Added SqueezeBox issue about spontaneous reboot
Changed lines 47-49 from:
  • In conclusion: I have slimserver (6.5.4) up and running from my slug, serving a SqueezeBox? in the living room about up to 10,000 songs. Performance wise, there is a penalty due to the 32MB available memory and the high memory footprint of slimserver. Still streaming is not a big deal, it's controlling the device. Have patience and you'll be fine. The "lazysearch" plugin is reasonably "fast" and hence very useful. The homepage (http://yourslug:9000) is slow, but the good thing is you don't need to access it too often, only for configuration. Browsing your music library can be done far more easy with Moose -- especially since it's quicker. The Weather screensaver is a nice add-on, providing me with quite accurate forecasts whenever the music is off. In short, it's operating correctly, I like the minimalistic approach, and still am training my patience.
to:
  • In conclusion: I have slimserver (6.5.4) up and running from my slug, serving a SqueezeBox? in the living room about up to 10,000 songs. Performance wise, there is a penalty due to the 32MB available memory and the high memory footprint of slimserver. Still streaming is not a big deal, though controlling the device is bit cumbersome. Have patience and you'll be fine. The "lazysearch" plugin is reasonably "fast" and hence very useful. The homepage (http://yourslug:9000) is slow, but the good thing is you don't need to access it too often, only for configuration. Browsing your music library can be done far more easy with Moose -- especially since it's quicker. The Weather screensaver is a nice add-on, providing me with quite accurate forecasts whenever the music is off. In short, it's operating correctly, I like the minimalistic approach, and still am training my patience.

Edit by PaulBrandt?, October 26th 2008:

  • Issue found: the SqueezeBox? spontaneously reboots itself very frequently. This issue has nothing to do with the NSLU and is resolved by downgrading the firmware of the SqueezeBox? to version 64; versions above 64 seem to introduce this issue. Refer to the slimserver fora, especially the one describing the issue: http://forums.slimdevices.com/showthread.php?t=35054
September 16, 2008, at 03:44 PM by PaulBrandt --
Changed lines 45-48 from:
 * Slimserver now IS able to scan the music directory. Whenever I add music to the directory, I issue a "chown -R guest.slimserver ./*" followed by a "chmod -R ugo+r ./*" . This resolves the issue.
 * Following S.E.'s suggestion to comment out various instances related to "AutoCommit?", the error messages related to "transactions not supported / failed to update isScanning" have disappeared. Note that this is also reduces functionality, although I'm not sure what functionality in particular.
 * In conclusion: I have slimserver (6.5.4) up and running from my slug, serving a SqueezeBox? in the living room about up to 10,000 songs. Performance wise, there is a penalty due to the 32MB available memory and the high memory footprint of slimserver. Still streaming is not a big deal, it's controlling the device. Have patience and you'll be fine. The "lazysearch" plugin is reasonably "fast" and hence very useful. The homepage (http://yourslug:9000) is slow, but the good thing is you don't need to access it too often, only for configuration. Browsing your music library can be done far more easy with Moose -- especially since it's quicker. The Weather screensaver is a nice add-on, providing me with quite accurate forecasts whenever the music is off. In short, it's operating correctly, I like the minimalistic approach, and still am training my patience. 
to:
  • Slimserver now IS able to scan the music directory. Whenever I add music to the directory, I issue a "chown -R guest.slimserver ./*" followed by a "chmod -R ugo+r ./*" . This resolves the issue.
  • Following S.E.'s suggestion to comment out various instances related to "AutoCommit?", the error messages related to "transactions not supported / failed to update isScanning" have disappeared. Note that this is also reduces functionality, although I'm not sure what functionality in particular.
  • In conclusion: I have slimserver (6.5.4) up and running from my slug, serving a SqueezeBox? in the living room about up to 10,000 songs. Performance wise, there is a penalty due to the 32MB available memory and the high memory footprint of slimserver. Still streaming is not a big deal, it's controlling the device. Have patience and you'll be fine. The "lazysearch" plugin is reasonably "fast" and hence very useful. The homepage (http://yourslug:9000) is slow, but the good thing is you don't need to access it too often, only for configuration. Browsing your music library can be done far more easy with Moose -- especially since it's quicker. The Weather screensaver is a nice add-on, providing me with quite accurate forecasts whenever the music is off. In short, it's operating correctly, I like the minimalistic approach, and still am training my patience.
September 16, 2008, at 03:43 PM by PaulBrandt --
Deleted lines 16-17:

[Edit by PaulBrandt?, September 19th, 2008: Slimserver now IS able to scan the music directory. Whenever I add music to the directory, I issue a "chown -R guest.slimserver ./*" followed by a "chmod -R ugo+r ./*" . This resolves the issue.]

Added lines 43-48:

Edit by PaulBrandt?, September 19th, 2008:

 * Slimserver now IS able to scan the music directory. Whenever I add music to the directory, I issue a "chown -R guest.slimserver ./*" followed by a "chmod -R ugo+r ./*" . This resolves the issue.
 * Following S.E.'s suggestion to comment out various instances related to "AutoCommit?", the error messages related to "transactions not supported / failed to update isScanning" have disappeared. Note that this is also reduces functionality, although I'm not sure what functionality in particular.
 * In conclusion: I have slimserver (6.5.4) up and running from my slug, serving a SqueezeBox? in the living room about up to 10,000 songs. Performance wise, there is a penalty due to the 32MB available memory and the high memory footprint of slimserver. Still streaming is not a big deal, it's controlling the device. Have patience and you'll be fine. The "lazysearch" plugin is reasonably "fast" and hence very useful. The homepage (http://yourslug:9000) is slow, but the good thing is you don't need to access it too often, only for configuration. Browsing your music library can be done far more easy with Moose -- especially since it's quicker. The Weather screensaver is a nice add-on, providing me with quite accurate forecasts whenever the music is off. In short, it's operating correctly, I like the minimalistic approach, and still am training my patience. 
September 16, 2008, at 03:26 PM by PaulBrandt --
Added lines 17-18:

[Edit by PaulBrandt?, September 19th, 2008: Slimserver now IS able to scan the music directory. Whenever I add music to the directory, I issue a "chown -R guest.slimserver ./*" followed by a "chmod -R ugo+r ./*" . This resolves the issue.]

May 27, 2008, at 12:12 PM by Graham White -- Added section with comments from Graham White
Changed lines 70-77 from:
to:

With thanks to Ben's information above and a few other snippets from around the web I got SqueezeCenter? 7.0.1 running on my SLUG. It's non-trivial and a maintenance nightmare, resulting in a very slow performing SqueezeCenter?. Due to the increased memory requirements the SLUG spends a lot of time paging!

I'm going to write some more detailed information over the next few days on my blog (http://gibbalog.blogspot.com/) of my experience getting this lot up and running. However, in brief I cross-compiled a new version of MySQL using the SLUG toolchain from Optware to make a previously known-working ipkg; Squeeze Center also has some new requirements above slimserver 6.5.4 for various Perl module that I've installed to my SLUG too.

Graham White on 27th May 2008.

May 26, 2008, at 10:58 AM by SE --
Changed lines 39-40 from:

to:
Added lines 43-44:

Changed line 55 from:

S.E. - 2008-05-26

to:

-- S.E, May 26th 2008

May 26, 2008, at 10:57 AM by SE --
Changed lines 39-40 from:
to:

May 26, 2008, at 10:56 AM by SE -- answered paul brandt\\\\
Changed lines 43-57 from:

BenMcDui 20080508:

to:

/opt/share/slimserver/scanner.pl line 137 -> add # to lines 137 (and following) ones (everything related to function "AutoCommit?")

/opt/share/slimserver/CPAN/DBI.pm line 1657 -> add # to lines 1657 and following ones (everything related to function "AutoCommit?")

Now "slimserver stop" and "slimserver start".

Possibly an additional error in playlist.pm will show up, then do the same as above.

This worked for me.

S.E. - 2008-05-26


BenMcDui? 20080508:

May 08, 2008, at 07:06 PM by BenMcDui -- small edit to my previous entry
Changed lines 44-45 from:

When trying to get Slimserver 6.4.1 installed following the instruction lower on this page, I got the two warnings:

to:

When trying to get Slimserver 6.5.1-1 installed following the instruction further down this page, I get the same two warnings:

Changed lines 50-51 from:

I noticed that, contrary to the machine on which I have Slimserver running since a few months, mysql has upgraded from 4.1.20 to 4.1.22. It's the only difference I have been able to find so far. You get 4.1.22 automatically when you do # install mysql. Unfortunately, it is not possible to find mysql 4.1.20 anymore on the web....

to:

I noticed that, since I successfully installed Slimserver on my other slug a few months ago, mysql has upgraded from 4.1.20 to 4.1.22. It's the only difference I have been able to find so far. You get mysql 4.1.22 automatically when you do # ipkg install mysql. Unfortunately, it is not possible to find mysql 4.1.20 anymore on the web....

Added line 54:
May 08, 2008, at 07:02 PM by BenMcDui -- fwe edits tpmy previous entry
Changed lines 48-50 from:

I noticed that, contrary to the machine on which I have Slimserver running since a few months, mysql has upgraded from 4.1.20 to 4.1.22. It's the only difference I have been able to find so far. Unfortunately, it is not possible to find mysql 4.1.20 anymore on the web....

to:

@]

I noticed that, contrary to the machine on which I have Slimserver running since a few months, mysql has upgraded from 4.1.20 to 4.1.22. It's the only difference I have been able to find so far. You get 4.1.22 automatically when you do # install mysql. Unfortunately, it is not possible to find mysql 4.1.20 anymore on the web....

Can someone with more understanding of mysql please expore this issue?

May 08, 2008, at 06:59 PM by BenMcDui -- Comment added to \"This guide needs update\"
Added lines 43-50:

BenMcDui 20080508: When trying to get Slimserver 6.4.1 installed following the instruction lower on this page, I got the two warnings:

[@Transactions not supported by database at /opt/share/slimserver/scanner.pl line 137. ERROR: Scanner: Failed to update isScanning: [Transactions not supported by database at /opt/share/slimserver/CPAN/DBI.pm line 1657.]

I noticed that, contrary to the machine on which I have Slimserver running since a few months, mysql has upgraded from 4.1.20 to 4.1.22. It's the only difference I have been able to find so far. Unfortunately, it is not possible to find mysql 4.1.20 anymore on the web....

May 05, 2008, at 10:59 AM by PaulBrandt -- additional info on issue with 6.5.4 optware package
Changed lines 10-11 from:
  • I didn't create a new user for slimserver to act upon.
to:
  • I didn't create a new user manually (user 'slim') for slimserver to act upon; apparently the install took care of that since my /etc/passwd now provides for a user 'slimserver': slimserver:x:1000:1:Linux User,,,:/home/slimserver:/dev/null
Changed lines 14-16 from:
  • I've got multiple MySQL instances running. As suggested in SlimServerOld I removed S70mysqld & K70msqld from init.d which both linked to ../../share/mysql/mysql.se -- This didn't seem to change anything
  • server is unable to scan the music directory (chmod -R 777 didn't do the trick), although it can play individual directories if you select one via the (soft) Squeezebox. Slimserver's log tells me, a.o.:
to:
  • I've got multiple MySQL instances running. As suggested in SlimServerOld I removed S70mysqld & K70msqld from init.d which both linked to ../../share/mysql/mysql.se -- This didn't seem to change anything from a functional perspective, although now a triplet of /opt/share/slimserver/Bin/mysql instances are running, and no other ones. I assume this actually relates to one instance.
  • server is unable to scan the music directory (chmod -R 777 didn't do the trick, neither a chown slimserver), although it can play individual directories if you browse it and select one via the (soft) Squeezebox.

Slimserver's log provides me, a.o., with the following message that is being generated during start of slimserver deamon:

Changed lines 30-35 from:

080426 9:18:52 [Warning] this binary does not contain INNODB storage engine

Transactions not supported by database at /opt/share/slimserver/scanner.pl line 137. ERROR: Scanner: Failed to update isScanning: [Transactions not supported by database at /opt/share/slimserver/CPAN/DBI.pm line 1657.] @]

to:

080426 9:18:52 [Warning] this binary does not contain INNODB storage engine@]

Added lines 33-39:

The following log message is being generated when trying to scan the music directory:

Transactions not supported by database at /opt/share/slimserver/scanner.pl line 137.
ERROR: Scanner: Failed to update isScanning: [Transactions not supported by database at /opt/share/slimserver/CPAN/DBI.pm line 1657.]
May 01, 2008, at 01:49 PM by PaulBrandt --
Added lines 29-31:

Transactions not supported by database at /opt/share/slimserver/scanner.pl line 137. ERROR: Scanner: Failed to update isScanning: [Transactions not supported by database at /opt/share/slimserver/CPAN/DBI.pm line 1657.]

Changed lines 34-35 from:

and indeed, /opt/share/slimserver/CPAN/arch/5.8.8/armv5b-softfloat-linux/auto/Compress/Zlib/ does not contain autosplit.ix

to:

and indeed, inspection confirms that /opt/share/slimserver/CPAN/arch/5.8.8/armv5b-softfloat-linux/auto/Compress/Zlib/ does not contain autosplit.ix

April 27, 2008, at 02:49 PM by PaulBrandt --
Changed lines 31-32 from:
to:

and indeed, /opt/share/slimserver/CPAN/arch/5.8.8/armv5b-softfloat-linux/auto/Compress/Zlib/ does not contain autosplit.ix

April 27, 2008, at 01:12 PM by PaulBrandt --
Changed lines 8-9 from:
  • Failed to sucessfully issue /opt/bin/mysqladmin -u root -h BS06 password 'new-password'
to:
  • Failed to sucessfully issue /opt/bin/mysqladmin -u root -h the_name_of_my_slug password 'new-password'. Error message:
    /opt/bin/mysqladmin: connect to server at the_name_of_my_slug failed
    error: 'lost connection to MySQL server during query'
April 27, 2008, at 01:05 PM by PaulBrandt --
Changed lines 6-10 from:
 * package installs, asks for a slimserver home directory
 * Issued successfully command /opt/bin/mysqladmin -u root password 'new-password' 
 * Failed to sucessfully issue /opt/bin/mysqladmin -u root -h BS06 password 'new-password'
 * I didn't create a new user for slimserver to act upon.
to:
  • package installs, asks for a slimserver home directory
  • Issued successfully command /opt/bin/mysqladmin -u root password 'new-password'
  • Failed to sucessfully issue /opt/bin/mysqladmin -u root -h BS06 password 'new-password'
  • I didn't create a new user for slimserver to act upon.
Changed lines 12-13 from:
 * slimserver runs successfully: Soft Squeezebox can connect, home page (my-slug-url:9000) is accessible.
 * server is unable to scan the music directory (chmod -R 777 didn't do the trick), although it can play individual directories if you select one via the (soft) Squeezebox. Slimserver's log tells me, a.o.:
to:
  • slimserver runs successfully: Soft Squeezebox can connect, home page (my-slug-url:9000) is accessible.
  • I've got multiple MySQL instances running. As suggested in SlimServerOld I removed S70mysqld & K70msqld from init.d which both linked to ../../share/mysql/mysql.se -- This didn't seem to change anything
  • server is unable to scan the music directory (chmod -R 777 didn't do the trick), although it can play individual directories if you select one via the (soft) Squeezebox. Slimserver's log tells me, a.o.:
Changed lines 29-30 from:
 * I've got multiple MySQL instances running. As suggested in SlimServerOld I removed S70mysqld & K70msqld from init.d which both linked to ../../share/mysql/mysql.se
to:
April 27, 2008, at 07:50 AM by PaulBrandt --
Changed lines 14-23 from:

[@Can't locate auto/Compress/Zlib/autosplit.ix in @INC (@INC contains: /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux/auto /opt/share/slimserver/CPAN/arch/5.8.8/armv5b-softfloat-linux /opt/share/slimserver/CPAN/arch/5.8.8/armv5b-softfloat-linux/auto /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux/auto /opt/share/slimserver/CPAN/arch/armv5b-softfloat-linux /opt/share/slimserver/lib /opt/share/slimserver/CPAN /opt/share/slimserver /opt/share/slimserver /opt/lib/perl5/5.8.8/armv5b-linux /opt/lib/perl5/5.8.8 /opt/lib/perl5/site_perl/5.8.8/armv5b-linux /opt/lib/perl5/site_perl/5.8.8 /opt/lib/perl5/site_perl .) at /opt/lib/perl5/5.8.8/AutoLoader?.pm line 160.

to:

[@Can't locate auto/Compress/Zlib/autosplit.ix in @INC (@INC contains:

 /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux
 /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux/auto
 /opt/share/slimserver/CPAN/arch/5.8.8/armv5b-softfloat-linux
 /opt/share/slimserver/CPAN/arch/5.8.8/armv5b-softfloat-linux/auto
 /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux/auto
 /opt/share/slimserver/CPAN/arch/armv5b-softfloat-linux /opt/share/slimserver/lib /opt/share/slimserver/CPAN
 /opt/share/slimserver /opt/share/slimserver /opt/lib/perl5/5.8.8/armv5b-linux /opt/lib/perl5/5.8.8
 /opt/lib/perl5/site_perl/5.8.8/armv5b-linux /opt/lib/perl5/site_perl/5.8.8 /opt/lib/perl5/site_perl .) at
 /opt/lib/perl5/5.8.8/AutoLoader?.pm line 160.
April 27, 2008, at 07:48 AM by PaulBrandt -- Results for slimserver 6.5.4 optware install
Added lines 5-22:

I´ve installed slimserver 6.5.4 using the optware package (ipkg install slimserver). The result was hopefull, yet not completely succesful:

 * package installs, asks for a slimserver home directory
 * Issued successfully command /opt/bin/mysqladmin -u root password 'new-password' 
 * Failed to sucessfully issue /opt/bin/mysqladmin -u root -h BS06 password 'new-password'
 * I didn't create a new user for slimserver to act upon.

Result:

 * slimserver runs successfully: Soft Squeezebox can connect, home page (my-slug-url:9000) is accessible.
 * server is unable to scan the music directory (chmod -R 777 didn't do the trick), although it can play individual directories if you select one via the (soft) Squeezebox. Slimserver's log tells me, a.o.:
Can't locate auto/Compress/Zlib/autosplit.ix in @INC (@INC contains: /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux/auto /opt/share/slimserver/CPAN/arch/5.8.8/armv5b-softfloat-linux /opt/share/slimserver/CPAN/arch/5.8.8/armv5b-softfloat-linux/auto /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux /opt/share/slimserver/CPAN/arch/5.8/armv5b-softfloat-linux/auto /opt/share/slimserver/CPAN/arch/armv5b-softfloat-linux /opt/share/slimserver/lib /opt/share/slimserver/CPAN /opt/share/slimserver /opt/share/slimserver /opt/lib/perl5/5.8.8/armv5b-linux /opt/lib/perl5/5.8.8 /opt/lib/perl5/site_perl/5.8.8/armv5b-linux /opt/lib/perl5/site_perl/5.8.8 /opt/lib/perl5/site_perl .) at /opt/lib/perl5/5.8.8/AutoLoader.pm line 160.
 at /opt/share/slimserver/CPAN/Compress/Zlib.pm line 15
080426  9:18:52 [Warning] this binary does not contain INNODB storage engine
 * I've got multiple MySQL instances running. As suggested in SlimServerOld I removed S70mysqld & K70msqld from init.d which both linked to ../../share/mysql/mysql.se

Any suggestions? -- PaulBrandt?, April 27th 2008

April 19, 2008, at 01:39 PM by Robert Witjes --
Changed lines 1-2 from:

Can some experts update the documentation for about installing slimserver on a NSLU2. Although i tried a few times installing via the procedure mentioned below, i didn't succeed in it. With the old installation procedure (for slimserver r6.3 and older) i didn''t succed as either. I am a rookie for about linux. Thanks in advance

to:

Can some experts update the documentation for about installing slimserver on a NSLU2. Although i tried a few times installing via the procedure mentioned below, i didn't succeed in it. With the old installation procedure (for slimserver r6.3 and older) i didn''t succeed either. I am a rookie for about linux. Feel free to click on edit and modify this discription. Thanks in advance

April 19, 2008, at 07:45 AM by Robert Witjes -- Request for update
Added lines 1-2:

Can some experts update the documentation for about installing slimserver on a NSLU2. Although i tried a few times installing via the procedure mentioned below, i didn't succeed in it. With the old installation procedure (for slimserver r6.3 and older) i didn''t succed as either. I am a rookie for about linux. Thanks in advance

April 02, 2008, at 08:08 AM by BenMcDui --
Changed lines 287-291 from:

FOLLOWING THREE LINES CORRECTED by author on 20080402: Slimserver expects a copy of the mysqld executable to be in the /opt/share/ss65/Bin, and you can solve this by:

 # mkdir opt/share/ss65/Bin
 # cp opt/libexec/mysqld /opt/share/ss65/Bin/
to:

FOLLOWING THREE LINES CORRECTED by author on 20080402:

Slimserver expects a copy of the mysqld executable in /opt/share/ss65/Bin, and you can solve this by:

 # mkdir /opt/share/ss65/Bin
 # cp /opt/libexec/mysqld /opt/share/ss65/Bin/
April 02, 2008, at 08:05 AM by BenMcDui --
Changed lines 286-287 from:

FOLLOWING LINES CORRECTION by author on 20080402:

to:

FOLLOWING THREE LINES CORRECTED by author on 20080402:

April 02, 2008, at 08:04 AM by BenMcDui -- streamlined my earlier mod. Responded to complaint below it.
Changed lines 285-287 from:

in slimserver.log. Slimserver expects a copy of the mysqld executable to be in the /opt/share/ss65/server/Bin, and you can solve this by:

 # cp opt/libexec/mysqld /opt/share/ss65/server/Bin/

CORRECTION by author on 20080402: mysqld must be in /opt/share/ss65/Bin/. Hence, the recommended commands are:

to:

in slimserver.log. FOLLOWING LINES CORRECTION by author on 20080402: Slimserver expects a copy of the mysqld executable to be in the /opt/share/ss65/Bin, and you can solve this by:

Changed lines 303-304 from:
to:

Response by BenMcDui? 20080402: apologies for the mistake; see my correction above, the modification of the bootup script would then not be needed.

April 02, 2008, at 07:54 AM by BenMcDui -- added a correction to issue mysqld
Changed lines 287-290 from:
to:

CORRECTION by author on 20080402: mysqld must be in /opt/share/ss65/Bin/. Hence, the recommended commands are:

 # mkdir opt/share/ss65/Bin
 # cp opt/libexec/mysqld /opt/share/ss65/Bin/
February 24, 2008, at 07:47 PM by Alexander Ulanov --
Changed lines 93-94 from:

save && flashfs commit && flashfs enable

to:

flashfs save && flashfs commit && flashfs enable

February 21, 2008, at 01:10 PM by fcarolo -- removed false wikilinks
Changed lines 4-5 from:

Installing and running Slimserver on Asus WL500G? Premium

to:

Installing and running Slimserver on Asus WL500G Premium

Changed lines 28-29 from:

Format usb hdd drive using PQMagic? (I've used PQMagic? v.8). Make primary partition of type ext3 and linux swap partition (I've made 2Gb swap)

to:

Format usb hdd drive using PQMagic (I've used PQMagic v.8). Make primary partition of type ext3 and linux swap partition (I've made 2Gb swap)

Changed lines 56-57 from:

/dev/scsi/host0/bus0/target0/lun0/part6 12181 24321 97522551 b W95 FAT32?

to:

/dev/scsi/host0/bus0/target0/lun0/part6 12181 24321 97522551 b W95 FAT32

February 21, 2008, at 09:33 AM by Alexander Ulanov --
Changed line 87 from:

[@]

to:

[@

Changed lines 90-91 from:

[@]

to:

@]

February 21, 2008, at 09:32 AM by Alexander Ulanov --
Added lines 85-91:

Save group and password of a new slimserver user

]
echo "/etc/passwd" >> /usr/local/.files 
echo "/etc/group" >> /usr/local/.files 
[
February 19, 2008, at 01:51 PM by Alexander Ulanov --
February 19, 2008, at 01:50 PM by Alexander Ulanov --
Added line 110:
February 19, 2008, at 01:49 PM by Alexander Ulanov -- pic resize
Changed line 121 from:

http://img148.imageshack.us/img148/940/slimserver1ps5.jpg

to:

http://img100.imageshack.us/img100/3683/slimserver1resizetr4.jpg

February 18, 2008, at 01:32 PM by Alexander Ulanov --
Added lines 120-121:

http://img148.imageshack.us/img148/940/slimserver1ps5.jpg

February 18, 2008, at 01:31 PM by Alexander Ulanov --
Changed lines 8-10 from:

Given: Squeezebox 3, asus wl500g premium, 200Gb Toshiba harddisk + Vipower usb box Todo: install and run Slimserver on asus

to:

Given: Squeezebox 3, asus wl500g premium, 200Gb Toshiba harddisk + Vipower usb box

Todo: install and run Slimserver on asus

Added line 119:

A.Ulanov

February 18, 2008, at 01:26 PM by Alexander Ulanov --
Added line 96:
Added line 104:
Changed lines 110-111 from:

In "Settings" field choose "Server settings" and specify there "Music folder": !!!!!/tmp/harddisk/music

to:

In "Settings" field choose "Server settings" and specify there "Music folder": /tmp/harddisk/music

February 18, 2008, at 01:24 PM by Alexander Ulanov --
Changed lines 72-75 from:

Code:

swapon /dev/scsi/host0/bus0/target0/lun0/part5

to:

swapon /dev/scsi/host0/bus0/target0/lun0/part5

Changed lines 78-79 from:

Code:

to:

[@

Deleted line 79:
Deleted line 80:
Changed lines 82-84 from:

chmod +x /usr/local/sbin/post-mount

to:

chmod +x /usr/local/sbin/post-mount@]

Changed lines 85-89 from:

Code:

save && flashfs commit && flashfs enable

to:

save && flashfs commit && flashfs enable

Changed lines 91-92 from:

Code:

to:

[@

Changed line 93 from:
 IP Config | WAN & LAN: Host Name in LAN IP Setting “wl500g” 
to:
 IP Config | WAN & LAN: Host Name in LAN IP Setting "wl500"; 
Added line 95:

@]

Added line 97:
Changed line 100 from:

5. Starting slimserver:

to:

5. Starting slimserver:

Changed lines 102-104 from:

Code: /opt/etc/init.d/S99slimserver start After a while (about 2 minutes) you will see “Slimserver started” message

to:

/opt/etc/init.d/S99slimserver start After a while (about 2 minutes) you will see "Slimserver started" message

Changed lines 105-106 from:

Code: netstat -l

to:

netstat -l

Changed lines 108-111 from:

In “Settings” field choose “Server settings” and specify there “Music folder”: /tmp/harddisk/music 6. Connect Squeezebox to slimserver : Choose “Connect to Slimserver” on your Squeezebox and enter it’s IP address (my is 192.168.24.1) Then you will see “Connecting to slimserver…” message on Squeezebox. It takes about 1.5 minutes to connect first time.

to:

In "Settings" field choose "Server settings" and specify there "Music folder": !!!!!/tmp/harddisk/music

6. Connect Squeezebox to slimserver :

Choose "Connect to Slimserver" on your Squeezebox and enter it's IP address (my is 192.168.24.1) Then you will see "Connecting to slimserver" message on Squeezebox. It takes about 1.5 minutes to connect first time.

Changed line 115 from:

P.S.Praise to oleo who cross-compiled slimserver and made a package (my task was to configure and test it)

to:
P.S.Praise to oleo who cross-compiled slimserver and made a package (my task was to configure and test it)
February 18, 2008, at 01:22 PM by Alexander Ulanov --
Changed lines 40-41 from:

fdisk -l

to:

fdisk -l

Changed lines 59-60 from:

Code:

to:

[@

Deleted line 60:
Deleted line 61:
Deleted line 62:
Deleted line 63:
Deleted line 64:
Changed lines 66-68 from:

ipkg install slimserver

to:

ipkg install slimserver@]

February 18, 2008, at 01:21 PM by Alexander Ulanov --
Changed lines 36-37 from:

telnet 192.168.24.1

to:

telnet 192.168.24.1

February 18, 2008, at 01:18 PM by Alexander Ulanov --
Changed lines 26-29 from:

2. Formatting. Format usb hdd drive using PQMagic? (I've used PQMagic? v.8). Make primary partition of type ext3 and linux swap partition (I've made 2Gb swap)

3. HDD plugging. Connect usb hdd to asus using both usb plugs and make sure that is "started"; and isn't flicking

to:

2. Formatting.

Format usb hdd drive using PQMagic? (I've used PQMagic? v.8). Make primary partition of type ext3 and linux swap partition (I've made 2Gb swap)

3. HDD plugging.

Connect usb hdd to asus using both usb plugs and make sure that is "started"; and isn't flicking

Deleted line 44:
Deleted line 45:
Deleted line 46:
February 18, 2008, at 01:17 PM by Alexander Ulanov --
Changed lines 26-31 from:

2. Formatting. Format usb hdd drive using PQMagic? (I've used PQMagic? v.8). Make primary partition of type ext3 and linux swap partition (I've made 2Gb swap)

3. HDD plugging. Connect usb hdd to asus using both usb plugs and make sure that is "started"; and isn't flicking

4. Installing and configuring slimserver

to:

2. Formatting. Format usb hdd drive using PQMagic? (I've used PQMagic? v.8). Make primary partition of type ext3 and linux swap partition (I've made 2Gb swap)

3. HDD plugging. Connect usb hdd to asus using both usb plugs and make sure that is "started"; and isn't flicking

4. Installing and configuring slimserver

Added line 41:
Added line 43:
Added line 45:
Added line 49:
Added line 51:
Added line 53:
Added line 55:
Added line 59:
Added line 61:
Added line 63:
Added line 65:
Added line 67:
Added line 69:
Added line 71:
Added line 73:
Changed lines 75-77 from:

I’ve used the /opt/share/slimserver dir as the slimserver user dir

to:

I've used the /opt/share/slimserver dir as the slimserver user dir

Added line 79:
Added line 81:
Changed lines 83-87 from:

create and configure startup file /usr/local/sbin/post-mount (that is automatically started during router booting after it detects usb drives) to bind hdd root to /opt and to make swap after each reboot:

to:

create and configure startup file /usr/local/sbin/post-mount (that is automatically started during router booting after

it detects usb drives) to bind hdd root to /opt and to make swap after each reboot:

Added line 89:
Added line 91:
Added line 93:
Added line 95:
Added line 97:
Added line 99:
Added line 101:
Changed lines 103-105 from:

Make the dir “music” on usb hdd and make it accessible:

to:

Make the dir "music"; on usb hdd and make it accessible:

Added line 107:
Added line 109:
February 18, 2008, at 01:09 PM by Alexander Ulanov --
Changed line 11 from:

Pre.

to:

Pre.

Changed lines 23-24 from:

1. Firmware. Install Oleg's custom firmware from wl500g.dyndns.org (forum wl500g.info)

to:

1. Firmware.

Install Oleg's custom firmware from wl500g.dyndns.org (forum wl500g.info)

February 18, 2008, at 01:08 PM by Alexander Ulanov --
Changed line 11 from:

MiniF?/A/Q.

to:

Pre.

Added line 22:
February 18, 2008, at 01:07 PM by Alexander Ulanov --
Changed line 11 from:
to:

MiniF?/A/Q.

Added line 13:
Added line 15:
Added line 17:
Added line 20:
Added line 23:
Added line 25:
Added line 27:
Added line 29:
February 18, 2008, at 01:06 PM by Alexander Ulanov --
Changed line 12 from:

1. Slimserver is very heavy for asus wl500gp since it is php+mysql, but it works and is able to broadcast music continuously – only the reaction on commands is very slow. Now I'm trying to find minimalistic configuration.

to:

1. Slimserver is very heavy for asus wl500gp since it is php+mysql, but it works and is able to broadcast music continuously; only the reaction on commands is very slow. Now I'm trying to find minimalistic configuration.

Changed line 14 from:

3. Don’t forget to do “flashfs save && flashfs commit && flashfs enable” or all new programs will be lost after you restart router

to:

3. Don't forget to do "flashfs save && flashfs commit && flashfs enable"; or all new programs will be lost after you restart router

Changed lines 18-20 from:

1. Firmware. Install Oleg’s custom firmware from wl500g.dyndns.org (forum wl500g.info) 2. Formatting. Format usb hdd drive using PQMagic? (I’ve used PQMagic? v.8). Make primary partition of type ext3 and linux swap partition (I’ve made 2Gb swap) 3. HDD plugging. Connect usb hdd to asus using both usb plugs and make sure that is “started” and isn’t flicking

to:

1. Firmware. Install Oleg's custom firmware from wl500g.dyndns.org (forum wl500g.info) 2. Formatting. Format usb hdd drive using PQMagic? (I've used PQMagic? v.8). Make primary partition of type ext3 and linux swap partition (I've made 2Gb swap) 3. HDD plugging. Connect usb hdd to asus using both usb plugs and make sure that is "started"; and isn't flicking

Changed line 23 from:

Code:

to:
Added line 25:
Changed line 27 from:

Code:

to:
Added line 29:
February 18, 2008, at 01:04 PM by Alexander Ulanov -- Installing and running Slimserver on Asus WL500G Premium
Changed lines 4-87 from:
to:

Installing and running Slimserver on Asus WL500G? Premium

This guide was posted also on the corresponding forum http://forums.slimdevices.com/showthread.php?t=43593

Given: Squeezebox 3, asus wl500g premium, 200Gb Toshiba harddisk + Vipower usb box Todo: install and run Slimserver on asus

MiniFAQ?. 1. Slimserver is very heavy for asus wl500gp since it is php+mysql, but it works and is able to broadcast music continuously – only the reaction on commands is very slow. Now I'm trying to find minimalistic configuration. 2. Asus setup steps are good described at http://wl500g.info/showthread.php?p=60933 3. Don’t forget to do “flashfs save && flashfs commit && flashfs enable” or all new programs will be lost after you restart router 4.The address of my router is 192.168.24.1

Howto steps: 1. Firmware. Install Oleg’s custom firmware from wl500g.dyndns.org (forum wl500g.info) 2. Formatting. Format usb hdd drive using PQMagic? (I’ve used PQMagic? v.8). Make primary partition of type ext3 and linux swap partition (I’ve made 2Gb swap) 3. HDD plugging. Connect usb hdd to asus using both usb plugs and make sure that is “started” and isn’t flicking 4. Installing and configuring slimserver Connect to asus via telnet and enter your username/password (admin/admin) Code: telnet 192.168.24.1 make sure that asus sees all ext3 and swap partitions: Code: fdisk -l output: Disk /dev/scsi/host0/bus0/target0/lun0/disc: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System /dev/scsi/host0/bus0/target0/lun0/part1 1 11918 95731303+ 83 Linux /dev/scsi/host0/bus0/target0/lun0/part2 11919 24321 99627097+ f W95 Ext'd (LBA) /dev/scsi/host0/bus0/target0/lun0/part5 11919 12180 2104483+ 82 Linux swap / Solaris /dev/scsi/host0/bus0/target0/lun0/part6 12181 24321 97522551 b W95 FAT32?

update package installer and install slimserver (it will install additional packages such as mysql automatically): Code: mkdir /tmp/harddisk/opt mount -obind /tmp/harddisk/opt /opt mkdir -p /opt/tmp/ipkg ipkg.sh update ipkg.sh install ipkg-opt ipkg update ipkg install slimserver I’ve used the /opt/share/slimserver dir as the slimserver user dir make swap Code: swapon /dev/scsi/host0/bus0/target0/lun0/part5 create and configure startup file /usr/local/sbin/post-mount (that is automatically started during router booting after it detects usb drives) to bind hdd root to /opt and to make swap after each reboot: Code: echo "#!/bin/sh" >> /usr/local/sbin/post-mount echo "/bin/mount -o bind,sync,noatime,rw /tmp/harddisk/opt /opt" >> /usr/local/sbin/post-mount echo "swapon /dev/scsi/host0/bus0/target0/lun0/part5" >> /usr/local/sbin/post-mount chmod +x /usr/local/sbin/post-mount save all installed programs Code: save && flashfs commit && flashfs enable Make the dir “music” on usb hdd and make it accessible: In asus interface: Code: USB Application | Samba: "Enable Samba Demo mode" and "Enable hidden read-write share".

 IP Config | WAN & LAN: Host Name in LAN IP Setting “wl500g” 

Finish (Save&Reboot) Primary partition will be available for reading using \\wl500g\share and for writing \\wl500g\share$ Make dir music in \\wl500g\share$ and copy some mp3 files there (I recommend copy only one album at first since it will take a lot of time to scan a big collection)

5. Starting slimserver: Run slimserver Code: /opt/etc/init.d/S99slimserver start After a while (about 2 minutes) you will see “Slimserver started” message Check that slimserver is listening at port 9000 Code: netstat -l Slimserver is available at http://192.168.24.1:9000 (and http://wl500g:9000 also). Start it in your browser In “Settings” field choose “Server settings” and specify there “Music folder”: /tmp/harddisk/music 6. Connect Squeezebox to slimserver : Choose “Connect to Slimserver” on your Squeezebox and enter it’s IP address (my is 192.168.24.1) Then you will see “Connecting to slimserver…” message on Squeezebox. It takes about 1.5 minutes to connect first time. Then choose to play some music.

P.S.Praise to oleo who cross-compiled slimserver and made a package (my task was to configure and test it)


January 27, 2008, at 06:25 AM by BrianZhou -- slimserver in optware
Added lines 1-4:

The guide needs update, now that slimserver 6.5.4 is in optware.


December 27, 2007, at 08:21 PM by Me --
Changed line 160 from:

mysqld & boot not starting slimserver

to:

mysqld & boot not starting slimserver

December 27, 2007, at 08:20 PM by Me -- add link to MusicBrowser
Changed line 120 from:

SlugOS/BE issues

to:

SlugOS/BE issues

Changed lines 134-135 from:

innodb

to:

innodb

Changed lines 144-145 from:

mysqld

to:

mysqld

Changed lines 169-170 from:

Slimserver does not scan music

to:

Slimserver does not scan music

Added lines 174-177:

Slimserver is slow

Try running MusicBrowser in addition to slimserver. It can playback via the slimserver, but you won't have to use the heavy slimserver GUI.

December 21, 2007, at 01:05 AM by fenton travers --
Changed lines 160-161 from:
  • Note I didn't find that this resolved the problem for the on boot process. I needed to change the bootup script to look like:
to:

mysqld & boot not starting slimserver

Note I didn't find that this resolved the problem for the on boot process. I needed to change the bootup script in step 12 to look like:

December 21, 2007, at 01:04 AM by fenton travers -- I found the bootup script didn\'t quite work, needed to add a path statement.
Added lines 160-167:
  • Note I didn't find that this resolved the problem for the on boot process. I needed to change the bootup script to look like:
 #!/bin/sh
 export PATH=$PATH:/opt/libexec:/opt/bin
 /opt/bin/slimserver start
November 21, 2007, at 01:40 PM by BenMcDui -- enhanced my latest contribution
Changed lines 162-163 from:

Ensure that the rights/ownership of your music library are correct. User slimserver must have rwx rights. Very often if music is placed onto you HDD "from the outside" this is not (yet) the case." For FAT or NTFS formatted disks: these do not allow you to change ownership and severely limit the possibilities to change rights. Mostly, owner=guest on those disks. As far as my solution goes: start slimserver as guest. By implication, you must ensure that user guest can write to /home/slimserver/slimserver.pref and ....my.cnf. Any ideas about a more elegant solution are most welcome!

to:

Ensure that the rights/ownership of your music library are correct. User slimserver must have rwx rights. Very often if music is placed onto you HDD "from the outside" this is not (yet) the case.

For FAT or NTFS formatted disks: these do not allow you to change ownership and severely limit the possibilities to change rights. Mostly, owner=guest on those disks. As far as my solution goes: start slimserver as guest. By implication, you must ensure that user guest can write to /home/slimserver/slimserver.pref and ....my.cnf. Also user guest must get rights on /opt/share/ss65; my solution (over the top?) is # chown -R guest /opt/share/ss65. Any ideas about a more elegant solution are most welcome!

November 21, 2007, at 01:28 PM by BenMcDui -- added FAT/NTFS to issue \"Slimserver does not scan...
Changed lines 162-163 from:

Ensure that the rights/ownership of your music library are correct. User slimserver must have rwx rights. Very often if music is placed onto you HDD "from the outside" this is not (yet) the case.

to:

Ensure that the rights/ownership of your music library are correct. User slimserver must have rwx rights. Very often if music is placed onto you HDD "from the outside" this is not (yet) the case." For FAT or NTFS formatted disks: these do not allow you to change ownership and severely limit the possibilities to change rights. Mostly, owner=guest on those disks. As far as my solution goes: start slimserver as guest. By implication, you must ensure that user guest can write to /home/slimserver/slimserver.pref and ....my.cnf. Any ideas about a more elegant solution are most welcome!

November 20, 2007, at 08:30 PM by BenMcDui -- added issue \"Slimserver does not scan music\"
Added lines 159-162:

Slimserver does not scan music

Ensure that the rights/ownership of your music library are correct. User slimserver must have rwx rights. Very often if music is placed onto you HDD "from the outside" this is not (yet) the case.

November 20, 2007, at 08:26 PM by BenMcDui -- added [@ @] enclosure
Added line 138:

[@

Changed line 140 from:
to:

@]

November 20, 2007, at 08:24 PM by BenMcDui -- split the Issue \\\\\\\"mysqld/innodb\\\\\\\" I once added, into two and modified them drastically
Changed lines 134-136 from:

mysqld/innodb

Having followed the above instructions scrupulously, this is the result:

to:

innodb

slimserver.log may (will?) tell you among other things:

071023 20:47:30 [Warning] this binary does not contain INNODB storage engine

It turns out to be not a harmful issue, in most cases slimserver will run fine.

mysqld

You may see:

Changed lines 148-152 from:

NSLU2# tail /home/slimserver/slimserver.log

2007-10-23 20:12:55.6150 Use of uninitialized value in join or string at /opt/li b/perl5/5.8.8/File/Spec/Unix.pm line 81. 2007-10-23 20:13:44.6362 ERROR: MySQLHelper?: startServer() Couldn't find a execu

to:

2007-10-23 20:41:14.9403 ERROR: MySQLHelper?: startServer() Couldn't find a execu

Deleted lines 149-155:

2007-10-23 20:26:51.0148 ERROR: MySQLHelper?: startServer() Couldn't find a execu table for 'mysqld'! This is a fatal error. Exiting. 2007-10-23 20:41:14.9403 ERROR: MySQLHelper?: startServer() Couldn't find a execu table for 'mysqld'! This is a fatal error. Exiting. 071023 20:47:30 [Warning] this binary does not contain INNODB storage engine 071023 20:47:34 [Warning] this binary does not contain INNODB storage engine 2007-10-23 20:47:39.8821 Warning: Migrating from 6.3.x used with MySQL!

Changed lines 152-200 from:

I have repeated everything but the same result. I can't believe this is true... has anybody got a clue?

With a normal installation Slimserver expects a copy of the mysqld executable to be in the Bin directory. A user can configure Slimserver to use an existing mysqld daemon. The warnings are because Slimserver expects innodb to be built into mysqld - Slimserver will run without innodb but there is a chance of problems.

Wow, that was quick.

I found out that mysqld was in /opt/libexec and not in /opt/bin. Although the PATH also contains /opt/libexec, Slimserver apparently doesn’t find it there. So I copied mysqld to /opt/bin and now SS finds it. You seem to be the expert and to know best if this should lead to an extra line in the instruction? Slimserver only looks in its Bin directory - in this case /opt/share/ss65/Bin not /opt/bin. An extra line examplaing this would be helpful.

Remains Slimserver’s complaint about innodb. Your version of MySQL is not built with innodb option - this requires about 8Mb more memory but it means multiuser performs locking on database records. Without innodb there could be database update problems with multi user or user change when scanner is updating but with small NAS it looks to be OK.

The webinterface works, I can modify settings and my Softsqueeze can get hold of Slimserver, it plays Internet radio.

BUT scanning the music library does not work. Slimserver accepts the ‘Music folder’ (it rejects folders that do not exist). After I click ‘Rescan’ Slimserver responds with ‘The server is now rescanning your Music Library’. I left it scanning the very small (test) library overnight but still 0 Artists etcetera.

The music library is OK, it is a subset of the big library my Windows bases Slimserver is using for years already.

What I found is that there (also?) seems to be an issue with OSDetect.pm. After I instruted Slimserver to Rescan:

NSLU2# tail /home/slimserver/slimserver.log
   frame 12: Slim::Web::HTTP::generateHTTPResponse /opt/share/ss65/Slim/Web/HTT P.pm line 690)
   frame 13: Slim::Web::HTTP::processURL (/opt/share/ss65/Slim/Web/HTTP.pm line 536)
   frame 14: Slim::Web::HTTP::processHTTP (/opt/share/ss65/Slim/Networking/Select.pm line 238)
   frame 15: (eval) (/opt/share/ss65/Slim/Networking/Select.pm line 238)
   frame 16: Slim::Networking::Select::select (/opt/share/ss65/slimserver.pl line 493)
   frame 17: main::idle (/opt/share/ss65/slimserver.pl line 446)
   frame 18: main::main (/opt/share/ss65/slimserver.pl line 1072)

Can't locate Slim/Utils/OSDetect.pm in @INC (@INC contains: /opt/share/ss65 /opt/lib/perl5/5.8.8/armv5b-linux /opt/lib/perl5/5.8.8 /opt/lib/perl5/site_perl/5.8.
8/armv5b-linux /opt/lib/perl5/site_perl/5.8.8 /opt/lib/perl5/site_perl .) at /opt/share/ss65/scanner.pl line 23.
BEGIN failed--compilation aborted at /opt/share/ss65/scanner.pl line 23.

NSLU2# find -name OSDetect.pm

./opt/share/ss65/Slim/Utils/OSDetect.pm

When slimserver is using its own mysqld daemon - it only looks in the Bin directory. Your OSDetect.pm issue may be associated with the archname issue above. A wiki is not a suitable place to debug - start a thread in the slimserver forum. In the meantime you can get more info by starting slimserver from shell prompt with --d_startup --d_server options.

OK, will do. Shall we delete all or part of the issue?

''Leave it as is - when a solution is found, it can be edited to summarise the problems and solutions. Start a thread in http://forums.slimdevices.com/ in the 3rd party Hardware forum - use topic title something like: IPKG Installation problem on NSLU2 Optware ''

>> I have posted one on http://forums.slimdevices.com/showthread.php?p=238128#post238128 and one on http://www.openfsg.com/forum/viewtopic.php?p=23226#23226

to:

in slimserver.log. Slimserver expects a copy of the mysqld executable to be in the /opt/share/ss65/server/Bin, and you can solve this by:

 # cp opt/libexec/mysqld /opt/share/ss65/server/Bin/

Having done this, the command

 # export PATH=$PATH:/opt/libexec:/opt/bin

would no longer be needed.

November 07, 2007, at 07:37 PM by fcarolo -- formatting
Changed lines 193-194 from:

When slimserver is using its own mysqld daemon - it only looks in the Bin directory. Your OSDetect?.pm issue may be associated with the archname issue above. A wiki is not a suitable place to debug - start a thread in the slimserver forum. In the meantime you can get more info by starting slimserver from shell prompt with --d_startup --d_server options.

to:

When slimserver is using its own mysqld daemon - it only looks in the Bin directory. Your OSDetect.pm issue may be associated with the archname issue above. A wiki is not a suitable place to debug - start a thread in the slimserver forum. In the meantime you can get more info by starting slimserver from shell prompt with --d_startup --d_server options.

October 26, 2007, at 02:20 PM by BenMcDui --
Changed lines 199-201 from:

something like: IPKG Installation problem on NSLU2 Optware ''

to:

something like: IPKG Installation problem on NSLU2 Optware ''

>> I have posted one on http://forums.slimdevices.com/showthread.php?p=238128#post238128 and one on http://www.openfsg.com/forum/viewtopic.php?p=23226#23226

October 26, 2007, at 11:49 AM by bpa --
Changed lines 195-199 from:

OK, will do. Shall we delete all or part of the issue?

to:

OK, will do. Shall we delete all or part of the issue?

''Leave it as is - when a solution is found, it can be edited to summarise the problems and solutions. Start a thread in http://forums.slimdevices.com/ in the 3rd party Hardware forum - use topic title something like: IPKG Installation problem on NSLU2 Optware ''

October 26, 2007, at 10:01 AM by BenMcDui -- Close issue \\\"mysql/innodb\\\"
Changed lines 193-195 from:

When slimserver is using its own mysqld daemon - it only looks in the Bin directory. Your OSDetect?.pm issue may be associated with the archname issue above. A wiki is not a suitable place to debug - start a thread in the slimserver forum. In the meantime you can get more info by starting slimserver from shell prompt with --d_startup --d_server options.

to:

When slimserver is using its own mysqld daemon - it only looks in the Bin directory. Your OSDetect?.pm issue may be associated with the archname issue above. A wiki is not a suitable place to debug - start a thread in the slimserver forum. In the meantime you can get more info by starting slimserver from shell prompt with --d_startup --d_server options.

OK, will do. Shall we delete all or part of the issue?

October 25, 2007, at 11:01 PM by bpa -- Answer to question in mid text
Changed lines 160-161 from:
to:

Slimserver only looks in its Bin directory - in this case /opt/share/ss65/Bin not /opt/bin. An extra line examplaing this would be helpful.

Changed lines 163-164 from:
to:

Your version of MySQL is not built with innodb option - this requires about 8Mb more memory but it means multiuser performs locking on database records. Without innodb there could be database update problems with multi user or user change when scanner is updating but with small NAS it looks to be OK.

October 25, 2007, at 10:35 PM by bpa -- response to query
Added lines 190-191:

When slimserver is using its own mysqld daemon - it only looks in the Bin directory. Your OSDetect?.pm issue may be associated with the archname issue above. A wiki is not a suitable place to debug - start a thread in the slimserver forum. In the meantime you can get more info by starting slimserver from shell prompt with --d_startup --d_server options.

October 25, 2007, at 12:41 PM by fcarolo -- formatting
Changed line 169 from:

What I found is that there (also?) seems to be an issue with OSDetect?.pm.

to:

What I found is that there (also?) seems to be an issue with OSDetect.pm.

Changed line 189 from:

=]

to:

@]

October 25, 2007, at 12:41 PM by fcarolo -- formatting
Added line 137:

[@

Deleted line 141:
Deleted line 143:
Deleted line 145:
Deleted line 147:
Deleted line 148:
Deleted line 149:
Changed lines 151-152 from:
to:

@]

Added line 172:

[@

Changed line 189 from:
to:

=]

October 25, 2007, at 10:17 AM by BenMcDui --
Added line 190:
October 25, 2007, at 10:15 AM by BenMcDui --
Added lines 160-191:

Wow, that was quick.

I found out that mysqld was in /opt/libexec and not in /opt/bin. Although the PATH also contains /opt/libexec, Slimserver apparently doesn’t find it there. So I copied mysqld to /opt/bin and now SS finds it. You seem to be the expert and to know best if this should lead to an extra line in the instruction?

Remains Slimserver’s complaint about innodb.

The webinterface works, I can modify settings and my Softsqueeze can get hold of Slimserver, it plays Internet radio.

BUT scanning the music library does not work. Slimserver accepts the ‘Music folder’ (it rejects folders that do not exist). After I click ‘Rescan’ Slimserver responds with ‘The server is now rescanning your Music Library’. I left it scanning the very small (test) library overnight but still 0 Artists etcetera.

The music library is OK, it is a subset of the big library my Windows bases Slimserver is using for years already.

What I found is that there (also?) seems to be an issue with OSDetect?.pm. After I instruted Slimserver to Rescan:

NSLU2# tail /home/slimserver/slimserver.log

   frame 12: Slim::Web::HTTP::generateHTTPResponse /opt/share/ss65/Slim/Web/HTT P.pm line 690)
   frame 13: Slim::Web::HTTP::processURL (/opt/share/ss65/Slim/Web/HTTP.pm line 536)
   frame 14: Slim::Web::HTTP::processHTTP (/opt/share/ss65/Slim/Networking/Select.pm line 238)
   frame 15: (eval) (/opt/share/ss65/Slim/Networking/Select.pm line 238)
   frame 16: Slim::Networking::Select::select (/opt/share/ss65/slimserver.pl line 493)
   frame 17: main::idle (/opt/share/ss65/slimserver.pl line 446)
   frame 18: main::main (/opt/share/ss65/slimserver.pl line 1072)

Can't locate Slim/Utils/OSDetect?.pm in @INC (@INC contains: /opt/share/ss65 /opt/lib/perl5/5.8.8/armv5b-linux /opt/lib/perl5/5.8.8 /opt/lib/perl5/site_perl/5.8. 8/armv5b-linux /opt/lib/perl5/site_perl/5.8.8 /opt/lib/perl5/site_perl .) at /opt/share/ss65/scanner.pl line 23. BEGIN failed--compilation aborted at /opt/share/ss65/scanner.pl line 23.

NSLU2# find -name OSDetect?.pm ./opt/share/ss65/Slim/Utils/OSDetect?.pm

October 24, 2007, at 12:25 AM by bpa --
Changed lines 95-96 from:

You can find a tar.gz file here of the relevant files. Some caveats:

to:

You can find a tar.gz file here of the relevant files. If you want help from the author - start a thread on Slimserver forum. Some caveats:

October 24, 2007, at 12:21 AM by bpa -- formatting
Added line 14:
Added line 96:
Added line 98:
Added line 100:
Added line 102:
October 24, 2007, at 12:18 AM by bpa -- Update for 6.5.4 and include ipkg build files
Added lines 12-15:

This is 6.5.4 version with a few corrections but this is for an fsg3 so NSLU2 users need to take care. http://homepage.eircom.net/~altondsl/slim/ss65_6.5.4-1_armeb.ipk

Added lines 94-99:

You can find a tar.gz file here of the relevant files. Some caveats: 1. It is not approved/reviewed by optware developers. 2. It is set up for FSG3 and so there are FSG3 specifics. 3. It has only been tested cross compiling and not native as FSG3 cannot compile some of the modules. http://homepage.eircom.net/~altondsl/slim/ss65ipkgmaker.tar.gz

Added lines 153-154:

With a normal installation Slimserver expects a copy of the mysqld executable to be in the Bin directory. A user can configure Slimserver to use an existing mysqld daemon. The warnings are because Slimserver expects innodb to be built into mysqld - Slimserver will run without innodb but there is a chance of problems.

October 23, 2007, at 11:30 PM by fcarolo -- note abaout PATH
Changed lines 47-48 from:

comment PeLu?: must be # /opt/bin/slimserver

to:

Note: /opt/bin/should be in your $PATH (from step 1), and will also be if you are using ssh to access your slug.

October 23, 2007, at 07:16 PM by PeLu --
Added line 125:
Added line 136:
Added line 138:
October 23, 2007, at 07:15 PM by PeLu --
Added line 122:
October 23, 2007, at 07:14 PM by PeLu --
Added line 120:
October 23, 2007, at 07:13 PM by PeLu --
Changed line 120 from:

=#= tail /home/slimserver/slimserver.log

to:

NSLU2# tail /home/slimserver/slimserver.log

October 23, 2007, at 07:10 PM by PeLu --
Changed line 118 from:

mysqld/innodb

to:

mysqld/innodb

Changed line 120 from:
  1. tail /home/slimserver/slimserver.log
to:

=#= tail /home/slimserver/slimserver.log

October 23, 2007, at 07:07 PM by PeLu -- Issue \"mysqld/innodb\" added
Added lines 118-136:

mysqld/innodb

Having followed the above instructions scrupulously, this is the result:

  1. tail /home/slimserver/slimserver.log

2007-10-23 20:12:55.6150 Use of uninitialized value in join or string at /opt/li b/perl5/5.8.8/File/Spec/Unix.pm line 81. 2007-10-23 20:13:44.6362 ERROR: MySQLHelper?: startServer() Couldn't find a execu table for 'mysqld'! This is a fatal error. Exiting.

2007-10-23 20:26:51.0148 ERROR: MySQLHelper?: startServer() Couldn't find a execu table for 'mysqld'! This is a fatal error. Exiting.

2007-10-23 20:41:14.9403 ERROR: MySQLHelper?: startServer() Couldn't find a execu table for 'mysqld'! This is a fatal error. Exiting.

071023 20:47:30 [Warning] this binary does not contain INNODB storage engine 071023 20:47:34 [Warning] this binary does not contain INNODB storage engine 2007-10-23 20:47:39.8821 Warning: Migrating from 6.3.x used with MySQL!

I have repeated everything but the same result. I can't believe this is true... has anybody got a clue?

October 23, 2007, at 06:12 PM by PeLu -- # slimserver -> # /opt/bin/slimserver
Changed lines 47-48 from:
to:

comment PeLu?: must be # /opt/bin/slimserver

October 03, 2007, at 07:09 PM by Gary --
Deleted lines 81-86:

Questions

- Step 2 Once the slimserver user and group have been created, are you supposed to do anything with them?

Added lines 84-87:

Makefile

Can someone publish the makefile to Optware svn so it can be updated for 6.5.4 and all future releases please?

September 24, 2007, at 01:02 PM by Gary -- typo
Changed lines 93-94 from:

Two options to reolve this:

to:

Two options to resolve this:

September 23, 2007, at 10:41 PM by Gary --
Changed lines 90-91 from:
to:
Changed lines 98-99 from:

- Speed

to:

Speed

September 23, 2007, at 10:41 PM by Gary --
Added line 91:
Added line 99:
September 23, 2007, at 10:40 PM by Gary -- MySQL and question on point 3
Changed lines 83-84 from:

There is an issue with this build - there seems to be too many mysql processes started. bpa of openfsg.com is looking into it.

to:

Questions

- Step 2 Once the slimserver user and group have been created, are you supposed to do anything with them?

Changed lines 89-91 from:

- It seems like the mysql server gets kicked off twice: once when it is installed and then again when slimserver starts up. - You shouldn't bother to install this on anything but a TurboSlug. Even turbo, scanning the whole music library took half an hour.

to:

- MySQL You may end up with two mysql processes running. One from the mysql install and another from slimserver. Two options to reolve this:

      http://wiki.slimdevices.com/index.cgi?ExistingMySQLInstance
      or
      remove the *70mysqld from /opt/etc/init.d (I had both K70mysqld and S70mysqld for some reason.

- Speed You shouldn't bother to install this on anything but a TurboSlug. Even turbo, scanning the whole music library took half an hour.

August 29, 2007, at 11:30 AM by henrik --
Added line 92:
Changed lines 94-95 from:
 /opt/bin/ipkg-opt install perl expat perl-compress-zlib  
to:
Added line 97:
Added line 100:
August 29, 2007, at 11:28 AM by henrik --
Changed lines 86-88 from:
  • It seems like the mysql server gets kicked off twice: once when it is installed and then again when slimserver starts up.
  • You shouldn't bother to install this on anything but a TurboSlug. Even turbo, scanning the whole music library took half an hour.
to:

- It seems like the mysql server gets kicked off twice: once when it is installed and then again when slimserver starts up. - You shouldn't bother to install this on anything but a TurboSlug. Even turbo, scanning the whole music library took half an hour.

Changed line 90 from:
  • Concerning point 3)
to:

- Concerning point 3)

Changed lines 94-95 from:
  • Concerning point 10)
to:

- Concerning point 10)

August 29, 2007, at 11:25 AM by henrik -- cleaning up messy wiki editing
Changed lines 18-19 from:
    /opt/share/ss65
to:
 /opt/share/ss65
Changed lines 22-25 from:
 # export PATH=$PATH:/opt/libexec:/opt/bin

2) Add the slimserver group and user by editing /etc/passwd and /etc/group. Create the /home/slimserver folder.

to:
 nslu2# export PATH=$PATH:/opt/libexec:/opt/bin

2) Add the "slimserver" group and user by editing /etc/passwd and /etc/group. Create the /home/slimserver folder.

Changed lines 28-43 from:
 # ipkg update; ipkg install perl expat mysql perl-compress-zlib

4) Create the /home/slimserver folder, and add the slimserver group (edit /etc/group) and slimserver user (edit /etc/passwd).

5) Change current directory to where the ss65_6.5.1-1_armeb.ipk has been saved.

6) install the Slimserserver package with the command

 # ipkg install ss65_6.5.1-1_armeb.ipk 

 Change the first line in /opt/share/ss65/slimserver.pl from "#!/usr/bin/perl -w" to "#!/opt/bin/perl -w", and fix some permissions:

 # chmod a=rw /opt/share/ss65/Slim/Utils

7) Edit /opt/share/ss65/MySQL/my.tt, add a "#" in front of "innodb_fast_shutdown = 1"

to:
 nslu2# ipkg update; ipkg install perl expat mysql perl-compress-zlib

4) Change current directory to where the ss65_6.5.1-1_armeb.ipk has been saved.

5) install the Slimserserver package with the command

 nslu2# ipkg install ss65_6.5.1-1_armeb.ipk 

6) Change the first line in /opt/share/ss65/slimserver.pl and ../scanner.pl from "#!/usr/bin/perl -w" to "#!/opt/bin/perl -w", and fix some permissions:

 nslu2# chmod a=rw /opt/share/ss65/Slim/Utils

7) Edit /opt/share/ss65/MySQL/my.tt, comment out the innodb_fast_shutdown line:

 #innodb_fast_shutdown  = 1
Changed lines 46-47 from:
 # slimserver
to:
 nslu2# slimserver
Changed lines 53-54 from:
 # slimserver info 
to:
 nslu2# slimserver info 
Changed lines 57-64 from:
 # slimserver start 

11) To see progress through log file you can do

 # tail /home/slimserver/slimserver.log

The following is a normal start - the last line about port 9000 indicate web interface is ready.

to:
 nslu2# slimserver start 

11) Watch the log to see if everything is OK. The following is a normal start - the last line about port 9000 indicate web interface is ready.

Changed lines 62-63 from:
 # tail /home/slimserver/slimserver.log
to:
 nslu2# tail /home/slimserver/slimserver.log
Changed lines 88-103 from:
  • Concerning point 3) with SlugOS/BE
     Prior to install those packages, on my SlugOS/BE I had to install optware and than use the commands
     /opt/bin/ipkg-opt udate
    /opt/bin/ipkg-opt install perl expat perl-compress-zlib  
  • Concerning point 6) with SlugOS/BE
    I hade to use the command /opt/bin/ipkg install ss65_6.5.1-1_armeb.ipk
    Not only slimserver.pl, but also scanner.pl needs the new perl-instruction (change first line)
  • Concerning point 10) with SlugOS/BE
   Prior to be able to start slimserver, I had to execute the fellowing commands:
   root@slimserver:/opt/share/ss65/CPAN/arch/5.8.8# mkdir armeb-linux
   root@slimserver:/opt/share/ss65/CPAN/arch/5.8.8# cp -a armv5b-softfloat-linux/* armeb-linux/
   This was neccessary since perl searched the modules in armeb-linux and not in armv5b-softfloat-linux since the package was compiled on FSG3 and not on NSLU2
   See also
   http://forums.slimdevices.com/showthread.php?t=36894
  • Concerning previous issue
   Use command "perl -V:archname" to get the correct name as the name "armeb-linux" may not be correct for all builds of Perl or Unslung/SlugOS.
to:

SlugOS/BE issues

  • Concerning point 3)

Prior to install those packages, on my SlugOS/BE I had to install optware and then use the commands

 /opt/bin/ipkg-opt update
 /opt/bin/ipkg-opt install perl expat perl-compress-zlib  
  • Concerning point 10)

Prior to be able to start slimserver, I had to execute the following commands:

 root@nslu2:/opt/share/ss65/CPAN/arch/5.8.8# mkdir armeb-linux
 root@nslu2:/opt/share/ss65/CPAN/arch/5.8.8# cp -a armv5b-softfloat-linux/* armeb-linux/

This was neccessary since perl searched the modules in armeb-linux and not in armv5b-softfloat-linux since the package was compiled on FSG3 and not on NSLU2. Use command "perl -V:archname" to get the correct name as the name "armeb-linux" may not be correct for all builds of Perl or Unslung/SlugOS. See also http://forums.slimdevices.com/showthread.php?t=36894

July 22, 2007, at 01:13 PM by Fabio Vassalli --
Changed line 99 from:
  • Concerning point 10) SlugOS/BE
to:
  • Concerning point 10) with SlugOS/BE
July 22, 2007, at 12:37 PM by Fabio Vassalli --
Changed line 92 from:
  • Concerning point 3)
to:
  • Concerning point 3) with SlugOS/BE
Changed line 96 from:
  • Concerning point 6)
to:
  • Concerning point 6) with SlugOS/BE
Changed lines 98-99 from:
  • Concerning point 10)
to:
    Not only slimserver.pl, but also scanner.pl needs the new perl-instruction (change first line)
  • Concerning point 10) SlugOS/BE
July 20, 2007, at 07:18 PM by fcarolo -- removed false wikilinks
Changed line 91 from:
  • You shouldn't bother to install this on anything but a TurboSlug?. Even turbo, scanning the whole music library took half an hour.
to:
  • You shouldn't bother to install this on anything but a TurboSlug. Even turbo, scanning the whole music library took half an hour.
Changed line 102 from:
   This was neccessary since perl searched the modules in armeb-linux and not in armv5b-softfloat-linux since the package was compiled on FSG3 and not on NUSLU2?
to:
   This was neccessary since perl searched the modules in armeb-linux and not in armv5b-softfloat-linux since the package was compiled on FSG3 and not on NSLU2
Changed line 106 from:
   Use command "perl -V:archname" to get the correct name as the name "armeb-linux" may not be correct for all builds of Perl or SlugOS?.
to:
   Use command "perl -V:archname" to get the correct name as the name "armeb-linux" may not be correct for all builds of Perl or Unslung/SlugOS.
July 19, 2007, at 01:42 PM by bpa --
Added lines 105-106:
  • Concerning previous issue
   Use command "perl -V:archname" to get the correct name as the name "armeb-linux" may not be correct for all builds of Perl or SlugOS?.
July 19, 2007, at 01:22 PM by Fabio Vassalli --
Changed lines 97-105 from:
    I hade to use the command /opt/bin/ipkg install ss65_6.5.1-1_armeb.ipk
to:
    I hade to use the command /opt/bin/ipkg install ss65_6.5.1-1_armeb.ipk
  • Concerning point 10)
   Prior to be able to start slimserver, I had to execute the fellowing commands:
   root@slimserver:/opt/share/ss65/CPAN/arch/5.8.8# mkdir armeb-linux
   root@slimserver:/opt/share/ss65/CPAN/arch/5.8.8# cp -a armv5b-softfloat-linux/* armeb-linux/
   This was neccessary since perl searched the modules in armeb-linux and not in armv5b-softfloat-linux since the package was compiled on FSG3 and not on NUSLU2?
   See also
   http://forums.slimdevices.com/showthread.php?t=36894
July 10, 2007, at 08:48 PM by Fabio Vassalli --
Deleted line 94:
July 10, 2007, at 08:47 PM by Fabio Vassalli --
Changed lines 18-19 from:
 /opt/share/ss65
to:
    /opt/share/ss65
Changed lines 93-95 from:

Prior to install those packages, on my SlugOS/BE I had to install optware and than use the commands /opt/bin/ipkg-opt udate /opt/bin/ipkg-opt install perl expat perl-compress-zlib

to:
     Prior to install those packages, on my SlugOS/BE I had to install optware and than use the commands
     /opt/bin/ipkg-opt udate

    /opt/bin/ipkg-opt install perl expat perl-compress-zlib  
  • Concerning point 6)
    I hade to use the command /opt/bin/ipkg install ss65_6.5.1-1_armeb.ipk
July 10, 2007, at 08:40 PM by Fabio Vassalli --
Added lines 92-95:
  • Concerning point 3)

Prior to install those packages, on my SlugOS/BE I had to install optware and than use the commands /opt/bin/ipkg-opt udate /opt/bin/ipkg-opt install perl expat perl-compress-zlib

May 23, 2007, at 10:39 AM by Henrik --
Changed lines 90-91 from:

- It seems like the mysql server gets kicked off twice: once when it is installed and then again when slimserver starts up. - You shouldn't bother to install this on anything but a TurboSlug?. Even turbo, scanning the whole music library took half an hour.

to:
  • It seems like the mysql server gets kicked off twice: once when it is installed and then again when slimserver starts up.
  • You shouldn't bother to install this on anything but a TurboSlug?. Even turbo, scanning the whole music library took half an hour.
May 23, 2007, at 10:38 AM by Henrik --
Deleted lines 15-16:

(see added notes at the bottom - Vince)

May 23, 2007, at 10:38 AM by Henrik -- Making Vinces additions more readable. Adding extra info at the bottom of a guide isnt really readble.
Changed lines 22-23 from:

1) Login as root

to:

1) Login as root, and make sure your PATH is correct:

 # export PATH=$PATH:/opt/libexec:/opt/bin
Changed lines 30-31 from:
 # ipkg update; ipkg install perl expat mysql
to:
 # ipkg update; ipkg install perl expat mysql perl-compress-zlib
Added lines 40-43:
 Change the first line in /opt/share/ss65/slimserver.pl from "#!/usr/bin/perl -w" to "#!/opt/bin/perl -w", and fix some permissions:

 # chmod a=rw /opt/share/ss65/Slim/Utils
Changed lines 91-108 from:

14 May 2007 - These instructions are nice and simple. I used them to do an successful install on my slug. There are a few steps missing, however:

1. Change the first line in /opt/share/ss65/slimserver.pl From #!/usr/bin/perl -w To #!/opt/bin/perl -w

2. Make sure the perl compress module is installed ipkg install perl-compress-zlib

3. Make sure your PATH includes /opt/libexec /opt/bin

4. I had to chmod a=rw on the directory /opt/share/ss65/Slim/Utils

Also, it seems like the mysql server gets kicked off twice: once when it is installed and then again when slimserver starts up.

And p.s. I wouldn't bother to install this on anything but a TurboSlug?. Even turbo, scanning the whole music library took half an hour.

to:

Issues

- It seems like the mysql server gets kicked off twice: once when it is installed and then again when slimserver starts up. - You shouldn't bother to install this on anything but a TurboSlug?. Even turbo, scanning the whole music library took half an hour.

May 14, 2007, at 06:34 PM by Vince --
Added lines 101-102:

And p.s. I wouldn't bother to install this on anything but a TurboSlug?. Even turbo, scanning the whole music library took half an hour.

May 14, 2007, at 06:17 PM by Vince --
Added lines 16-17:

(see added notes at the bottom - Vince)

Added lines 98-99:

4. I had to chmod a=rw on the directory /opt/share/ss65/Slim/Utils

May 14, 2007, at 06:08 PM by Vince --
Changed lines 83-84 from:
  • These instructions are nice and simple. I used them to do an successful install on my slug May 14, 2007. There are a few steps missing, however:
to:

14 May 2007 - These instructions are nice and simple. I used them to do an successful install on my slug. There are a few steps missing, however:

May 14, 2007, at 06:07 PM by Vince -- These instructions are good but not quite complete
Added lines 82-96:
  • These instructions are nice and simple. I used them to do an successful install on my slug May 14, 2007. There are a few steps missing, however:

1. Change the first line in /opt/share/ss65/slimserver.pl From #!/usr/bin/perl -w To #!/opt/bin/perl -w

2. Make sure the perl compress module is installed ipkg install perl-compress-zlib

3. Make sure your PATH includes /opt/libexec /opt/bin

Also, it seems like the mysql server gets kicked off twice: once when it is installed and then again when slimserver starts up.

April 26, 2007, at 10:45 AM by Henrik --
Changed lines 73-74 from:

12) By default slimserver will not start as part of boot - if you want this then add an executable script as /opt/etc/init.d/S85slimserver

to:

12) By default slimserver will not start as part of boot - if you want this then add an executable script as /opt/etc/init.d/S85slimserver:

Changed lines 76-78 from:
  1. !/bin/sh

/opt/bin/slimserver start

to:
 #!/bin/sh
 /opt/bin/slimserver start
April 26, 2007, at 10:45 AM by Henrik --
Changed lines 24-26 from:

3) Install the perl, expat and mysql packages. The slimserver ipkg will request them but it is better to do manually in case there are problems, you'll know where to look.

to:

3) Install the perl, expat and mysql packages. The slimserver ipkg will request them but it is better to do manually in case there are problems, you'll know where to look.

Added line 58:
Changed lines 73-77 from:

12) By default slimserver will start as part of boot - if you do not want this then use

 # slimserver disable.
to:

12) By default slimserver will not start as part of boot - if you want this then add an executable script as /opt/etc/init.d/S85slimserver

#!/bin/sh

/opt/bin/slimserver start
April 26, 2007, at 10:31 AM by Henrik --
Changed lines 37-38 from:

7) Edit ""/opt/share/ss65/MySQL/my.tt"", add a "#" in front of "innodb_fast_shutdown = 1"

to:

7) Edit /opt/share/ss65/MySQL/my.tt, add a "#" in front of "innodb_fast_shutdown = 1"

April 26, 2007, at 09:00 AM by Henrik --
Changed lines 37-38 from:

7) Edit /opt/share/ss65/MySQL/my.tt, add a "#" in front of "innodb_fast_shutdown = 1"

to:

7) Edit ""/opt/share/ss65/MySQL/my.tt"", add a "#" in front of "innodb_fast_shutdown = 1"

April 26, 2007, at 08:59 AM by Henrik --
Changed lines 37-38 from:

7) If it install goes OK, try the command

to:

7) Edit /opt/share/ss65/MySQL/my.tt, add a "#" in front of "innodb_fast_shutdown = 1"

8) If it install goes OK, try the command

Changed lines 46-47 from:

8) If it works. then try

to:

9) If it works. then try

Changed lines 50-51 from:

9) To start slimserver used the command below - it will take a couple of minutes before your see a "Slimserver Started message"

to:

10) To start slimserver used the command below - it will take a couple of minutes before your see a "Slimserver Started message"

Changed lines 54-55 from:

10) To see progress through log file you can do

to:

11) To see progress through log file you can do

Changed lines 73-74 from:

11) By default slimserver will start as part of boot - if you do not want this then use

to:

12) By default slimserver will start as part of boot - if you do not want this then use

April 24, 2007, at 07:11 PM by Henrik --
Changed lines 27-28 from:
 # ipkg install perl expat mysql
to:
 # ipkg update; ipkg install perl expat mysql
April 24, 2007, at 07:10 PM by Henrik --
Changed lines 22-23 from:

2) You must have the ipkg bootstrap 1.05 or better installed.

to:

2) Add the slimserver group and user by editing /etc/passwd and /etc/group. Create the /home/slimserver folder.

April 24, 2007, at 07:05 PM by Henrik --
Changed lines 20-24 from:

Login as root

You must have the ipkg bootstrap 1.05 or better installed.

Install the perl, expat and mysql packages.

to:

1) Login as root

2) You must have the ipkg bootstrap 1.05 or better installed.

3) Install the perl, expat and mysql packages.

Changed lines 29-35 from:

Create the /home/slimserver folder,

and add the slimserver group (edit /etc/group) and slimserver user (edit /etc/passwd).

Change current directory to where the ss65_6.5.1-1_armeb.ipk has been saved.

install the Slimserserver package with the command

to:

4) Create the /home/slimserver folder, and add the slimserver group (edit /etc/group) and slimserver user (edit /etc/passwd).

5) Change current directory to where the ss65_6.5.1-1_armeb.ipk has been saved.

6) install the Slimserserver package with the command

Changed lines 37-38 from:

If it install goes OK, try the command

to:

7) If it install goes OK, try the command

Changed lines 44-45 from:

If it works. then try

to:

8) If it works. then try

Changed lines 48-50 from:

To start slimserver used the command below

it will take a couple of minutes before your see a "Slimserver Started message"

to:

9) To start slimserver used the command below - it will take a couple of minutes before your see a "Slimserver Started message"

Changed lines 52-53 from:

To see progress through log file you can do

to:

10) To see progress through log file you can do

Changed lines 71-73 from:

By default slimserver will start as part of boot

if you do not want this then use

to:

11) By default slimserver will start as part of boot - if you do not want this then use

April 24, 2007, at 07:01 PM by Henrik --
Changed lines 20-25 from:

Login as root

  • You must have the ipkg bootstrap 1.05 or better installed.
  • Install the perl, expat and mysql packages. The slimserver ipkg will request them but it is better to do manually in case there are problems, you'll know where to look.
to:

Login as root

You must have the ipkg bootstrap 1.05 or better installed.

Install the perl, expat and mysql packages.

The slimserver ipkg will request them but it is better to do manually in case there are problems, you'll know where to look.

Changed lines 29-34 from:
  • Create the /home/slimserver folder, and add the slimserver group (edit /etc/group) and slimserver user (edit /etc/passwd).
  • Change current directory to where the ss65_6.5.1-1_armeb.ipk has been saved.
  • install the Slimserserver package with the command
to:

Create the /home/slimserver folder,

and add the slimserver group (edit /etc/group) and slimserver user (edit /etc/passwd).

Change current directory to where the ss65_6.5.1-1_armeb.ipk has been saved.

install the Slimserserver package with the command

Changed lines 38-39 from:
  • If it install goes OK, try the command
to:

If it install goes OK, try the command

Changed lines 45-46 from:
  • If it works. then try
to:

If it works. then try

Changed lines 49-50 from:
  • To start slimserver used the command below - it will take a couple of minutes before your see a "Slimserver Started message"
to:

To start slimserver used the command below

it will take a couple of minutes before your see a "Slimserver Started message"

Changed lines 54-55 from:
  • To see progress through log file you can do
to:

To see progress through log file you can do

Changed lines 73-74 from:
  • By default slimserver will start as part of boot - if you do not want this then use
to:

By default slimserver will start as part of boot

if you do not want this then use

April 24, 2007, at 06:59 PM by Henrik --
Changed lines 20-21 from:
  • Login as root
to:

Login as root

April 24, 2007, at 06:58 PM by Henrik --
Changed lines 20-24 from:
  • Login as root
  • You must have the ipkg bootstrap 1.05 or better installed.
  • Install the perl, expat and mysql packages. The slimserver ipkg will request them but it is better to do manually in case there are problems, you'll know where to look.
to:
  • Login as root
  • You must have the ipkg bootstrap 1.05 or better installed.
  • Install the perl, expat and mysql packages. The slimserver ipkg will request them but it is better to do manually in case there are problems, you'll know where to look.
Changed lines 32-33 from:
  • install the Slimserserver package with the command
to:
  • install the Slimserserver package with the command
Changed lines 35-37 from:
  • If it install goes OK, try the command
to:
  • If it install goes OK, try the command
Changed lines 43-44 from:
  • If it works. then try
to:
  • If it works. then try
Changed lines 47-48 from:
  • To start slimserver used the command below - it will take a couple of minutes before your see a "Slimserver Started message"
to:
  • To start slimserver used the command below - it will take a couple of minutes before your see a "Slimserver Started message"
Added line 52:
Changed lines 69-72 from:
  • By default slimserver will start as part of boot - if you do not want this then use

slimserver disable.

to:
  • By default slimserver will start as part of boot - if you do not want this then use
 # slimserver disable.
April 24, 2007, at 06:56 PM by Henrik --
Added line 21:
Added line 23:
Changed lines 25-26 from:
 ipkg install perl expat mysql
to:
 # ipkg install perl expat mysql
Added line 28:
Added line 30:
Changed line 32 from:
 ipkg install ss65_6.5.1-1_armeb.ipk 
to:
 # ipkg install ss65_6.5.1-1_armeb.ipk 
Changed lines 34-35 from:
 slimserver
to:
 # slimserver
Changed lines 40-41 from:
 slimserver info 
to:
 # slimserver info 
Changed lines 43-44 from:
 slimserver start 
to:
 # slimserver start 
Deleted lines 45-48:
 tail /home/slimserver/slimserver.log

The following is a normal start - the last line about port 9000 indicate web interface is ready.

Added lines 48-51:

The following is a normal start - the last line about port 9000 indicate web interface is ready. [@

 # tail /home/slimserver/slimserver.log
Changed line 61 from:
to:

@]

April 24, 2007, at 06:54 PM by Henrik --
Changed line 3 from:

This guide is mostly copied from http://www.openfsg.com/forum/viewtopic.php?p=14920#14920 . All credits go to *bpa of openfsg.com*.

to:

This guide is mostly copied from http://www.openfsg.com/forum/viewtopic.php?p=14920#14920 . All credits go to bpa of openfsg.com.

Changed lines 17-19 from:

/home/slimserver /opt/share/ss65

to:
 /home/slimserver
 /opt/share/ss65
Changed line 23 from:

ipkg install perl expat mysql

to:
 ipkg install perl expat mysql
Changed line 27 from:

ipkg install ss65_6.5.1-1_armeb.ipk

to:
 ipkg install ss65_6.5.1-1_armeb.ipk 
Changed lines 29-30 from:

slimserver

to:
 slimserver
Changed lines 32-33 from:

Usage: /opt/bin/slimserver {start|stop|status|enable|disable|firewall|wanenable|wandisable|info}

to:
 Usage: /opt/bin/slimserver {start|stop|status|enable|disable|firewall|wanenable|wandisable|info} 
Changed lines 35-36 from:

slimserver info

to:
 slimserver info 
Changed lines 38-39 from:

slimserver start

to:
 slimserver start 
Changed lines 41-42 from:

tail /home/slimserver/slimserver.log

to:
 tail /home/slimserver/slimserver.log
Changed lines 45-46 from:

[= # tail /home/slimserver/slimserver.log

to:
 # tail /home/slimserver/slimserver.log
Changed lines 48-54 from:

2007-01-22 20:39:37.8519 Attempt to free unreferenced scalar: SV 0x1bc6b4c. 2007-01-22 20:40:51.0064 Use of uninitialized value in join or string at /opt/lib/perl5/5.8.8/File/Spec/Unix.pm line 81. 2007-01-22 20:42:07.4538 Your data source needs to be configured. Please open your web browser, 2007-01-22 20:42:07.4763 go to the following URL, and click on the "Server Settings" link.

2007-01-22 20:42:07.4785 The URL to access SlimServer is now:

to:
 2007-01-22 20:39:37.8519 Attempt to free unreferenced scalar: SV 0x1bc6b4c.
 2007-01-22 20:40:51.0064 Use of uninitialized value in join or string at /opt/lib/perl5/5.8.8/File/Spec/Unix.pm line 81.
 2007-01-22 20:42:07.4538 Your data source needs to be configured. Please open your web browser,
 2007-01-22 20:42:07.4763 go to the following URL, and click on the "Server Settings" link.

 2007-01-22 20:42:07.4785 The URL to access SlimServer is now:
Changed lines 56-59 from:

=]

  • If you wish to access slimserver by web from WAN port open firewall with

slimserver firewall.

to:
Changed line 61 from:

There is an issue with this build - there seems to be too many mysql processes started. *bpa of openfsg.com* is looking into it.

to:

There is an issue with this build - there seems to be too many mysql processes started. bpa of openfsg.com is looking into it.

April 24, 2007, at 06:50 PM by Henrik -- Move old cruft to SlimServerOld
Changed lines 1-305 from:

Installing Slimserver on the NSLU2

Of course, you've already installed Unslung. (I'm running 4.20, but more recent versions should work fine)

Enable telnet

 http://IP-address-of-your-slug/Management/telnet.cgi

First I installed dropbear (UseDropBearForRemoteAccess) so I could use ssh to access my slug.

 # ipkg update
 # ipkg install dropbear
 # reboot

You'll need Perl to run SlimServer (BuildPerlOnYourNSLU2Box) - don't worry, perl is now pre-built, so this is easy:

 # ipkg update
 # ipkg install unslung-feeds
 # ipkg update
 # ipkg install perl

Go download SlimServer Perl source code (I used v6.0.2)

 http://www.slimdevices.com/su_downloads.html

Installing Slimserver is as easy as using tar xzvf Slimserver_v6.0.2.tar.gz

I decided mine should live in /usr/local with data in /etc/slim-data

 # cd /usr/local
 # tar xzvf /root/Slimserver_v6.0.2.tar.gz
 # cd /etc
 # mkdir slim-data

Slim server needed the following Perl modules: DBD::SQLite XML::Parser HTML::Parser Compress::Zlib. However, the slimserver code provides a way to get those missing packages, but you need a C compiiler and a few other things. So the next step was to install the native tools, (NativelyCompileUnslungPackages).

This is simply:

 # ipkg install unslung-devel

You'll also need the which command, as well as expat (if which complains about missing "libz.so", run "ipkg install zlib" ):

 # ipkg install which
 # ipkg install expat

Now edit the file /usr/local/SlimServer_v6.0.2/Bin/build-perl-modules.pl to add some options to the XML Parser, this is because expat is installed in a non-standard location on the slug. (you need to add the XML Parser section)

my %packageOptions = (

    'Template-Toolkit-2.13' => {

        'Makefile.PL' => join(' ', qw(
            TT_DOCS=n
            TT_SPLASH=n
            TT_THEME=n
            TT_EXAMPLES=n
            TT_EXAMPLES=n
            TT_EXTRAS=n
            TT_QUIET=y
            TT_ACCEPT=y
            TT_DBI=n
            TT_LATEX=n
        )),
    },

    'DBD-SQLite-1.08' => {

        'env' => [qw(DBI-1.46/blib/lib: DBI-1.46/blib/arch)],
    },

    'XML-Parser-2.34' => {
        'Makefile.PL' => join(' ', qw(
            EXPATLIBPATH=/opt/lib
            EXPATINCPATH=/opt/include
        )),
    },

);

Now run the SlimServer script to get the missing modules

 # /usr/local/SlimServer_v6.0.2/Bin/build-perl-modules.pl

Now, give it a try..

 # cd /usr/local/SlimServer_v6.0.2
 # ./slimserver.pl --daemon --prefsfile /etc/slim-data/slimserver.pref --cachedir /etc/slim-data

A few of these steps will take a while to complete, be patient. Starting the server can be pretty slow, but it will start.

To check out the server: http://IP-address-of-your-slug:9000

I don't yet have a squeezebox, but softsqueeze seems to work with this. I do have some pauses, but I strongly suspect that this is related to the softsqueeze player and not the server. Windows media player seems to work well with slimserver, just follow the directions for remote streaming.


Ole adds: Works like a charm (note that browsing, searching etc. has been reported to be slow. If you are like me, and buy the NSLU to be a dedicated SlimServer, then you might want to take that into consideration). At the moment I do not have any unmanagable speed issues.


Fritz adds: This worked well for me with one exception. build-perl-modules.pl errored out because it could not find make. Once I added /opt/bin to my path everything worked well. Enter into the shell the following:

 # PATH=$PATH:/opt/bin
 # export PATH
 # /usr/local/SlimServer_v6.1.1/Bin/build-perl-modules.pl

Luke confirms: I had to do this step too for v6.2.2, to deal with the following error:

 # which: No such file or directory

Jan adds: For unslung 6.8 you should also add /opt/armeb/bin to your path:

 # PATH=$PATH:/opt/armeb/bin

Otherwhise the build-perl-modules.pl fails when calling gcc... Error message is Building.. armv5b-softfloat-linux-gcc: No such file or directory make: *** [Zlib.o] Error 127 Couldn't find a valid dynamic library for Compress-Zlib-1.33.tar.gz - something is wrong. Exiting!


Works in Openslug 2.5, as the perl ipk's now seem to run correctly:

 # ipkg install perl perl-modules

However, you will need to copy typemap and xsubpp from a perl source tree to the local perl library folders (they're missing for some reason):

 # wget http://ftp.funet.fi/pub/CPAN/src/perl-5.8.7.tar.gz
 # tar -xzvf perl-5.8.7.tar.gz
 # cp perl-5.8.7/lib/ExtUtils/typemap /usr/lib/perl5/5.8.7/ExtUtils/typemap
 # cp perl-5.8.7/lib/ExtUtils/xsubpp /usr/lib/perl5/5.8.7/ExtUtils/xsubpp

Then install gcc and friends:

 # ipkg install gcc gcc-symlinks binutils make libc6-dev coreutils libexpat-dev

Finally extract slimserver and compile modules:

 # wget http://www.slimdevices.com/downloads/SlimServer_v6.1.1/SlimServer_v6.1.1.tar.gz
 # cd /usr/local
 # tar -xzvf /root/SlimServer_v6.1.1.tar.gz
 # /usr/local/SlimServer_v6.1.1/Bin/build-perl-modules.pl

Note: you *will* require a decent amount of swap to run the Slimserver and even then it will be a little slow (e.g. don't try and play your entire music collection at once)


Steinar adds: SlimServer runs fine without swap on a 64MB slug. It takes about a minute to start on a 266MHz slug, 64MB, no swap, OpenSlug 2.7. File scanning, however, still takes a very, very long time (it may take hours) if the music collection is big (10,000+ tracks). Once started, SlimServer runs fast enough, except when trying to play huge playlists (it may then need a few minutes to get started). My SlimServer has a load around 60% while serving two synchronised Squeezeboxes. Memory usage is about 37MB. The web pages load a bit slowly, but are still perfectly useable.


Paul Webster adds: SlimServer 6.2.0 seems to work as well. Following same procedure (clearly .. changing the version number in the directory names) - with the modification suggested by Fritz to get "make" into the path before building. It is busy scanning at the moment. But looking forward to see if interactive performance is improved because one of the claims for 6.2 is that it speeds up some of the database accesses.


Marc Pelzer adds: "SlimServer_v6.2.1" needs the C caching application "ccache" to build the Compress-Zlib-1.33.tar.gz. You can get it from here: http://ccache.samba.org/ It compiles fine on my slug after installing all necessary dev tools (ipkg install gcc gcc-symlinks make binutils libc6-dev coreutils libexpat-dev)


Chris Kantarjiev adds: This worked just fine on Unslung5.5b with "SlimServer_v6.2.1". Except ... I wanted to run it as user slimserver instead of root. When I do that, SQLite? complains that it can't create a temporary table, even though I think I got all the permissions right. It would be good to fix this. Running fine on a 266MHz Slug, 64MB, process size is about 38M with 6600 tunes. To make WMA files work (especially for Internet radio), you'll want to load ffmpeg and lame with ipkg - note that some of the libraries you need end up in /opt/lib.


H. Lima adds: After several unsuccessful trials to use mt-daapd server and wmamp (wmam11b itunes client) I switched to Slimserver and wrote a slimp3 client for the wma11b (available here and it has been working very well for days already. If you own a wma11b you should check it out!


Could someone please turn slimserver into a complete ipkg package or maybe just offer the missing pieces. That way most of us can avoid having to install a native toolchain and compile the stuff ourselves.

Anyway I couldn't wait and I installed the crosstool-native packages + make on unslung-3.18. This works great too! I have slimserver 6.2.1 running now as user slimserver. For that, make sure the user slimserver has approriate entries in /etc/passwd and also check that /var/tmp has permissions drwxrwxrwt.


Wibbleman adds: ......IT DOES WORK - AND ITS NOT TOO COMPLICATED!!...... .......- Slug 5.5/Slim6.2.1 (Mar 2006)...... I put off loading Slimserver for a while, cause it looked far too complex for me, but I just followed the main instructions at the top of this page and it all worked, dont think I had to do anything special/undocumented. Note that on an de-underclocked SLUG it still took maybe 20mins for the build to run, and maybe 2-3 mins for slimserver to start, but it all works. Web is slow, but works. Ive only tested on a 6 file library, and interent radio, but works fine. I am away next week so maybe I will point the SLUG at my 15,000 track MP3? collection and see if its finished by the weekend!

(Update - Even scanning a small 40 song library takes ages, 10-20mins? and uses 95% CPU - what on earth is the code doing in there??. I have also installed TwonkyMedia? Server on the same box, so the same music collection can feed into SLIMP3? and Netgear MP101? players, and noted;

  SLIM SERVER V6.2.1.......feeding SLIMP3?.............30-60% CPU continuously  
  TWONKY V3.1..............feeding Netgear MP101?......a blip of 50% CPU say for 1 second every 40 seconds ? - avg <2% CPU

(The Twonky server seems to index the 40 track MP3? collection about 100x faster too!)

UPDATE II.. Ok, Slimserver is now running MUCH better. There was an "httpd" process that kept appearing, consuming up to 90% CPU, that was causing the problem. I assumed this was the slim server web interface, but not sure it was. If I "kill -9" the process then everything speeds up to an acceptable level, similar to what other users are reporting. I also added extra swap space, but for some reason I dont think that was the main reason its speeded up. Yes, it is now acceptable and usable - with the performance before it was just not usable. The 30-60% CPU utilisation of slimserver.pl (as detailed above) is the same, but its usuable. [One remaining problem, a couple of times the slimserver has hung for about 5-9 minutes at the end of a track, then continues on without problem - not investigated this yet]


(Comment: I run SlimServer 6.2.0 on a turbo-slug, Unslung 5.5, lotsa swapspace. My collection amounts to about 12000 mp3, scanning them all and building the database (16M big) takes about 6 hours. It's OK AFAIK, it happens at night while I'm catching some Z's. Remains to see how fast/slow the rescanning is. My SqueezeBox? works just fine with the server, with a few exceptions. Browsing is smooth enough, but *asking* for a particular bunch of information takes a little while. For example, when I do "Browse genre" there's a slight delay in the box before it responds - obviously this is because the slug can't perform the query fast enough. Once the information has been queried, browsing it is fine. The streaming works just fine, occasionally (like once every 3-4 hours) there's a short pause in the stream, in between tunes. All in all it's acceptable, but I suspect that a collection with over 20 000 mp3's could prove to be too much.)


flipflip adds: I successfully installed SlimServer 6.2.1 on a Synology Diskstation 101j (Firmware 2.0.1 - 3.0281).
Update Apr 17 06: This is now documented and available for download here: [http://oinkzwurgl.org/software/slimserver]


dan adds: those of you who have ogg vorbis files in your collection will need a couple extra steps... first, install the ivorbis-tools ipkg, then find the convert.conf file in your slimserver dir and swap all the ogg stanzas using sox (which doesn't support using tremor yet) for the ones using oggdec (also, something is afoot with the oggdec -R option where it wants an argument, but doesn't seem to care what the arg is, hence the "x" below). Then, you'll notice running oggdec and lame at the same time chokes the poor slug. I couldn't figure out how to get the ogg-to-wav section to be the only one, so I had to modify the ogg-to-mp3 one to look like this:

ogg mp3 * *

        [oggdec] --raw x -Q -o - $FILE$

So now my oggs and mp3s are both happily playing (under SlimServer 6.2.2). I second the SQL-slowness comment above - took a quick look and it seems like there's potential to speed up the couple crucial queries, especially if you don't use moodmagic and might be willing to have it not remember where in the browse lists you last were. Haven't poked into it too deeply yet though.


flipflip adds: Users of a DS101j? NAS might want to try my easy way of installing SlimServer using the firmware upgrade function of the DS. Yes, that's right, there's no need to enable telnet or poke around in a shell to make it running. Check my homepage at [http://oinkzwrugl.org/software/ssods/] and the threads in the slimdevices forum at [http://forums.slimdevices.com/showthread.php?p=110216#post110216] (English) and [http://forums.slimdevices.com/showthread.php?p=110220#post110220] (Deutsch) for further details. Regards, flipflip


ajcooper adds: I've installed Slimserver with no problems, however there are two things missing. One, when I restart by NSLU2 I have to telnet in and manually restart the slimserver, can this be automated? Also, alot of my collection is AAC format (unprotected) - can I install a decoder or do I have to change everything over to MP3??


headworx adds: works like a charm, I added autostart for Slimserver - the details are on my blog: [http://techbulletins.blogspot.com/2006/08/slimserver-embedded.html]


excubey adds: I did it a little differently from headworx, adding a simple start script in the /opt/etc/init.d directory . I called S100slim (could be anything), and added these lines using vi:

(pound symbol)!/bin/sh
/slim

Once you do that, be sure to chmod +x S100slim to make it executable. You can see we are calling another script called "slim" For me, it looks like this: (modelled on nslu2-linux's slimserver install instructions), I store it in the root dir

cd /usr/local/SlimServer_v6.3.0
./slimserver.pl --daemon --prefsfile /etc/slim-data/slimserver.pref --cachedir /etc/slim-data

That's it!


something changed. Several people (including me) have problems to install (make) slimserver. Have a look at the folloeing links: http://forums.slimdevices.com/showthread.php?t=27162 http://forums.slimdevices.com/showthread.php?t=26723

Any ideas what happened?

Nigel adds: SlimServer_6.2.1 was working fine with Unslung 5.5Beta. I upgraded using ipkg for about the first time in six months. The result is a missing libexpat.so.0 as the replacement expat package has moved on to libexpat.so.1. While SlimServer _v6.2.1 and _v6.3.1 both rebuilt/built OK and run, neither play some internet radios URLs?. They fetch and even bring up the spectrum display just before starting the audio but then drop back. The problem is SlimServer side as SlimServer on a PC works fine. Using libexpat.so.1 causes Apache to crash so it looks as if the two versions of libexpat are not binary compatible. Thus a 'crude fix' using a symlink does not work either. 'Googling' shows the problem of Apache and libexpat Suse 10.0. If you have a working SlimServer on Unslung5.5Beta stay away from ipkg upgrade at the moment. I forced expat back to Libexpat.so.0 but that does not work either. It looks like packages have become incompatible. Hoping it will get fixed soon as it beyond my ability to tackle.


I found a pre-compiled tar-ball (http://homepage.eircom.net/~altondsl/slim/SlimServer_v6.3.1arm.tar.gz) of SlimServer 6.3.1 on OpenFSG Forums (http://www.openfsg.com/forum/viewtopic.php?p=9964#9964) that works on Unslung 5.8Beta. Just unpack it and run it, don't try to compile.

Many thanks to Bryan who made the tar-ball. Now I can enjoy my music again!


Next to BPA's precompiled SlimServer_v6.3.1 it is also not very difficult to install version 6.5.1 (do not install 6.5.0 since 6.5.1 has less bugs and give much less troubles, I even thinks it uses less resources).

Installing version 6.5.1 it quite simular as the version described above.

Before you start create a new user which will run SlimServer, it cannot be root. Most people use "slim", you can create it wit the web interface of the slug.

Before unpacking the tarball install MySQL with:

 # dpkg install mysql

After the succesfull installation remove the MySQL diversion script (or symbolic link) in /opt/etc/init.s/Sxxmysqld

Next change the path in:

 # export PATH=$PATH/sbin:/bin:/usr/sbin:/usr/bin:/opt/bin:/opt/armeb/bin:/opt/bin:/opt/sbin:/opt/bin:/opt/bin:/opt/armeb/bin:/opt/libexec:/opt/sbin:/opt/libexec

Make the user "slim" owner of your music directory, /usr/local/slimserver and /etc/sim-data I've made it myself simple by using:

 # chown -R slim /etc/slim-data
 # chown -R slim /usr/local/slimserver
 # chown -R slim /<your music directory>

Now you can run "build-perl-modules.pl",possibly you run into troubles with Compress-Zlib-1.41. This can be resolved by going to the directory where Compress-Zlib-1.41 and run the following commands:

 # perl Makefile.PL
 # make
 # make install

Atfer this you can run "build-perl-modules.pl" again. Now it should complete without critical errors.

When it is finished go to the directory /usr/local/slimserver/MySQL and change the file "my.tt". Put a # for the line "inno_db_fast_shutdown=1".

If everything goes as planned you can start with (being is the installation directory):

 # ./slimserver.pl --daemon --user slim --prefsfile /etc/slim-data/slimserver.pref --cachedir /etc/slim-data --cliport 0 --pidfile /usr/local/slimserver/slimserver.pid --logfile /usr/local/slimserver/log/slimserver.log

The log file is usefull trouble shooting. Be sure making the log-directory with:

 # mkdir /usr/local/slimserver/log

For trouble shooting you can use:

 # ./slimserver.pl --user slim --prefsfile /etc/slim-data/slimserver.pref --cachedir /etc/slim-data --d_server --d_scan

Step by step you can see what the SlimServer is doing and see where the problems arise. You can stop the SlimServer with ^c.

Using the webinterface is sluggish.

The procedure I descibed above worked for me serveral times, I've put it together reading several topics on the slimdevices forum. It does not work for releases below version 6.5.0.


I did not get far :

  1. /usr/local/SlimServer_v6.5.1/Bin/build-perl-modules.pl

Can't locate File/Which.pm in @INC (@INC contains: /usr/local/slimserver/CPAN CP AN /opt/lib/perl5/5.8.8/armv5b-linux /opt/lib/perl5/5.8.8 /opt/lib/perl5/site_pe rl/5.8.8/armv5b-linux /opt/lib/perl5/site_perl/5.8.8 /opt/lib/perl5/site_perl .)

 at /usr/local/SlimServer_v6.5.1/Bin/build-perl-modules.pl line 20.

BEGIN failed--compilation aborted at /usr/local/SlimServer_v6.5.1/Bin/build-perl -modules.pl line 20.

it had to be /usr/local/slimserver ... so I had to rename 'mv /usr/local/SlimServer_v6.5.1 /usr/local/slimserver'

and PATH=$PATH:/opt/armeb/bin export PATH

then it ran but .....

Downloading DBD-mysql-3.0002.tar.gz to: /public Uncompressing.. Configuring.. PERL5LIB?=/public/DBI-1.50/blib/lib:/public/DBI-1.50/blib/arch /usr/bin/perl Make file.PL Can't exec "mysql_config": No such file or directory at Makefile.PL line 76. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Failed to determine directory of mysql.h. Use

  perl Makefile.PL --cflags=-I<dir>

This is just all too painful

to:

Installing Slimserver on the NSLU2

This guide is mostly copied from http://www.openfsg.com/forum/viewtopic.php?p=14920#14920 . All credits go to *bpa of openfsg.com*. You can find the outdated NSLU2 SlimServer doc at SlimServerOld.

Downloading

You can find the current build of Slimserver 6.5.1 here. The slimserver code is final but the supporting scripts are not quite finished.

http://homepage.eircom.net/~altondsl/slim/ss65_6.5.1-1_armeb.ipk

You can use a browser or wget or curl to downloads the file onto the NSLU2.

Installing

This install puts files in the following directories - so if you already use them move your files elsewhere. /home/slimserver /opt/share/ss65

  • Login as root
  • You must have the ipkg bootstrap 1.05 or better installed.
  • Install the perl, expat and mysql packages. The slimserver ipkg will request them but it is better to do manually in case there are problems, you'll know where to look.

ipkg install perl expat mysql

  • Create the /home/slimserver folder, and add the slimserver group (edit /etc/group) and slimserver user (edit /etc/passwd).
  • Change current directory to where the ss65_6.5.1-1_armeb.ipk has been saved.
  • install the Slimserserver package with the command

ipkg install ss65_6.5.1-1_armeb.ipk

  • If it install goes OK, try the command

slimserver

The response should be Usage: /opt/bin/slimserver {start|stop|status|enable|disable|firewall|wanenable|wandisable|info}

  • If it works. then try

slimserver info

  • To start slimserver used the command below - it will take a couple of minutes before your see a "Slimserver Started message"

slimserver start

  • To see progress through log file you can do

tail /home/slimserver/slimserver.log

The following is a normal start - the last line about port 9000 indicate web interface is ready.

# tail /home/slimserver/slimserver.log http://nslu2:9000/ 2007-01-22 20:39:37.8519 Attempt to free unreferenced scalar: SV 0x1bc6b4c. 2007-01-22 20:40:51.0064 Use of uninitialized value in join or string at /opt/lib/perl5/5.8.8/File/Spec/Unix.pm line 81. 2007-01-22 20:42:07.4538 Your data source needs to be configured. Please open your web browser, 2007-01-22 20:42:07.4763 go to the following URL, and click on the "Server Settings" link. 2007-01-22 20:42:07.4785 The URL to access SlimServer is now: http://nslu2:9000/

  • If you wish to access slimserver by web from WAN port open firewall with

slimserver firewall.

  • By default slimserver will start as part of boot - if you do not want this then use

slimserver disable.

There is an issue with this build - there seems to be too many mysql processes started. *bpa of openfsg.com* is looking into it.

April 22, 2007, at 10:05 PM by Ag --
Changed lines 285-305 from:
to:

then it ran but .....

Downloading DBD-mysql-3.0002.tar.gz to: /public Uncompressing.. Configuring.. PERL5LIB?=/public/DBI-1.50/blib/lib:/public/DBI-1.50/blib/arch /usr/bin/perl Make file.PL Can't exec "mysql_config": No such file or directory at Makefile.PL line 76. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Can't exec "mysql_config": No such file or directory at Makefile.PL line 454. Failed to determine directory of mysql.h. Use

  perl Makefile.PL --cflags=-I<dir>

This is just all too painful

April 22, 2007, at 09:50 PM by Ag --
Added lines 278-285:

it had to be /usr/local/slimserver ... so I had to rename 'mv /usr/local/SlimServer_v6.5.1 /usr/local/slimserver'

and PATH=$PATH:/opt/armeb/bin export PATH

April 22, 2007, at 09:38 PM by Ag --
Changed lines 266-269 from:
to:

I did not get far :

April 22, 2007, at 09:37 PM by Ag --
Added lines 265-274:
  1. /usr/local/SlimServer_v6.5.1/Bin/build-perl-modules.pl

Can't locate File/Which.pm in @INC (@INC contains: /usr/local/slimserver/CPAN CP AN /opt/lib/perl5/5.8.8/armv5b-linux /opt/lib/perl5/5.8.8 /opt/lib/perl5/site_pe rl/5.8.8/armv5b-linux /opt/lib/perl5/site_perl/5.8.8 /opt/lib/perl5/site_perl .)

 at /usr/local/SlimServer_v6.5.1/Bin/build-perl-modules.pl line 20.

BEGIN failed--compilation aborted at /usr/local/SlimServer_v6.5.1/Bin/build-perl -modules.pl line 20.

February 03, 2007, at 10:45 PM by indexx --
Deleted lines 264-268:

comment: installation of slimserver 6.5.1 runs fine here. all perl modules are built and the server starts. but rescaning the music directory fails with the following error (slimserver.log):

ERROR: DBD::mysql::db commit failed: Commmit ineffective while AutoCommit? is on at /usr/local/SlimServer_v6.5.1/CPAN/DBIx?/Class/Storage/DBI.pm line 706.

February 03, 2007, at 09:51 PM by indexx --
Changed lines 267-268 from:

installation of slimserver 6.5.1 runs fine. all perl modules are built and the server starts. but rescaning the music directory fails with the following error (slimserver.log):

to:

comment: installation of slimserver 6.5.1 runs fine here. all perl modules are built and the server starts. but rescaning the music directory fails with the following error (slimserver.log):

February 03, 2007, at 09:49 PM by indexx --
Changed lines 264-269 from:

The procedure I descibed above worked for me serveral times, I've put it together reading several topics on the slimdevices forum. It does not work for releases below version 6.5.0.

to:

The procedure I descibed above worked for me serveral times, I've put it together reading several topics on the slimdevices forum. It does not work for releases below version 6.5.0.


installation of slimserver 6.5.1 runs fine. all perl modules are built and the server starts. but rescaning the music directory fails with the following error (slimserver.log):

ERROR: DBD::mysql::db commit failed: Commmit ineffective while AutoCommit? is on at /usr/local/SlimServer_v6.5.1/CPAN/DBIx?/Class/Storage/DBI.pm line 706.

January 05, 2007, at 08:49 PM by Michel -- Updated installation for release 6.5.x
Changed lines 220-264 from:

Many thanks to Bryan who made the tar-ball. Now I can enjoy my music again!

to:

Many thanks to Bryan who made the tar-ball. Now I can enjoy my music again!


Next to BPA's precompiled SlimServer_v6.3.1 it is also not very difficult to install version 6.5.1 (do not install 6.5.0 since 6.5.1 has less bugs and give much less troubles, I even thinks it uses less resources).

Installing version 6.5.1 it quite simular as the version described above.

Before you start create a new user which will run SlimServer, it cannot be root. Most people use "slim", you can create it wit the web interface of the slug.

Before unpacking the tarball install MySQL with:

 # dpkg install mysql

After the succesfull installation remove the MySQL diversion script (or symbolic link) in /opt/etc/init.s/Sxxmysqld

Next change the path in:

 # export PATH=$PATH/sbin:/bin:/usr/sbin:/usr/bin:/opt/bin:/opt/armeb/bin:/opt/bin:/opt/sbin:/opt/bin:/opt/bin:/opt/armeb/bin:/opt/libexec:/opt/sbin:/opt/libexec

Make the user "slim" owner of your music directory, /usr/local/slimserver and /etc/sim-data I've made it myself simple by using:

 # chown -R slim /etc/slim-data
 # chown -R slim /usr/local/slimserver
 # chown -R slim /<your music directory>

Now you can run "build-perl-modules.pl",possibly you run into troubles with Compress-Zlib-1.41. This can be resolved by going to the directory where Compress-Zlib-1.41 and run the following commands:

 # perl Makefile.PL
 # make
 # make install

Atfer this you can run "build-perl-modules.pl" again. Now it should complete without critical errors.

When it is finished go to the directory /usr/local/slimserver/MySQL and change the file "my.tt". Put a # for the line "inno_db_fast_shutdown=1".

If everything goes as planned you can start with (being is the installation directory):

 # ./slimserver.pl --daemon --user slim --prefsfile /etc/slim-data/slimserver.pref --cachedir /etc/slim-data --cliport 0 --pidfile /usr/local/slimserver/slimserver.pid --logfile /usr/local/slimserver/log/slimserver.log

The log file is usefull trouble shooting. Be sure making the log-directory with:

 # mkdir /usr/local/slimserver/log

For trouble shooting you can use:

 # ./slimserver.pl --user slim --prefsfile /etc/slim-data/slimserver.pref --cachedir /etc/slim-data --d_server --d_scan

Step by step you can see what the SlimServer is doing and see where the problems arise. You can stop the SlimServer with ^c.

Using the webinterface is sluggish.

The procedure I descibed above worked for me serveral times, I've put it together reading several topics on the slimdevices forum. It does not work for releases below version 6.5.0.

November 17, 2006, at 01:14 PM by Lars Persson Fink --
Changed lines 218-219 from:

I found a pre-compiled tar-ball (http://homepage.eircom.net/~altondsl/slim/SlimServer_v6.3.1arm.tar.gz) of SlimServer 6.3.1 on !OpenFSG? Forums (http://www.openfsg.com/forum/viewtopic.php?p=9964#9964) that works on Unslung 5.8Beta. Just unpack it and run it, don't try to compile.

to:

I found a pre-compiled tar-ball (http://homepage.eircom.net/~altondsl/slim/SlimServer_v6.3.1arm.tar.gz) of SlimServer 6.3.1 on OpenFSG Forums (http://www.openfsg.com/forum/viewtopic.php?p=9964#9964) that works on Unslung 5.8Beta. Just unpack it and run it, don't try to compile.

November 17, 2006, at 01:11 PM by Lars Persson Fink --
Changed lines 218-219 from:

I found a pre-compiled tar-ball (http://homepage.eircom.net/~altondsl/slim/SlimServer_v6.3.1arm.tar.gz) of SlimServer 6.3.1 on OpenFSG? Forums (http://www.openfsg.com/forum/viewtopic.php?p=9964#9964) that works on Unslung 5.8Beta. Just unpack it and run it, don't try to compile.

to:

I found a pre-compiled tar-ball (http://homepage.eircom.net/~altondsl/slim/SlimServer_v6.3.1arm.tar.gz) of SlimServer 6.3.1 on !OpenFSG? Forums (http://www.openfsg.com/forum/viewtopic.php?p=9964#9964) that works on Unslung 5.8Beta. Just unpack it and run it, don't try to compile.

November 17, 2006, at 01:10 PM by Lars Persson Fink -- Pre-compiled tar-ball of SlimServer 6.3.1 available
Added lines 216-220:

I found a pre-compiled tar-ball (http://homepage.eircom.net/~altondsl/slim/SlimServer_v6.3.1arm.tar.gz) of SlimServer 6.3.1 on OpenFSG? Forums (http://www.openfsg.com/forum/viewtopic.php?p=9964#9964) that works on Unslung 5.8Beta. Just unpack it and run it, don't try to compile.

Many thanks to Bryan who made the tar-ball. Now I can enjoy my music again!

September 17, 2006, at 02:04 PM by Nigel Gerdes --
Changed line 215 from:

SlimServer_6.2.1 was working fine with Unslung 5.5Beta. I upgraded using ipkg for about the first time in six months. The result is a missing libexpat.so.0 as the replacement expat package has moved on to libexpat.so.1. While SlimServer _v6.2.1 and _v6.3.1 both rebuilt/built OK and run, neither play some internet radios URLs?. They fetch and even bring up the spectrum display just before starting the audio but then drop back. The problem is SlimServer side as SlimServer on a PC works fine. Using libexpat.so.1 causes Apache to crash so it looks as if the two versions of libexpat are not binary compatible. Thus a 'crude fix' using a symlink does not work either. 'Googling' shows the problem of Apache and libexpat Suse 10.0. If you have a working SlimServer on Unslung5.5Beta stay away from ipkg upgrade at the moment. I forced expat back to Libexpat.so.0 but that does not work either. It looks like packages have become incompatible. Hoping it will get fixed soon as it beyond my ability to tackle.

to:

Nigel adds: SlimServer_6.2.1 was working fine with Unslung 5.5Beta. I upgraded using ipkg for about the first time in six months. The result is a missing libexpat.so.0 as the replacement expat package has moved on to libexpat.so.1. While SlimServer _v6.2.1 and _v6.3.1 both rebuilt/built OK and run, neither play some internet radios URLs?. They fetch and even bring up the spectrum display just before starting the audio but then drop back. The problem is SlimServer side as SlimServer on a PC works fine. Using libexpat.so.1 causes Apache to crash so it looks as if the two versions of libexpat are not binary compatible. Thus a 'crude fix' using a symlink does not work either. 'Googling' shows the problem of Apache and libexpat Suse 10.0. If you have a working SlimServer on Unslung5.5Beta stay away from ipkg upgrade at the moment. I forced expat back to Libexpat.so.0 but that does not work either. It looks like packages have become incompatible. Hoping it will get fixed soon as it beyond my ability to tackle.

September 17, 2006, at 02:01 PM by Nigel Gerdes --
Changed line 215 from:

SlimeServer?_6.2.1 was working fine with Unslung 5.5Beta. I upgraded using ipkg for about the first time in six months. The result is a missing libexpat.so.0 as the replacement expat package has moved on to libexpat.so.1. While SlimServer _v6.2.1 and _v6.3.1 both rebuilt/built OK and run, neither play some internet radios URLs?. They fetch and even bring up the spectrum display just before starting the audio but then drop back. The problem is SlimServer side as SlimServer on a PC works fine. Using libexpat.so.1 causes Apache to crash so it looks as if the two versions of libexpat are not binary compatible. Thus a 'crude fix' using a symlink does not work either. 'Googling' shows the problem of Apache and libexpat Suse 10.0. If you have a working SlimServer on Unslung5.5Beta stay away from ipkg upgrade at the moment. I forced expat back to Libexpat.so.0 but that does not work either. It looks like packages have become incompatible. Hoping it will get fixed soon as it beyond my ability to tackle.

to:

SlimServer_6.2.1 was working fine with Unslung 5.5Beta. I upgraded using ipkg for about the first time in six months. The result is a missing libexpat.so.0 as the replacement expat package has moved on to libexpat.so.1. While SlimServer _v6.2.1 and _v6.3.1 both rebuilt/built OK and run, neither play some internet radios URLs?. They fetch and even bring up the spectrum display just before starting the audio but then drop back. The problem is SlimServer side as SlimServer on a PC works fine. Using libexpat.so.1 causes Apache to crash so it looks as if the two versions of libexpat are not binary compatible. Thus a 'crude fix' using a symlink does not work either. 'Googling' shows the problem of Apache and libexpat Suse 10.0. If you have a working SlimServer on Unslung5.5Beta stay away from ipkg upgrade at the moment. I forced expat back to Libexpat.so.0 but that does not work either. It looks like packages have become incompatible. Hoping it will get fixed soon as it beyond my ability to tackle.

September 17, 2006, at 01:58 PM by Nigel Gerdes -- Problem with ipkg and libexpat.so.0
Changed lines 212-216 from:

Any ideas what happened?

to:

Any ideas what happened?

SlimeServer?_6.2.1 was working fine with Unslung 5.5Beta. I upgraded using ipkg for about the first time in six months. The result is a missing libexpat.so.0 as the replacement expat package has moved on to libexpat.so.1. While SlimServer _v6.2.1 and _v6.3.1 both rebuilt/built OK and run, neither play some internet radios URLs?. They fetch and even bring up the spectrum display just before starting the audio but then drop back. The problem is SlimServer side as SlimServer on a PC works fine. Using libexpat.so.1 causes Apache to crash so it looks as if the two versions of libexpat are not binary compatible. Thus a 'crude fix' using a symlink does not work either. 'Googling' shows the problem of Apache and libexpat Suse 10.0. If you have a working SlimServer on Unslung5.5Beta stay away from ipkg upgrade at the moment. I forced expat back to Libexpat.so.0 but that does not work either. It looks like packages have become incompatible. Hoping it will get fixed soon as it beyond my ability to tackle.

September 11, 2006, at 07:26 PM by groucho --
Changed lines 206-212 from:

That's it!

to:

That's it!


something changed. Several people (including me) have problems to install (make) slimserver. Have a look at the folloeing links: http://forums.slimdevices.com/showthread.php?t=27162 http://forums.slimdevices.com/showthread.php?t=26723

Any ideas what happened?

September 02, 2006, at 09:22 PM by excubey --
Changed lines 195-196 from:

excubey adds: to add a simple start script, place it in the /opt/etc/inid.d directory and call it for instance S100slim, add these lines using vi or whatever:

to:

excubey adds: I did it a little differently from headworx, adding a simple start script in the /opt/etc/init.d directory . I called S100slim (could be anything), and added these lines using vi:

Changed line 200 from:

then be sure to chmod +x S100slim to make it executable. You can see we are calling another script called "slim"

to:

Once you do that, be sure to chmod +x S100slim to make it executable. You can see we are calling another script called "slim"

September 02, 2006, at 09:14 PM by excubey --
Changed line 203 from:

cd /usr/local/SlimServer_v6.3.0

to:

cd /usr/local/SlimServer_v6.3.0 \\

September 02, 2006, at 09:14 PM by excubey --
Changed line 197 from:

(pound symbol)!/bin/sh

to:

(pound symbol)!/bin/sh \\

September 02, 2006, at 09:13 PM by excubey --
Changed lines 195-197 from:

excubey adds: a simple start script, placed in the /in /opt/etc/inid.d call it for instance called S100slim, add these lines using vi or whatever:

to:

excubey adds: to add a simple start script, place it in the /opt/etc/inid.d directory and call it for instance S100slim, add these lines using vi or whatever:

September 02, 2006, at 09:12 PM by excubey --
Changed line 198 from:
  1. !/bin/sh
to:

(pound symbol)!/bin/sh

September 02, 2006, at 09:11 PM by excubey --
Changed lines 197-198 from:

"#!/bin/sh

to:
  1. !/bin/sh
September 02, 2006, at 09:11 PM by excubey --
Changed line 197 from:

="#!/bin/sh

to:

"#!/bin/sh

Changed line 199 from:

=

to:
Changed line 202 from:

=

to:
Changed line 205 from:

=

to:
September 02, 2006, at 09:10 PM by excubey --
Changed lines 197-198 from:
  1. !/bin/sh
to:

="#!/bin/sh

Changed line 199 from:
to:

=

Changed line 202 from:
to:

=

Changed line 205 from:
to:

=

September 02, 2006, at 09:09 PM by excubey -- easy startup for slimserver
Changed lines 193-207 from:

headworx adds: works like a charm, I added autostart for Slimserver - the details are on my blog: [http://techbulletins.blogspot.com/2006/08/slimserver-embedded.html]

to:

headworx adds: works like a charm, I added autostart for Slimserver - the details are on my blog: [http://techbulletins.blogspot.com/2006/08/slimserver-embedded.html]


excubey adds: a simple start script, placed in the /in /opt/etc/inid.d call it for instance called S100slim, add these lines using vi or whatever:

  1. !/bin/sh

/slim

then be sure to chmod +x S100slim to make it executable. You can see we are calling another script called "slim" For me, it looks like this: (modelled on nslu2-linux's slimserver install instructions), I store it in the root dir

cd /usr/local/SlimServer_v6.3.0 ./slimserver.pl --daemon --prefsfile /etc/slim-data/slimserver.pref --cachedir /etc/slim-data

That's it!

August 28, 2006, at 07:10 PM by Jan -- addition to previous message
Changed lines 114-117 from:
  1. PATH=$PATH:/opt/armeb/bin

Otherwhise the build-perl-modules.pl fails when calling gcc...

to:
 # PATH=$PATH:/opt/armeb/bin

Otherwhise the build-perl-modules.pl fails when calling gcc... Error message is Building.. armv5b-softfloat-linux-gcc: No such file or directory make: *** [Zlib.o] Error 127 Couldn't find a valid dynamic library for Compress-Zlib-1.33.tar.gz - something is wrong. Exiting!

August 28, 2006, at 06:59 PM by Jan -- Addition for unslung 6.8
Added lines 113-117:

Jan adds: For unslung 6.8 you should also add /opt/armeb/bin to your path:

  1. PATH=$PATH:/opt/armeb/bin

Otherwhise the build-perl-modules.pl fails when calling gcc...

August 21, 2006, at 05:29 PM by headworx --
Changed lines 182-184 from:

ajcooper adds: I've installed Slimserver with no problems, however there are two things missing. One, when I restart by NSLU2 I have to telnet in and manually restart the slimserver, can this be automated? Also, alot of my collection is AAC format (unprotected) - can I install a decoder or do I have to change everything over to MP3??

to:

ajcooper adds: I've installed Slimserver with no problems, however there are two things missing. One, when I restart by NSLU2 I have to telnet in and manually restart the slimserver, can this be automated? Also, alot of my collection is AAC format (unprotected) - can I install a decoder or do I have to change everything over to MP3??


headworx adds: works like a charm, I added autostart for Slimserver - the details are on my blog: [http://techbulletins.blogspot.com/2006/08/slimserver-embedded.html]

June 23, 2006, at 05:17 AM by ajcooper -- New install -auto start and AAC
Changed lines 180-182 from:

flipflip adds: Users of a DS101j? NAS might want to try my easy way of installing SlimServer using the firmware upgrade function of the DS. Yes, that's right, there's no need to enable telnet or poke around in a shell to make it running. Check my homepage at [http://oinkzwrugl.org/software/ssods/] and the threads in the slimdevices forum at [http://forums.slimdevices.com/showthread.php?p=110216#post110216] (English) and [http://forums.slimdevices.com/showthread.php?p=110220#post110220] (Deutsch) for further details. Regards, flipflip

to:

flipflip adds: Users of a DS101j? NAS might want to try my easy way of installing SlimServer using the firmware upgrade function of the DS. Yes, that's right, there's no need to enable telnet or poke around in a shell to make it running. Check my homepage at [http://oinkzwrugl.org/software/ssods/] and the threads in the slimdevices forum at [http://forums.slimdevices.com/showthread.php?p=110216#post110216] (English) and [http://forums.slimdevices.com/showthread.php?p=110220#post110220] (Deutsch) for further details. Regards, flipflip


ajcooper adds: I've installed Slimserver with no problems, however there are two things missing. One, when I restart by NSLU2 I have to telnet in and manually restart the slimserver, can this be automated? Also, alot of my collection is AAC format (unprotected) - can I install a decoder or do I have to change everything over to MP3??

May 17, 2006, at 10:16 PM by flipflip -- Added Links to an easy installable SlimServer package for the DS101j
Changed lines 178-180 from:

So now my oggs and mp3s are both happily playing (under SlimServer 6.2.2). I second the SQL-slowness comment above - took a quick look and it seems like there's potential to speed up the couple crucial queries, especially if you don't use moodmagic and might be willing to have it not remember where in the browse lists you last were. Haven't poked into it too deeply yet though.

to:

So now my oggs and mp3s are both happily playing (under SlimServer 6.2.2). I second the SQL-slowness comment above - took a quick look and it seems like there's potential to speed up the couple crucial queries, especially if you don't use moodmagic and might be willing to have it not remember where in the browse lists you last were. Haven't poked into it too deeply yet though.


flipflip adds: Users of a DS101j? NAS might want to try my easy way of installing SlimServer using the firmware upgrade function of the DS. Yes, that's right, there's no need to enable telnet or poke around in a shell to make it running. Check my homepage at [http://oinkzwrugl.org/software/ssods/] and the threads in the slimdevices forum at [http://forums.slimdevices.com/showthread.php?p=110216#post110216] (English) and [http://forums.slimdevices.com/showthread.php?p=110220#post110220] (Deutsch) for further details. Regards, flipflip

May 14, 2006, at 09:52 PM by dk --
Changed lines 171-178 from:

Update Apr 17 06: This is now documented and available for download here: [http://oinkzwurgl.org/software/slimserver]

to:

Update Apr 17 06: This is now documented and available for download here: [http://oinkzwurgl.org/software/slimserver]


dan adds: those of you who have ogg vorbis files in your collection will need a couple extra steps... first, install the ivorbis-tools ipkg, then find the convert.conf file in your slimserver dir and swap all the ogg stanzas using sox (which doesn't support using tremor yet) for the ones using oggdec (also, something is afoot with the oggdec -R option where it wants an argument, but doesn't seem to care what the arg is, hence the "x" below). Then, you'll notice running oggdec and lame at the same time chokes the poor slug. I couldn't figure out how to get the ogg-to-wav section to be the only one, so I had to modify the ogg-to-mp3 one to look like this:

ogg mp3 * *

        [oggdec] --raw x -Q -o - $FILE$

So now my oggs and mp3s are both happily playing (under SlimServer 6.2.2). I second the SQL-slowness comment above - took a quick look and it seems like there's potential to speed up the couple crucial queries, especially if you don't use moodmagic and might be willing to have it not remember where in the browse lists you last were. Haven't poked into it too deeply yet though.

May 09, 2006, at 07:22 PM by Werner Teeling -- @comment Fritz: added \'enter into the shell the following\' (commands), to make clear it is not an edit in the .pl file. (Confused me, as it might confuse other linux-starters)
Added line 105:

Enter into the shell the following:

May 06, 2006, at 10:10 PM by Luke --
Changed line 109 from:

Luke confirms: I had to do this step too for v6.2.2, to deal with an error

to:

Luke confirms: I had to do this step too for v6.2.2, to deal with the following error:

May 06, 2006, at 10:09 PM by Luke -- confirmed user suggestion to add opt/bin to path
Added lines 109-111:

Luke confirms: I had to do this step too for v6.2.2, to deal with an error

 # which: No such file or directory
April 17, 2006, at 12:40 AM by flipflip -- redundant text replaced with a link to the original page
Changed lines 166-168 from:

flipflip adds: I successfully installed SlimServer 6.2.1 on a Synology Diskstation 101j (Firmware 2.0.1 - 3.0281). This is roughly how I did it. Enabled telnet using an USB2IDE? connector and the ext2.sys driver for windows. Bootstrapped as in DS101BootStrap (see my comments on that page). Installed (ipkg) some tools (vim perl expat unslung-devel bash bc bzip2 tar findutils file grep coreutils gzip lsof rsync sqlite which zlib). Then I took perl from the openslug/cross/3.6-beta feed (packages perl, libperl, perl-dev, perl-misc, perl-pod and perl-module-*). Since those would install in /usr i manually installed them using something like ar x .. ; tar --strip-path=2 -xzvf data.tar.gz for each package with the help of bash. Then I took GCC from NativeFloatingPointToolchain. Since the arch on my DS101j? is armeb-linux I had to link the GCC binaries to the right name (e.g. armv5b-softfloat-linux-gcc to armeb-linux-gcc). Slimserver's Bin/build_perl_modules (or so) did not work for me. So I just got all the necessary tarballs and built and installed them manually (note: you do not really need ccache as somebody pointed out above, just eliminate all ccache from the Makefiles so that it does gcc directly). That's it! Roughly, as said.

I have about 5500 mp3 files (~30GB). Indexing took less than one hour. Re-indexing takes about 5 minutes (2 albums added, some id3 changes in a few albums). Starting Slimserver takes about 1 minute. After that it uses 18MB of RAM, still leaving a few MBs? for cache and all Diskstations Services running. Playing an mp3 slimserver uses a few CPU percents. Operation on the player is smooth, searching etc. reacts almost immediately. The webinterface ain't that smooth, but is absolutely usable.

to:

flipflip adds: I successfully installed SlimServer 6.2.1 on a Synology Diskstation 101j (Firmware 2.0.1 - 3.0281).
Update Apr 17 06: This is now documented and available for download here: [http://oinkzwurgl.org/software/slimserver]

March 30, 2006, at 07:15 PM by flipflip -- Report on successful installation on a DS101j
Changed lines 164-168 from:

(Comment: I run SlimServer 6.2.0 on a turbo-slug, Unslung 5.5, lotsa swapspace. My collection amounts to about 12000 mp3, scanning them all and building the database (16M big) takes about 6 hours. It's OK AFAIK, it happens at night while I'm catching some Z's. Remains to see how fast/slow the rescanning is. My SqueezeBox? works just fine with the server, with a few exceptions. Browsing is smooth enough, but *asking* for a particular bunch of information takes a little while. For example, when I do "Browse genre" there's a slight delay in the box before it responds - obviously this is because the slug can't perform the query fast enough. Once the information has been queried, browsing it is fine. The streaming works just fine, occasionally (like once every 3-4 hours) there's a short pause in the stream, in between tunes. All in all it's acceptable, but I suspect that a collection with over 20 000 mp3's could prove to be too much.)

to:

(Comment: I run SlimServer 6.2.0 on a turbo-slug, Unslung 5.5, lotsa swapspace. My collection amounts to about 12000 mp3, scanning them all and building the database (16M big) takes about 6 hours. It's OK AFAIK, it happens at night while I'm catching some Z's. Remains to see how fast/slow the rescanning is. My SqueezeBox? works just fine with the server, with a few exceptions. Browsing is smooth enough, but *asking* for a particular bunch of information takes a little while. For example, when I do "Browse genre" there's a slight delay in the box before it responds - obviously this is because the slug can't perform the query fast enough. Once the information has been queried, browsing it is fine. The streaming works just fine, occasionally (like once every 3-4 hours) there's a short pause in the stream, in between tunes. All in all it's acceptable, but I suspect that a collection with over 20 000 mp3's could prove to be too much.)


flipflip adds: I successfully installed SlimServer 6.2.1 on a Synology Diskstation 101j (Firmware 2.0.1 - 3.0281). This is roughly how I did it. Enabled telnet using an USB2IDE? connector and the ext2.sys driver for windows. Bootstrapped as in DS101BootStrap (see my comments on that page). Installed (ipkg) some tools (vim perl expat unslung-devel bash bc bzip2 tar findutils file grep coreutils gzip lsof rsync sqlite which zlib). Then I took perl from the openslug/cross/3.6-beta feed (packages perl, libperl, perl-dev, perl-misc, perl-pod and perl-module-*). Since those would install in /usr i manually installed them using something like ar x .. ; tar --strip-path=2 -xzvf data.tar.gz for each package with the help of bash. Then I took GCC from NativeFloatingPointToolchain. Since the arch on my DS101j? is armeb-linux I had to link the GCC binaries to the right name (e.g. armv5b-softfloat-linux-gcc to armeb-linux-gcc). Slimserver's Bin/build_perl_modules (or so) did not work for me. So I just got all the necessary tarballs and built and installed them manually (note: you do not really need ccache as somebody pointed out above, just eliminate all ccache from the Makefiles so that it does gcc directly). That's it! Roughly, as said.

I have about 5500 mp3 files (~30GB). Indexing took less than one hour. Re-indexing takes about 5 minutes (2 albums added, some id3 changes in a few albums). Starting Slimserver takes about 1 minute. After that it uses 18MB of RAM, still leaving a few MBs? for cache and all Diskstations Services running. Playing an mp3 slimserver uses a few CPU percents. Operation on the player is smooth, searching etc. reacts almost immediately. The webinterface ain't that smooth, but is absolutely usable.

March 24, 2006, at 10:10 AM by Wibbleman --
Changed line 162 from:

UPDATE II.. Ok, Slimserver is now running MUCH better. There was an "httpd" process that kept appearing, consuming up to 90% CPU, that was causing the problem. I assumed this was the slim server web interface, but not sure it was. If I "kill -9" the process then everything speeds up to an acceptable level, similar to what other users are reporting. I also added extra swap space, but for some reason I dont think that was the main reason its speeded up. Yes, it is now acceptable and usable - with the performance before it was just not usable.

to:

UPDATE II.. Ok, Slimserver is now running MUCH better. There was an "httpd" process that kept appearing, consuming up to 90% CPU, that was causing the problem. I assumed this was the slim server web interface, but not sure it was. If I "kill -9" the process then everything speeds up to an acceptable level, similar to what other users are reporting. I also added extra swap space, but for some reason I dont think that was the main reason its speeded up. Yes, it is now acceptable and usable - with the performance before it was just not usable. The 30-60% CPU utilisation of slimserver.pl (as detailed above) is the same, but its usuable. [One remaining problem, a couple of times the slimserver has hung for about 5-9 minutes at the end of a track, then continues on without problem - not investigated this yet]

March 23, 2006, at 10:57 AM by Wibbleman --
Changed lines 155-156 from:

I put off loading Slimserver for a while, cause it looked far too complex for me, but I just followed the main instructions at the top of this page and it all worked, dont think I had to do anything special/undocumented. Note that on an de-underclocked SLUG it still took maybe 20mins for the build to run, and maybe 2-3 mins for slimserver to start, but it all works. Web is slow, but works. Ive only tested on a 6 file library, and interent radio, but works fine. I am away next week so maybe I will point the SLUG at my 15,000 track MP3? collectionand see if its finished by the weekend!

to:

I put off loading Slimserver for a while, cause it looked far too complex for me, but I just followed the main instructions at the top of this page and it all worked, dont think I had to do anything special/undocumented. Note that on an de-underclocked SLUG it still took maybe 20mins for the build to run, and maybe 2-3 mins for slimserver to start, but it all works. Web is slow, but works. Ive only tested on a 6 file library, and interent radio, but works fine. I am away next week so maybe I will point the SLUG at my 15,000 track MP3? collection and see if its finished by the weekend!

Added lines 161-162:

UPDATE II.. Ok, Slimserver is now running MUCH better. There was an "httpd" process that kept appearing, consuming up to 90% CPU, that was causing the problem. I assumed this was the slim server web interface, but not sure it was. If I "kill -9" the process then everything speeds up to an acceptable level, similar to what other users are reporting. I also added extra swap space, but for some reason I dont think that was the main reason its speeded up. Yes, it is now acceptable and usable - with the performance before it was just not usable.

March 22, 2006, at 12:39 PM by zupidupi --
Changed line 162 from:

(Comment: I run SlimServer 6.2.0 on a turbo-slug, Unslung 5.5, lotsa swapspace. My collection amounts to about 12000 mp3, scanning them all and building the database (16M big) takes about 6 hours. It's OK AFAIK, it happens at night while I'm catching some Z's. Remains to see how fast/slow the rescanning is. My SqueezeBox? works just fine with the server, with a few exceptions. Browsing is smooth enough, but *asking* for a particular bunch of information takes a little while. For example, when I do "Browse genre" there's a slight delay in the box before it responds - obviously this is because the slug can't perform the query fast enough. Once the information has been queried, browsing it is fine. I suppose that maintaining a properly and consistently tagged collection helps a bit - correct me if I'm wrong. The streaming works just fine, occasionally (like once every 3-4 hours) there's a short pause in the stream, in between tunes. All in all it's acceptable, but I suspect that a collection with over 20 000 mp3's could prove to be too much.)

to:

(Comment: I run SlimServer 6.2.0 on a turbo-slug, Unslung 5.5, lotsa swapspace. My collection amounts to about 12000 mp3, scanning them all and building the database (16M big) takes about 6 hours. It's OK AFAIK, it happens at night while I'm catching some Z's. Remains to see how fast/slow the rescanning is. My SqueezeBox? works just fine with the server, with a few exceptions. Browsing is smooth enough, but *asking* for a particular bunch of information takes a little while. For example, when I do "Browse genre" there's a slight delay in the box before it responds - obviously this is because the slug can't perform the query fast enough. Once the information has been queried, browsing it is fine. The streaming works just fine, occasionally (like once every 3-4 hours) there's a short pause in the stream, in between tunes. All in all it's acceptable, but I suspect that a collection with over 20 000 mp3's could prove to be too much.)

March 19, 2006, at 08:15 PM by Zupidupi --
Changed lines 160-162 from:

(The Twonky server seems to index the 40 track MP3? collection about 100x faster too!)

to:

(The Twonky server seems to index the 40 track MP3? collection about 100x faster too!)


(Comment: I run SlimServer 6.2.0 on a turbo-slug, Unslung 5.5, lotsa swapspace. My collection amounts to about 12000 mp3, scanning them all and building the database (16M big) takes about 6 hours. It's OK AFAIK, it happens at night while I'm catching some Z's. Remains to see how fast/slow the rescanning is. My SqueezeBox? works just fine with the server, with a few exceptions. Browsing is smooth enough, but *asking* for a particular bunch of information takes a little while. For example, when I do "Browse genre" there's a slight delay in the box before it responds - obviously this is because the slug can't perform the query fast enough. Once the information has been queried, browsing it is fine. I suppose that maintaining a properly and consistently tagged collection helps a bit - correct me if I'm wrong. The streaming works just fine, occasionally (like once every 3-4 hours) there's a short pause in the stream, in between tunes. All in all it's acceptable, but I suspect that a collection with over 20 000 mp3's could prove to be too much.)

March 19, 2006, at 06:50 PM by Wibbleman --
Changed lines 155-160 from:

I put off loading Slimserver for a while, cause it looked far too complex for me, but I just followed the main instructions at the top of this page and it all worked, dont think I had to do anything special/undocumented. Note that on an de-undercloked SLUG it still took maybe 20mins for the build to run, and maybe 2-3 mins for slimserver to start, but it all works. Web is slow, but works. Ive only tested on a 6 file library, and interent radio, but works fine. I am away next week so maybe I will point the SLUG at my 15,000 track MP3? collectionand see if its finished by the weekend!

(Update - Even scanning a samll 40 song library takes ages, 10-20mins? and uses 95% CPU - what on earth is the code doing in there??. I have alsoinstalled TwonkY? MEdia? sevrer on the same box, so the case music collection can feed into SLIMP3? and Netgear MP101? players, and noted;

  SLIM SERVER V6.2.1.......feeding SLIMP3?.............30-60% CPU continuously  (1 or 2 players running)
  TWONKY V3.1..............feeding Netgear MP101?......50% CPU say  second every 40 seconds ?

(The Twonky server seems to hack its way around the 40 track MP3? collection about 100x faster too!)

to:

I put off loading Slimserver for a while, cause it looked far too complex for me, but I just followed the main instructions at the top of this page and it all worked, dont think I had to do anything special/undocumented. Note that on an de-underclocked SLUG it still took maybe 20mins for the build to run, and maybe 2-3 mins for slimserver to start, but it all works. Web is slow, but works. Ive only tested on a 6 file library, and interent radio, but works fine. I am away next week so maybe I will point the SLUG at my 15,000 track MP3? collectionand see if its finished by the weekend!

(Update - Even scanning a small 40 song library takes ages, 10-20mins? and uses 95% CPU - what on earth is the code doing in there??. I have also installed TwonkyMedia? Server on the same box, so the same music collection can feed into SLIMP3? and Netgear MP101? players, and noted;

  SLIM SERVER V6.2.1.......feeding SLIMP3?.............30-60% CPU continuously  
  TWONKY V3.1..............feeding Netgear MP101?......a blip of 50% CPU say for 1 second every 40 seconds ? - avg <2% CPU

(The Twonky server seems to index the 40 track MP3? collection about 100x faster too!)

March 19, 2006, at 06:47 PM by Wibbleman --
Changed lines 154-155 from:

Wibbleman adds: ......IT DOES WORK...... !! .......- Slug 5.5/Slim6.2.1 (Mar 2006)...... I put off loading Slimserver for a while, cause it looked far too complex for me, but I just followed the main instructions at the top of this page and it all worked, dont think I had to do anything special/undocumented. Note that on an de-undercloked SLUG it still took maybe 20mins for the build to run, and maybe 2-3 mins for slimserver to start, but it all works. Web is slow, but works. Ive only tested on a 6 file library, and interent radio, but works fine. I am away next week so maybe I will point the SLUG at my 15,000 track MP3? collectionand see if its finished by the weekend! (Update - Even scanning a samll 40 song library takes ages, 10-20mins? and uses 95% CPU - what on earth is the code doing in there??)

to:

Wibbleman adds: ......IT DOES WORK - AND ITS NOT TOO COMPLICATED!!...... .......- Slug 5.5/Slim6.2.1 (Mar 2006)...... I put off loading Slimserver for a while, cause it looked far too complex for me, but I just followed the main instructions at the top of this page and it all worked, dont think I had to do anything special/undocumented. Note that on an de-undercloked SLUG it still took maybe 20mins for the build to run, and maybe 2-3 mins for slimserver to start, but it all works. Web is slow, but works. Ive only tested on a 6 file library, and interent radio, but works fine. I am away next week so maybe I will point the SLUG at my 15,000 track MP3? collectionand see if its finished by the weekend!

(Update - Even scanning a samll 40 song library takes ages, 10-20mins? and uses 95% CPU - what on earth is the code doing in there??. I have alsoinstalled TwonkY? MEdia? sevrer on the same box, so the case music collection can feed into SLIMP3? and Netgear MP101? players, and noted;

  SLIM SERVER V6.2.1.......feeding SLIMP3?.............30-60% CPU continuously  (1 or 2 players running)
  TWONKY V3.1..............feeding Netgear MP101?......50% CPU say  second every 40 seconds ?

(The Twonky server seems to hack its way around the 40 track MP3? collection about 100x faster too!)

March 19, 2006, at 01:01 PM by Wibbleman --
Changed lines 154-155 from:

Wibbleman adds: IT WORKS !! - Slug 5.5/Slim6.2.1 (Mar 2006) I put off loading Slimserver for a while, cause it looked far too complex for me, but I just followed the main instructions at the top of this page and it all worked, dont think I had to do anything special/undocumented. Note that on an de-undercloked SLUG it still took maybe 20mins for the build to run, and maybe 2-3 mins for slimserver to start, but it all works. Web is slow, but works. Ive only tested ona 6 file library, and interent radio, but works fine. I am away next week so maybe I will point the SLUG at my 15,000 track MP3? collectionand see if its finished by the weekend!

to:

Wibbleman adds: ......IT DOES WORK...... !! .......- Slug 5.5/Slim6.2.1 (Mar 2006)...... I put off loading Slimserver for a while, cause it looked far too complex for me, but I just followed the main instructions at the top of this page and it all worked, dont think I had to do anything special/undocumented. Note that on an de-undercloked SLUG it still took maybe 20mins for the build to run, and maybe 2-3 mins for slimserver to start, but it all works. Web is slow, but works. Ive only tested on a 6 file library, and interent radio, but works fine. I am away next week so maybe I will point the SLUG at my 15,000 track MP3? collectionand see if its finished by the weekend! (Update - Even scanning a samll 40 song library takes ages, 10-20mins? and uses 95% CPU - what on earth is the code doing in there??)

March 19, 2006, at 09:00 AM by Wibbleman -- Update Mar 2006
Changed lines 152-155 from:

Anyway I couldn't wait and I installed the crosstool-native packages + make on unslung-3.18. This works great too! I have slimserver 6.2.1 running now as user slimserver. For that, make sure the user slimserver has approriate entries in /etc/passwd and also check that /var/tmp has permissions drwxrwxrwt.

to:

Anyway I couldn't wait and I installed the crosstool-native packages + make on unslung-3.18. This works great too! I have slimserver 6.2.1 running now as user slimserver. For that, make sure the user slimserver has approriate entries in /etc/passwd and also check that /var/tmp has permissions drwxrwxrwt.


Wibbleman adds: IT WORKS !! - Slug 5.5/Slim6.2.1 (Mar 2006) I put off loading Slimserver for a while, cause it looked far too complex for me, but I just followed the main instructions at the top of this page and it all worked, dont think I had to do anything special/undocumented. Note that on an de-undercloked SLUG it still took maybe 20mins for the build to run, and maybe 2-3 mins for slimserver to start, but it all works. Web is slow, but works. Ive only tested ona 6 file library, and interent radio, but works fine. I am away next week so maybe I will point the SLUG at my 15,000 track MP3? collectionand see if its finished by the weekend!

March 18, 2006, at 09:52 PM by Geert Janssen --
Added lines 151-152:

Anyway I couldn't wait and I installed the crosstool-native packages + make on unslung-3.18. This works great too! I have slimserver 6.2.1 running now as user slimserver. For that, make sure the user slimserver has approriate entries in /etc/passwd and also check that /var/tmp has permissions drwxrwxrwt.

March 17, 2006, at 05:51 PM by Geert Janssen -- Share missing libraries
Changed lines 146-150 from:

H. Lima adds: After several unsuccessful trials to use mt-daapd server and wmamp (wmam11b itunes client) I switched to Slimserver and wrote a slimp3 client for the wma11b (available here and it has been working very well for days already. If you own a wma11b you should check it out!

to:

H. Lima adds: After several unsuccessful trials to use mt-daapd server and wmamp (wmam11b itunes client) I switched to Slimserver and wrote a slimp3 client for the wma11b (available here and it has been working very well for days already. If you own a wma11b you should check it out!


Could someone please turn slimserver into a complete ipkg package or maybe just offer the missing pieces. That way most of us can avoid having to install a native toolchain and compile the stuff ourselves.

February 23, 2006, at 01:06 PM by H Lima -- Slimserver and wma11b
Changed lines 143-146 from:

Chris Kantarjiev adds: This worked just fine on Unslung5.5b with "SlimServer_v6.2.1". Except ... I wanted to run it as user slimserver instead of root. When I do that, SQLite? complains that it can't create a temporary table, even though I think I got all the permissions right. It would be good to fix this. Running fine on a 266MHz Slug, 64MB, process size is about 38M with 6600 tunes. To make WMA files work (especially for Internet radio), you'll want to load ffmpeg and lame with ipkg - note that some of the libraries you need end up in /opt/lib.

to:

Chris Kantarjiev adds: This worked just fine on Unslung5.5b with "SlimServer_v6.2.1". Except ... I wanted to run it as user slimserver instead of root. When I do that, SQLite? complains that it can't create a temporary table, even though I think I got all the permissions right. It would be good to fix this. Running fine on a 266MHz Slug, 64MB, process size is about 38M with 6600 tunes. To make WMA files work (especially for Internet radio), you'll want to load ffmpeg and lame with ipkg - note that some of the libraries you need end up in /opt/lib.


H. Lima adds: After several unsuccessful trials to use mt-daapd server and wmamp (wmam11b itunes client) I switched to Slimserver and wrote a slimp3 client for the wma11b (available here and it has been working very well for days already. If you own a wma11b you should check it out!

February 08, 2006, at 04:43 AM by Chris Kantarjiev --
Changed line 143 from:

Chris Kantarjiev adds: This worked just fine on Unslung5.5b with "SlimServer_v6.2.1". Except ... I wanted to run it as user slimserver instead of root. When I do that, SQLite? complains that it can't create a temporary table, even though I think I got all the permissions right. It would be good to fix this. Running fine on a 266MHz Slug, 64MB, process size is about 38M with 6600 tunes.

to:

Chris Kantarjiev adds: This worked just fine on Unslung5.5b with "SlimServer_v6.2.1". Except ... I wanted to run it as user slimserver instead of root. When I do that, SQLite? complains that it can't create a temporary table, even though I think I got all the permissions right. It would be good to fix this. Running fine on a 266MHz Slug, 64MB, process size is about 38M with 6600 tunes. To make WMA files work (especially for Internet radio), you'll want to load ffmpeg and lame with ipkg - note that some of the libraries you need end up in /opt/lib.

January 27, 2006, at 01:06 AM by Chris Kantarjiev -- problems when using --user
Added lines 142-143:

Chris Kantarjiev adds: This worked just fine on Unslung5.5b with "SlimServer_v6.2.1". Except ... I wanted to run it as user slimserver instead of root. When I do that, SQLite? complains that it can't create a temporary table, even though I think I got all the permissions right. It would be good to fix this. Running fine on a 266MHz Slug, 64MB, process size is about 38M with 6600 tunes.

December 09, 2005, at 05:37 AM by Marc Pelzer -- added SlimServer_v6.2.1 hints
Added lines 137-141:

Marc Pelzer adds: "SlimServer_v6.2.1" needs the C caching application "ccache" to build the Compress-Zlib-1.33.tar.gz. You can get it from here: http://ccache.samba.org/ It compiles fine on my slug after installing all necessary dev tools (ipkg install gcc gcc-symlinks make binutils libc6-dev coreutils libexpat-dev)

October 25, 2005, at 07:50 AM by Paul Webster --
Added lines 132-136:

Paul Webster adds: SlimServer 6.2.0 seems to work as well. Following same procedure (clearly .. changing the version number in the directory names) - with the modification suggested by Fritz to get "make" into the path before building. It is busy scanning at the moment. But looking forward to see if interactive performance is improved because one of the claims for 6.2 is that it speeds up some of the database accesses.

October 06, 2005, at 07:09 AM by Steinar Midtskogen -- Experiences with a 64MB slug
Changed line 131 from:

Steinar adds: SlimServer runs fine without swap on a 64MB slug. It takes about 65 seconds to start on a 266MHz slug, 64MB, no swap, OpenSlug 2.5.

to:

Steinar adds: SlimServer runs fine without swap on a 64MB slug. It takes about a minute to start on a 266MHz slug, 64MB, no swap, OpenSlug 2.7. File scanning, however, still takes a very, very long time (it may take hours) if the music collection is big (10,000+ tracks). Once started, SlimServer runs fast enough, except when trying to play huge playlists (it may then need a few minutes to get started). My SlimServer has a load around 60% while serving two synchronised Squeezeboxes. Memory usage is about 37MB. The web pages load a bit slowly, but are still perfectly useable.

September 21, 2005, at 11:24 AM by Steinar Midtskogen -- Added a note about running SlimServer on a 64MB slug.
Changed lines 128-131 from:

Note: you *will* require a decent amount of swap to run the Slimserver and even then it will be a little slow (e.g. don't try and play your entire music collection at once)

to:

Note: you *will* require a decent amount of swap to run the Slimserver and even then it will be a little slow (e.g. don't try and play your entire music collection at once)


Steinar adds: SlimServer runs fine without swap on a 64MB slug. It takes about 65 seconds to start on a 266MHz slug, 64MB, no swap, OpenSlug 2.5.

September 07, 2005, at 11:39 AM by Anaonymous -- Incorrect package name
Changed lines 120-121 from:
 # ipkg install gcc gcc-symlinks binutils make libc6-dev coreutils libexpat0-dev
to:
 # ipkg install gcc gcc-symlinks binutils make libc6-dev coreutils libexpat-dev
August 11, 2005, at 09:52 AM by ioc2k --
Changed line 110 from:

Working in Openslug 2.5, as perl now seems to work correctly:

to:

Works in Openslug 2.5, as the perl ipk's now seem to run correctly:

Changed line 113 from:

However, you will need to copy typemap and xsubpp from a perl source tree to the local perl library folders as they're missing for some reason:

to:

However, you will need to copy typemap and xsubpp from a perl source tree to the local perl library folders (they're missing for some reason):

Changed line 119 from:

Then install compiler and friends:

to:

Then install gcc and friends:

Changed line 122 from:

Extract slimserver software and compile modules:

to:

Finally extract slimserver and compile modules:

Changed line 128 from:

Note: you *will* require a decent amount of swap to compile perl and/or run the Slimserver, otherwise the Out Of Memory killer will rear its ugly head

to:

Note: you *will* require a decent amount of swap to run the Slimserver and even then it will be a little slow (e.g. don't try and play your entire music collection at once)

August 11, 2005, at 01:38 AM by ioc2k --
Changed lines 120-121 from:
 # ipkg install gcc gcc-symlinks binutils make libc6-dev coreutils
to:
 # ipkg install gcc gcc-symlinks binutils make libc6-dev coreutils libexpat0-dev
August 11, 2005, at 01:36 AM by ioc2k -- openslug 2.5 changes
Changed lines 110-114 from:

Also works on Openslug...

Install native compile tools (see OpenSlugNativeCompileEnvironment)

Download, untar and compile perl manually (as perl ipk is broken in Openslug):

to:

Working in Openslug 2.5, as perl now seems to work correctly:

 # ipkg install perl perl-modules

However, you will need to copy typemap and xsubpp from a perl source tree to the local perl library folders as they're missing for some reason:

Changed lines 116-121 from:
 # cd perl-5.8.7
 # sh Configure -Dprefix=/usr/local -Dinstallprefix=/usr/local -Dusedl -Dloclibpth="/usr/lib" -Dlocincpth="/usr/include" -Dinstallusrbinperl -Dd_u32align -de
 # make
 # make install

Download, untar Slimserver and run module build script (you do *not* need to edit it):

to:
 # cp perl-5.8.7/lib/ExtUtils/typemap /usr/lib/perl5/5.8.7/ExtUtils/typemap
 # cp perl-5.8.7/lib/ExtUtils/xsubpp /usr/lib/perl5/5.8.7/ExtUtils/xsubpp

Then install compiler and friends:

 # ipkg install gcc gcc-symlinks binutils make libc6-dev coreutils

Extract slimserver software and compile modules:

Deleted lines 127-128:

Run as before :)

August 10, 2005, at 12:11 PM by rwhitby --
Changed lines 112-113 from:

Install native compile tools (see OpenSlugNativeCompileEnvironment?)

to:

Install native compile tools (see OpenSlugNativeCompileEnvironment)

August 10, 2005, at 12:09 PM by rwhitby --
Changed line 8 from:

First I installed dropbear (UseDropBearForRemoteAccess?) so I could

to:

First I installed dropbear (UseDropBearForRemoteAccess) so I could

Changed lines 15-16 from:

You'll need Perl to run SlimServer (BuildPerlOnYourNSLU2Box?) - don't worry, perl is now pre-built, so this is easy:

to:

You'll need Perl to run SlimServer (BuildPerlOnYourNSLU2Box) - don't worry, perl is now pre-built, so this is easy:

Changed lines 38-39 from:

and a few other things. So the next step was to install the native tools, (NativelyCompileUnslungPackages?).

to:

and a few other things. So the next step was to install the native tools, (NativelyCompileUnslungPackages).

August 01, 2005, at 09:11 AM by ioc2k --
Changed lines 126-127 from:
 # /usr/local/SlimServer_v6.1.0/Bin/build-perl-modules.pl
to:
 # /usr/local/SlimServer_v6.1.1/Bin/build-perl-modules.pl
August 01, 2005, at 06:24 AM by Fritz -- May need to add /opt/bin to path
Added lines 104-109:

Fritz adds: This worked well for me with one exception. build-perl-modules.pl errored out because it could not find make. Once I added /opt/bin to my path everything worked well.

 # PATH=$PATH:/opt/bin
 # export PATH
 # /usr/local/SlimServer_v6.1.1/Bin/build-perl-modules.pl

July 24, 2005, at 01:42 PM by ioc2k --
Changed lines 106-107 from:

Install native compile tools and run OpenSlugDevInst?.sh script (see OpenSlugNativeCompileEnvironment?)

to:

Install native compile tools (see OpenSlugNativeCompileEnvironment?)

July 24, 2005, at 01:41 PM by ioc2k --
Changed line 119 from:
 # tar -xzvf /root/SlimServer_v6.1.1.tar.gz
to:
 # tar -xzvf /root/SlimServer_v6.1.1.tar.gz
July 24, 2005, at 01:40 PM by ioc2k --
Changed lines 116-119 from:

Download, untar Slimserver and run module build script as before (you do *not* need to edit it):

to:

Download, untar Slimserver and run module build script (you do *not* need to edit it):

 # wget http://www.slimdevices.com/downloads/SlimServer_v6.1.1/SlimServer_v6.1.1.tar.gz
 # cd /usr/local
 # tar -xzvf /root/SlimServer_v6.1.1.tar.gz
July 24, 2005, at 01:36 PM by ioc2k --
Changed lines 108-111 from:

Compile perl manually (as perl ipk is broken in Openslug):

to:

Download, untar and compile perl manually (as perl ipk is broken in Openslug):

 # wget http://ftp.funet.fi/pub/CPAN/src/perl-5.8.7.tar.gz
 # tar -xzvf perl-5.8.7.tar.gz
 # cd perl-5.8.7
Changed line 116 from:

Untar Slimserver and run module build script as before (you do *not* need to edit it):

to:

Download, untar Slimserver and run module build script as before (you do *not* need to edit it):

July 24, 2005, at 01:31 PM by ioc2k -- Openslug additons
Changed lines 101-118 from:

Ole adds: Works like a charm (note that browsing, searching etc. has been reported to be slow. If you are like me, and buy the NSLU to be a dedicated SlimServer, then you might want to take that into consideration). At the moment I do not have any unmanagable speed issues.

to:

Ole adds: Works like a charm (note that browsing, searching etc. has been reported to be slow. If you are like me, and buy the NSLU to be a dedicated SlimServer, then you might want to take that into consideration). At the moment I do not have any unmanagable speed issues.


Also works on Openslug...

Install native compile tools and run OpenSlugDevInst?.sh script (see OpenSlugNativeCompileEnvironment?)

Compile perl manually (as perl ipk is broken in Openslug):

 # sh Configure -Dprefix=/usr/local -Dinstallprefix=/usr/local -Dusedl -Dloclibpth="/usr/lib" -Dlocincpth="/usr/include" -Dinstallusrbinperl -Dd_u32align -de
 # make
 # make install

Untar Slimserver and run module build script as before (you do *not* need to edit it):

 # /usr/local/SlimServer_v6.1.0/Bin/build-perl-modules.pl

Run as before :)

Note: you *will* require a decent amount of swap to compile perl and/or run the Slimserver, otherwise the Out Of Memory killer will rear its ugly head

July 24, 2005, at 01:14 PM by ole --
Changed lines 44-45 from:

You'll also need the which command, as well as expat

to:

You'll also need the which command, as well as expat (if which complains about missing "libz.so", run "ipkg install zlib" ):

Added lines 99-101:

Ole adds: Works like a charm (note that browsing, searching etc. has been reported to be slow. If you are like me, and buy the NSLU to be a dedicated SlimServer, then you might want to take that into consideration). At the moment I do not have any unmanagable speed issues.

July 06, 2005, at 02:52 AM by Roo --
Changed lines 3-4 from:

Of course, you've already installed unslung. (I'm running 4.20, but more recent versions should work fine)

to:

Of course, you've already installed Unslung. (I'm running 4.20, but more recent versions should work fine)

Changed lines 6-7 from:

http://IP-address-of-your-slug/Management/telnet.cgi

to:
 http://IP-address-of-your-slug/Management/telnet.cgi
Changed lines 96-97 from:

To check out the server: http://IP-address-of-your-slug:9000

to:

To check out the server: http://IP-address-of-your-slug:9000

July 05, 2005, at 01:58 PM by roo_at_magma_ca -- Initial version
Added lines 1-98:

Installing Slimserver on the NSLU2

Of course, you've already installed unslung. (I'm running 4.20, but more recent versions should work fine)

Enable telnet http://IP-address-of-your-slug/Management/telnet.cgi

First I installed dropbear (UseDropBearForRemoteAccess?) so I could use ssh to access my slug.

 # ipkg update
 # ipkg install dropbear
 # reboot

You'll need Perl to run SlimServer (BuildPerlOnYourNSLU2Box?) - don't worry, perl is now pre-built, so this is easy:

 # ipkg update
 # ipkg install unslung-feeds
 # ipkg update
 # ipkg install perl

Go download SlimServer Perl source code (I used v6.0.2)

 http://www.slimdevices.com/su_downloads.html

Installing Slimserver is as easy as using tar xzvf Slimserver_v6.0.2.tar.gz

I decided mine should live in /usr/local with data in /etc/slim-data

 # cd /usr/local
 # tar xzvf /root/Slimserver_v6.0.2.tar.gz
 # cd /etc
 # mkdir slim-data

Slim server needed the following Perl modules: DBD::SQLite XML::Parser HTML::Parser Compress::Zlib. However, the slimserver code provides a way to get those missing packages, but you need a C compiiler and a few other things. So the next step was to install the native tools, (NativelyCompileUnslungPackages?).

This is simply:

 # ipkg install unslung-devel

You'll also need the which command, as well as expat

 # ipkg install which
 # ipkg install expat

Now edit the file /usr/local/SlimServer_v6.0.2/Bin/build-perl-modules.pl to add some options to the XML Parser, this is because expat is installed in a non-standard location on the slug. (you need to add the XML Parser section)

my %packageOptions = (

    'Template-Toolkit-2.13' => {

        'Makefile.PL' => join(' ', qw(
            TT_DOCS=n
            TT_SPLASH=n
            TT_THEME=n
            TT_EXAMPLES=n
            TT_EXAMPLES=n
            TT_EXTRAS=n
            TT_QUIET=y
            TT_ACCEPT=y
            TT_DBI=n
            TT_LATEX=n
        )),
    },

    'DBD-SQLite-1.08' => {

        'env' => [qw(DBI-1.46/blib/lib: DBI-1.46/blib/arch)],
    },

    'XML-Parser-2.34' => {
        'Makefile.PL' => join(' ', qw(
            EXPATLIBPATH=/opt/lib
            EXPATINCPATH=/opt/include
        )),
    },

);

Now run the SlimServer script to get the missing modules

 # /usr/local/SlimServer_v6.0.2/Bin/build-perl-modules.pl

Now, give it a try..

 # cd /usr/local/SlimServer_v6.0.2
 # ./slimserver.pl --daemon --prefsfile /etc/slim-data/slimserver.pref --cachedir /etc/slim-data

A few of these steps will take a while to complete, be patient. Starting the server can be pretty slow, but it will start.

To check out the server: http://IP-address-of-your-slug:9000

I don't yet have a squeezebox, but softsqueeze seems to work with this. I do have some pauses, but I strongly suspect that this is related to the softsqueeze player and not the server. Windows media player seems to work well with slimserver, just follow the directions for remote streaming.