01-26-2012
11:21 PM
- last edited on
02-12-2013
05:46 AM
by
AskTheLeaf
Manual Steps to install FAT+ Mod 2.23 with utilities
Required
- FAT+ or GO Flex TV, currently installed with official FW 2.20 for either US or EMEA region
- USB drive, any USB drive formatted with FAT32.
- Seb_123 Mod FW 2.23 for your region, download at
US version Mod 2.23 image
MD5: 49FBC5C5DAC94FB02B709E9896E23DC9
- Bin-pack, see number 9 below.
Recommended
If possible, Mod FW 2.23 should be flashed while the FAT+ is connected to the router by wire throught the Ethernet port. If it is not feasible to use wire, go ahead with wireless. It works for most users, but some users have reported problem flashing MOD 2.23 while the FAT+/GoFlex TV is connecting with the USB Wifi adapter. This might be just some wireless driver issues in the FAT+.
Installation
1. Extract the file install.img from the downloaded FW, copy this file to the root directory of the USB drive. Make sure that it's the only file there. It's OK to have other folders, but the install.img should be the only file.
2. Power on the FAT+, set the FAT+ IP address to a static address on the FAT+ menu (wire/wireless).
3. Unplug all USB drives that are connected to the FAT+, if there is any.
4. Insert the USB drive with FW image into the FAT+ front USB port (For GOFlex TV, use the back USB port), wait until it finish indexing.
5. On a Windows PC, open a Command Prompt (or Mac OSX terminal, Linux shell, ...) and telnet into the FAT+ by using the static IP address, for example if the IP address is 192.168.0.100. The user name is root, no password necessary
telnet 192.168.0.100
6. At the telnet command prompt, check for the FW image on the USB drive
ls -l /tmp/usbmounts/sda1
it should show the install.img file there
7. Start installing the FW by enter the following command at the telnet prompt
kill -6 1
8. Watch the TV screen for the FW update progress. Wait until it finished and the Main menu is displayed. At this point, the Mod FW 2.23 has been successfully installed. If any thing went wrong, follow the Cold Method of installing FW 2.20 to recover. If that does not work then installing Rescue FW 1.55, and then upgrade back to FW 2.20 using USB method (see prairiedog sticky thread for information)
9. To install all the utilities (optware, samba, busybox, nano,...) from the bin-pack, use the following README.txt instruction (also inside the downloaded bin-pack). There are 2 ways to install the binpack: using manual steps instruction, or using a tar file.
Download binpack 1.4 here (updated 01/31/12)
or
Download binpack 1.4 tarball here (updated 01/31/12)
Binpack 1.4 description:
Installing Utilties on FAT+ Mod 2.23 (Mod FW by Seb_123, version April 17) For use with FATplus-Mod-2.23-binpack-bodhi-1.4.zip 1. Install Oleg Optware and BusyBox ================================ - Use a USB drive (flash or HDD) formatted with FAT32 - Create a top level directory /bin on this USB drive - Copy all files in this bin pack to the USB /bin directory - Unplug all USB drives currently connected to the FAT+ - Power up the FAT+ and insert this USB drive. This USB drive will be mounted at /tmp/usbmounts/sda1 - Telnet into the FAT+. User name is root, no password necessary. - Execute the optware installation /tmp/usbmounts/sda1/bin/optware-install.sh - When it's done, copy the autorun.sh (or merge the content if there is one already in /usr/local/etc). And for convenience, also copy BusyBox binary. This autorun.sh start busybox FTP during power ON. So it's recommended that both files are copied to /usr/local/etc/ as followed: cp /tmp/usbmounts/sda1/bin/autorun.sh /usr/local/etc/ cp /tmp/usbmounts/sda1/bin/busybox-mipsel /usr/local/etc/ - Execute the mount command to check if /opt is now mounted mount 2. Setup Command Paths for nano and busybox (added in 1.2) ======================================================= - Change directory to the USB drive bin directory and execute the script. NOTE: this script must be executed at the USB drive directory where the bin pack is (/tmp/usbmounts/sda1/bin or /tmp/usbmounts/sdb1/bin ...) cd /tmp/usbmounts/sda1/bin ./setup-commands-path.sh - copy the new autorun.sh to /usr/local/etc (or merge with current content if autorun.sh version 1.1 has been modified) cd /tmp/usbmounts/sda1/bin cp autorun.sh /usr/local/etc/ - manually set the PATH (this will be done automatically in profile) export PATH=$PATH:/usr/local/etc/bin
3. Install Samba2
==============
- Modify the /tmp/usbmounts/sda1/bin/smb.conf so that the line
interfaces = 192.168.0.51/24
matches the FAT+ IP address. Note that the FAT+ should be assigned a static IP address before
this so that Samba will work consistently. Whenever the FAT+ IP address changed, the smb.conf must be modified
to match the new IP, so static IP is best. There is also a line for workgroup, which can be left as is. If after installation, Samba
fails to share the USB drive(s), this workgroup should be looked at and adjusted to whatever the Windows workgroup is.
workgroup = WORKGROUP
- Execute the samba installation
/tmp/usbmounts/sda1/bin/samba_install.sh
- When it's done, the current USB drive is shared automatically under the share named "media". This is a directory
under /usr/local/etc. There are 3 symlinks in this share, usb-sda1, usb-sdb1, and usb-sdc1. Whenever a USB drive is plugged in,
it is automatically shared in that order. If a USB hub is used to connect more than 3 drives, then more symlinks
should be created to accomodate more USB drives, for example:
ln -s /tmp/usbmounts/sdd1 /usr/local/etc/media/usb-sdd1
and so on.
- Check the samba share if it appears on other PC in the network. On Windows, it should appear as
"media on FAT+ (VENUS)". Visit this share, and all USB drives will shown as shared folder usb-sda1, usb-sdb1,....
- Note that the FAT+ mini USB port will always get the first letter sda1 if a Free Agent GO drive is in that slot during power ON (does not
matter how many drives are connected). But if it is inserted later, then it will get sdb1, sdc1,... depending on how many USB drives were already
plugged in.
4. Install Transmission (added in 1.3) ======================================================= - Change directory to the USB drive TOP directory and execute the script. NOTE: this script must be executed at the USB drive TOP level directory (/tmp/usbmounts/sda1 or /tmp/usbmounts/sdb1 ...). If the drive is at sda1: cd /tmp/usbmounts/sda1 - Run the installation script ./bin/transmission_install.sh - copy the run script to /usr/local/etc cp ./bin/run_transmission.sh /usr/local/etc/ - copy or merge the autorun.sh script to /usr/local/etc. Set the global flag for Transmission to YES so that Transmission is started automatically after a cold start (power disconnected), or reboot. Or set the flag to NO so Tranmission will not be started automatically (use run_transmission.sh to start manually). cp ./bin/autorun.sh /usr/local/etc/ - start transmission cd /usr/local/etc ./run_transmission.sh Control Transmission (added in 1.3) ================================================== ===== - To control transmission, i.e. adding torrents, change settings, and password follow the 2 steps below 1. To control transmission using Web browser After running this script to start transmission, on your browser enter URL http://x.x.x.x:8181/transmission/web (where x.x.x.x is the FAT+ IP address) to start the Transmission control GUI. username is transmission, password is fatplus. 2. To change password, stop tranmission at the telnet prompt killall transmission-daemon then edit the transmission setting file in the USB drive /tmp/usbmounts/sda1/transmission/settings.json to replace the hashed password with plain text password (it will be hashed automatically after transmission started): the rpc-password line in the json file looks like this "rpc-password": "{1ff68df803da3975545aed61a9b1a52adfa3991auZrFBUHf ", replace it with your new password in plain text (put it inside the double quote) "rpc-password": "whatever is the new password" run this script (run_transmission.sh) again to start transmission 3. For complete instruction in using the Web Interface see this web site https://trac.transmissionbt.com/wiki/WebInterface Keep Alive (added in 1.3) ========================= To keep the FAT+ running without automatically going to sleep after idling for 1 hour - modify /usr/local/etc/bin/keep-alive.sh to change "192.168.0.51" to the FAT+ IP address (the local host IP 127.0.0.1 should work fine acording to hexcide, but I could not make it work for some reason) Unicode font supports (added in 1.4) =================================== To replace the fonts with newer versions that support Vietnamese, Arabic,... subtitles. Root Password (added in 1.4) ============================ - add passwd for root: fatplus root password file is overmounted in /usr/local/etc so that the box is secured. NOTE1: to ensure that password change is OK, telnet into the box in a separate session using the default password fatplus first before implement this change (so that you can reverse the change). After rerun /usr/local/etc/autorun.sh, open another telnet session and try testing the login using the default password fatplus and the new password. NOTE2: use mkpasswd to generate a new password, and then edit the /usr/local/etc/passwd file to copy/paste the new password into the root passwd location in the first line (7VRN4/P8MW5A2 is fatplus in encrypted form) root:7VRN4/P8MW5A2:0:0:root::/bin/sh ************************************************** ************************************************** *************** Update log Update 1.1 ========== - Modified autorun.sh to 1. Add waiting period of 20 seconds before starting services. 2. Add /opt mounting check to avoid double mounting. 3. Stop and start samba with log redirected to /tmp to avoid writing to flash. Update 1.2 ========== - Added 2 files: profile and setup-commands-path.sh 1. Set the system PATH variable to include /usr/local/etc/bin. This is possible by mounting /etc/profile to /usr/local/etc/profile to allow modification. 2. Set the symlinks for /opt/bin/nano and all busybox commands to /usr/local/et/bin. This will enable commands execution without typing the full path. - Modified autorun.sh to mount profile Update 1.3 ========== - Added 4 files: transmission_install.sh, settings.json, keep-alive.sh, and run_transmission.sh Transmission installation and running is fully scripted (no need to edit settings.json or other scripts) - Modified 1 file: autorun.sh Provide global flags to run various utilities, including flag to start Transmission To upgrade from binpack 1.2, copy all files in this bin pack to the USB bin directory /tmp/usbmounts/sda1/bin. And then follow the "Install Transmission" section above to install it, if desired. To update only autorun.sh, after copying files to USB bin directory, merge or copy this autorun.sh to /usr/local/etc. Also copy the keep-alive.sh to /usr/local/etc/bin (if this feature is enable in autorun.sh, it will be invoked). Update 1.4 ========== - Modified 2 files: setup-commands-path.sh, autorun.sh. - Added 3 files: arial.ttf, freesans.ttf, passwd - Added nano installation as part of setup-commands-path # copy 3 new files cp /tmp/usbmounts/sda1/bin/freesans.ttf /usr/local/etc/freesans.ttf cp /tmp/usbmounts/sda1/bin/arial.ttf /usr/local/etc/arial.ttf cp /tmp/usbmounts/sda1/bin/passwd /usr/local/etc/passwd # rerun setup commands path cd /tmp/usbmounts/sda1/bin ./setup-commands-path.sh #copy autorun.sh cp /tmp/usbmounts/sda1/bin/autorun.sh /usr/local/etc/ Finally, 1. to verify the password, see the "Root Password" section above. 2. to verify the binpack was installed and working correctly, unplug all USB drives and restart the FAT+ using reboot command reboot
Binpack 1.4 tarball description:
Installing Utilties on FAT+ Mod 2.23 (Mod FW by Seb_123, version April 17) with FATplus-Mod-2.23-binpack-bodhi-1.4.tar (MD5: 37536d39eb30fca1e4d840411d0ad917) - Instead of going through each steps in the installation instruction for binpack 1.4. This archive can be used to restore the whole installation to /usr/local/etc. This is my clean copy of the installation. Since the stock FW does not provide tar utility with un/compress option (-z), this tar file is uncompressed (about 40MB). - Download this tar file FATplus-Mod-2.23-binpack-bodhi-1.4.tar and put it on the top level directory of a USB drive. - After flashing Mod 2.23 FW, telnet into the FAT+, at the top level directory /, untar this archive tar -xvf /tmp/usbmounts/sda1/FATplus-Mod-2.23-binpack-bodhi-1.4.tar - See installation instruction in the binback 1.4 for description of all installed utilities, and modification needed to run in your individual environment (e.g. IP address, password,...)
Solved! Go to Solution.
01-30-2012 12:00 PM
I've made a typo in autorun.sh
(nmbd was not started) so Samba does not work in the latest binpack. I'll upload the new bin and tar file. In the mean time, if anybody has problem with Samba in Mod 2.23, check your autorun.sh and make sure that these 4 lines are correct:
/opt/sbin/smbd -D; echo "Started smbd" /opt/sbin/nmbd -D; echo "Started nmbd"
bodhi
01-31-2012 12:21 AM
Original post updated (corrected zip and tar file were uploaded).
01-31-2012 11:52 AM - edited 01-31-2012 01:33 PM
telneted in and "kill -6 1" kills the display, the seagate remains powered on but unresponsive. Update screen never comes up. Any advice?
Boots up fine after pulling the plug but still at 2.20.
Was running stock 2.23. Recovered to 1.55, updated to stock 2.20 and you got the rest. lol
***Update: Redownloaded the image. Tried again but wired instead of over wireless. Same problem
==================================================
Venus login: root
warning: cannot change to home directory
BusyBox v1.1.3 (2010.08.17-14:27+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
/ # ls -l /tmp/usbmounts/sda1
drwxrwxrwx 10 root root 4096 Jan 31 13:39 Sarah
-rwxrwxrwx 1 root root 40099840 Jan 31 15:11 install.img
/ # kill -6 1
/ #
Connection to host lost. <--- seagate GUI shuts off, but update screen never comes up. power LED stays lit.
****************
******** 2nd Update. FINALLY everything clicked and I got it installed. =D
02-05-2012 07:44 PM
02-05-2012 10:25 PM
bartolm wrote:
Hi bodhi, Thanks for putting this together. Successfully installed the Mod 2.23 today, but I can't get Samba to work. Installed it 1st from the tarball and then went back and did all the manual installation steps. I did check for the typo correction mentioned in your post. Transmission does work. One thing I can't figure out: After installation, where is smb.conf located? I want to make sure it's looking for the correct static IP address for my FAT+. Thanks for the help.
bartolm,
smb.conf is in /usr/local/etc/oleg-optware/etc/samba. Since /opt is mounted at /usr/local/etc/oleg-optware, you can change directory using either:
cd /usr/local/etc/oleg-optware/etc/samba
or
/opt/etc/samba
Also, if you use Mac OSX Lion, beware that it has problem with samba 2 (I posted recently about this here). Samba on Windows or Linux PC should have no problem connecting to the FAT+.
bodhi
03-07-2012 06:57 PM
I'll link this thread in my thread for mod 2.23 ![]()
03-16-2012 04:47 PM
Hi all,
I just recently flashed my FAT+ with the Mod 2.23 firmware, but I have a question... When I install the utilities do I need to keep the USB drive permanently attached to my FAT+ in order for them to work? As well as my Seagate harddrive? I'm really new to this, but I'm a pretty fast learner.
Thanks to all who have helped make the FAT+ an even MORE enjoyable device ![]()
P.S. Is there a way to get my FAT+ seen by say my kids Xbox 360? I have an attached drive with all their digital movies and it would be GREAT if they could watch them from their own room.
03-16-2012 05:47 PM - edited 03-16-2012 05:49 PM
BonnieC1977 wrote:Hi all,
I just recently flashed my FAT+ with the Mod 2.23 firmware, but I have a question... When I install the utilities do I need to keep the USB drive permanently attached to my FAT+ in order for them to work? As well as my Seagate harddrive? I'm really new to this, but I'm a pretty fast learner.
Thanks to all who have helped make the FAT+ an even MORE enjoyable device
P.S. Is there a way to get my FAT+ seen by say my kids Xbox 360? I have an attached drive with all their digital movies and it would be GREAT if they could watch them from their own room.
BonnieC,
After you installed mod 2.23, you can remove the USB drive that you used to install with. Just attach the drive with movies.
Important: the samba share created by the mod 2.23 binpack will allow everybody in the network to see the files on all USB drives attached to the FAT+. So if you don't want your kids to see certain non-kids stuff (e.g. rated R or above) then don't put them on the USB drives.
I don't have an Xbox360, but did your Windows, Linux PCs, and Xbox360 see the same networks files before on some network attached storage? if they did, they should see the FAT+ files the same way.
Mac OSX Lion is another different story. It has some problem with older Samba version, which is what I used in the Mod 2.23 binpack 1.4. (The newer Samba version is too big, does not fit inside the FAT+ free space).
03-16-2012 06:30 PM - edited 03-16-2012 07:55 PM
Thanks SOOO much for the quick reply Bodhi.... I'm planning on reflashing everything and starting anew.... This time around I plan on using the tarball binpack in hopes that everything will go much smoother the second time around ![]()
As for the Xbox, I use to have the HDD that is now attached to my FAT+ on a Windows pc that quit on me and I had TVersity in order for the files on my HDD to be seen on the Xbox.... I'm guessing that Samba now has the same purpose as Tversity did on my WinXP pc?
*** I just reflashed and installed the tarball binpack.... After removing the USB drive used to install the binpack how do I go about editing the IP and Passwords for Transmission and Samba? I can't seem to find the settings.json or the smb.conf file anywhere. Also when I try to run Transmission it gives me the following error
/usr/local/etc # ./run_transmission.sh
ERROR: Transmission directory not found in USB drives
Please help!
03-16-2012 06:59 PM
BonnieC1977 wrote:Thanks SOOO much for the quick reply Bodhi.... I'm planning on reflashing everything and starting anew.... This time around I plan on using the tarball binpack in hopes that everything will go much smoother the second time around
As for the Xbox, I use to have the HDD that is now attached to my FAT+ on a Windows pc that quit on me and I had TVersity in order for the files on my HDD to be seen on the Xbox.... I'm guessing that Samba now has the same purpose as Tversity did on my WinXP pc?
BonnieC,
Regarding Tversity, unfortunately not the same as Samba. Samba is a network file sharing utility, so it allows any PC that uses Samba file sharing protocol to share the files in the network. Tversity is DLNA/uPnP server, which transcodes video/music/pictures and share them in the network for any PC, media player, or TV that implement runs a DLNA client to see the files shared by Tversity. This is how I understand Tversity works a while ago.
I don't have the Xbox360 so can't say for sure, but if you can run a browser on the Xbox then it could possibly see the files through its, too (browser can use Samba protocol). I don't know if people has discovered someway for the Xbox360 to see Samba shares, you might want to look for that in Xbox360 forums.
Have fun :-)
03-17-2012 07:04 AM
Hi Bodhi,
I reflashed and installed the tarball binpack last night and after removing the USB drive used to install the binpack how do I go about editing the IP and Passwords for Transmission and Samba? I can't seem to find the settings.json or the smb.conf file anywhere. Also when I try to run Transmission it gives me the following error
/usr/local/etc # ./run_transmission.sh
ERROR: Transmission directory not found in USB drives
03-17-2012 02:28 PM
BonnieC,
To run transmission, you will need to have a USB drive plugged in and it has the Transmission folder structure on it. You can copy all folders and files (the settings.json is in there) from the installation USB drive (the USB stick that you used to install) into these directory. Look at the content of the installation USB drive on your PC and you will find these folders. If you have both drives plugged into your PC, you can just drag the transmission folder from the installation drive to the USB drive that you will use for downloading.
/transmission
/transmission/BitTorrent
/transmission/BitTorrent/Incomplete
/transmission/BitTorrent/sources
The reason it worked when you have the installation USB drive still plugged in was because the script has created this directory structure for you on that drive. But when you start using Transmission for real, a hard drive is usually needed, because the files downloaded will be large. However, you can just use any USB drive (flash or HDD) to test run, and then later use a hard drive for real operation.
The Mod FW autorun.sh will try to find an attached USB drive that has this folder structure and files in it. If it can't find the folder "transmission" on any of the attached USB drive then it will give you that error.
Hope this clarifed the issue :-) Sorry the instruction was not very detailed. It was intended for experienced Transmission users, and I was hoping that the installation script (transmission.sh) would serve as the instruction.
Let me know if you have more question!
03-18-2012 04:09 PM
Thank you Bodhi you are awesome!
I am having 2 minor issues now that I have gotten everything up and running.
1. Keep-Alive.sh does not seem to be functioning.... I changed the IP as per the instructions, but my FAT+ continues to go to "sleep" after about an hour. Therefore stopping the torrents I'm trying to download.
2. Transmission is not restarting automatically after setting it to "YES" in the autorun.sh
If you have any suggestions on how I can get these working properly I greatly appreciate it.
Again thank you SOOOOO much for your patience with this "newbie" ![]()
03-18-2012 11:24 PM
BonnieC,
The best way to make sure that every thing is runnning is:
Unplug all other USB drives from the FAT+ if any, keep the downloading USB drive attached, and then do either 1 or 2 below:
1. Unplug the power and wait for about 30 seconds and plug it in. This is the ultimate test, because it will verify that you can run the Mod FW after a power failure :-)
or
2. Telnet into the box and type the reboot command at the shell prompt:
reboot
You will be disconnected from the telnet session. Wait for the the FAT+ menu to come up on the TV screen.
========
Finally, after seeing the FAT+ menu, you can telnet back in, you will see keepalive.sh running, and transmission is running by executing the command:
ps -deaf
Note: Always use NTFS format for the downloading USB drive. This allows large files to be stored, and also avoids potential problems with reboot when a Linux Ext2/Ext3 formatted USB drive is attached to the FAT+.
03-19-2012 05:58 PM
what's the difference between this and the firmware in seagate support download
03-20-2012 11:49 AM
03-21-2012 02:34 PM
The rss setup is really very simple. I'd write some instruction for this.
03-22-2012 10:27 AM
That would be GREAT Bodhi! ![]()
I'm having a little problem with my attached 500gb Freeagent Desk drive. It seems to have gotten corrupted
I am no longer able to download torrents to the drive via Transmission... I keep getting a "Read-only file system" error.... I now realize that my HDD is NTFS formatted and that may be the culprit... Is there any way that I can fix this without having to format the entire drive and lose everything?
I don't have enough space on my laptop to transfer all my files over. I do have plenty of space on my Freeagent drive and am wondering if I can't create a partition to transfer my files to and then format the corrupted partition??? I of course would need some instruction on how to go about doing this ![]()
Any help will be greatly appreciated!
03-22-2012 01:20 PM - edited 03-22-2012 01:25 PM
BonnieC,
No, it is not a good idea to continue using the HDD
you should immediately try to offload the files to somewhere else. Linux OS is pretty good in this aspect, when it encounters error in writing to a disk (given the HDD was mounted with the option) it will change the disk file system to Read-Only so that you will have a chance to recover data. After that, reformat the disk to NTFS again on a PC. NTFS is not a problem, the UFS driver that the FAT+ uses is not very good (i.e. bugs exist) but if you are careful then it won't cause problem. In a previous thread somewhere in this forum, I've discussed how to avoid HDD/flash USB drive problem with the FAT+ (gotta find the link again, perhaps prairiedog has linked it in the sticky thread ? :-)
In a nutshell, always power down the FAT+ before you remove the drive. And whenever you attach the drive to a PC, run a quick error check (uncheck the auto fix so it won't take a long time).
PS. Here is the link to the post: http://forums.seagate.com/t5/FreeAgent-Theater-and
03-22-2012 02:29 PM
Thank you for the response Bodhi... I will see where I can transfer my files too.
I visited the link to the post you suggested and I would love to know how I would go about automating the following command you suggest using to avoid problems in the future.
"- Do a remount so that the drive is safe to remove any time later (this can be automated in Mod FW 2.23)
mount -o remount,rw,sync /tmp/usbmounts/sdxx"
You're the greatest! ![]()
03-22-2012 03:33 PM
You're welcome, I'm glad I can help
I have to think about this, as there are a few options.
03-22-2012
11:51 PM
- last edited on
04-13-2012
01:57 PM
by
AskTheLeaf
This instruction was based mostly from Dm's post. Thanks to Dm for getting all information regarding RSS feeds, and figured out how to set it up initially.
Here is a simple step-by-step instruction to help interested users set up personal RSS feeds in Mod FW 2.23.
1. At the FAT+ main menu, select Internet and go to Weather page, create a favorite. If in the US, use Zip code to let the FAT+ find your city.
2. Telnet into the box and verify that the directory and the favorite was created
/usr/local/etc/dvdplayer/savedrss/scripts/map/myfa
3. Copy the main menu (in this example, the menu is for US) to the same location where the weather map was saved:
cp /usr/local/bin/scripts/menu_US.rss /usr/local/etc/dvdplayer/savedrss/scripts/
4. Edit the file menu_US.rss using nano editor (you can also copy this file to a PC, edit it, then copy it back if desired):
- At the end of the menu_US.rss file, insert your new item between the "Empty item" ( this empty item ends at -->) and the end marker of the channel (</channel>). Note that each item starts with <item> and ends with </item>.
- In this example, I used the RSS URL for Nature, copied from metafeeds.com
<!-- <item> <title>Empty item 8</title> <link>http://</link> <media:thumbnail url="image/blankicon.jpg" /> </item> --> <item> <title>PBS Nature</title> <link>http://www.metafeeds.com/channel/nature.rss</link> <media:thumbnail> <script> state = getDrawingItemState(); if (state == "focus"){ "/usr/local/etc/rss/fav_focus.jpg"; } else { "/usr/local/etc/rss/fav_unfocus.jpg"; } </script> </media:thumbnail> </item> </channel> </rss>
5. Create the directory to hold the thumbnails files for this new item:
mkdir /usr/local/etc/rss
6. At this point, the only remaining things needed are the 2 jpg thumbnail files: fav_focus.jpg, fav_unfocus.jpg. These 2 jpg files will be used in the FAT+ Internet menu so that the item appear in focus so that you can press OK and go into the RSS page. The item switches to unfocus when you navigate away to the others services in the Internet menu.
The simple thing to do is to save these 2 jpg images inserted at the end this post and copy them to /usr/local/etc/rss/ and name the first one fav_focus.jpg, the second one fav_unfocus.jpg
7. On the FAT+, exit to the main menu, and navigate to the Internet menu (or power cycle the FAT+, should work either way). The new item should now appear at the end of the Internet menu. Have fun :-)
8. To add more feeds:
- Go to metafeeds.com or other sites that people have found many Internet feeds and copy the URL (URL name should end with rss).
- Edit the menu_US.rss again to insert new item by cut/paste the last created item (PBS Nature) right after it.
- Modify the URL with the new feed URL, and title name.
At this point, you can use the same focus/unfocus JPG files, but that will be confusing because the 2 RSS feeds in the menu will look the same :-) So perhaps the best things to do is to find JPG thumbnails that you really like, make an identical copy, and use a picture editing tool (e.g. Picasa) and add the focus marker to the 1st thumbnail, and unfocus marker to the 2nd. Rename them to something like: Science_focus.jpg, Science_unfocus.jpg (if the title name is Science). Copy them to /usr/local/etc/rss, and then edit the new item in menu_US.rss to point to these 2 files.
Note that usually the RSS pages from the "feeds" site contain several video streams. Also certain streams will need new or updated SW library (e.g. rtmplib) to play, and the FAT+ does not have the SW. Some users have figured out how to add these SW to the FAT+ Mod FW 2.23 (I have to find that post and link it here).
9. To use existing RSS pack (Dm rsspack)
You can also copy some existing RSS menu (see Xlive menu from DM's rsspack mentioned in this post), and add the whole thing to your /usr/local/etc/dvdplayer/savedrss/scripts/ directory. However, it's too big and barely fit inside the FAT+, so you will need an external USB drive location to store them.
I prefer to add each feed as I find an interesting one, so it will take little space from the limited memory in the FAT+. Usually a feed menu will contain several video streams so it's not too bad. Besides, Internet RSS feeds might have been obsolete, and it's frustrating to have a whole screen of RSS feeds that don't work :-).
10. Password protect your RSS feeds
If the Xlive menu is used, the menu should be password protected. There are certain feeds from metafeeds.com that are adult-oriented. To add password protected menu, again see Dm's post. In Dm's post, the Jumpstart menu script was modified to so that it requires a password to go into the page.
RSS instruction and thumbs:
http://www.mediafire.com/download.php?x3rigcvic578
04-01-2012 01:47 PM
Hello Bodhi,
I had to reinstall mod firware again and now i am messed up. I tried to intall binpack but i am getting some errors.
/ # /tmp/usbmounts/sda1/bin/optware-install.sh
mkdir: Cannot create directory `oleg-optware': File exists
Installing uclibc-opt (0.9.28-13) to root...
package uclibc-opt suggests installing ipkg-opt
Installing ipkg-opt (0.99.163-10) to root...
Configuring ipkg-opt
Configuring uclibc-opt
Updating /opt/etc/ld.so.cache
Successfully terminated.
Downloading http://ipkg.nslu2-linux.org/feeds/optware/oleg/cro
wget: ipkg.nslu2-linux.org: Unknown host
An error ocurred, return value: 1.
Collected errors:
ipkg_download: ERROR: Command failed with return value 1: `wget -q -P /opt/ip kg-eUNFh3 http://ipkg.nslu2-linux.org/feeds/optware/oleg/cro
It's not downloading ipkg. I don't know what to do?
04-01-2012 03:18 PM
Newuser,
Probably just a temporary outage. I've just checked this by entering the URL directly to the browser
http://ipkg.nslu2-linux.org/feeds/optware/oleg/cro
and it was downloaded fine.
Please try again!
-bodhi
04-03-2012 04:48 PM
Thanks ,i tried it again today and it worked.
Is there anyway i can disable power button on remote, so someone do not turn FAT+ off? Because my hard drive is connected to it and my all music files are there that is synced with itunes on my pc. I just want to disable it so noone can turn it off in my house. Is there anyway i can do it except taking that red button out from my remote ![]()
Thank you ![]()
04-03-2012 08:50 PM
newuser21 wrote:Thanks ,i tried it again today and it worked.
Is there anyway i can disable power button on remote, so someone do not turn FAT+ off? Because my hard drive is connected to it and my all music files are there that is synced with itunes on my pc. I just want to disable it so noone can turn it off in my house. Is there anyway i can do it except taking that red button out from my remote
Thank you
Yes, you can, with irfake. One of our forum members has used irfake succesfully here. I did not have it in the binpack, though.
04-05-2012 03:24 PM - edited 04-06-2012 08:17 AM
04-06-2012 02:13 PM
newuser21 wrote:
Thank you for the info.
I will pass on it for now.
One more ques.
Is it possible to access FAT+ attached network storage outside home network? Without PC? I searched on google could not figure out. I have dd-wrt installed on my router. Thanks for your time.
No, currently it's not possible to access the FAT+ storage from outside home network. We will need extra sw packages to make that happen. With appropriate sw packages installed, and then open a port on the router that allows traffics to the FAT+, then you can access files away from home. However, to do this, you will need to use a USB drive for extra storage (since the FAT+ /usr/local/etc is now almost full so I don't think more can be squeezed in :-)
04-07-2012 09:29 AM
Ok got it. Thank you ![]()
04-09-2012 05:19 PM - edited 04-10-2012 11:47 AM
Hi Bodhi,
I've been looking into installing Deluge for torrent downloads (much more features than transmission), but once again I don't know how to go about uninstalling transmission and installing Deluge. Would you be able to help me out with that?
Thanks again ![]()
P.S. Thank you for the detailed instructions on adding custom Rss feeds. You made it SOOOO easy to get it done.
04-10-2012 10:04 PM
BonnieC1977 wrote:Hi Bodhi,
I've been looking into installing Deluge for torrent downloads (much more features than transmission), but once again I don't know how to go about uninstalling transmission and installing Deluge. Would you be able to help me out with that?
Thanks again
P.S. Thank you for the detailed instructions on adding custom Rss feeds. You made it SOOOO easy to get it done.
BonnieC,
I think the benefit of deluge hardly making up for the works that go into installing it. You will need to use a USB drive to do this. The FAT+ memory is almost full right now
what would be the feature that you need that Transmission does not provide?
04-11-2012 10:29 AM - edited 04-11-2012 10:40 AM
Bodhi,
My biggest problem with Transmission is queuing... If I have multiple torrents on my list for downloading I can only do one at a time and once one is finished downloading it doesn't automatically start the downloading process for the next torrent in queue.... This is a real pain since I don't really want to have to keep logging into the WebUI to start each torrent individually. Maybe there is a setting in Transmission that I'm not aware of that would fix this?
Another thing is Transmission keeps disconnecting in the middle of a download, then when I restart it via Telnet and try to resume my download I get and error saying the directory where my torrent was downloading does not exist ![]()
04-11-2012 11:59 PM
That's does not sound right! please pos the content of your settings.json here and I will take a look. Also post the output of the 2 commands below. For the ls command, you don't need to include the files that you're downloading, only the directories. That's the lower case l and the capital R (l stands for long, R stands for Recursive).
mount
ls -lR /tmp/usbmounts/*
04-12-2012 10:44 AM
Hi Bodhi,
Below I'm posting all the content you asked to see.
I have also noticed that when powering the FAT+ on/off via remote the Keep-alive command and Transmission do not start up unless I reboot via Telnet... Is that normal?
Thank u for the help ![]()
Mount command:
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
none on /proc type proc (rw,nodiratime)
devpts on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
none on /tmp type ramfs (rw)
/dev/mtdblock/2 on /usr/local/Resource type squashfs (ro)
/dev/mtdblock/3 on /usr/local/etc type yaffs (rw,noatime)
/dev/mtdblock/3 on /etc/passwd type yaffs (rw,noatime)
/dev/mtdblock/3 on /usr/local/Resource/FreeSans.ttf type yaffs (rw,noatime)
/dev/rd/0 on /mnt/rd type vfat (rw,nodiratime,fmask=0022,dmask=0022,codepage=cp43
/dev/mtdblock/3 on /usr/local/Resource/ar_egbjk.ttf type yaffs (rw,noatime)
/dev/scsi/host2/bus0/target0/lun0/part1 on /tmp/usbmounts/sda1 type ufsd (rw,nodiratime,nls=utf8,nls=utf8,uid=0,gid=0,fmask
/dev/mtdblock/3 on /opt type yaffs (rw,noatime)
/dev/mtdblock/3 on /etc/profile type yaffs (rw,noatime)
/dev/scsi/host2/bus0/target0/lun0/part1 on /usr/local/etc/transmission type ufsd (rw,nodiratime,nls=utf8,nls=utf8,uid=0,gid=0,fmask
ls -lR command:
/tmp/usbmounts/sda1:
drwxrwxrwx 1 root root 4096 Apr 9 23:33 $RECYCLE.BIN
-rwxrwxrwx 1 root root 44902 Sep 26 2009 FreeAgentDesktopNext.ico
drwxrwxrwx 1 root root 4096 Apr 9 23:15 System Volume Information
-rwxrwxrwx 1 root root 67 Apr 9 23:26 autorun.inf
drwxrwxrwx 1 root root 4096 Apr 12 17:30 transmission
/tmp/usbmounts/sda1/$RECYCLE.BIN:
drwxrwxrwx 1 root root 4096 Apr 9 23:33 S-1-5-21-1038015821-2482138329-1863963033-1000
/tmp/usbmounts/sda1/$RECYCLE.BIN/S-1-5-21-10380158
-rwxrwxrwx 1 root root 544 Apr 9 23:33 $IK394DX.dat
-rwxrwxrwx 1 root root 1036 Apr 7 13:32 $RK394DX.dat
-rwxrwxrwx 1 root root 129 Apr 9 23:33 desktop.ini
/tmp/usbmounts/sda1/System Volume Information:
-rwxrwxrwx 1 root root 20480 Apr 9 23:15 tracking.log
/tmp/usbmounts/sda1/transmission:
drwxrwxrwx 1 root root 4096 Apr 10 18:59 blocklists
-rwxrwxrwx 1 root root 304 Apr 10 21:56 dht.dat
drwxrwxrwx 1 root root 4096 Apr 11 18:11 incomplete
drwxrwxrwx 1 root root 4096 Apr 11 18:10 movies
drwxrwxrwx 1 root root 4096 Apr 12 17:30 resume
-rwxrwxrwx 1 root root 2681 Apr 12 13:29 settings.json
drwxrwxrwx 1 root root 4096 Apr 6 04:01 sources
-rwxrwxrwx 1 root root 155 Apr 12 17:30 stats.json
drwxrwxrwx 1 root root 4096 Apr 11 18:12 torrents
/tmp/usbmounts/sda1/transmission/blocklists:
-rwxrwxrwx 1 root root 384336 Apr 10 18:59 badpeers-blocklist.bin
-rwxrwxrwx 1 root root 3208 Apr 10 18:59 hijacked-blocklist.bin
-rwxrwxrwx 1 root root 1814656 Apr 10 18:59 level1-blocklist.bin
-rwxrwxrwx 1 root root 596944 Apr 10 18:59 level2-blocklist.bin
-rwxrwxrwx 1 root root 133608 Apr 10 18:59 level3-blocklist.bin
-rwxrwxrwx 1 root root 2461624 Apr 10 18:59 primarythreasts-blocklist.bin
-rwxrwxrwx 1 root root 21896 Apr 10 18:59 spyware-blocklist.bin
/tmp/usbmounts/sda1/transmission/incomplete:
drwxrwxrwx 1 root root 4096 Apr 10 19:03 filename
drwxrwxrwx 1 root root 4096 Apr 10 22:17 filename
drwxrwxrwx 1 root root 4096 Apr 11 18:10 filename
drwxrwxrwx 1 root root 4096 Apr 11 18:04 filename
drwxrwxrwx 1 root root 4096 Apr 11 17:51 filename
/tmp/usbmounts/sda1/transmission/incomplete/file
/tmp/usbmounts/sda1/transmission/incomplete/file:
/tmp/usbmounts/sda1/transmission/incomplete/file:
drwxrwxrwx 1 root root 4096 Apr 11 18:04 file.avi.part
/tmp/usbmounts/sda1/transmission/incomplete/file.a
-rwxrwxrwx 1 root root 0 Apr 12 16:14 file.avi.part
/tmp/usbmounts/sda1/transmission/incomplete/file:
-rwxrwxrwx 1 root root 0 Apr 12 16:14 file.avi.part
/tmp/usbmounts/sda1/transmission/incomplete/[ filename ] - file:
-rwxrwxrwx 1 root root 743321390 Apr 12 17:35 file.avi.part
drwxrwxrwx 1 root root 4096 Apr 10 19:03 file.txt
/tmp/usbmounts/sda1/transmission/incomplete/[ filename ] - file.txt:
/tmp/usbmounts/sda1/transmission/movies:
drwxrwxrwx 1 root root 4096 Apr 10 03:47 file1
drwxrwxrwx 1 root root 4096 Apr 9 23:32 file2
drwxrwxrwx 1 root root 4096 Apr 9 23:33 file3
drwxrwxrwx 1 root root 4096 Apr 10 00:23 file4
/tmp/usbmounts/sda1/transmission/resume:
-rwxrwxrwx 1 root root 5958 Apr 11 18:13 file.64469c16b4abd42b.resume
-rwxrwxrwx 1 root root 11342 Apr 12 17:30 file2.3621a1a57f6fc6ca.resume
/tmp/usbmounts/sda1/transmission/sources:
/tmp/usbmounts/sda1/transmission/torrents:
-rwxrwxrwx 1 root root 8756 Apr 11 18:12 file.64469c16b4abd42b.torrent
-rwxrwxrwx 1 root root 29451 Apr 11 17:48 file2.3621a1a57f6fc6ca.torrent
settings.json content:
"alt-speed-down": 30,
"alt-speed-enabled": false,
"alt-speed-time-begin": 480,
"alt-speed-time-day": 62,
"alt-speed-time-enabled": false,
"alt-speed-time-end": 1020,
"alt-speed-up": 30,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": true,
"blocklist-url": "",
"cache-size-mb": 4,
"dht-enabled": true,
"download-dir": "/usr/local/etc/transmission/movies",
"download-limit": 100,
"download-limit-enabled": 0,
"download-queue-enabled": true,
"download-queue-size": 5,
"encryption": 2,
"idle-seeding-limit": 30,
"idle-seeding-limit-enabled": false,
"incomplete-dir": "/usr/local/etc/transmission/incomplete",
"incomplete-dir-enabled": true,
"lazy-bitfield-enabled": true,
"lpd-enabled": false,
"max-peers-global": 200,
"message-level": 2,
"open-file-limit": 1024,
"peer-congestion-algorithm": "",
"peer-limit-global": 240,
"peer-limit-per-torrent": 60,
"peer-port": 46969,
"peer-port-random-enabled": 1,
"peer-port-random-high": 65535,
"peer-port-random-low": 46012,
"peer-port-random-on-start": false,
"peer-socket-tos": "default",
"pex-enabled": true,
"port-forwarding-enabled": false,
"preallocation": 1,
"prefetch-enabled": 1,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"queue-stalled-enabled": true,
"queue-stalled-minutes": 30,
"ratio-limit": 2,
"ratio-limit-enabled": true,
"rename-partial-files": true,
"rpc-authentication-required": true,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "{2a4f8add91b950f19d00325554c867a5e2863279gY.faWnN
"rpc-port": 9091,
"rpc-url": "/transmission/",
"rpc-username": "bonnie",
"rpc-whitelist": "*.*.*.*",
"rpc-whitelist-enabled": true,
"scrape-paused-torrents-enabled": true,
"script-torrent-done-enabled": false,
"script-torrent-done-filename": "",
"seed-queue-enabled": false,
"seed-queue-size": 10,
"speed-limit-down": 1000,
"speed-limit-down-enabled": true,
"speed-limit-up": 30,
"speed-limit-up-enabled": true,
"start-added-torrents": true,
"trash-original-torrent-files": false,
"umask": 0,
"upload-limit": 100,
"upload-limit-enabled": 0,
"upload-slots-per-torrent": 14,
"utp-enabled": true,
"watch-dir": "/usr/local/etc/transmission/movies",
"watch-dir-enabled": 0
04-13-2012 05:38 PM - edited 04-13-2012 05:42 PM
BonnieC,
1. First take out
"download-queue-enabled": true,
"download-queue-size": 5,
because it sounds like you don't want any queuing? let all torrents start downloading once you add it. If you ever need to postpone a torrent, keep it really simple by "Pausing" the torrent.
2. It's true that the remote power off button will stop keep-alive. I think also Transmission. There is really no way around it. If the FAT+ box is used for Transmission then it should never be turned off, anyway
If you ever need to temporarily slow the traffics because Transmisison is interferring with other Internet usage then you can put it in "Turtle" mode using the Tranmission Web GUI.
Number 1 above might be related to the problem with the "directory not found". So let's see how it goes there. You should see all torrents started right after you've added them.
You might be interested in this: if you use a smart phone (iPhone or Android), then you can monitor torrents and perform most of the commands using your web browser on the phone ![]()
04-14-2012 06:54 AM
Hi Bodhi,
It seems you misunderstood me.
What I am looking for is to queue torrents. Which does not seem to be working in Transmission. If I add more that one torrent they all start downloading at the same time and end up freezing the FAT+.
04-15-2012 02:43 PM
BonnieC1977 wrote:Hi Bodhi,
It seems you misunderstood me.
What I am looking for is to queue torrents. Which does not seem to be working in Transmission. If I add more that one torrent they all start downloading at the same time and end up freezing the FAT+.
I see. I never tried torrents queuing on the FAT+ so was not aware that it has some problem. It is to be expected, though. Because the optware Transmission version we installed is pretty old, and it might not have the fixes for that problem. As I said, you can get around it by not using queue at all. Just pause all torrents and resume only ones you want to be active. And just log in using your phone (if you have one that is capable of browsing internet) or your PC and resume the torrent(s). I will track this down (version that has fixes) when I have time to do that :-)
04-24-2012 03:33 PM
first of all,, Im so sorry for my very weak English.
Thank you for your usefull tutorial (Mod 2.23 Firmware - Manual Steps to install FAT+ Mod 2.23 with utilities).
I do everything you said on your tutorial and everything done ok, but when play a movie with srt subtitle(movie & subtitle has Exact Same name), Farsi(Persian) characters are invisible but english and symbol character show fine.
what I do wrong?
thank you again dear friend
04-24-2012 10:03 PM
The Mod 2.23 FW with lastest binpack should support Farsi. See this thread.
- Did you install the latest binpack? or use the tar file?
- Did you try an English subtitle srt file with the exact same name?
04-25-2012 12:44 AM - edited 04-25-2012 11:47 AM
question 1: I did Install the tar file.
question 2:Right now I play a Movie with English Srt subtitle with the exact same name and everythings is ok.
i did'nt install the binpack ,this binpack installation is neccessary?
04-25-2012 09:43 PM
The tar file includes everything. So there is no need to install the binpack if you used the tar file to install.
The only way to know for sure is: attach your srt subtitle file here, and I will try it out to see if my FAT+ can display it correctly (or post a link where I can download a Farsi subtitle file). And then, if it does not display correctly on my FAT+, you will need to try it on your PC following the same steps inuris did in the thread I posted above (find the arial.ttf file that can be used to display Farsi subtitle, and post that true type font arial.ttf file back here and I will try it,....).
04-26-2012 02:16 AM - edited 04-26-2012 04:21 PM
Thank you Bodhi for Helping me ![]()
in this rar file I put 3 Farsi srt file and take screenshot of them to Show how looks like farsi word on the srt file.
and put a arial.ttf font which is installed by default on my system which display farsi very well on software that soppurt UNICODE features like KMPlayer or K-lite Mega codedc pack(media player classic)
the file version of Arial that I've sent is 5.10
I'm searchig on the net and found it about arial font:
Arial
arial.ttf, arialbd.ttf, arialbi.ttf and ariali.ttf)
Source: Supplied with the Windows XP SP2 (service pack 2) update. Older versions were supplied with various Microsoft products and the Smart package of Microsoft's core fonts project.
Stats: Version 3.00 has 1,674 glyphs and 909 kerning pairs Support: Arabic script (Arabic, Ajami, Azeri, Balochi, Berber, Brahui, Kazakh, Kirghiz Kurdish, Lahnda, Jawi, Pashto, Persian, Shahmukhi, Sindhi, Uighur, Urdu, Uzbek), Cyrillic (Russian plus other Slavic and non-Slavic languages), Greek, Hebrew, Latin, Vietnamese.
Warning: Versions prior to 3.00 supported only the Arabic letters used for Arabic and Persian languages.
OpenType Layout Tables: Arabic (default, MAR)
04-27-2012 12:47 AM
Hamed wrote:Thank you Bodhi for Helping me
in this rar file I put 3 Farsi srt file and take screenshot of them to Show how looks like farsi word on the srt file.
and put a arial.ttf font which is installed by default on my system which display farsi very well on software that soppurt UNICODE features like KMPlayer or K-lite Mega codedc pack(media player classic)
the file version of Arial that I've sent is 5.10
I'm searchig on the net and found it about arial font:
Arial
arial.ttf, arialbd.ttf, arialbi.ttf and ariali.ttf)
Source: Supplied with the Windows XP SP2 (service pack 2) update. Older versions were supplied with various Microsoft products and the Smart package of Microsoft's core fonts project.
Stats: Version 3.00 has 1,674 glyphs and 909 kerning pairs Support: Arabic script (Arabic, Ajami, Azeri, Balochi, Berber, Brahui, Kazakh, Kirghiz Kurdish, Lahnda, Jawi, Pashto, Persian, Shahmukhi, Sindhi, Uighur, Urdu, Uzbek), Cyrillic (Russian plus other Slavic and non-Slavic languages), Greek, Hebrew, Latin, Vietnamese.
Warning: Versions prior to 3.00 supported only the Arabic letters used for Arabic and Persian languages.
OpenType Layout Tables: Arabic (default, MAR)
Hamed,
Good news! the current installation of the arial.ttf font in Mod 2.23 tar file does work with Farsi. There is no need to install another ttf file.
Now when you said it did not work, I think it might be just a matter of starting up the FAT+/GoFlexTV correctly. Try this:
- telnet into the FAT+
- at the command line, type
reboot
- wait until the FAT+ menu appear on the TV screen, select the movie file with Farsi subtitle and try to play it. If the subtitle display OK then congrats :-)
- if the subtitles did not display correctly, telnet into the FAT+ again, and type 3 commands
ps
mount
ls -l /usr/local/etc
- copy the output of all 3 commands and post here.
-bodhi
04-27-2012 05:31 AM - edited 04-27-2012 05:36 AM
Dear bodhi I did what you said but again did not show Farsi Character.
and accordint to your post which you said Farsi subtitle diplayed correctly on your FAT+ im thinking maybe I making a mistake in my proccess.
my Goflex TV region is EMEA and when i try to mod with EMEA vesion mod file, Farsi character not displayed then i reinstall US 2.20 FW and telnet to 2.23 US mode file and in the last i install your Tar file and play a movie with Farsi Subtitle and Farsi Character Finally displayed but not correctly.
I'll show you Problem with Picture :
http://up98.org/upload/server1/02/i/fq9i2dar8md1fe
50% of my problem solved(((FARSI Letters displayed))) but text direction in Farsi is right to left but goflexTV from left to right shows the Farsi word that create problem and makes Farsi word unreadable.
PS:
PID Uid VmSize Stat Command
1 root 376 S init
2 root SWN [ksoftirqd/0]
3 root SW< [events/0]
4 root SW< [khelper]
5 root SW< [kthread]
6 root SW< [kblockd/0]
7 root SW [khubd]
8 root SW [rpc-1]
9 root SW [rpc-3]
10 root SW [pdflush]
11 root SW [pdflush]
12 root SW [kswapd0]
13 root SW< [aio/0]
14 root SW< [cifsoplockd]
15 root SW< [cifsdnotifyd]
16 root SW [eth0]
17 root SW [mtdblockd]
29 root 380 S init
30 root 380 S init
33 root 380 S init
36 root 380 S init
187 root 400 S inetd
206 root SW< [sata_eh/0]
214 root SW [scsi_eh_0]
215 root SW [scsi_eh_1]
218 root 148 S ./RootApp DvdPlayer
220 root 148 S ./RootApp DvdPlayer
222 root 7084 S < DvdPlayer
223 root 148 S ./RootApp DvdPlayer
225 root 7084 S DvdPlayer
226 root 7084 S N DvdPlayer
227 root 7084 S N DvdPlayer
234 root 7084 S DvdPlayer
235 root 7084 S DvdPlayer
237 root 7084 S DvdPlayer
239 root 7084 S DvdPlayer
240 root 7084 S DvdPlayer
241 root 7084 S DvdPlayer
242 root 7084 S DvdPlayer
243 root 7084 S N DvdPlayer
244 root 7084 S DvdPlayer
245 root 7084 S DvdPlayer
246 root 7084 S DvdPlayer
247 root 7084 S DvdPlayer
248 root 7084 S DvdPlayer
249 root 7084 S DvdPlayer
251 root 7084 S DvdPlayer
252 root 7084 S DvdPlayer
279 root 7084 S DvdPlayer
288 root 7084 S DvdPlayer
289 root 7084 S DvdPlayer
290 root 7084 S DvdPlayer
291 root 7084 S DvdPlayer
294 root 7084 S DvdPlayer
295 root 7084 S DvdPlayer
366 root 1252 S /opt/sbin/smbd -D
377 root 1172 S /opt/sbin/nmbd -D
384 root 416 S /bin/sh /usr/local/etc/bin/keep-alive.sh
386 root 424 S /bin/sh /usr/local/etc/bin/keep-alive.sh
387 root 272 S sleep 3300
400 root 204 S /usr/local/etc/bin/syslogd -C64
433 root 328 S telnetd
434 root 512 S -sh
448 root 372 R ps
mount:
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
none on /proc type proc (rw,nodiratime)
devpts on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
none on /tmp type ramfs (rw)
/dev/mtdblock/2 on /usr/local/Resource type squashfs (ro)
/dev/mtdblock/3 on /usr/local/etc type yaffs (rw,noatime)
/dev/rd/0 on /mnt/rd type vfat (rw,nodiratime,fmask=0022,dmask=0022,codepage=cp4
37,iocharset=iso8859-1)
/dev/mtdblock/3 on /etc/passwd type yaffs (rw,noatime)
/dev/mtdblock/3 on /usr/local/Resource/FreeSans.ttf type yaffs (rw,noatime)
/dev/mtdblock/3 on /usr/local/Resource/ar_egbjk.ttf type yaffs (rw,noatime)
/dev/mtdblock/3 on /opt type yaffs (rw,noatime)
/dev/mtdblock/3 on /etc/profile type yaffs (rw,noatime)
ls -l /usr/local/etc
-rwxr-xr-x 1 root root 778552 Jan 26 2012 arial.ttf
-rwxr-xr-x 1 root root 3127 Jan 30 2012 autorun.sh
drwxr-xr-x 1 root root 2048 Oct 23 18:07 bin
-rwxr-xr-x 1 root root 1542944 Jan 30 2012 busybox-mipsel
drwxr-xr-x 1 500 500 2048 Oct 23 18:47 dvdplayer
-rwxr-xr-x 1 root root 451388 Jan 26 2012 freesans.ttf
lrwxrwxrwx 1 root root 8 Oct 23 18:07 hdd -> /tmp/hdd
drwxr-xr-x 1 500 500 2048 Jan 30 2012 hdd.old
-rw-r--r-- 1 500 500 20 Jul 7 2010 hosts
-rw-r--r-- 1 root root 0 Jan 25 2012 initsa
drw-rw-rw- 1 root root 2048 Jan 27 2012 lost+found
-rw-r--r-- 1 500 500 4 Jul 7 2010 magic
drwxrwxrwx 1 root root 2048 Oct 23 18:07 media
drwxr-xr-x 1 root root 2048 Jan 30 2012 oleg-optware
-rwxr-xr-x 1 root root 476 Jan 26 2012 passwd
drwxr-xr-x 1 500 500 2048 Oct 23 18:06 ppp
-rwxr-xr-x 1 root root 1123 Jan 26 2012 profile
-rw-r--r-- 1 root root 230 Oct 23 18:47 resolv.conf
-rwxr-xr-x 1 root root 1759 Jan 26 2012 run_transmission.sh
drwxr-xr-x 1 root root 2048 Jan 26 2012 transmission
04-27-2012 02:19 PM - edited 04-27-2012 03:39 PM
OK. So now we know why it was not working for you. If you install Mod 2.23 FW for EMEA region. You will then need to install the latest binpack to have Farsi subtitle working. The tar file was created after I've installed US version of Mod 2.23. There must be some settings in there that caused the subtitle direction to reset to left-to-right.
Try this first: reflash the EMEA Mod 2.23 FW, and telnet in and install the tar file. Immediately after installing the tar file, do a reboot by typing "reboot" at the command prompt. See if it works.
If that reboot above did not work, the problem can be only be solved by reflashing the Mod 2.23 FW for EMEA. And then download and intall the binpack manually. If you're comfortable with Linux command lines, then follow the instructions to install the binpack in the first post, don't use the tar file.
PS. When I compared the letters in the Srt subtitles file with what were being displayed on the screen, the letters looked similar. But since I don't know Farsi, I could not really tell if they were reversed :-) Since they din't look jumbled with weird graphics, I've assumed that they were OK.![]()
04-27-2012 03:39 PM
I gonna kill myself. ![]()
i do both way you said to me but problem not solved.
dear bodhi I'm so sorry because I took your time.
04-27-2012 03:44 PM
So what did you see after you've installed EMEA Mod FW and binpack? did the Farsi letters display OK? and the direction of the subtitles still reversed? Please describe exactly what you saw on the screen.
04-27-2012 03:53 PM
The problem actually is i'dont see any of farsi letters when i use EMEA mod file.
04-27-2012 04:05 PM
Even after installing binpack 1.4?
©2012 Seagate Technology LLC