Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 19 12311 ... LastLast
Results 1 to 10 of 188
  1. #1
    Senior Member
    Join Date
    Jun 2006
    Posts
    747

    Easy Squeezecenter Install on Buffalo LinkStation Pro/Live (v7.3.3)

    *****
    I HAVE NOW CREATED A NEW SET OF THESE INSTRUCTIONS USING THE STOCK BUFFALO FIRMWARE. SEE THREAD ENTITLED "EVEN EASIER SQUEEZECENTER INSTALL ON BUFFALO LINKSTATION PRO AND LINKSTATION LIVE" at http://forums.slimdevices.com/showthread.php?t=62842. The instructions in this thread still work, but the version in the other thread will install Squeezecenter with many fewer steps required, and chances of bricking your unit are further reduced.

    CURRENTLY, THE IPKG PROCESS INSTALLS SQUEEZECENTER 7.3.3. FUTURE AVAILABILITY OF SQUEEZCENTER 7.4 AND HIGHER VIA THIS METHOD IS UNKNOWN DUE TO TECHNICAL CHANGES MADE IN THE SQUEEZECENTER SOFTWARE THAT IMPACT ITS COMPATIBILITY WITH THE BOTH THE STOCK BUFFALO FIRMWARE AND JTYMOD FIRMWARE. The latest version of Squeezecenter available as IPKG can always be seen at http://ipkg.nslu2-linux.org/feeds/un...cross/Packages. (Search that page for "squeezecenter".)
    *****

    IPKG and JTYMOD: THE EASY WAY TO INSTALL SQUEEZECENTER ON BUFFALO LINKSTATION PRO (LS-GL) OR LINKSTATION LIVE (HS-DHGL & LS-CHL) MODELS WITH ARM PROCESSOR

    This set of instructions is based on numerous threads such as http://forums.slimdevices.com/showthread.php?t=52466 started by forum member bzhou and other SlimDevices forum threads, http://buffalo.nas-central.org/forum...t=4075&p=39162, http://buffalo.nas-central.org/index...(for_end-users), and various other web pages. I haven’t created anything new here. I’ve just put together all the pieces in one place to make a straightforward step-by-step instruction set for users who don’t know any Linux. It is essentially a “For Dummies” guide to installing Squeezecenter on a LinkStation Pro or LinkStation Live.

    This installation process has been tested from a Windows Vista 64-bit PC to both a LinkStation Pro (LS-GL series) and LinkStation Live (HS-DHGL series). The process should be the same from any PC running Windows XP or Vista. If you’re running a Mac, somebody else will need to come up with directions. If you’re running Linux and know what you’re doing, you shouldn’t need these “For Dummies” instructions.

    I have tested this installation process to both a LinkStation Pro LS-GL series and LinkStation Live HS-DHGL series which use an ARM processor. I have NOT tested this process on any other LinkStation models, although other users have now confirmed that the new LinkStation Live LS-CHL also uses an ARM processor, and Squeezecenter can be installed on it the same way.

    These instructions will probably NOT work with a LinkStation EZ or LinkStation Mini, which have much different hardware architectures. You could very well brick your unit if you try, rendering it a useless doorstop. You have been warned.

    What are IPKG and JTYMOD?
    IPKG (Itsy Package Management System) is a quick and easy way to get Squeezecenter installed on a Buffalo LinkStation Pro or LinkStation Live. (See http://handhelds.org/moin/moin.cgi/Ipkg for more info on IPKG.)

    JTYMOD is a hacked version of standard LinkStation firmware that retains Buffalo’s graphical web interface for controlling the LinkStation. IPKG can be used without JTYMOD, but JTYMOD simplifies the installation of IPKG. (More info on JTYMOD is at http://buffalo.nas-central.org/index...abled_firmware.)

    For the average Joe or Jane user, IPKG and JTYMOD form the simplest method to get Squeezecenter installed on a LinkStation Pro or LinkStation Live with minimal entry of coded commands. Linux power users will likely prefer the complete control of a full FreeLink installation (such as via the process documented in this thread by forum member farallon http://forums.slimdevices.com/showthread.php?t=46005 ), freeing the LinkStation from the walled-garden of Buffalo firmware. But if all you want to do is just run Squeezecenter on the LinkStation, IPKG is a revelation for its comparative simplicity. And IPKG allows for easy updating to new versions of Squeezecenter with only a few coded commands. The only minor hitch is that before you can upgrade to a new version of Squeezecenter someone has to make the IPKG package for it.

    With JTYMOD (or the stock Buffalo firmware), after Squeezecenter is installed, the LinkStation graphical web interface permits you to control many settings of the LinkStation without further use of Telnet or SSH and Linux code commands. And you can configure shared folders without using Samba, which I find particularly appealing. If you don't even know what Samba is, then IPKG with JTYMOD is the way for you. You don't even have to know what Linux is.

    Why use JTYMOD?
    Why should you install JTYMOD firmware if IPKG Squeezecenter can be installed with the stock Buffalo firmware? Telnet access is not built into the stock Buffalo firmware, but it is built into JTYMOD. More significantly, the Linux “wget” command, which is necessary to install IPKG, is missing from the stock Buffalo firmware. What I found most useful about JTYMOD, and the main reason to use it, is that it includes the “wget” command, simplifying the IPKG installation process. Telnet access and the missing “wget” command can be added to the stock Buffalo firmware by using Java and Linux commands, and doing so is fairly simple for people who know Linux. But for the average Joe or Jane PC computer user who doesn’t know anything about Linux, installing JTYMOD firmware is easier than getting “wget” into the stock Buffalo firmware. Someone more experienced than I am with Linux could probably write instructions similar to these for the stock firmware, but attempting that process myself, I ran into a variety of problems that I couldn’t figure out how to get around. But then, I barely know anything about Linux. The entirety of my Linux experience has been derived from loading Squeezecenter (and/or the older Slimserver) on Buffalo LinkStations. If you want to try your hand at adding “wget” to the stock Buffalo firmware instead of loading JTYMOD, see “SOLUTIONS for missing WGET” at http://buffalo.nas-central.org/forum...hp?f=19&t=4075. If you don’t already know how to do what is described there, just avoid the issue by using JTYMOD as described here.

    General instructions for installing JTYMOD firmware are available through links at http://buffalo.nas-central.org/index...abled_firmware, although the instructions below here step you through the process.


    ***WARNING***
    BEFORE UPDATING THE FIRMWARE FOR YOUR LINKSTATION, BE SURE TO HAVE ALL YOUR FILES BACKED UP ELSEWHERE.

    ***WARNING***
    EXECUTING ANY HACKING INSTRUCTIONS SUCH AS THESE COULD RENDER YOUR LINKSTATION INOPERABLE IF DONE IMPROPERLY.

    ***DISABLE FIREWALL***
    BEFORE PROCEEDING, TEMPORARILY TURN OFF WINDOWS FIREWALL UNTIL YOU HAVE COMPLETED THE SQUEEZECENTER INSTALLATION. The Firewall may interfere with the firmware update. You can access the Windows Firewall setting in Control Panel->Security.

    These instructions assume that you are starting with a fresh (empty) LinkStation. If you already have many files stored on your LinkStation, you should back them up elsewhere and reformat the LinkStation disk drive before proceeding. (In the web browser interface, reformat the drive through Disk Management->Disk Format. If you don't know how to do that, consult your LinkStation documentation for specific instructions on reformatting the disk drive.)

    Now, on to the installation, contained in the following series of posts.
    Last edited by TiredLegs; 2010-06-02 at 15:04.

  2. #2
    Senior Member
    Join Date
    Jun 2006
    Posts
    747

    ***Step 1: INSTALL JTYMOD FIRMWARE***

    ***STEP 1: INSTALL JTYMOD FIRMWARE***

    The process of installing JTYMOD firmware varies depending on whether you are using a LinkStation Pro or a LinkStation Live.

    If you are using a LinkStation Pro, follow the instructions in Step 1A.

    If you are using a LinkStation Live, skip past Step1A and follow the instructions in Step 1B.

    ***STEP1A: INSTALL JTYMOD FIRMWARE ON LINKSTATION PRO***
    This section applies only to LinkStation Pro hardware. If you are using a LinkStation Live, skip to Step 1B.

    Download JTYMOD firmware from http://oh1jty.toimii.net/linkstation...03-jtymod5.zip (or a later version that would be listed in the “Download from” area on the JTYMOD web page http://buffalo.nas-central.org/index...abled_firmware.)

    Extract the JTYMOD firmware from the zip file using a standard zip utility. This will create a new folder containing several files.
    EXTREMELY IMPORTANT: Inside the firmware folder, immediately delete the file u-boot.buffalo.updated. (If accidentally installed, on some versions of the hardware, the file could brick your LinkStation.)

    To permit the LinkStation firmware updater utility (LSUpdater.exe) to safely install JYTMOD, you will need to edit the file lsupdater.ini using a basic text editor such as Notepad, which is included with Windows. Do not use Microsoft Word to edit the file. That application creates hidden characters that would cause problems. The edit of lsupdater.ini allows activation of Debug mode to prevent inadvertently installing a u-boot.buffalo.updated file that could brick your unit

    In the file lsupdater.ini file, add the following text to the end of the contents:

    [SpecialFlags]
    Debug = 1

    Save and close the file.
    Double click the firmware updater application LSUpdater.exe in the JYTMOD directory. DO NOT CLICK UPDATE YET!
    Before you do anything else, copy down the IP address of your LinkStation. It will probably be in the form 192.168.1.XXX, where the last three digits are determined by your network router.

    Then, in the Windows Taskbar at the bottom of your screen, right-click on the Buffalo Updater.
    Select Debug.
    UNCHECK the box for Update BOOT in the upper right. This prevents inadvertent installation of a u-boot.buffalo.updated file that could brick your unit. (If you already deleted that file, this step shouldn’t be necessary, but it is better to be on the safe side.)
    Leave the boxes checked for KERNEL, initrd, and rootfs.
    Click OK to exit the Debug window.

    In the Buffalo Updater window, now click Update.
    If you are asked for an admin password, enter “password” (without the quotes).
    The JTYMOD firmware installation will now proceed. The LinkStation will reboot itself several times. Wait until the firmware installation is completely finished (takes about 10 minutes). Ignore any error messages at the end of the firmware update.

    Now skip past Step 1B and proceed to Step 2 below, entitled LINKSTATION CONFIGURATION. All remaining steps are the same whether you are using a LinkStation Pro or a LinkStation Live.


    ***STEP1B: INSTALL JTYMOD FIRMWARE ON LINKSTATION LIVE***
    This section applies only to LinkStation Live hardware. If you are using a LinkStation Pro, you should follow the instructions in Step 1A instead.

    If you haven’t already done so, download the stock Buffalo firmware for your LinkStation Live to your computer. Get the firmware file from http://www.buffalotech.com/support/downloads/. Be certain to get the firmware which corresponds to your exact model of LinkStation (e.g. HS-DH1000GL), otherwise the updater software that comes with it won’t be able to find your unit to update. You can locate the exact model number of your LinkStation on a printed label on your unit. You can also retrieve the model number electronically using Buffalo Navigator software.

    Extract the Buffalo firmware from the zip file using a standard zip utility. This should create a new folder containing several files.
    EXTREMELY IMPORTANT: Inside the firmware folder, immediately delete the file u-boot.buffalo.updated. (If accidentally installed, the file could brick your LinkStation.)

    Normally the Buffalo firmware updater utility (LSUpdater.exe) does not detect a LinkStation which is already running the firmware revision that came with the updater. To get around this, edit the file lsupdater.ini using a text editor such as Notepad:

    Change:
    [Flags]
    VersionCheck = 1
    to be
    [Flags]
    VersionCheck = 0

    Also, to allow activation of Debug mode to prevent inadvertently installing a u-boot.buffalo.updated file that could brick your unit, add:

    [SpecialFlags]
    Debug = 1

    Then, edit the file linkstation_version.txt as follows: (versions shown are from 2.10 firmware):

    VERSION=VERSION=2.10-0.01
    increase version number, e.g. VERSION=2.20-001

    BOOT=1.09
    DO NOT CHANGE

    KERNEL=2007/03/07 14:16:20
    make date newer, e.g. KERNEL=2008/03/07 11:16:12

    INITRD=2007/06/12 17:37:02
    make date newer, e.g. INITRD=2008/06/12 17:37:02

    ROOTFS=2007/09/05 14:38:55
    make date newer, e.g. ROOTFS=2008/09/05 14:38:55

    The above edits to the linkstation_version.txt file are only to trick LSUpdater when it checks that the update is newer than the firmware installed on the LinkStation. It will only install what appears to be newer firmware. (The dates are only used as a check by LSUpdater to compare with dates encoded in the firmware on the LinkStation. It only matters that they are more recent than the firmware that is running at the time you flash, and what you choose for them will not be recorded on the LinkStation.)

    Download JTYMOD firmware from http://oh1jty.toimii.net/linkstation...03-jtymod5.zip (or a later version that would be listed in the “Download from” area on the JTYMOD web page http://buffalo.nas-central.org/index...abled_firmware.)

    Extract the JTYMOD firmware from the zip file using a standard zip utility. This will create a new folder containing several files.
    EXTREMELY IMPORTANT: Inside the firmware folder, immediately delete the file u-boot.buffalo.updated. (If accidentally installed, the file could brick your LinkStation.)

    Copy these three files from the JTYMOD directory, and paste them into the directory containing the stock Buffalo firmware:
    uImage.buffalo
    initrd.img
    hddrootfs.img

    Confirm that you wish to overwrite (replace) the corresponding files in the directory containing the stock firmware.

    Double click the Buffalo firmware updater LSUpdater.exe in the directory to which you just copied those files. DO NOT CLICK UPDATE YET!
    Before you do anything else, copy down the IP address of your LinkStation. It will likely be in the form 192.168.1.XXX, where the last three digits are determined by your network router.

    Then, in the Windows Taskbar at the bottom of your screen, right-click on the Buffalo Updater.
    Select Debug.
    UNCHECK the box for Update BOOT in the upper right. This prevents inadvertent installation of a u-boot.buffalo.updated file that could brick your unit. (If you already deleted that file, this step shouldn’t be necessary, but it is better to be on the safe side.)
    Leave the boxes checked for KERNEL, initrd, and rootfs.
    Click OK to exit the Debug window.

    In the Buffalo Updater window, now click Update.
    If you are asked for an admin password, enter “password” (without the quotes).
    The JTYMOD firmware installation will now proceed. The LinkStation will reboot itself several times. Wait until the firmware installation is completely finished (takes about 10 minutes). When you get the message that the updater couldn’t confirm a response, click No.

    Proceed to Step 2 below, entitled LINKSTATION CONFIGURATION. All remaining steps are the same whether you are using a LinkStation Pro or a LinkStation Live.
    Last edited by TiredLegs; 2009-01-19 at 19:18. Reason: Revised for Squeezecenter 7.3.1

  3. #3
    Senior Member
    Join Date
    Jun 2006
    Posts
    747

    ***Step 2: BASIC LINKSTATION CONFIGURATION***

    ***STEP 2: BASIC LINKSTATION CONFIGURATION***

    Point your web browser to http://192.168.1.XXX, substituting the actual LinkStation IP address that you copied down before you installed JTYMOD.

    Login to LinkStation via the web browser, using the default username and password
    user: admin
    password: password

    The resulting window will look like the standard Buffalo LinkStation browser window, but it will say “FreeStation” in the upper left, and it has some additional settings not in the standard firmware.

    Set a static IP Address for your LinkStation, so your Squeezeboxes will always know where to find your Squeezecenter server:
    Go to Network->IP Address Properties.
    Select the radio button to Disable Automatic via DHCP.
    Change the entry in the IP Address box to be 192.168.1.130
    Click Apply.
    Click the link to confirm the new IP Address.

    Your web browser will now be at http://192.168.1.130/cgi-bin/top.cgi.
    Log in again:
    user: admin
    password: password

    Set up a folder to deposit your music files into:
    Go to Shared Folders->Shared Folders Setup.
    Click Add.
    Enter a Shared Folder Name, such as “MUSIC” [without the quotes] and a description, such as “My music for Squeezebox”.
    Leave Windows and Apple support checked.
    Leave the radio button for Read/Write selected.
    Click the radio button for Recycle Bin to Disable.
    [If you leave the Recycle Bin enabled, music files that you think you deleted from the Music folder will still be there, and will still be scanned by Squeezecenter.]
    You may also enter Access Restrictions on this page, although you may leave that disabled, in which case anyone on your local network will be able to access the music folder to add or delete files.
    Click Apply.

    You need to reset the root password so that you will be able to login to the LinkStation via Telnet, which you will do shortly.
    Go to Maintenance->Debug.
    Click “Clear Root Password”.

    Enable Telnet:
    Go to Maintenance->Services
    Select the radio button to enable Telnet daemon
    Click Apply.
    The colored dot next to “Telnet state” should now be green.

    You may now close the web browser page and proceed to Step 3.
    Last edited by TiredLegs; 2009-01-06 at 06:17. Reason: disable recycle bin in shared folders

  4. #4
    Senior Member
    Join Date
    Jun 2006
    Posts
    747

    ***Step 3: TELNET INTO LINKSTATION***

    ***STEP 3: TELNET INTO LINKSTATION***

    MAKE SURE THAT YOU HAVE TEMPORARILY TURNED OFF WINDOWS FIREWALL. You can access this setting in Control Panel->Security.

    If you are running Windows Vista, you may need to enable Telnet on your computer.
    Go to Control Panel->Programs->Programs and Features
    In the panel on the left side, select "Turn Windows Features On and Off".
    Check "Telnet Client".
    Click the OK button.

    Login to the LinkStation using Telnet:
    Open a command prompt window on your computer. In Windows, you can do this by entering CMD.EXE in the text entry bar on your Windows Startup menu or Windows Explorer.

    The best way to enter commands in the prompt window is to copy and paste them from these instructions. In Windows, you paste a command into the prompt window by right-clicking in the window, then selecting Paste (CTRL-V does not work in the prompt window).

    In the command prompt window, enter
    telnet 192.168.1.130
    Login as “root” [without the quotes]. No password is needed.

    If the LinkStation fails to connect via Telnet, make sure that your Windows Firewall is turned off.
    Also, JTYMOD firmware automatically disables Telnet after a period of time. This reduces the chances that a third party could hack into your LinkStation. So if you are still unable to connect to your LinkStation via Telnet, you may need to re-enable Telnet in the LinkStation. To do that, go back to the LinkStation configuration window in your web browser at http://192.168.1.130/cgi-bin/top.cgi.
    Log in again as:
    user: admin
    password: password
    Go to Maintenance->Services
    If the colored dot next to “Telnet state” is not green, select the radio button to enable Telnet daemon.
    Click Apply.
    The colored dot next to “Telnet state” should turn green.
    You should now be able to login to the LinkStation via Telnet in the command prompt window.

    Once logged in via Telnet, you are ready to install IPKG and Squeezecenter.
    Last edited by TiredLegs; 2008-12-27 at 12:47.

  5. #5
    Senior Member
    Join Date
    Jun 2006
    Posts
    747

    ***Step 4: INSTALL IPKG AND SQUEEZECENTER***

    ***STEP 4: INSTALL IPKG AND SQUEEZECENTER***

    Install IPKG:
    While connected to the LinkStation via Telnet, enter these commands in the command prompt window:
    mkdir /mnt/disk1/tmp

    cd /mnt/disk1/tmp

    wget http://ipkg.nslu2-linux.org/feeds/op..._1.2-5_arm.xsh

    sh lspro-bootstrap_1.2-5_arm.xsh

    Install Squeezecenter:
    The IPKG Squeezecenter package is currently v7.3.1.

    Enter these commands in the command prompt window:
    /opt/bin/ipkg update

    /opt/bin/ipkg install squeezecenter bash flac sed sox

    Five or ten minutes into the execution of the last command above, it may pause and ask you to enter the SQUEEZECENTER_HOME location. If that comes up, just hit the Enter key, which will select the default location (/home/slimserver).

    To fix some technical issues and prevent problems with scanning your music library, before you run Squeezecenter, you need to edit a few files. You will do this by using the “sed” text editor built into Linux. [With help from forum member bzhou, we've debugged the automatic editing process using sed, so you no longer need to manually edit the files using "vi" as was previously described in this thread.]

    cd /opt/share/squeezecenter

    /opt/bin/sed -i.orig -e '/dbh->STORE.*AutoCommit.*0/s/^/#/' /opt/lib/perl5/site_perl/5.8.8/arm-linux/DBI.pm

    /opt/bin/sed -i.orig -e '/dbh->STORE.*AutoCommit.*0/s/^/#/' CPAN/DBI.pm

    /opt/bin/sed -i.orig -e "/Slim::Schema->storage->dbh->{'AutoCommit'} = 0/s/^/#/" scanner.pl

    /opt/bin/sed -i.orig -e "/Slim::Schema->storage->dbh->{'AutoCommit'} = 0/s/^/#/" Slim/Schema/Playlist.pm

    /opt/bin/sed -i.orig -e "/Slim::Schema->storage->dbh->{'AutoCommit'} = 0/s/^/#/" Slim/Music/Import.pm


    You are now ready to launch Squeezecenter. Enter:
    /opt/etc/init.d/S99squeezecenter start

    After the command prompt returns, you can type exit to end the Telnet session.
    Wait at least five minutes to be sure that Squeezecenter has fully started. Then point your web browser to http://192.168.1.130:9000 to run the initial Squeezecenter setup.
    On the SqueezeNetwork Account page of the setup, if you don’t have a SqueezeNetwork account already, or if you don’t even know what SqueezeNetwork is, just click Skip to move on. You can configure SqueezeNetwork later.
    When the setup asks for the location of your music folder, you should find the shared folder that you created earlier at mnt/disk1/[your folder name], e.g. mnt/disk1/music. You can skip entering a Playlist folder location for now by clicking Next without selecting a folder.
    By the time you click Finish in the Squeezecenter setup, any Squeezeboxes connected to your network should have found the Squeezecenter server.

    Don’t forget to turn your Windows Firewall back on!

    You can now load up the music folder on your LinkStation with all your music files. You access the folder from your computer by using Windows Explorer and selecting Map Network Drive.

    If you reboot your LinkStation, Squeezecenter restarts automatically, so no need to manually launch it.


    ***UPGRADING SQUEEZECENTER***

    After Squeezecenter is installed, to update to a newer version when it's available, I had to uninstall and reinstall IPKG and Squeezecenter. To do that, Telnet in to the LinkStation as described above, then enter this sequence of commands:

    cd /mnt/disk1/tmp

    sh lspro-bootstrap_1.2-5_arm.xsh

    rm -rf /mnt/disk1/.optware

    rm -rf /usr/lib/ipkg

    reboot

    After the reboot is complete, Telnet back in to the LinkStation as described above, then enter:

    cd /mnt/disk1/tmp


    sh lspro-bootstrap_1.2-5_arm.xsh

    /opt/bin/ipkg update

    /opt/bin/ipkg install squeezecenter bash flac sed sox

    After a new version is installed, you will need to re-edit the files using the "sed" commands, the same as you did in Step 4 above, in order for music scanning to work correctly.

    After the Squeezecenter reinstall is complete, start Squeezecenter:

    /opt/etc/init.d/S99squeezecenter start

    If Squeezecenter fails to start up properly, you might need to reboot your LinkStation. You can do this from Telnet by entering:

    reboot

    ***YOU CAN HELP***

    Special thanks goes to forum member bzhou, who has been making and maintaining the IPKG versions of Squeezecenter.

    If you find value in using the IPKG method of installing Squeezecenter, you can help fund its hosting costs by making a contribution on the Linux Optware site http://nslu2-linux.org/wiki/Main/Donate.

    Enjoy your new Squeezecenter server. If you discover any errors in the above instructions, please post in this thread, and I will adjust the instructions accordingly.
    Last edited by TiredLegs; 2009-06-08 at 06:24. Reason: Added installation of sox for support of hi-res music files on SB3 (SB Classic)

  6. #6
    Junior Member
    Join Date
    Dec 2008
    Posts
    2
    Hi TiredLegs

    Just wanted to let you know that I've succeeded in getting Squeezecenter up & running on an LS-CHL model. It seems to use arm processor so I found your instructions easy to follow & priceless.
    I simplified things by using acp commander to open root access to the LS. Once that was done, I didn't need to modify the firmware (JTYMOD) and went straight into the ipkg section. "wget" is present so it was all quite simple.. - DBI.pm was read-only but once that was changed, the instructions were spot-on.

    many thanks!!

    Ferris

  7. #7
    Junior Member
    Join Date
    Dec 2008
    Posts
    4
    Great work TiredLegs!

    I also put Squeezecenter 7.3.1 on a LS-CHL by omitting all the difficult steps. Here's my version, simplified for the stock LS-CHL firmware 1.07 and Windows:

    Log in:
    ----------------------
    Download acp_commander.jar from (http://downloads.buffalo.nas-central..._commander.jar) and put it in some folder on your Windows PC (i.e. C:\Acp_commander)
    Get the ip address of your NAS from your router or Buffalo util (i.e. 192.168.1.11)
    Disable Windows firewall (really)
    From the dos prompt in Windows (right-click to paste copied lines of text into the dos window, not CTRL-V):
    C:\Acp_commander>java -jar acp_commander.jar -t 192.168.X.XX -o
    re-enable Windows firewall (finally)
    From the dos prompt in Windows:
    C:\Acp_commander>telnet 192.168.X.XX
    login as "root", no password
    LS-CHL3E6 login: root

    The Java utility temporarily enables telnet support, it must be run after every reboot of the NAS if you want to log in with telnet again. Type exit anytime you want to end the telnet session.

    Install the bootstrap:
    ----------------------

    root@LS-CHL3E6:~# mkdir /mnt/disk1/tmp
    root@LS-CHL3E6:~# cd /mnt/disk1/tmp
    root@LS-CHL3E6:/mnt/disk1/tmp# wget http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/lspro-bootstrap_1.2-5_arm.xsh
    root@LS-CHL3E6:/mnt/disk1/tmp# sh lspro-bootstrap_1.2-5_arm.xsh

    The bootstrap appends ipkg and other linux utilities to the OS.

    Update the package list and install Squeezecenter:
    ----------------------

    root@LS-CHL3E6:/mnt/disk1/tmp# ipkg update
    root@LS-CHL3E6:/mnt/disk1/tmp# ipkg upgrade
    root@LS-CHL3E6:/mnt/disk1/tmp# ipkg install flac squeezecenter bash sed

    This will take some time to download/install everything. Press enter at the end to select the default SQUEEZECENTER_HOME location.

    Modify Squeezecenter to fix the music library search flaw:
    ----------------------

    root@LS-CHL3E6:~# chmod 644 /opt/lib/perl5/site_perl/5.8.8/arm-linux/DBI.pm
    root@LS-CHL3E6:~# cd /opt/share/squeezecenter
    root@LS-CHL3E6:/opt/share/squeezecenter# sed -i.orig -e '/dbh->STORE.*AutoCommit.*0/s/^/#/' /opt/lib/perl5/site_perl/5.8.8/arm-linux/DBI.pm CPAN/DBI.pm
    root@LS-CHL3E6:/opt/share/squeezecenter# sed -i.orig -e "/Slim::Schema->storage->dbh->{'AutoCommit'} = 0/s/^/#/" scanner.pl Slim/Schema/Playlist.pm Slim/Music/Import.pm

    edit: corrected sed command syntax. Sorry!

    sed is a command line editor that will insert the # character to comment out lines in the following files and save originals as *.orig
    sed gives no response when run and the copy/paste action into a windows telnet box can be abbreviated in a disturbing way, use arrow keys to examine the line if unsure. The crazy characters are real. Note: Running these commands more than once will overwrite the backup with a modified version and insert another # sign in the active version, but will not cause any other problems.


    Verify the modification of each file:
    ----------------------
    diff /opt/lib/perl5/site_perl/5.8.8/arm-linux/DBI.pm /opt/lib/perl5/site_perl/5.8.8/arm-linux/DBI.pm.orig
    diff /opt/share/squeezecenter/CPAN/DBI.pm /opt/share/squeezecenter/CPAN/DBI.pm.orig
    diff /opt/share/squeezecenter/scanner.pl /opt/share/squeezecenter/scanner.pl.orig
    diff /opt/share/squeezecenter/Slim/Schema/Playlist.pm /opt/share/squeezecenter/Slim/Schema/Playlist.pm.orig
    diff /opt/share/squeezecenter/Slim/Music/Import.pm /opt/share/squeezecenter/Slim/Music/Import.pm.orig

    Each command should return some very linuxey garlbeygook. In the middle of each "paragraph" should be the same line listed twice, marked with -/+ signs to indicate after/before. The first version (modified) should have the # character near the beginning, the second version (original) should not. If the diff command shows nothing, sed must not have worked - try again starting with the chmod command or go commando and edit all 5 files with vi to comment out the following offending lines:

    # $dbh->STORE('AutoCommit', 0);
    # Slim::Schema->storage->dbh->{'AutoCommit'} = 0;

    Restart the linkstation:
    ----------------------
    root@LS-CHL3E6:/mnt/disk1/tmp# reboot

    Type exit or press Ctrl-C to return to the dos prompt while it reboots, use the up/down arrow keys to re-enter the java and telnet lines to log back in (remember to disable/enable firewall again).

    Check that the server is running after the reboot:
    ----------------------
    root@LS-CHL3E6:~# /opt/etc/init.d/S99squeezecenter status (status, start, or stop as needed)
    check logfile with: tail /home/slimserver/squeezecenter.log (tail shows the end of the file, cat shows the entire file. There's surely lots of errors.)

    Add some music:
    ----------------------
    Access the NAS from Windows by putting the address \\192.168.X.XX\share in Start->Run. Create a "music" folder and a "music\playlists" folder to be referenced in the next step. Copy a handful of songs over to test. (These folders are visible in linux/telnet under /mnt/disk1/share/)

    Enter address http://192.168.X.XX:9000 in your web browser to setup Squeezecenter. Allow a minute or two for Squeezecenter to start after a reboot/restart, even after the status command shows it running.

    It's painfully slow, a bit unreliable, and I get lots of errors like:
    Slim::Networking::SqueezeNetwork::PrefSync::_syncU p_error (576) Sync Up failed: No such player: 59:de:90:d8:b4:c6
    and:
    mDNSResponderPosix: Error reading service file /home/slimserver/cache/mDNS.conf
    and of course:
    (1398) Warning: [13:27:57.1954] commit ineffective with AutoCommit enabled at /opt/share/squeezecenter/CPAN/DBIx/Class/Storage/DBI.pm line 706.

    But it works! Thanks to all that worked so tirelessly to make this possible!
    Last edited by vespa; 2009-03-08 at 16:02. Reason: fixed sed command syntax

  8. #8
    Senior Member
    Join Date
    Jun 2006
    Posts
    747
    Glad that people have been able get Squeezecenter up and running.

    When I originally attempted to install Squeezecenter using IPKG on my own LinkStation Pro, I tried to use acp commander, but I ran into several java errors that I couldn't figure out how to get around. Those errors might have been related to the particular PC I was using to do the install. Nevertheless, I spent hours trying to get acp commander to work, but never succeeded.

    Then I the discovered JTYMOD firmware, and it worked the very first time. So I figured I would write up the instructions that way.

    The sed commands to edit the files never worked in my set up, so I resorted to the manual editing with vi. I wish the sed commands did work, because it was harder to explain the vi steps in instructions. [Note: sed commands have now been corrected and inserted into the original instructions.]

    Of course, any method that achieves the objective of getting Squeezecenter running is a success.
    Last edited by TiredLegs; 2009-05-02 at 07:00.

  9. #9
    Junior Member
    Join Date
    Jan 2009
    Posts
    7
    I have installed squeezecenter and i think its working as intended. But my controller keeps showing me the "Error: Missing Firmware Server can't connect ot internet to obtain firmware update" but as i read the guideline I can do nothing about this?

    Its very annoying as it ruins the use of the controller as you cant see half the screen duo to the constant spamming of the error message. Do you know how this can be solved?

  10. #10
    Senior Member
    Join Date
    Jun 2006
    Posts
    747
    Quote Originally Posted by nbramsen View Post
    I have installed squeezecenter and i think its working as intended. But my controller keeps showing me the "Error: Missing Firmware Server can't connect ot internet to obtain firmware update" but as i read the guideline I can do nothing about this?

    Its very annoying as it ruins the use of the controller as you cant see half the screen duo to the constant spamming of the error message. Do you know how this can be solved?
    I don't have a controller, so I don't know how to address your problem. Perhaps you can post a question about that error message in the Duet forum, where others might have experienced the same issue.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •