Buffalo Linkstation Install Optware Packages

1101

Buffalo Linkstation Install Optware Packages

Install pyload on a Router. The Buffalo Linkstation live v3 and pro v3. To install the needed packages for pyLoad. Aria2 download manager for Buffalo NAS LS-WVL. Existing Buffalo NAS version is 1.64Mod Go to to update 2. Install Optware.

Board bottom image LinkStation Pro Duo LS-WVL/R1 Machine Feroceon-KW (Kirkwood) Board MVLSWV CPU 88FR131 (88F6282) 1.6GHz Clock Speed (arm5te) RAM 256MB Flash ROM 512KB SPI flash + 512MB Hynix NAND flash Other NIC 1000/100/10Mbps USB 1 x USB 2.0 HiSpeed internal HDD ST32000542AS IDE/SATA Controller Drive Capacity 2TB, 4TB Fan initial Networkname LS-WVL. (last 3 are the end of the MAC address) SOFTWARE Toolchains Opened Firmwares • Telnet/SSH enabled firmware • (and LW-WVL) • (and LW-WVL) • (and LW-WVL) using dm-crypt Development Tools GPL Kernel Prebuild packages • Optware feed is cs08q1armel (untested) • Available packages: • See Optware & IPKG Installation Guide below.

Buffalo Linkstation Install Optware Packages

Confirmed to work on LS-WVL. • Guide to IPKG: HARDWARE Board Please add here if you find or do some pictures. Hardware Hacks Please add here if you find or do some hardware hacks.

Other Please add here if you find or do some hardware hacks. Optware & IPKG Install Guide Once you have root access, you can start to install packages using IPKG.

NOW EVEN EASIER, USING STOCK BUFFALO FIRMWARE! IPKG WITH STOCK BUFFALO FIRMWARE: THE EVEN EASIER WAY TO INSTALL SQUEEZECENTER ON BUFFALO LINKSTATION PRO (LS-GL) OR LINKSTATION LIVE (HS-DHGL & LS-CHL) MODELS WITH ARM PROCESSOR CURRENTLY, THE IPKG PROCESS DESCRIBED IN THIS THREAD 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 STOCK BUFFALO FIRMWARE. (THE SAME ISSUE ALSO AFFECTS COMPATIBILITY WITH JTYMOD FIRMWARE FOR BUFFALO LINKSTATIONS.) The latest version of Squeezecenter available as IPKG can always be seen at (Search that page for 'squeezecenter'.) This is a revised set of instructions to further simplify installation of Squeezecenter on Buffalo LinkStations. The prior instructions (at were written to install JTYMOD modified firmware in the LinkStation before installing IPKG Squeezecenter. Those instructions still work, but this version of instructions will install Squeezecenter with the stock Buffalo firmware. I was finally able to overcome what turned out to be simple problem that had previously prevented me from installing IPKG Squeezecenter on my own LinkStations with the stock firmware.

So these new instructions eliminate the need to install any firmware at all. Now, fewer steps are required, and chances of bricking your unit are further reduced.

In addition, if you are using a LinkStation Live model, the method described in this thread retains the “Live” functionality of the stock firmware that JTYMOD firmware loses. The “Live” functionality includes web access, a print server, and built-in DLNA media server, although DLNA is not used by Squeezeboxes. (JTYMOD is a modified version of LinkStation Pro firmware. When installed on a LinkStation Live, it makes the Live behave like a Pro.) Be aware, however, that a number of users have reported that the web access functionality for the LinkStation Live uses port 9000, which conflicts with Squeezecenter's use of that same port. Therefore, LinkStation Live users may need to disable web access functionality in the device, or manually reconfigure the LinkStation Live or Squeezecenter to use a different port for web access. (If you already have Squeezecenter installed on your LinkStation Live and are encountering this problem, see post #88 in this thread for how to change the Squeezecenter setting.) If you already have JTYMOD installed on a LinkStation Pro or LinkStation Live HS-DHGL and wish to revert to the stock firmware to perform the Squeezecenter installation in this thread, see post #7. At this time, the specific procedure to revert a LinkStation Live LS-CHL is still unclear.

(I don't have an LS-CHL to test with.) Once again, 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 Linux.

It is essentially a “For Dummies” guide to installing Squeezecenter on a LinkStation Pro or LinkStation Live. Thanks especially to forum member bzhou for maintaining the IPKG version of Squeezecenter.

If you find value in using the IPKG installation of Squeezecenter, you can help fund its hosting costs, by making a contribution on the Linux Optware site And thanks also to forum member vespa for outlining the easier steps for use with the stock firmware on the LS-CHL in the earlier thread (see post I have tested this installation process from a Windows Vista 64-bit PC to both a LinkStation Pro (LS-GL series) and LinkStation Live (HS-DHGL series). Users also have reported success using this installation process with the newer LinkStation Live (LS-CHL series) and LinkStation Pro Duo (LS-WGL series). As far as I know, this set of instructions only works on the LinkStation models listed above. (These models use an ARM processor.) These instructions may or may not work with other LinkStation models, and you could brick your unit if you try, so only attempt to do so at your own risk. The installation process should be the same from any PC running Windows XP or Vista. If you’re running a Mac, somebody else will need to adapt the directions.

If you're running Linux and know what you're doing, you shouldn't need these “For Dummies” instructions. What is IPKG? IPKG (Itsy Package Management System using Optware) is a quick and easy way to get Squeezecenter installed on a Buffalo LinkStation Pro or LinkStation Live. (See for more info on IPKG.) For the average Joe or Jane user, IPKG is 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 ), 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.

After Squeezecenter is installed, the LinkStation graphical web interface permits you to control many settings of the LinkStation without further use of Telnet or Linux code commands, as would be the case for a full FreeLink installation of Squeezecenter. And by retaining the stock firmware, you can configure shared folders without using Samba, which I find particularly appealing. If you don’t even know what Samba is, IPKG Squeezecenter will save you many headaches of configuring access permissions.

***WARNING*** BEFORE UNDERTAKING THIS PROCESS ON 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. PROCEED AT YOUR OWN RISK. ***DISABLE FIREWALL*** BEFORE PROCEEDING, TEMPORARILY TURN OFF WINDOWS FIREWALL UNTIL YOU HAVE COMPLETED THE SQUEEZECENTER INSTALLATION. The Firewall may interfere with the process. 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. NOTE THAT MOST LINUX COMMANDS USED IN THIS INSTALLATION ARE CASE SENSTIVITE, e.g.

“Squeezecenter” is not the same as “SQUEEZECENTER” or “squeezecenter”. To minimize entry errors, I recommend that you enter the commands by cutting and pasting them from these directions, rather than retyping them. Your computer must be connected to the Internet for this procedure to work, because some of the commands download files from online servers. ***STEP 1: BASIC LINKSTATION CONFIGURATION*** Point your web browser to substituting the actual IP address of your LinkStation.

If you don’t know the IP address of your LinkStation, use the Buffalo NAS Navigator utility that came with your LinkStation to find it. Login to LinkStation via the web browser, using the default username and password user: admin password: password I strongly recommend setting 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 Log in again: user: admin password: password Set up a folder for the Squeezecenter installation procedure to deposit some necessary files into: Go to Shared Folders->Shared Folders Setup.

Enter the Shared Folder Name, “share” [without the quotes]. You must use the name “share” for this folder. Leave Windows and Apple support checked. Leave the radio button for Read/Write selected. Click the radio button for Recycle Bin to Disable. Set up a folder to deposit your music files into: Go to Shared Folders->Shared Folders Setup.

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.

You may now close the web browser page and proceed to Step 2. ***STEP 2: TELNET INTO THE LINKSTATION*** Telnet is a way to communicate with the LinkStation that permits much greater access to the LinkStation than can be done via the web browser interface.

These instructions use Telnet to get Squeezecenter installed on the LinkStation. The stock Buffalo firmware does not include Telnet access, so the steps below add it, along with a missing “wget” command necessary for the Squeezecenter installation procedure. (Note: the LinkStation Live LS-CHL models already have “wget” enabled, but the exact procedure below should still work fine on those models. If someone discovers otherwise, please post your findings in this thread.) 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.

On your PC, go to the directory C: Temp. Create a new directory there with the name “LinkStationTelnet”. Make certain there are no spaces in the directory name. You should now have C: Temp LinkStationTelnet. From download and save the file acp_commander.jar in the new directory C: Temp LinkStationTelnet. 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, change the directory to C: Temp LinkStationTelnet: cd C: Temp LinkStationTelnet Run acp_commander to install Telnet on the LinkStation and use the “addons” option to install the wget command: java -jar acp_commander.jar -t 192.168.1.130 -o -addons If you receive a SocketTimeoutException error, it probably means your Windows Firewall is still enabled. Disable Windows Firewall and try the command again.

Now, 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 still turned off. Once logged in via Telnet, you are ready to install IPKG and Squeezecenter. ***UPGRADING SQUEEZECENTER*** After Squeezecenter is installed, you can easily update to a newer version when the IPKG for it becomes available.

There is no reason to do this procedure unless a newer IPKG is available. You can see the current Squeezecenter version number that is available as an IPKG at (Search the page for 'squeezecenter'.) New streamlined upgrade procedure (thanks boomjoe): /opt/etc/init.d/S99squeezecenter stop /opt/bin/ipkg update /opt/bin/ipkg upgrade After a new version is installed, you will probably need to re-edit the files using the sed command lines, the same as you did in Step 3 above, in order for music scanning to work correctly. After the Squeezecenter reinstall is complete, you might again need to remove a file that sometimes prevents Squeezecenter from starting up properly: rm /home/slimserver/squeezecenter.pid 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 Bear in mind that a new IPKG version only becomes available after a knowledgeable and considerate person makes it from an official Squeezecenter release. Slim Devices does not make the IPKG.

I do not make the IPKG. (I don’t even know how.) Enjoy your new Squeezecenter server. ********** For those of you who have already installed JTYMOD firmware and wish to revert to the stock firmware to perform the Squeezecenter installation described in this thread, the procedure in this post should revert you to the stock firmware. ********** Before proceeding, be sure to have all your files backed up somewhere other than the LinkStation. This firmware installation process should leave files intact in your shared folders on the LinkStation, but it is much better to be on the safe side whenever installing firmware.

Download the stock Buffalo firmware for your LinkStation Pro or LinkStation Live to your computer. Get the firmware file from 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.) The Buffalo firmware updater utility (LSUpdater.exe) may not detect a LinkStation which is already running JTYMOD firmware. 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 already running, and what you choose for them will not be recorded on the LinkStation.) Double click the Buffalo firmware updater LSUpdater.exe. DO NOT CLICK UPDATE YET!

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 firmware installation should 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.

You may also have other error messages appear at the end of the process, but they don’t necessarily mean anything went wrong. To confirm that the firmware installation succeeded, point your web browser to, substituting the actual IP address of your LinkStation. You should be able to login with the default username and password: user: admin password: password Once logged in, you should now see the stock Buffalo firmware web interface, which says “LinkStation” in the upper left, rather than “FreeStation” that would appear when JTYMOD is installed. I have just downloaded the lschl-107.zip and the text file contains the following: VERSION=1.07-0.65 BOOT=1.22 KERNEL=2009/02/23 17:13:14 INITRD=2009/02/23 17:13:56 ROOTFS=2009/02/23 17:13:40 FILE_BOOT = u-boot.buffalo.updated FILE_KERNEL = uImage.buffalo FILE_INITRD = initrd.img FILE_ROOTFS = hddrootfs.img So should I still change as per your previous posting, or leave it as it is? The dates are all newer than the JTYMOD firmware dates already, so you shouldn't need to change those.

However, you will probably still need to increase the 'VERSION=' number to one higher than the firmware version number currently running in the LinkStation. Try that and report back.

After formatting, I tried using your steps to revert back to stock 1.07 firmware failed, no matter what edits I made to the text or boot options files. My NAS is a LS-CHL, however, on closer inspection, navigation reports a LS-GL (Pro) model instead! I guess that might be expected, as you have mentioned that the JTYMOD firmware is primarily designed to be used on the LS-GL (Pro). That's maybe why I tried downloading the correct firmware (lschl-107.zip), made the necessary changes (deleted that UPDATED file, edited text file, enabled debug), LSUpdater keeps complaining LS-CHL is not found. So now, I had downloaded the correct LS-GL firmware (1.15) and was able to revert back to the stock firmware, which is good news to me. BUT, my model is a LS-CHL now working on a LS-GL firmware, with lesser functionality. How do I 'upgrade' back to my original LS-CHL 1.07 firmware?

I don't have an LS-CHL model myself to test it, but it works on the other models: Log into the LinkStation via Telnet. Enter this command to open up the boot_options file using the vi text editor: vi /boot/boot_options press the [i] keyboard key to enter 'edit mode'. Enter this line into the file: MENU_TIMEOUT=EM Press the [ESC] key to get out of edit mode Enter ZZ [Shift-Z, twice in a row] to save and exit the file. Reboot the LinkStation: reboot The LinkStation should reboot to an 'emergency mode' state where you can install the stock firmware. You might still need to do it with the edited version number and dates. OK, I retried the following as a last resort. Download both LS-GL and LS-CHL firmware versions.

Since my NAS is recognised by NasNavi as a LS-GL version, let it be. My workaround was to overwrite the common files of the LS-GL with the LS-CHL version: - hddrootfs.img - initrd.img - u-boot.buffalo.updated - uImage.buffalo and leave the files of LS-GL intact: - linkstation_version.txt - LSUpdater.exe - lsupdater.ini The above 3 stock LS-GL files is to fool the installer to still look for my LS-GL device while forcing the LS-CHL img & boot files to the NAS. I followed the steps in to force a firmware update to revert back to LS-CHL. After forcing the firmware upload, the NAS restarts, make the necessary static IP address changes, did whatever changes I can remember, followed by another restart, and viola! NasNavi now correctly reports the LS-CHL device on my home network. There is a another new problem though, the top LED frequently alternates between violet & blue. NasNavi2 reports this as E22: Error mounting disk2/3/4.

Appears it is constantly scanning (& attempt to mount) the other 3 non-existent drive. Now I am really stumped. What shall I do next? OK, I retried the following as a last resort.

Download both LS-GL and LS-CHL firmware versions. Since my NAS is recognised by NasNavi as a LS-GL version, let it be. My workaround was to overwrite the common files of the LS-GL with the LS-CHL version: - hddrootfs.img - initrd.img - u-boot.buffalo.updated - uImage.buffalo and leave the files of LS-GL intact: - linkstation_version.txt - LSUpdater.exe - lsupdater.ini The above 3 stock LS-GL files is to fool the installer to still look for my LS-GL device while forcing the LS-CHL img & boot files to the NAS. I followed the steps in to force a firmware update to revert back to LS-CHL. After forcing the firmware upload, the NAS restarts, make the necessary static IP address changes, did whatever changes I can remember, followed by another restart, and viola!

NasNavi now correctly reports the LS-CHL device on my home network. There is a another new problem though, the top LED frequently alternates between violet & blue. NasNavi2 reports this as E22: Error mounting disk2/3/4. Appears it is constantly scanning (& attempt to mount) the other 3 non-existent drive. Now I am really stumped. What shall I do next? That type of file substitution was going to be my next suggestion.

Glad you were able to make it work. However, the Error mounting disk2/3/4 seems like it loaded the firmware for a LinkStation Quad, rather than a LinkStation Live. Perhaps that is related to loading the new u-boot file, which I would not have recommended. You might want to post in the Buffalo forum for a solution to the error. OK, yet another update.

I was thinking of running to the service center to get it fixed, started deleting off my MP3/Sharedfiles and the SC (/opt.) files, did an erase of the HDD. Rebooted and the alternating violet/blue lights went away and showed a steady blue LED instead.:) Hence I saved a trip down to the service centre.:p For those who own this LSLive (LS-CHL model), AND taken the earlier steps of using step 1B (and wish to revert back to stock firmware, please take note of this potential problem. To clarify, the alternating violet/blue light happens: - AFTER force-upgrading from LS-GL to LS-CHL, and - BEFORE applying TiredLegs's instructions show in this first page I therefore conclude there is nothing wrong with his steps involved.

So if LS-CHL users have this problem, please get it fixed by doing a system/HDD init and complete erase of the HDD before proceeding further. Also, take note that the rear 3-way switch should be set to the ON position, rather than AUTO (powersave mode) position.

I found that the NAS goes to sleep after a period of inactivity, and the SC is unable to wake up the NAS at all. A scheduled shutdown (accessible in the Web UI) is a better choice.

Thanks to TiredLegs all for the tips/tricks. The installation appears to have gone well, although I didn't understand all the commands or the messages!! I started slimserver and went to login using:9000 IP access and straight away it asks me for a username and password - I have tried the linkstation admin password I have but it is rejected - what password / user is it looking for. Right figured out that my user access for the linkstation works, but I just get to the buffalo web access page that lists all the files on the machine. There is no sign of slimserver?

Are there any checks that anyone can suggest. I feared this would not be as simple as I hoped - all help gladly received - only bought the squeezebox on the great support offered hear.

The installation appears to have gone well, although I didn't understand all the commands or the messages!! I started slimserver and went to login using:9000 IP access and straight away it asks me for a username and password - I have tried the linkstation admin password I have but it is rejected - what password / user is it looking for. It's perfectly fine not to understand the commands and messages, as long as you enter them exactly as instructed. I don't even understand all of them. The first setup screen that appears at:9000 is asking for your SqueezeNetwork account information.

If you don't already have a SqueezeNetwork account, just clip 'Skip' in the lower right. You can set that up anytime later.

Basically, SqueezeNetwork lets you listen to Internet radio stations by using a remotely located server operated by Slim Devices. At any given time, a Squeezebox can be connected either to a SqueezeCenter server on your local network (i.e. The LinkStation you just loaded SqueezeCenter onto), or to SqueezeNetwork, but not both at the same time. You can sign up for a free SqueezeNetwork account at www.squeezenetwork.com. For more info on SqueezeNetwork, see http://wiki.slimdevices.com/index.php/SqueezeNetwork.

Right figured out that my user access for the linkstation works, but I just get to the buffalo web access page that lists all the files on the machine. There is no sign of slimserver? Are there any checks that anyone can suggest. I feared this would not be as simple as I hoped - all help gladly received - only bought the squeezebox on the great support offered hear. If you followed the instructions for setting the IP address, you would find SqueezeCenter at as you apparently did before. Thanks for replying. I changed to the static IP address for the linkstation LS-CHL to 192.168.1.130 as mentioned at the start of the instructions - and I can log onto this through the web page - however this gives just the web interface to the linkstation - when I try 192.168.1.130:9000 I get no page available.

Actually just ried again and I get the web interface to the linkstation with the list of folders - I have not seen the slimserver interface at all - this makes me wonder if it is running at all - the squeezebox cannot pick it up either. Thanks for replying. I changed to the static IP address for the linkstation LS-CHL to 192.168.1.130 as mentioned at the start of the instructions - and I can log onto this through the web page - however this gives just the web interface to the linkstation - when I try 192.168.1.130:9000 I get no page available. If you haven't done this already, reboot the LinkStation and wait about five minutes before trying the:9000 page again.

If that fails, you might need to Telnet back into the LinkStation, and manually start Squeezecenter: /opt/etc/init.d/S99squeezecenter start If it tells you that SqueezeCenter is already running, but you don't see the SqueezeCenter interface at:9000, then stop and restart SqueezeCenter. /opt/etc/init.d/S99squeezecenter stop /opt/etc/init.d/S99squeezecenter start You could be experiencing the problem with the /home/slimserver/squeezecenter.pid file mentioned at the end of post #4. Thanks again for the help - I have a tired mind trying to sort this out. Anyway - back onto it again - removed the software - seemed to go OK.

Reloaded - got confirmation along the way saying it was fully loaded. Go through the start command - again get confirmation it has started OK - get a PID number (whatever that is). Go to the web address and it just takes me to my web access to the linkstation i.e. Without the:9000 extension. I can't seem to get to the slimserver interface. It always takes me to the linkstation web interface (for which I am always logged in - how do you logout?) Frustrating this one. Another thing I noticed from the multiple reinstalls.

When I doubleclick on the my NAS icon in NasNavi2, on top of the MP3 & share & utilities folder, there is this additional folder '.optware' and 'tmp' with their comments as recovered. On first thought, i assumed they are the recovered files (due to some reason). These 2 folders are created by SC and once i stopped SC and deleted them off, my entire SC folder (/opt/etc/.) is missing when I telnet into the NAS. The question being, are those recovered files critical or not?

Another thing I noticed from the multiple reinstalls. When I doubleclick on the my NAS icon in NasNavi2, on top of the MP3 & share & utilities folder, there is this additional folder '.optware' and 'tmp' with their comments as recovered. On first thought, i assumed they are the recovered files (due to some reason). These 2 folders are created by SC and once i stopped SC and deleted them off, my entire SC folder (/opt/etc/.) is missing when I telnet into the NAS. The question being, are those recovered files critical or not? Yes I also have those two additional folders created and titled as recovered. PID is the process id number.

Every running program (process) has a unique number given to it by the operating system when it is started. When I installed squeezecenter on a Linkstation mini last year something called twonky provided by Buffalo was using port 9000 and so I instructed squeezecenter to use 9001 to avoid the conflict.

To make the change I think I edited the configuration file /opt/etc/squeezecenter.conf and restarted squeezecenter but I am not 100% sure. The version of linkstation I have - linkstation live with Bitorrent doesn't use twonky - the media server says PVconnect at the bottem. For the edit that you mentioned above, is that through telnet or notepad in windows? The more I think about it this seems to be the sticking point - has anyone got instructions for a non expert on how to change the config of slimserver to change port? Bare in mind I can't get to the web access.

>For the edit that you mentioned above, is that through telnet or notepad >in windows? I would have used telnet and the vi editor to make changes. >The more I think about it this seems to be the sticking point - has >anyone got instructions for a non expert on how to change the config of >slimserver to change port? Change 9000 to 9001 in the file mentioned and then stop/start squeezecenter.

Squeezecenter is big, some would say bloated, software that expects lots of supporting software present. The OS supplied by Buffalo on the Linkstation is a somewhat stripped down version of Linux. For those familiar with using unix, the process of working out what is wrong and fixing it is reasonably straightforward although time-consuming and frustrating. It wasted several evenings of my time and, with hindsight, it would have been wiser to have paid a bit more for a low powered 'proper' computer with a full OS. For those unfamiliar with unix, I suspect diagnosing and fixing squeezecenter problems on a cut down version of Linux is going to be very time consuming. >Bare in mind I can't get to the web access. I have looked at the squeezecenter web access once or twice but do not recall using it for anything significant.

I think it is probably wholly optional? >For the edit that you mentioned above, is that through telnet or notepad >in windows? I would have used telnet and the vi editor to make changes. >The more I think about it this seems to be the sticking point - has >anyone got instructions for a non expert on how to change the config of >slimserver to change port? Change 9000 to 9001 in the file mentioned and then stop/start squeezecenter.

For those unfamiliar with unix, I suspect diagnosing and fixing squeezecenter problems on a cut down version of Linux is going to be very time consuming. >Bare in mind I can't get to the web access. I have looked at the squeezecenter web access once or twice but do not recall using it for anything significant. I think it is probably wholly optional?

Nothing better for me to do on this rainy bank holiday! Saw these easy instructions, and even though I don't really need new server for SC, I thought I would give it a try. Some 30 minutes later it was up and running.

Even playing back some music. Nice instructions. After getting this running as described above, I copied over some 7000 FLAC files, which took about 7 hours and then ran the database scan, which took 70 minutes on the Linkstation vs. 20 minutes on my old AMD Athlon XP based PC. All my music files were found, but 3 album art covers went missing somehow. The server was happy supporting my SB3 and 2 SBRs, with remote control using iPeng.

The standard web interface was too slow for anything other than occasional use, but iPeng seemed to run with few noticeable pauses. The server did crash once in about 48 hours, and that forced me to telnet in to run the appropriate command from the init scripts by hand (I did not want to reboot the entire NAS, as others were still using it for file services). I think it is remarkable that this works as well as it does, but I don't feel that I would actively choose to use this as my regular Squeezecenter box on an everyday basis based on the underpowered nature of the chipset inside the NAS and the heavy demands placed on it at times by SC. I am expecting that the next Squeezecenter 7.4 will improve this quite a bit when it comes to Scanning music collection. It would be ideal if the web interface would run a bit faster too, but I guess that won't be a major impact of 7.4.

However, using Squeezeplay, a SBC or iPeng would largely obviate the need for a speedy web interface. Best regards.

Thanks for the reply - any chance of detailing step by step instructions of how to change the port - I have no idea how to edit or even find the file? Sorry to be a pain - decided to try slimcentre on the PC to just see how it works and it is good - just need to make that final step and get it running standalone on the NAS. Nothing better for me to do on this rainy bank holiday! I have already posted what I can recall. I do not know what I prodded and poked or the fine details of the issues only the broad picture. To repeat, squeezecenter is not software that is designed to run on small devices, it needs a full OS with loads of high level supporting software. Getting it to work on small devices with a cut down OS is possible if you have the appropriate knowledge and the time but it is not a particularly sensible thing to do.

One approach might be to install a full version of the latest version of Debian Linux which supports the ARM chip and motherboard used by the Linkstation (or, at least, the one in my Linkstation Mini). This would not only allow all the required software to be easily installed but would also make the box secure enough to put on the net - the Buffalo software is wholly inadequate in the respect given that it is trivial and widely posted how to gain root access. I have not done this and so am not speaking from experience but it is where I would start if I had just bought the box (and was not able to return it to the shop and buy a low powered PC). In order to fix whatever is wrong with your current installation you first need to diagnose/establish the problem.

It would seem unlikely to me that you are going to receive sensible instructions on how to fix an unknown problem. Given your lack of knowledge about how to go about this I think you may better to change tactics: pass the problem to someone with appropriate knowledge, run squeezecenter on more suitable hardware, replace squeezecenter with more appropriate software for the hardware, etc. I have already posted what I can recall. I do not know what I prodded and poked or the fine details of the issues only the broad picture. To repeat, squeezecenter is not software that is designed to run on small devices, it needs a full OS with loads of high level supporting software.

Getting it to work on small devices with a cut down OS is possible if you have the appropriate knowledge and the time but it is not a particularly sensible thing to do. One approach might be to install a full version of the latest version of Debian Linux which supports the ARM chip and motherboard used by the Linkstation (or, at least, the one in my Linkstation Mini). This would not only allow all the required software to be easily installed but would also make the box secure enough to put on the net - the Buffalo software is wholly inadequate in the respect given that it is trivial and widely posted how to gain root access. I have not done this and so am not speaking from experience but it is where I would start if I had just bought the box (and was not able to return it to the shop and buy a low powered PC).

In order to fix whatever is wrong with your current installation you first need to diagnose/establish the problem. It would seem unlikely to me that you are going to receive sensible instructions on how to fix an unknown problem.

Given your lack of knowledge about how to go about this I think you may better to change tactics: pass the problem to someone with appropriate knowledge, run squeezecenter on more suitable hardware, replace squeezecenter with more appropriate software for the hardware, etc. While honestguv is correct that Squeezecenter is pushing the capabilities of the LinkStation, there are dozens and possibly hundreds of people out there successfully using Squeezecenter on their LinkStations. The instructions in this thread are intended for people who just want to do that in the simplest way possible. Yes, the web UI for Squeezecenter is slow, but it works. In many cases, people are using the UI on their Squeezeboxes and don't need to use the web UI other than for some initial set up. Whether or not Buffalo's software is secure enough to put the box on the Internet is independent of anything to do with installing Squeezecenter on it.

For the purposes of installing and using Squeezecenter, the box only needs to be connected to the Internet during the installation. Once Squeezecenter is installed and running, a router's firewall could block any external access to it. (I wouldn't recommend using a LinkStation as a web server, Squeezecenter or not, but that's a different story.) Linux power users should go the route of installing FreeLink, as described in a different thread. The Squeezecenter problem that u415270 is having seems to be unique, and it may very well take a Linux power user to diagnose and fix it, but that should not be taken as a blanket dismissal of the LinkStation as a usable platform for a Squeezecenter server. I've been running Squeezecenter and its predecessor Slimserver on my own LinkStations for four or five years, and for me, the advantages of using a small, low power NAS for that purpose far outweigh the disadvantages.

Learned Colleagues: Well everything is loaded but I'm having a devil of a time with the following. My NAS (LinkStation Pro LS-1000GL, latest firmware, v 1.15 from 2004) constantly drops SqueezeCenter after successfully loading it. Something I'm doing wrong here? Is there some sort of autorun program I can load to constantly ensure that SqueezeCenter is loaded? My SqueezeBox Remote often cannot find my LinkStation and when it does see it, it rarely makes a connection.

I've tried using a direct IP address connection (192.168.1.130), but that doesn't work at all. Anyway to help facillitate a connection? BTW, SqueezeBox components work fine. If I load SqueezeCenter on a network PC, all is well with the world. Please help!!! Am I doomed to have a small, outdated computer relegated as the SqueezeCenter?

And if I am facing this sentence, how do I undo all the changes I made to my NAS without bricking it? Thanks in advance!! Learned Colleagues: Well everything is loaded but I'm having a devil of a time with the following. My NAS (LinkStation Pro LS-1000GL, latest firmware, v 1.15 from 2004) constantly drops SqueezeCenter after successfully loading it. Something I'm doing wrong here?

Is there some sort of autorun program I can load to constantly ensure that SqueezeCenter is loaded? My SqueezeBox Remote often cannot find my LinkStation and when it does see it, it rarely makes a connection. I've tried using a direct IP address connection (192.168.1.130), but that doesn't work at all. Anyway to help facillitate a connection? BTW, SqueezeBox components work fine. If I load SqueezeCenter on a network PC, all is well with the world. Please help!!!

Am I doomed to have a small, outdated computer relegated as the SqueezeCenter? And if I am facing this sentence, how do I undo all the changes I made to my NAS without bricking it? Thanks in advance!! I am currently running Squeezecenter on my own LinkStation Pro LS-500GL installed by the process described in this thread. The IPKG Squeezecenter install already sets up an autorun script to load Squeezecenter every time you reboot the LinkStation.

When you say that yours 'drops' Squeezecenter, can you describe exactly what you are seeing? What happens, for example, if you enter: /opt/etc/init.d/S99squeezecenter status If Squeezecenter is not starting correctly upon reboot of the LinkStation, it may be due to the squeezecenter.pid problem described at the end of post #4 in this thread.

I strongly suggest that all users assign a fixed IP address to their Squeezecenter server. If you can't get it to work that way, you won't have any better luck getting it to work with a randomly assigned IP address.

When you say 'that doesn't work at all', what exactly do you mean? What do you get when you open the web UI for Squeezecenter, i.e. By 'Squeezebox Remote' are you referring to a Controller? Is it that your Controller cannot find the server? If so, that would seem like a WiFi or networking problem. Do you have a regular Squeezebox that you can connect via hardwired ethernet to your router?

If so, that could isolate whether the issue is a Squeezecenter issue or a networking issue. If you installed Squeezecenter via the process described in this thread with the stock firmware, you can easily remove it with virtually no danger of bricking the unit. You really haven't done anything to it other than load some software. You can remove Squeezecenter and IPKG by this sequence: cd /mnt/disk1/tmp sh lspro-bootstrap_1.2-5_arm.xsh rm -rf /mnt/disk1/.optware rm -rf /usr/lib/ipkg reboot. 2: What do I see when I try 192.168.1.130:9000? Sometimes I get to SqueezeCenter, but most times I get a “Internet Explorer cannot display the webpage” Error.

My handheld (let's call that the remote) can't 'find' the NAS most times and is a wireless connection, but the network is fine. And when it does see the NAS by name, not by IP address, it has a bear of a time connecting. The little box with the audio outputs is a wired network connection.

I know everything is working fine because the second I load SqueezeCenter on a computer also wired into the same network, everybody finds each other and I can play music through the computer-resident SqueezeCenter. I'll work on the rest this evening/weekend. Thanks for the help!

2: What do I see when I try 192.168.1.130:9000? Sometimes I get to SqueezeCenter, but most times I get a “Internet Explorer cannot display the webpage” Error.

If I restart SqueezeCenter via Telnet commands, I'll get it back. For this reason, I'm saying my NAS is dropping it, but I'll verify with your first comment on checking status this weekend. As for the Remote/Controller discussion, I'm screwed up on the terminology so please forgive. My handheld (let's call that the remote) can't 'find' the NAS most times and is a wireless connection, but the network is fine. And when it does see the NAS by name, not by IP address, it has a bear of a time connecting.

The little box with the audio outputs is a wired network connection. I know everything is working fine because the second I load SqueezeCenter on a computer also wired into the same network, everybody finds each other and I can play music through the computer-resident SqueezeCenter. I'll work on the rest this evening/weekend. Thanks for the help! That does indeed sound like a Squeezecenter problem, although there also could be be networking issues related to the Controller. The first thing I would try is the fix for the squeezecenter.pid problem (seen end of post #4 in this thread). Since I performed that fix on my own unit I have had no problems running Squeezecenter.

Will doing a normal firmware upgrade ruin the squeezecenter install? I recommend uninstalling Squeezecenter and IPKG by this procedure prior to upgrading the firmware: cd /mnt/disk1/tmp sh lspro-bootstrap_1.2-5_arm.xsh rm -rf /mnt/disk1/.optware rm -rf /usr/lib/ipkg reboot Then install the new firmware per instructions from Buffalo. After you have the new firmware running, reinstall Squeezecenter from scratch as described in the opening posts of this thread (it's quick once you know how to do it). Wow what a crazy installation this was.

After getting the new CHL station, I went to install it, and it worked. Rebooted and it went to EM mode. After trying to get it out of EM mode for a while, using combinations of telnet, and the direct ethernet linkup method, i finally was able to get the thing re-flashed and into japanese! After getting it back into english, my hard drive gives me a BAD SECTORS warning, and constant flashing. I was able to disk clean it, and then reflash again with check marks on all the debug options and away those went.

Finally, I reinstalled the server, rebooted a few times just to make sure, and it still works. Now I am doing a massive transfer of media over via USB hard drive to Linkstation using telnet.

I hope i dont wake up tomorrow with a bad hard drive like I did the other day. Btw, one thing i did do different, which i followed the original post from 'vespa' was to reboot immediately after completing the install and sed commenting, instead of starting the server immediately. This method worked, whereas the first time I tried it (and previous times before that), it'd work but as soon as i reboot, it'd go into EM mode and more misery. Btw, one thing i did do different, which i followed the original post from 'vespa' was to reboot immediately after completing the install and sed commenting, instead of starting the server immediately. This method worked, whereas the first time I tried it (and previous times before that), it'd work but as soon as i reboot, it'd go into EM mode and more misery. Has anybody else experienced that changing the reboot order made this difference with the LS-CHL?

I can't think of any reason why it should make a difference, but if so, I can alter the instructions. Hi, I was searching around looking for the best solution to get sc up and running, I have an old SLUG that has served me very well over the years but it is painfully slow at anything taxing, I also have a linkstation but did not think that would be up to the job. I found some really complex instructions for installing sc on the linkstation but they were way above me!

Having stumbled across this thread I followed the instructions and it was very easy and all works - fantastic. I would like to install the latest 'nightly' build but I don't know how. (only so some of the Napster play list issues are sorted). Otherwise - thank you for taking the time to set the instructions out so well. I'm back.:) Had the thing crash hard on me again.

The linkstation first started showing a bad sector error, and then eventually went into EM mode. After trying to fix it for a while, formatting, trying to use xfs_repair, etc etc, and reinstalling a few times - I couldnt get it to run stable without going back into EM mode. I was about to give up. And then I decided, let's try to find the 'stock' firmware, and in this case, I mean 1.06 firmware for the CHL.

I originally received the CHL with 1.06, but proceeded to install 1.07 on it in both of my CHL drives I bought (the first one, and the exchanged one). After getting this, I rebooted it a few times to make sure it wouldn't boot into EM mode again. Then I installed the squeezecenter again and again rebooted a couple times just to make sure the boxes wasnt tricking me.:) Finally, loaded up my library using direct USB to USB transfer so that took a couple hours. After that I didn't let the SC do a scan because that's when it crashed last time! I rebooted another time just to make sure, and then tried to do a Library load from itunes (changed the directories in the xml), which worked once but only loaded 1/3rd of my library. Then after numerous attempts of getting the library loaded, I gave up and did the full directory scan. It seemed to scan much faster this time!

It was very slow on the first attempt before it eventually crashed overnight. Anyway, I came home from work today expecting to see it fail on me, but its running and I'm streaming music on it right now! So I don't know if my conclusions are valid or not, but from my experience thus far, using a 500gb LS-CHL Live v3 station are: the 1.07 firmware was unstable while the 1.06 firmware has worked flawlessly thus far, and second, I rebooted after installing slimserver before starting it. I don't know if the second conclusion has any validity since I didn't try to start it right away on the 1.06 firmware (didnt need to).

Ok thanks for reading, and much kudos to TiredLegs, Vespa, and others! Bit stuck on my install, so hoping someone can help out. I'm telnetted on, but don't seem to be able to download anything through wget. My Windows fireall is turned off, but not sure what else to alter.

I got IPKG installed by downloading the arm.xsh to my desktop adn copying it onto the share, but can't perform any later stages. Below is what I get mnt/disk1/share# /opt/bin/ipkg update Downloading h ttp://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/Packages.gz An error ocurred, return value: 1. Collected errors: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /opt/ipkg-cZUhOv h ttp://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/Packages.gz' (I had to break links due to it being my 1st post, but they're not really important to the message.) Thanks for any help. Sorry for 3 posts in a row, but I thought I had it working, and seem to be close!

Squeezecenter seems to be properly installed, and looks to start up correctly (just the telnet prompt, not letting me in via the web). After a minute or two it dies - I don't get a prompt saying so, but the following command tells me it has. Root:/home/slimserver# /opt/etc/init.d/S99squeezecenter status Checking for SlimServer: not running - last PID 11097) The end of /home/slimserver/squeezecenter.log below seems to imply it dies because port 9000 is already in use.

Any idea why, or how to resolve it? Is this why some people switch to port 9001, and if so, is there a way to free 9000 up again?

[09-05-16 19:] Slim::Schema::init (154) Warning: Creating new database - empty database or database from 6.3.x found [09-05-16 19:] Slim::Plugin::MusicMagic::Plugin::initPlugin (150) Can't connect to port 10002 - MusicIP disabled. [09-05-16 19:] main::checkDataSource (911) Warning: Schema updated or no tracks in the database, initiating scan. [09-05-16 19:] Slim::Utils::Misc::msg (1122) Warning: [19:] commit ineffective with AutoCommit enabled at /opt/share/squeezecenter/CPAN/DBIx/Class/Storage/DBI.pm line 706. [09-05-16 19:] Slim::Web::HTTP::openport (200) Can't setup the listening port 9000 for the HTTP server: Address already in use [09-05-16 19:] Log::Log4perl::Logger::and_die (861) Warning: Can't setup the listening port 9000 for the HTTP server: Address already in use at /opt/share/squeezecenter/Slim/Web/HTTP.pm line 200. Sorry for 3 posts in a row, but I thought I had it working, and seem to be close!

Any idea why, or how to resolve it? Is this why some people switch to port 9001, and if so, is there a way to free 9000 up again? [09-05-16 19:] Slim::Schema::init (154) Warning: Creating new database - empty database or database from 6.3.x found [09-05-16 19:] Slim::Plugin::MusicMagic::Plugin::initPlugin (150) Can't connect to port 10002 - MusicIP disabled. [09-05-16 19:] main::checkDataSource (911) Warning: Schema updated or no tracks in the database, initiating scan. [09-05-16 19:] Slim::Utils::Misc::msg (1122) Warning: [19:] commit ineffective with AutoCommit enabled at /opt/share/squeezecenter/CPAN/DBIx/Class/Storage/DBI.pm line 706. [09-05-16 19:] Slim::Web::HTTP::openport (200) Can't setup the listening port 9000 for the HTTP server: Address already in use [09-05-16 19:] Log::Log4perl::Logger::and_die (861) Warning: Can't setup the listening port 9000 for the HTTP server: Address already in use at /opt/share/squeezecenter/Slim/Web/HTTP.pm line 200 I appear to have the same problem - port 9000 is used by the internet access on the linkstation.

I also read with interest the experience of minatori. I think I will try and revert back to 1.06 and see how it goes. On the Port 9000 thing - Yes, it conflicts with LinkStation Live. Either turn off your web access in the Live. Or change the port on the SqueezeCenter. I also find that even after I change the port in Squeezecenter, or even manually through the server.pref file, it reverts back to Port 9000 anyway.

So far it's stayed at Port 9900 for me, but I also haven't restarted the server yet. (it goes back everytime I reboot now. Not sure why - didnt before). On the itunes playlist, it should be able to - you may have to turn on the itunes plugin and manually add the address to the xml file. However, I didnt have much luck with it. It worked once, but only about 15% of the files ended up showing up in my library, and then I tried it again, and it finds everything, but once the actual scan completes, it all got cleared away.:( I ended up just doing a complete directory scan.

On the Port 9000 thing - Yes, it conflicts with LinkStation Live. Either turn off your web access in the Live. Or change the port on the SqueezeCenter.

I also find that even after I change the port in Squeezecenter, or even manually through the server.pref file, it reverts back to Port 9000 anyway. So far it's stayed at Port 9900 for me, but I also haven't restarted the server yet. (it goes back everytime I reboot now. Not sure why - didnt before). On the LinkStation Live, you should be able to change its web access port to something other than 9000. On the Web Access ->Service Setup page, disable 'Auto-Configure Firewall (UPnP)'.

Then you can enter a different port, although you would need to manually configure your router's firewall to forward the chosen port number. EDIT: It also may be possible to change the UPnP Web Access port to a different number via Telnet access, although I don't know how to do that. You might want to post a question about it on the LinkStation Live forum at http://forum.buffalo.nas-central.org/viewforum.php?f=39. On the LinkStation Live, you should be able to change its web access port to something other than 9000.

On the Web Access ->Service Setup page, disable 'Auto-Configure Firewall (UPnP)'. Then you can enter a different port, although you would need to manually configure your router's firewall to forward the chosen port number.

EDIT: It also may be possible to change the UPnP Web Access port to a different number via Telnet access, although I don't know how to do that. MS Office 2003 Pro Japanese. You might want to post a question about it on the LinkStation Live forum at I think I could kiss you.

After removing the web access in the linkstation setup I can finally see Slimserver running on the linkstation. Only problem now is that after scanning my directory, it can't find any of my music. I had saved it all to directory share cd music, but when I go into browse in slimserver it will not go any deeper than share. I also tried ls under the share directory in telnet and couldn't see any more folders - any ideas?

I carried out all of the file changes (twice to make sure) that you gave in your instructions. It could just be my router setting, but even if I use UPnP or not, and manually change the port number, it still defaults to 9000 for the internal local internet address. Whats funny is that inbound external internet will use the manually assigned port number I use. U415270 - is the link to your share folder something like this: /mnt/disk1/share/cd/music/? Yes- found it now after a bit of digging in all the folders, I origninally looking in LSCHL share. Thanks again for all the help - database is chugging through my 3300 songs.

Really looking forward to PC less music streaming. Been following the splendid instructions to the letter, and everything works fine - until i reboot my linkstation mini! After that, my /opt/ folder turns out to be empty. Reinstalling and rebooting after every critical step shows, that after executing /'opt/bin/ipkg install squeezecenter bash flac sed' everything from my /opt/ directory is gone. Just before, all the /share and /bin and whatnot were there, and after the reboot, they vanished. Looking into that line, the installation of squeezecenter seems to be the cause for the mysterious disappearance, as bash, flac and sed install just fine, or rather don't have an effect on my /opt/ folder. Without the reboot my squeezecenter works like a charm.

But since i'd like my nas to auto power-down and wake it up via my squeezebox and its WOL packages, no way i can leave it at/like that. I appreciate your help, dodo all right, figured it out by myself: after rebooting i was telneting to the mini again - but executing the acp_commander again. This apparently killed the /opt/ directory. Activating the telnet daemon did the trick - and is more comfortable anyways. Fascinating thread - I wish I read it before purchasing the linkstation mini.

Does anyone know if this will work on that? ------- ANswer: Well, since I am a Linux user I figured I should go ahead and try it myself.

So yes, this does work for the LinkStation Mini (LS-WS). Ten-thousand good-karmas onto TiredLegs for putting that together in one easy-to-follow place. Only possible gotcha for someone who doesn't know Linux: on my LS mini 1TB, I am not using the redundancy feature (that has one of the 2 500GB disks mirror the other for data safety), instead I'm using the full 1TB as disk storage. I don't know if that had anything to do with it, but when I created the Music directory from the Web-UI, it placed it in /mnt/array1 (not in /mnt/disk1 as TLs instructions say). Hello All, First post on this forum. I found the thread through a Google search specifically on this subject. Without checking compatibility, I recently bought a Buffalo Linkstation LS-CHL 1TB and Squeezebox Duet.

I've not studied the instructions at the start of this thread in detail yet. It's all well-beyond my IT skills so I'll be cutting and pasting my way through it later this week. Having read some of the responses, the key thing I'm keen to find out is will I do any irreparable damage to my Linkstation by trying and failing to install the Squeezebox? If there's a good chance I'll end up doing something that I can't undo which will sub-optimise the Linkstation (particularly with my already referred to low-level IT skills!) then I'd be highly reluctant to have a go. Can someone put my mind at rest or issue a reasonable warning? First post on this forum. I found the thread through a Google search specifically on this subject.

Without checking compatibility, I recently bought a Buffalo Linkstation LS-CHL 1TB and Squeezebox Duet. I've not studied the instructions at the start of this thread in detail yet. It's all well-beyond my IT skills so I'll be cutting and pasting my way through it later this week. Having read some of the responses, the key thing I'm keen to find out is will I do any irreparable damage to my Linkstation by trying and failing to install the Squeezebox? If there's a good chance I'll end up doing something that I can't undo which will sub-optimise the Linkstation (particularly with my already referred to low-level IT skills!) then I'd be highly reluctant to have a go.

Can someone put my mind at rest or issue a reasonable warning? Welcome to the Squeezebox forum. While it is possible that you could brick your unit in the process, the risk is fairly low because the procedure described in this thread just loads some software without changing the firmware. In the case of the LinkStation LS-CHL model specifically, a number of people have experienced a conflict in which both the LinkStation's built-in web server and Squeezecenter are trying to use the same port number (9000). That problem would only occur if you want to enable your LinkStation to be a web server (i.e. To let people access your LinkStation files from the wide open Internet). If you're only looking to serve music from the LinkStation to the Squeezebox on your local network, it should work fine.

If you want to back out the Squeezecenter installation after you've done it (or had it fail to take for some reason), you can remove Squeezecenter and IPKG by this sequence: cd /mnt/disk1/tmp sh lspro-bootstrap_1.2-5_arm.xsh rm -rf /mnt/disk1/.optware rm -rf /usr/lib/ipkg reboot. ***STEP 2: TELNET INTO THE LINKSTATION*** cd C: Temp LinkStationTelnet Run acp_commander to install Telnet on the LinkStation and use the “addons” option to install the wget command: java -jar acp_commander.jar -t 192.168.1.130 -o -addons If you receive a SocketTimeoutException error, it probably means your Windows Firewall is still enabled.

Disable Windows Firewall and try the command again. Now, 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 still turned off.

Once logged in via Telnet, you are ready to install IPKG and Squeezecenter. Thanks TiredLegs. Excellent instructions! I just had one question. I have it all setup, on a Linkstation Live 500Gb fixed IP. When I reboot the linkstation I have to redo the java acp_commander update to setup telnet to get back onto the linkstation. This same command also lets the squeezecenter come up and accessible to the squeezebox.

Excellent instructions! I just had one question. I have it all setup, on a Linkstation Live 500Gb fixed IP. When I reboot the linkstation I have to redo the java acp_commander update to setup telnet to get back onto the linkstation. This same command also lets the squeezecenter come up and accessible to the squeezebox.

Am I missing a step to harden the linkstation so I don't have to redo this one step. Anyone else have this issue. I do plan on switching the linkstation off when I'm not using it. Thanks, jmcg Maybe didn't explain that too well. I have everything setup, working nicely. On reboot or poweroff, I can't get to the Squeezecenter gui and I can't telnet in, so it doesn't look like some services have started. I have to to the part above to install telnet and whatever else it does and immediately the squeezecenter is accessible and i can telnet on.

Does it everytime. Thanks in advance of any info.

Update, got telnet going, easy uncomment in /etc/init.d/rcS. Squeezecentre came up itself then after a few mins. Really does take a good 5mins+ to let the load averages calm down to make it usable on the GUI/iPeng on a ipod touch.

I'm new to this and have been trying SqueezeCenter on my LinkStation Pro (v2) prior to buying a SB Boom. Thanks to these instructions from TiredLegs (which worked really well:) ) I have installed SC without any problem. However I'd really like to get AlienBBC working so need to install (and possibly compile) mplayer. I can see there are quite a few posts where people have been trying to get mplayer working, mainly on LinkStations running Freelink. Has anyone managed this on the Buffalo firmware?

If so could you kindly point me in the right direction. I just had one question. I have it all setup, on a Linkstation Live 500Gb fixed IP. When I reboot the linkstation I have to redo the java acp_commander update to setup telnet to get back onto the linkstation.

This same command also lets the squeezecenter come up and accessible to the squeezebox. Am I missing a step to harden the linkstation so I don't have to redo this one step.

Anyone else have this issue. I do plan on switching the linkstation off when I'm not using it. If Squeezecenter does not automatically restart upon rebooting of the LinkStation, see the very end of post #4 in this thread for possible solution. If Squeezecenter does not automatically restart upon rebooting of the LinkStation, see the very end of post #4 in this thread for possible solution.

Cheers mate, the lack of telnet daemon coupled with the initial slow startup time gave the impression that nothing was starting. Wasn't giving it long enough. Once I had telnet enabled all the time I could see it working.

For anyone setting this up, I used a Linkstation Pro Live 500Gb, have 21000+ songs, 1400 albums (168Gb), wired linkstation and wired squeezebox using iPeng to control it (or the http gui). Using a wired connection to the squeezebox definetly brought the load averages down on the linkstation as opposed to wireless. Results when I try to ping ipkg.nslu2-linux.org from linkstation. Root@LS-CHL7E2:/mnt/disk1/tmp# ping ipkg.nslu2-linux.org ping: bad address 'ipkg.nslu2-linux.org' /etc/resolv.conf shows nameserver 24.25.5.148 nameserver 24.25.5.147 which is what i had on my tables originally. I can ping both of these just fine from my desktop. Here are the results when I try to ping from the Linkstation. LS-CHL7E2 login: root No mail.

Root@LS-CHL7E2:~# ping 24. Bondan Prakoso Tetap Semangat. 25.5.148 PING 24.25.5.148 (24.25.5.148): 56 data bytes. You should be getting a reply to the ping, e.g. PING 24.25.5.148 (24.25.5.148): 56 data bytes 84 bytes from 24.25.5.148: icmp_seq=0 ttl=26 time=176.5 ms Therefore it looks like there's something wrong with your connection to the internet - probably the default gateway. When you do 'route' you should have something like this: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface * 255.255.255.0 U 0 0 0 eth0 default 0.0.0.0 UG 0 0 0 eth0.where is the IP address of the router (e.g. Broadband) that takes you out to the internet.

If it's missing you need to configure it - it's probably easiest just to use the standard Linkstation web interface. I have spent the last 2 days trawling through the forums trying to see if i can get slimserver/squeezecenter running on my Terastation live, this thread is the closest i can find. Is the only thing i have to do to get it working replace the ipkg bootstrapping script for the LS pro/live mkdir /mnt/disk1/tmp cd /mnt/disk1/tmp wget sh lspro-bootstrap_1.2-5_arm.xsh with this one for the terastation pro/live? Mkdir /mnt/array1/tmp cd /mnt/array1/tmp wget sh teraprov2-bootstrap_1.2-5_arm.xsh I am a total newbie at this and i really dont want to kill my terastation so any guidance will be greatly appreciated.

Just noticed SqueezeCenter has a new version (7.3.3), and the latest ipkg version is 7.3.2-2. Not sure how to go about doing that myself, is there somoene to prod? -Christo I don't actually know the process by which ipkg packages get made. If you're highly tech savvy with Linux, you might be able to figure it out from info at the Optware site However, you should not prod anyone else! Currently, a private individual who has no affiliation with Slim Devices has been making the ipkg versions at his own convenience. Attempting to push the process might just convince that person to not bother with the effort if he's going to get pestered. Not every X.X.X minor version change will necessarily get made into an ipkg.

But hang tight, and it usually shows up in due course. You can always see the current Squeezecenter version number that is available as an IPKG at (Search the page for 'squeezecenter'.). I am using 7.3.2 from the original Tired legs instructions -How do you upgrade to 7.3.3? See post #5 in this thread for the process.

Any time IPKG Squeezecenter is installed, it uses the most recently released IPKG version. Info on which Squeezecenter version is currently available as IPKG is always at Note, however, that you might want to see various posts in the forum about problems running 7.3.3 in general (not specific to LinkStation). I would not necessarily upgrade to 7.3.3 unless you have a particular reason to do so. ***UPGRADING SQUEEZECENTER*** This sequence removes the existing IPKG and Squeezecenter from your LinkStation: 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. This sequence installs the latest versions of IPKG and Squeezecenter: cd /mnt/disk1/tmp wget ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/lspro-bootstrap_1.2-5_arm.xsh sh lspro-bootstrap_1.2-5_arm.xsh /opt/bin/ipkg update /opt/bin/ipkg install squeezecenter bash flac sed Great instructions, good work.

Just one question and possible suggestion. I'm not sure why you are removing the optware package and bootstrap just to do an upgrade? Do you have a reason? Seems like a lot more work than just doing an 'ipkg upgrade'. Here's what I would do to upgrade: /opt/etc/init.d/S99squeezecenter stop /opt/bin/ipkg update /opt/bin/ipkg upgrade The instructions above in order are basically stopping your squeezecenter software, then updating the ipkg lists so it knows what to upgrade, then upgrading your installed packages. This will download and configure your installed packages. When the process is done it will return 'Successfully terminated.'

You'll still need to do the sed commands and in my case update the /opt/etc/squeezecenter.conf if you have changed your http port to 9001. Just a suggestion. Great instructions, good work. Just one question and possible suggestion.

I'm not sure why you are removing the optware package and bootstrap just to do an upgrade? Do you have a reason? Seems like a lot more work than just doing an 'ipkg upgrade'.

Here's what I would do to upgrade: /opt/etc/init.d/S99squeezecenter stop /opt/bin/ipkg update /opt/bin/ipkg upgrade The instructions above in order are basically stopping your squeezecenter software, then updating the ipkg lists so it knows what to upgrade, then upgrading your installed packages. This will download and configure your installed packages. When the process is done it will return 'Successfully terminated.' You'll still need to do the sed commands and in my case update the /opt/etc/squeezecenter.conf if you have changed your http port to 9001. Just a suggestion. I don't recall the specific issue, but when I originally wrote the instructions (which were intended for use with JTYMOD firmware), I tried the type of sequence you suggest, and it didn't work. I can give it another shot the next time I want to upgrade my own LinkStation to a new version of Squeezecenter and see if everything goes OK now.

I've changed some album artwork tags, but squeezecenter isn't picking up the new tags even after a full library rescan. I want to clear the cache on my SC linkstation install to see if this fixes the problem. Can anybody help with the commands to do this?

Not sure it answers your question but /opt/etc/squeezecenter.conf lists where the squeezecenter cache is located (/home/slimserver/cache on mine), and there is an 'Artwork' directory under that. I don't really know if you want to clear that, but there it is. I have succeeded in getting it to work but for one thing.

I completed the set up and exited the C: command window but now want to add the last instruction if Squeezbox doesn't start up after reboot. What do I need to put into the command window to get to the right directory to put in this:- /opt/etc/init.d/S99squeezecenter stop rm /home/slimserver/squeezecenter.pid /opt/etc/init.d/S99squeezecenter start Apart from ths little niggle it was very simple to follow and get set up. Thanks TiredLegs Regards Keith.

I have succeeded in getting it to work but for one thing. I completed the set up and exited the C: command window but now want to add the last instruction if Squeezbox doesn't start up after reboot. What do I need to put into the command window to get to the right directory to put in this:- /opt/etc/init.d/S99squeezecenter stop rm /home/slimserver/squeezecenter.pid /opt/etc/init.d/S99squeezecenter start Apart from ths little niggle it was very simple to follow and get set up. Thanks TiredLegs Regards Keith You need to be logged into the LinkStation via Telnet to enter those commands. You should be able to do that again just by entering telnet and whatever IP address your LinkStation has, e.g.: telnet 192.168.1.130 Login as user “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.

Once you're connected by Telnet, you can enter the commands from within any directory.