מדריך להתקנת PGI 1.3 ב-CUBEREVO

מצורף מדריך להתקנת אימג" PGI 1.3 בממיר CUBEREVO ב FLASH אבל העיקרון עובד
לגביי כל אימג" בהתקנת FLASH . בנוסף מצורפים קישורים להורדת קובץ אימג" PGI 1.3
וקובץ ה-ADDON 0.9 ל PGI 1.3 הקבצים נקיים לחלוטין להתקנה חדשה וטריה לכל מי
שסבל מבעיות בהתקנה קודמת.














URL=https://2img.net/r/ihimg/photo/my-images/208/pgi3.png/][/URL]














http://www.2shared.com/file/4TxOJZG4/addon-v009pgi.html




http://www.2shared.com/file/xtppBDQw/PGI-91-v13.html


בהצלחה.

MBD

תודה רבה
Lily allen



Lily allen

אם היה הסבר שלב שלב ביוטיוב בוידאו זה היה 100 אחוז

Information on Alternative Network Connection Types
==============================================================================

Contents:

0. Setting up WLAN/USB adapters
1. General information about PPP connections using PPPd
2. GPRS/EDGE connections using USB connected mobile phones with CDC-ACM driver
3. High Speed 3G/UMTS/CDMA USB modems
4. Analog modems and other RS232 devices (using additional PL2303 based USB to Serial converter)
5. PPPoE (PPP over Ethernet) using built-in LAN adapter
6. Additional notes on PPP connections



0. Setting up Wi-Fi/USB adapters
==============================================================================

0.0 This image supports the WLAN/USB devices based on the following Ralink chipsets: RT2870 and RT3070. The actual devices built with those chips are numerous and can be found inside many well known adapters produced by D-Link, Linksys, Netgear, Belkin and others. Here is a non-exhaustive list of the verified devices:

D-Link DWA-125 (A1/A2)
D-Link DWA-140 (B1/B2)
D-Link DWA-160 B1
Linksys WUSB-100N v2
SMC EZ Connection N
TP-Link TL-WN727N (v1.3/v2.0)
Edimax EW-7711U*N

0.1 The connection setup is performed by editing two configuration files (or just one in case you want to use DHCP): /var/etc/Wireless/RT*STA/RT*STA.dat and /var/interfaces_wlan. The following procedure should be performed only once, during initial setup. All the commands described below should be executed via Telnet. Connect your WLAN adapter to the USB port and run the command:

iwconfig

You should see several network interfaces, including the following (the keyword is wlan0):

wlan0 RT2870 Wireless ESSID:""
Mode:Auto Frequency=2.412 GHz
Link Quality=10/100 Signal level:0 dBm Noise level:-143 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

The above output means that there has been a new wireless device created called wlan0 and that your WLAN adapter based on the RT2870 chipset has been recognised. Keep the chipset name in mind (it follows "wlan0" label in the output) as it will be required for the next step. If the the chipset name is not shown (happens for some devices from time to time) you can execute the following command: lsmod. That should display all of the currently loaded kernel modules and you should be able to get the the chipset name from that output (rt2870 or rt3070).

0.2 Locate the directory inside /var/etc/Wireless which matches the chipset name you've just obtained. Inside that directory there will be a similarly named file with a .dat extension. For instance, in this example the file will be called /var/etc/Wireless/RT2870STA/RT2870STA.dat. That file is an ordinary text file that should can edited using a standard Unix compatible plain text editor. You must put your wireless network settings into this file. The absolute minimum for WPA or WPA2 encrypted connection is:

SSID=Your-Acces-Point-SSID
AuthMode=OPEN | SHARED | WEPAUTO | WPAPSK | WPA2PSK | WPANONE (pick one, see below for detailed description)
EncrypType=NONE | WEP | TKIP | AES (self-explanatory, pick one)
WPAPSK=Pre-Shared-Key (if required)

AuthMode can be one of the following:
OPEN no encryption
SHARED shared key (basically, WEP encryption)
WEPAUTO automatic change between OPEN and SHARED
WPAPSK WPA mode with pre-shared key
WPA2PSK WPA2PSK mode with pre-shared key
WPANONE WPA with pre-shared key in AdHoc mode

0.3 You can skip this step if you want to use DHCP settings for your wireless interface, otherwise you need to edit the file /var/interfaces_wlan. You should specify the IP configuration for the wlan0 interface in this file as follows (change the values that suit your network):

iface wlan0 inet static
address 192.168.1.25
netmask 255.255.255.0
gateway 192.168.1.1

If you want to use DHCP again, just put the following into this file:
iface wlan0 inet dhcp

0.4 Try bringing up the interface using the following command:

ifup -i /var/interfaces_wlan wlan0

If everything works fine (check the configuration with ipaddr, ifconfig, iwconfig, etc.), then you do not need to do anything else and the next time you reboot your receiver the wireless connection will be established automatically.



1. General information about PPP connections using PPPd
==============================================================================

1.0 All the connection methods described in the rest of this document make use of the PPP protocol and PPPd service which has been made available on Cuberevo for the first time ever by the PGI team. The difference between these connection types is only in the commands that will be sent to your modem device and in some PPPd settings.

1.1 In addition to the PPPd service, the PGI image contains full support for iptables, i.e. Linux firewall, which (if configured the right way) allows to protect the receiver from external attacks that can become a reality once the receiver is directly connected to the Internet. iptables also allow things like Internet connection sharing using NAT and masquerading, although you should keep in mind the hardware and software limitations as well as the fact that you will have to configure iptables yourself for such purposes.

1.2 It should be made clear that this document is NOT a complete guide to PPPd and iptables. The ultimate configuration will most likely be different for each user. All the information "missing" in this document can be easily found on the Internet. This document serves just one purpose: to explain where all of the configuration parts are located and the general approach to configuring various PPP connection types. The details can then be tailored by users to suit their needs.

1.3 The minimum requirement for all types of PPP connection (except PPPoE) is to establish a SERIAL LINK between the receiver and your "modem device" (no matter whether it is an old-school dial-up modem or the latest HSDPA/3G device). Since the built-in RS232 port is used for debugging (and is not available at all on 91HD) the only feasible way is to use the receiver's USB port. To turn the USB port into a serial communication device a special driver is required (depending on the connected device type), so ultimately, the PPP connection requires a USB connected device which has driver support for Cuberevo. The procedure to find out whether your modem device is supported by Cuberevo is described below in the relevant section. The PPPoE connection does not require any special drivers as it uses the built in LAN interface and all the necessary drivers are already a part of the PGI image.

1.4 If your USB port is already being used (for instance, by a storage device) and you want to connect a second device to it, you can try using good quality USB 2.0 hub, ideally a powered hub with its own power source.

1.5 After you have successfully set up your PPP connection as described below you can set the PPP parameter in pgi.conf and the connection will be established automatically every time the receiver is restarted. It is possible to control the PPP connection using the scripts menu plugin (available via the WWW button on the remote by default, except 91HD where this menu can be called via the OSD plug-in menu -> script plugin). Finally, you can enable "on-demand connection" (using already supplied templates in the /var/etc/ppp/peers directory) where connection will be established only when there is a need for it (and will be terminated automatically after period of inactivity).



2. GPRS/EDGE connections using USB connected mobile phones with CDC-ACM driver
==============================================================================

2.0 The cdc-acm.ko Linux kernel driver is supplied with the image to enable support for certain mobile phones with a USB interface and CDC-ACM standard support. There is no exhaustive list of the supported phone models, but there is a very good chance for many older Nokia phones that use the CA-53 (and similar) data cable. All steps described below should be performed only once during the initial setup. All the commands should be executed via Telnet.

2.1 Connect your phone using a compatible USB data cable and type the following command: dmesg
If the last lines of the output contain the output similar to the following:

cdc_acm: no version magic, tainting kernel.
drivers/usb/class/cdc-acm.c: Ignoring extra header, type -3, length 4
cdc_acm 2-1:1.1: ttyACM0: USB ACM device
usbcore: registered new driver cdc_acm
drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters

then the phone has been detected with the cdc-acm driver and the chances of getting a connection are very good. In any case, you have to see the message about "ttyACM...: USB ACM device".

2.2 Check if the ttyACM device has been created using the following command: ls -ls /dev/ttyACM*

crw-rw---- 1 root root 166, 0 Mar 18 10:34 /dev/ttyACM0

If the output is similar to the above (there can be more than one device with the ttyACM name), then everything is going well. Otherwise there is a problem with the device compatibility.

2.3 Now that we have a serial device for communication with the phone the PPPd service can make use it. PPPd related configuration is contained in several files. A special chat-script is one of them. It contains the modem "AT-commands" sent to the modem to establish the required connection. The actual chat-script can be located anywhere on the system but it is good practice to keep it in the directory /var/etc/ppp/chats, already allocated for this purpose. There are already several "out of the box" templates in this directory. One of them is called gprs.chat and can be used as a template for GPRS connections. Most likely it will have to be modified to fit your Internet provider settings (as a bare minimum you need to change the Access Point name set by default to "internet").

2.4 Sometimes you will have to change more commands in the chat file, depending on your phone model and ISP settings. It is advisable to search for your particular settings on the Internet as they are most likely already have been described by somebody else. It is also possible to use the "picocom" utility supplied with PGI images to check your modem configuration and to test various AT commands. Picocom allows sending AT commands directly to your modem via the serial device and displaying modem replies. In fact it is possible to fully control your modem using this utility. Start your modem session as follows: "picocom -c /dev/ttyACM0" (with local echo) or "picocom /dev/ttyACM0" (without local echo). To exit picocom session press CTRL+A immediately followed by CTRL+Q. Once the session is established you can try various AT commands to display or set your modem parameters. For instance, AT&V should display all possible commands and settings, while ATI should show manufacturer information/IMEI, etc. More commands can be seen here: http://en.wikipedia.org/wiki/Hayes_command_set#GSM , however, most manufacturers have their own custom AT commands which allow configuring additional parameters (see 3.1 below, for example).

2.5 Once the chat script is ready the actual PPPd configuration file, also known as the "peer" file, needs to be created. This file MUST reside in the /var/etc/ppp/peers directory. During PPPd start the file name is used as the parameter and most of the PPPd settings will be read from there. The settings include the chat script name (from 2.3 above), the serial interface speed, and importantly, the serial device name (from 2.2 above). If you have several /dev/ttyACM* devices, you have to try them in turn to see which one is really the one you want. There already exists a template called /var/etc/ppp/peers/gprs that contains some typical settings for GPRS connection. Some ISPs may require a user name and password to be supplied. You have to use the additional settings in the peers file as well as to modify the chap-secrets or pap-secrets file located in /var/etc/ppp/, although the standard practice is not to use any logins for GPRS connections. Additional information on the peer file options can be found on the Internet. Also it is worth checking Linux man-pages for PPPd.

2.6 Now you can test the connection by launching PPPd with the following command:

pppd call <filename> &

where <filename> is the name of the file from /var/etc/ppp/peers directory (step 2.5).

If all the settings are correct, then there should be some activity on your phone related to creating a GPRS connection. The Telnet session should then have some output similar to the following:

[PGI ~]$ pppd call gprs &

Script /sbin/chat -v -f /var/etc/ppp/chats/gprs.chat finished (pid 1287), status = 0x0
Serial connection established.
using channel 2
Using interface ppp0
Connect: ppp0 <--> /dev/ttyACM0
Warning - secret file /etc/ppp/pap-secrets has world and/or group access
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x49aa270e> <pcomp> <accomp>]
rcvd [LCP ConfRej id=0x1 <magic 0x49aa270e> <pcomp> <accomp>]
sent [LCP ConfReq id=0x2 <asyncmap 0x0>]
rcvd [LCP ConfAck id=0x2 <asyncmap 0x0>]
rcvd [LCP ConfReq id=0x0 <auth pap> <mru 1500> <asyncmap 0xa0000>]
No auth is possible
sent [LCP ConfRej id=0x0 <auth pap>]
rcvd [LCP ConfReq id=0x1 <mru 1500> <asyncmap 0xa0000>]
sent [LCP ConfAck id=0x1 <mru 1500> <asyncmap 0xa0000>]
sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
rcvd [IPCP ConfReq id=0x0 <addr y.y.y.y>]
sent [IPCP ConfAck id=0x0 <addr y.y.y.y>]
rcvd [IPCP ConfNak id=0x1 <addr x.x.x.x> <ms-dns1 z.z.z.z> <ms-dns2 z.z.z.z>]
sent [IPCP ConfReq id=0x2 <addr x.x.x.x> <ms-dns1 z.z.z.z> <ms-dns2 z.z.z.z>]
rcvd [IPCP ConfAck id=0x2 <addr x.x.x.x> <ms-dns1 z.z.z.z> <ms-dns2 z.z.z.z>]
Script /etc/ppp/ip-pre-up started (pid 1291)
Script /etc/ppp/ip-pre-up finished (pid 1291), status = 0x0
local IP address x.x.x.x
remote IP address y.y.y.y
primary DNS address z.z.z.z
secondary DNS address z.z.z.z

You can verify your new IP configuration by using standard commands such as "ip address", etc.:

ip address

ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 3
link/ppp
inet x.x.x.x peer y.y.y.y/32 scope global ppp0

where x.x.x.x is your newly obtained external IP address.

To watch the PPP traffic you can use the following command: pppstats -w1 (press CTRL+C to stop)

To disconnect an active PPP connection use the command: killall pppd

2.7 If all works OK and you are happy with the connection, you can enable the option to start a connection automatically every time the receiver is powered on. To enable this option you have to specify the peer file name (from /var/etc/ppp/peers directory) in pgi.conf (PPP parameter). For the example above, the parameter will be as follows: PPP="gprs". Don't forget about the possibility to manually control PPP connections (see 1.5 above)



3. High Speed 3G/CDMA/HSDPA USB modems
==============================================================================

3.0 All in all, setting up the PPPd service to work with the high-speed USB modems is no different at all to the procedure for setting up a GPRS connection (described above in section 2). There is, however, slightly more work required to get the serial device initially recognised. The problem with many of the existing high-speed USB modems comes from their hardware feature designed for Windows OS. This feature is known as Zero-CD and works as follows. When you connect your USB modem to a PC for the first time, it presents itself not as a real modem but as a storage device which contains (Windows) drivers and some additional (Windows) software. After you install these drivers, the behaviour changes. Now every time you connect this modem to the same system, the already-installed (Windows) drivers automatically change the device operation mode from "storage device" to "data", so that the actual modem functionality can be used. This works OK in Windows, but does not work at all (or very poorly) in Linux. Linux kernel will see devices such as a CD-ROM or flash media.

You can easily check if your modem is one of such "double-standards" devices. Connect the device to the receiver's USB port and type the following command in the Telnet session: dmesg

If the output looks similar to the following (in this example a Toshiba G450 USB 3G modem is used):

usb 2-1: new full speed USB device using ST40-ohci and address 3
usb 2-1: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at X
usb-storage: waiting for device to settle before scanning
Vendor: Toshiba Model: Rev: X.XX
Type: CD-ROM ANSI SCSI revision: XX
usb-storage: device scan complete

The above output means that the modem has the Zero-CD feature and has been recognised by the kernel as a CD-ROM drive so it has to be switched into a modem mode. If, on the other hand, you would see something like the following:

usb 2-1: new full speed USB device using ST40-ohci and address XX
usb 2-1: configuration #1 chosen from 1 choice

... that means that the modem does not need mode switching and most likely will work as is.

3.1 What to do if the modem requires switching its operating mode? It is necessary to point out that some USB modems can be switched into a permanent "data" mode with their own (usually Windows) software. This mode of operation is always preferred, but not many devices support such a feature. You should Google for your specific device behaviour. For example, a lot of Huawei 3G USB modems can be permanently switched with the following AT commands:

Modem only: AT^U2DIAG=0
Modem + CD-ROM: AT^U2DIAG=1
Modem + CD-ROM + Card Reader: AT^U2DIAG=255
Modem + Card Reader: AT^U2DIAG=256

Although, before you can issue such commands your device must already be in the modem-only mode. Therefore, it is likely that you will have to make use of usb_modeswitch utility.

3.2 In all other cases where permanent switching is impossible a usb_modeswitch utility should be used to get the device working in the right mode. The utility has a database of supported devices which it uses during the switching process. If your device requires mode switching, it is important to check whether your device is present in that database. To see your actual device's ID, use "lsusb" command in Telnet. To check if your USB ID is present in the usb_modeswitch database, execute the following Telnet command: ls -1 /usr/share/usb_modeswitch If your ID is NOT in the list of the supported devices then either usb_modeswitch knows nothing about your device or your device does not need mode switching. If your ID is in the list, then there is a relatively good chance that it can be switched into the right mode, although it is never guaranteed to work with all of the listed devices since the older Linux kernel used in this receiver is rather picky about USB communications.

NOTE: The usb_modeswitch database is updated from time to time with new device models and can be found on the usb_modeswitch website ( http://www.draisberghof.de/usb_modeswitch/ ). It is possible to update the usb_modeswitch database on the receiver without the need to install new firmware image. You only need to place the updated files into the /var/etc/usbmodeswitch.d directory.

3.3 If everything is set up correctly, the modem will be switched into the data mode upon the reboot and there will be one or more devices created in the /dev directory. The switch is only successful if there is new device created in /dev called /dev/ttyUSB0 (there may be more than one ttyUSB device for some modems) with an alias device called /dev/gsmmodem. If nothing of this sort happens, the best way to start troubleshooting is to enable usb_modeswitch logging in /var/etc/usb_modeswitch.conf and then check the log files in the /var/log directory (do not forget to reboot every time you change something in the configuration files).

3.4 The rest of the settings for the actual chat-script and PPPd peer config are similar to what is described for a GPRS connection above (steps 2.3 - 2.7) The difference will be in the serial device name (/dev/gsmmodem instead of /dev/ttyACM0) and the port speed (typically 460800 instead of 115200). Most likely some AT-commands in the chat script will have to be changed to enable UMTS/3G mode. There are some templates available for 3G connections in /var/etc/ppp/chats and /var/etc/ppp/peers directories which will have to be modified to suit your situation (see 2.4 above).

3.5 Certain high-speed modems that require SIM cards to function may need their PIN code function deactivated (if possible) using the software supplied with the device. If you do not look after this you may end up with a locked device and will have to use a PUK code to unlock it. Some devices support entering a PIN code via AT-commands. You should check all the required settings via AT commands using the supplied picocom utility (see 2.4 above).



4. Analog modems and other RS232 devices
==============================================================================

4.0 The built-in RS232 port cannot be used for connecting serial devices as it is already being used for debugging and some models like the 91HD do not have it at all. It is possible to turn the receiver's USB port into a standard serial port using a USB-to-Serial converter (sold separately). These adapters are cheap and easy to find online. They are being sold under various names on eBay and other online stores dealing in PC components. The only requirement is that the converter MUST be Prolific PL2303 chipset based (NOT the FTDI chipset!). Thus, using such a device, ANY analog modem (even your ancient dial-up V.xx modem) can be used. Some mobile phones also have RS232 compatible outputs (a few older Siemens models are known to work this way) and can be used to establish GRPS connection.

4.1 Once you have connected your USB-to-Serial converter to the receiver's USB port, execute the following command in a Telnet session: dmesg

You should see output similar to the following:

pl2303: no version magic, tainting kernel.
drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
pl2303 2-1:1.0: pl2303 converter detected
usb 2-1: pl2303 converter now attached to ttyUSB0
usbcore: registered new driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver

If you see a message like "pl2303 converter now attached to ttyUSB0" it means that your converter has been successfully recognised and a new serial device has been created.

4.2 Check the newly created serial device ttyUSB0 using the following command: ls -ls /dev/ttyUSB*

crw-rw---- 1 root root 188, 0 Mar 18 12:29 /dev/ttyUSB0

4.3 The rest of the configuration is identical to the one described in steps 2.3 - 2.7 above. The difference will be that the serial device name is now not /dev/ttyACM0 but /dev/ttyUSB0 instead. Naturally, you have to adjust the chat-script and the PPPd peer file to suit your connection type.



5. PPPoE (PPP over Ethernet) using built-in LAN adapter
==============================================================================

5.0 There is no need to load any special drivers to enable PPPoE connection for your ISP. All the necessary components have already been installed in the PGI firmware and the existing configuration templates can be used with minimal changes.

5.1 Edit the template called /var/etc/ppp/peers/pppoe. Most likely you will only need to change the "name" parameter to match your PPPoE login name.

5.2 Put your PPPoE connection password into /var/etc/ppp/chap-secrets (just replace the "password" with your own one) in the supplied template.

5.3 Put the peer file name (the file described in 5.1) into pgi.conf, i.e. PPP="pppoe" and restart the receiver. The connection will be established automatically. For manual connection testing you can use the same procedures described in 2.6 above (replace "gprs" with "pppoe" in the pppd command)

5.4 To check for PPPoE concentrators in your LAN you can use a small utility called pppoe-discovery. This is for information only and does not affect any configuration. A sample output with detected access concentrator is shown below:

[PGI ~]$ pppoe-discovery
Access-Concentrator: teleprov009
--------------------------------------------------
AC-Ethernet-Address: 00:10:33:11:ea:26



6. Additional notes on PPP connections
==============================================================================

In this section there are several important notes about using PPP connections with PPPd. They should be studied carefully before you start any troubleshooting.

6.1 Default Route also known as the IP Gateway
Suppose you are connected to your receiver over its LAN interface called eth0, which obviously has its own IP settings. It doesn't matter how the settings were configured (statically or using DHCP), but one of those settings is called the default route, which can point to your Internet router or simply nowhere, depending on how your network is set up. When the PPP connection is established using PPPd, a new network interface called ppp0 is being created. That interface receives some IP configuration (normally, automatically from the ISP). If, during the PPP connection attempt, your system already has a default gateway (which is most likely when at least one network interface is already configured) then the new default gateway sent by your PPP connection provider will simply be ignored. This may lead to a situation where you have successfully connected the PPP interface with a correct IP configuration, but Internet access does not function. That happens because of all your requests are still trying to go over the "old" default route, and not the one proposed to you by your ISP. To avoid such problem, there exists a special script in PGI image, called /var/etc/ppp/ip-pre-up which runs just before the actual PPP interface is brought up (after the connection has already been established). This script does a few other things (see below) but what it also does is delete your current default route (it saves it into a file though). This makes it possible to set up a new default route as soon as you get its value from ISP automatically and the Internet connection will function OK. When the PPP connection is terminated another script called /var/etc/ppp/ip-down runs and automatically restores the previously saved default route. You can use these scripts for any other pre- and post-configuration associated with your PPP connections.

6.2 DNS settings
The situation with DNS settings is almost identical to the one described above in 6.1. Many ISPs send their own DNS settings during the connection phase and once the PPPd service receives them, it creates a file called /var/etc/ppp/resolv.conf with those new settings. The problem is that the file in this location has no effect on the actual system until it is placed directly into the /var directory. The PGI team took care of this in the already mentioned /var/etc/ppp/ip-pre-up and /var/etc/ppp/ip-down scripts, which will do all the dirty work for you. The scripts will copy the new DNS settings into the correct location and will restore the old settings once the PPP connection has been terminated. If your provider does NOT send the DNS settings, you may need to adjust these scripts to set the DNS settings statically or in some other way that fits your situation.

6.3 Working with iptables
Every time a PPP connection is established your receiver will most likely get an external IP on the Internet (also known as public IP). Most ISPs will not do anything special to protect your connection from the outside world, so in 99.9% cases you will end up with a connection that has an external IP address which is COMPLETELY OPEN TO THE OUTSIDE WORLD. The idea of just about anybody in this world being able to control your receiver and its files, as well as use it as a stop-over on the way to compromise the rest of your home network, most likely does not sound very appealing to you! To prevent such incidents and to protect your receiver from the outside world, the PGI team has included full iptables support in their image. In short, iptables can be used as the very effective Linux firewall, although do not expect a fancy GUI for its setup. If you really want to take full advantage of all iptables functionality you have to become a Linux networking specialist. Luckily, PGI provides a very simple, yet effective, set of iptables rules 'out of the box'. These rules are activated using the already mentioned /var/etc/ppp/ip-pre-up script. The rules will reject all INCOMING connections from the ppp0 interface, thus making your receiver invisible on the Internet. The outgoing connections will work OK. The rules are not meant to be final or the best ever - feel free to change them as you see fit.

The iptables abilities do not end here. If configured properly, iptables can be used to enable Internet connection sharing, where your receiver can act as a "router". You can use NAT or masquerading technologies, you can set various logging options or allow certain services through. Although the fine tuning of iptables may require in-depth knowledge and experience, you can find a lot of ready-made iptables rules on the Internet and modify them to suit your own requirements.


Good luck connecting!
PGI Team

+-------------------+
| PGI v1.3, Kumonga |
+-------------------+


THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. UNDER NO CIRCUMSTANCES WILL THE PGI SOFTWARE AUTHORS BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR EXEMPLARY DAMAGES, DATA LOSS OR HARDWARE MALFUNCTION, ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE UNDER NEGLIGENCE OR EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BY INSTALLING AND USING THE SOFTWARE YOU ACCEPT ALL THE TERMS AND CONDITIONS OF THIS AGREEMENT.


Table of Contents
===============================================================================

- Before You Install
- Change List for PGI 1.3
- Change List for PGI 1.2
- Change List for PGI 1.1
- Change List for PGI 1.0
- Colour Buttons Functions
- Notes on Multiboot
- Configuring PGI Settings Using OSD Menu
- Configuring PGI Settings Using pgi.conf



Before You Install
===============================================================================

If you are upgrading from PGI 0.7.3 or lower, you should be aware of some major differences between this version of the image and your current version, namely:

- This image contains newer Linux kernel, newer drivers as well as updated user interface
- The channel recordings from older images are NOT compatible with this image (but can be converted, see CONVERTER_en.txt)
- The plugins from older images are NOT compatible with this image and have to be updated to work correctly
- It is HIGHLY recommended to have swap space available to take full advantage of new EPG functions in PGI 1.x and to avoid performance problems (refer to HDD_en.txt)

This release (non-USB version) includes 2 image files:

usb_config.img => contains multiboot config ONLY (useful for multiboot restoring, see "Notes on Multiboot" below)
usb_kernel_root_db.img => contains main image WITHOUT multiboot config

If you are upgrading from PGI 0.8 or higher, it is enough to install usb_kernel_root_db.img only. You can do it very easily via receiver's OSD menu with the image on a USB stick or uploaded to /media or /tmp.

If you flash the usb_kernel_root_db.img, your existing multiboot config will NOT be touched. This is helpful when you want to preserve your multiboot and makes upgrades from earlier PGI or DGS version easier. However, if you had non-DGS based image in your flash memory (like e2) prior to installing PGI image, then the new image may not be bootable (permanent BOOTING message) or it may boot but your IP settings cannot be saved, etc. If this is the case with your installation, simply install usb_config.img from this archive in addition to usb_kernel_root_db.img (the order does not matter) and press and hold 0 button during power on until you see PGI-FLASH message on the front display.

ATTENTION: do not confuse MULTIBOOT config with UBOOT. They are not the same thing! Multiboot config comes as usb_config.img and contains a bunch of text (i.e., configuration commands), while Uboot is delivered as usb_uboot.img and contains the actual binary code (something like BIOS on a PC). Most boot related problems (especially when there were non-DGS images running on your receiver) can be solved by flashing a proper multiboot config. Uboot code, on the other hand, changes VERY rarely. There was some confusion about the Uboot supplied with PGI 0.8 which caused some receivers not to boot properly. If you are not sure which Uboot version you have, we recommend using the following one: http://goo.gl/4ksBp (select one that fits your model).



Change List for PGI 1.3
===============================================================================

- New: Recording 2 channels from the same transponder works now
- New: Current programme remaining/elapsed time can be displayed in minutes or as perecent in the channel list (new option in the PGI Settings menu)
- New: Programme description is shown in the channel list (1 column + 3 EPG events mode), this is optional and can be turned on or off via the PGI Settings menu
- New: Added DiSeqC 1.0/1.1 settings for motorised dishes used in so-called "cascaded" configurations: Motor + DiSeqC
- New: Last watched recording is remembered in the recordings list
- New: Added/removed and changed some HDD related options, please read HDD_en.txt (even if you have done so before)
* HDD_MEDIA, NFS_REC and NFS_REC_PROTO parameters in pgi.conf have been merged into a single parameter called MEDIA_DEVICE
* MEDIA_DEVICE can now be specified using partition's UUID as well as classic /dev/sdxX syntax
* Included mkdosfs utilities to format disk/USB flash partitions as FAT32
* All swap partitions on all available devices are now mounted automatically, i.e. swap does not need to be 1st partition on your disk
* Swap can be an ordinary file now (see new parameter called SWAP_FILE in HDD_en.txt)
- New: Added/removed and changed some USB 3G/UMTS modem related options (see NETWORK_en.txt)
* Removed USB_MODEM option from pgi.conf since USB_modeswitch now operates automatically
* PPPD_PEER parameter has been renamed to PPP; ATTENTION: PPP must be set to a valid value for USB_modeswitch to work (at boot)!
* Added picocom utility for testing and setting up your USB modems (see NETWORK_en.txt for usage example)
* Improved 3G modem config templates in /var/etc/ppp including "on-demand" connections (dial up only when required, autodisconnect when idle)
- Fix: Improvements for non-persistent epg.dat handling (when there is no USB/SATA storage used), less problems with channel list "freezing", etc.
- Fix: EPG database structure changes: stopping recordings should be faster now (all existing EPG data will need to be refreshed)
- Fix: Instant recording popup setting for shutdown/standby power option is working correctly now
- Fix: Recording names are displayed correctly now
- Fix: Editing recording name (instead of recorded channel name) is possible now
- Fix: WebTV was not working correctly when the second tuner was used
- Fix: DVB subtitles fixes and improvements (especially for Nordic channels)
- Fix: Timeline in EPG Grid moves properly now
- Update: OpenSSL, USB_modeswitch, Busybox, MC, Freetype, SQLite, Dropbear, e2fsprogs and Transponder DB updates
- Removed: "Weather Info" option is gone - the service is non-functional due to the expired subscription to the online service



Change List for PGI 1.2
===============================================================================

- Change: EPG database structure changes; after installing this image all existing EPG data will need to be refreshed
- Change: removed EPG 'Multi-TP' scanning flag from web interface; EPG for channels from other TPs is now read automatically
- New: left/right keys allow viewing the detailed EPG info in the epg list (press "EPG", then "i" on a program name and then left/right)
- Fix: power button "turn off with long press" behaviour is back to normal
- Fix: moving channels up and down in the Fav lists is working like it should
- Fix: corrected navigation in Fav list when one or more Fav groups have been deleted using PC-Editor
- Fix: EPG for DVB-T now shows program names properly
- Update: FreeType, mc, iptables, USB_modeswitch updated to the latest versions
- Downgrade: db.dat revision downgraded to R13329 to be compatible with the PC-Editor (purely a label, no data or db structure is affected!)



Change List for PGI 1.1
===============================================================================

- New: picons support (see new option in pgi.conf called PICONS below)
- New: allow the power popup when a recording is active, only shows the sleep timer when a recording is active, other options are not shown
- New: added "Default Power Control" option to PVR Settings which applies the selected value to the power control of all instant recordings and timers
- New: fast forward and rewind in the MP3 player; short press goes to next/previous track, longer press does FF/REW, speed increases if the button is held longer
- New: MP3 player can now play unlimited file size, file size was originally limited to the amount of free memory
- New: Hebrew language added
- Fix: CI modules crashes
- Fix: crash in the settings wizard on first boot
- Fix: initial wizard would run many times even after channel scan and reboot
- Fix: sometimes there would be no video/audio until channel change after stopping the timeshift
- Fix: DiSeqC settings are now reset when adding the next LNB in fixed Sat
- Fix: corrected multiboot for USB/sda options
- Fix: deleting last recording caused wrong OSD information
- Fix: crashes on shutdown while fetching EPG
- Fix: startup scripts corrections for boxes without CI modules
- Fix: changing audio tracks when watching recordings did not always work
- Fix: optimisations in EPG handling and related stability fixes
- Update: updated Web interface, SQLite and BusyBox libraries to the latest versions



Change List for PGI 1.0
===============================================================================

- New: EPG handling is completely rewritten, EPG is now stored in SQLite database (needs HDD/USB to persist, see Special Notes above)
- New: EPG from more non-standard providers is now supported (see /var/etc/epg/private_epg_info)
- New: improvements to background EPG scanning, new web interface for TP selection for EPG scan (see Special Notes above)
- New: new icon on the info banner that shows when EPG data is being received from TP (see Special Notes above)
- New: reworked simple channel list - more EPG info, next event, remaining time & TP info
- New: reworked favorite group handling - FAV name on top, each group starts with channel number 1, including radio channels
- New: same channel correctly recognised in multiple FAV groups when zapping with up/down
- New: improved AAC decoding
- New: aspect ratio setting is memorised per each channel (see /var/etc/ar.conf for more info on custom AR)
- New: added bookmarks and a screen saver to Shoutcast radio
- New: recording name is shown on VFD during playback
- New: allow LNB/TP editing and channel scanning when recording timers are present
- New: jump EPG list with left/right keys
- New: any script can be assigned to a colour button via standard web interface (see /var/www/cgi-bin/system/plugins/scripts_addon_user.conf)
- New: added binaries for DynDNS.org and no-ip.com dynamic DNS services (see /var/bin/init.d/start.dyndns)
- New: added scp and Midnight Commander to the image (run 'mc' or 'mc -s' from the Telnet session) including new visual editor: 'mcedit'
- New: more free space in /var directory (ATTENTION: DO NOT use /var for storing EPG database file!!!)
- New: changed multiboot config (see Notes on Multiboot below)
- New: improvements in M3U files parser, by default the file /var/www/list.m3u is used (can be edited by the user)
- Fix: channel scanning would stop before scanning all channels
- Fix: aspect ratio sometimes reset when using timeshift
- Fix: simultaneous recording and watching of 2 encrypted channels on the same TP (including PiP)
- Fix: playback of recordings which contain partially scrambled data does not break in the middle (skips to the next descrambled point)
- Fix: time above timeshift cursor shows timeshift time, not current time
- Fix: recording list caused crashes under various conditions and did not delete last recording
- Fix: attempt to fix TCP receive window too high for hanging bit-torrent client / FTP transfer
- Fix: non-ASCII characters are displayed correctly in mounted Windows shares
- Fix: fix for Cyrillic characters in the RSS reader that caused caused crashes with some RSS channels
- Fix: multiple PiP fixes
- Fix: multiple PVR fixes
- Fix: multiple subtitles fixes (known issues with FreeSat subtitles)
- Fix: countless number of general panics and crashes fixes
- Fix: DST offset fix for the Web interface
- Update: recording converter handles special chars better, general improvements to converter
- Update: updated most libraries and binaries (busybox, e2fsprogs, sqlite, USB_modeswitch, nano, dropbear and more)
- Change: USB devices accessed via /mnt/usb/sd... are now mounted without the "sync" option (see /var/etc/mount.sdx1 for more info)
- Removed: YouTube, Multiroom, Post-Descrambling



Colour Buttons Functions
===============================================================================

All buttons listed below can have their action changed on all receiver models using the web interface. Starting with PGI 1.0 the possible actions for buttons can be extended with user scripts (see /var/www/cgi-bin/system/plugins/scripts_addon_user.conf)

The inital buttons assignment is as follows:

Red button (on all models) => Change Aspect Ratio
Green button (on Cuberevo 250/200 only) => Script Panel Plugin
Yellow button (on Cuberevo 250/200 only) => Change Audio Track
WWW button (on models with WWW button) => Script Panel Plugin

NOTE: The script plugin calls scripts from /var/bin, so you can add your own scripts if you place them in that directory and start their names with with "scrplg-..."



Notes on Multiboot
===============================================================================

If you want to flash another multiboot after installing PGI, consider the following. In PGI's usb_config.img the multiboot configuration is as follows:

0 - boot PGI from internal flash memory
1 - boot PGI from external USB device sdb1 (when you have internal HDD as sda used for swap/media)
2 - boot PGI from external USB device sdb2 (when you have internal HDD as sda used for swap/media)
3 - boot PGI from internal SATA HDD device sda3 (when sda1/sda2 is used for swap/media)
4 - boot PGI from internal SATA HDD device sda4 (when sda1/sda2 is used for swap/media)
5 - boot PGI from internal SATA HDD device sda5 (when sda1/sda2 is used for swap/media)
6 - boot PGI from external USB device sda3 (when you do NOT have internal HDD and sda1/sda2 is swap/media)
7 - boot PGI from external USB device sda4 (when you do NOT have internal HDD and sda1/sda2 is swap/media)
8 - PGI boot pause (pauses boot sequence and provides network access to fix problems with db.dat or pgi.conf)
9 - PGI settings restore (see the BACKUP_DIR option in pgi.conf)

If you are not satisfied with this layout or if one or more of the buttons do not work the way you wish, it is much easier to simply change those buttons' actions than to flash the complete multiboot (and lose the new functionality for buttons 8 and 9). The multiboot options can be easily edited to your liking with the Telnet commands: fw_printenv and fw_setenv. For instance, if you flash some different multiboot config you may want to restore the functionality for buttons 8 and 9.

The /boot directory of the PGI image contains a reference copy of the multiboot config supplied with the image (usb_config.img) as well as the actual commands that you can use to restore certain buttons' actions (multi_conf.txt)



Configuring PGI Settings Using OSD Menu
===============================================================================

Some PGI-only settings are available in the main OSD menus "Settings" -> "PGI Settings" and "Front Panel".

EPG BACKGROUND SCANNING + EPG SCAN TIME
Controls background scanning for fresh EPG data. If this feature is enabled, certain transponders will be automatically scanned for new EPG data every 24 hours (at a specified time). If your receiver has two tuners that are able to receive the same satellites, then the scanning process is completely transparent as the second tuner will be used for EPG scanning. If your box has only one tuner or if the second tuner is not able to receive the same satellite then the scanning will be done only if the receiver is in Standby mode (i.e., partially on). ATTENTION: Do not confuse background scanning with processing usual EPG data while watching live channel. Even if background scanning is turned off, the EPG will be received and stored from the transponders which are used for watching live channels.
You can select which transponders should be scanned in the background mode by using the web interface (EPG section -> "EPG Scanning Settings"). If you do NOT select any TPs for BG scanning (default state) AND you enable EPG background scanning AND you have some FAV lists in your database, then the receiver will go through each and every transponder in all of your favourites (at a specified time) and will try to get EPG from all of them. Sometimes this may be overwhelming, so it is better to pick the necessary TPs in the web interface.

ZAP TO RECORD
This option is only of interest to you if you card cannot decrypt more than one channel at the same time. If you turn this option on, the receiver will not allow watching/recording/PiP for more than one encrypted channel at the same time. In addition, it will try to zap to the channel before recording in even if the live channel was on the same transponder to avoid decoding wrong channel.

POWER OFF ACTION
Sets action required to power off the receiver with the power button. The "Hold" setting means that you have to keep the power button pressed for a couple of seconds to power off the receiver. If you short press it in the "Hold" mode then the Sleep Timer menu will be called. The "Press" setting reverses the behaviour.

SHOW DEVICE BANNER
Show or hide the OSD banner which displays the connected and disconnected, CAM module and USB devices. The "Skip 1st" value will disable the banner only the first time it is called. "Always" will show the banner every time and "Never" will prevent it from ever showing up. This option is useful to get rid of the banner showing every time you start the receiver if you have CI device or USB storage device connected.

FAST SUBFEED SWITCHING
This function is only useful for those who use sub-channel feature (do not confuse with PiP!) Normally, every time you change the sub-channel the whole TP get scanned for new sub-channels. If you are sure that you already have all of the required sub-channels scanned before then you can speed up sub-channel switching process by enabling this option which will skip TP re-scanning.

INITIAL EPG LAYOUT
Allows to choose whether the single-channel or multi-channel EPG view is opened first when pressing the EPG button. The default setting is to open the multi-channel EPG view first.

CHANNEL LIST PROGRAMME TIME
Allows to select whether to display the current programme time as "remaining time in minutes" or "elapsed time in percent" in the channel list (affects only the current programme info).

EXTRA VIDEO LAYER
Allows to choose between having simultaneous video output via HDMI and SCART (CVBS mode only!) or having better image quality for PiP.

DISPLAY BRIGHTNESS
Sets the front panel display brightness (for those models that support this function). The higher the value the brighter is the display.

ALL CAPS FOR CHANNEL NAMES
Allows to automatically convert channel names to use capital letters only for the front panel display.



Configuring Settings Using /var/etc/pgi.conf
===============================================================================

The system services specific configuration is located in /var/etc/pgi.conf. All lines starting with # are treated as comments. The lines like OPTION="VALUE" set various parameters. The file can be modified either by any text editor that saves files in a plain text format. PGI image has 3 such editors already built in: vi, nano and mc-edit. All of them can be used within Telnet session. Alternatively, you can use some special Telnet commands to quickly modify single parameter.

The following commands can help modifying pgi.conf easily:

conflist (simply displays current settings)
confget (displays the value of certain option only)
confset (sets new value for the given option)

The option names are NOT case sensitive, however, their values usually ARE, so do pay attention!

Here are some examples:

conflist
confget BACKUP_DIR
confset webtv yes

The options are read from pgi.conf only once during the boot sequence, so if you want to commit your changes, you need to reboot the receiver. Below is a detailed description of some of the parameters that can be set in pgi.conf. Some more (storage device related) parameters can be found in HDD_en.txt. Do not be put off by the large number of options! The receiver will work fine with most of them untouched. They only need to be changed if you require some additional functionality or modified behaviour.


BACKUP_DIR
Sets the directory name for backing up and restoring all user settings (normally, on the internal HDD or on the external device). It is very convenient to backup all the settings before flashing a new image and then to restore in one quick operation. The backup and restore functions must be invoked manually using the script plugin, which is available in PGI via the WWW button on the remote (or 91HD, where this plugin can be called via the plugins menu).
Default value: "/media/pgi-backup" (for backing up to the same device which is used for channels recording)
Example: BACKUP_DIR="/mnt/usb/sda2/backup" (for using the directory called "backup" on a USB stick)

CI_INIT
Enable or disable support for CI modules. To load less drivers set to "no".
Possible values: "yes", "no"
Default value: "yes"
Example: CI_INIT="no"

CRON
Enable or disable cron service which allows certain repeating tasks (like user scripts) to be to run at a certain time, for example, every day or every hour, etc. The service uses a configuration file that can be modified using a Telnet command: "crontab -e" which uses the syntax described here: http://en.wikipedia.org/wiki/Cron#crontab_syntax
Possible values: "yes", "no"
Default value: "no"
Example: CRON="yes"

DEBUG
Should only be used to troubleshoot problems and should never be permanently enabled. With this option set to "yes", the boot sequence logs will be written into the /var/log directory and the receiver will not automatically reboot or shutdown in case of major problem.
Possible values: "yes", "no"
Default value: "no"
Example: DEBUG="yes"

EPG_DATA_DIR
Sets the directory name for storing persistent EPG data. By default it is set to "/media" which implies that you MUST have storage device connected and configured for PVR functions (channel recording, timeshift, etc.). If you do not want to use PVR and simply want to have EPG data stored on a USB stick, you can change this value (see example below). Be aware that if you use USB stick for EPG storage, you should NOT disconnect it before the receiver is fully shutdown to prevent data corruption.
ATTENTION: You should never use /var for EPG data storage! If you change the default value, you have to make sure that the specified directory already exists as it will not be created automatically.
Default value: "/media"
Example: EPG_DATA_DIR="/mnt/usb/sda1" (using a USB stick, without internal HDD)

ETH_ADDR_LOW
If the receiver is not cleanly shut down, the MAC address of your box may change. This option tries to solve that problem. If you set option to "auto", then the current MAC address (as reported by ifconfig) will be set for the next boot. If you want a custom MAC address, you can hard code it with this option. It is only possible to choose the last three blocks of the MAC address. The first three blocks are fixed and will always be "00:13:18". If you do not want your MAC address to be touched, set this option to "none".
Possible values: "auto", "none" or user defined address
Default value: "none"
Example: ETH_ADDR_LOW="ab:cd:ef" (the final MAC will be: 00:13:18:ab:cd:ef)

MEDIA_CLEAN
Enables or disables automated cleanup of your temporary media files. The cleanup job runs every 3 hours and removes all tmp directories in the /media directory which are older than the number of MINUTES specified here. If this parameter is set to a value other than 0 or "no", then the cron daemon will be started, whether you have enabled it or not. The recommended value for MEDIA_CLEAN is several hours (240 minutes or more), but the actual value will depend on the size of your HDD, how much TV you watch and whether you want to be able to "convert" some of the older timeshift files into actual recordings (there is a web interface option for that). Do not confuse the interval between cleaning attempts (which is fixed to 3 hours) and the "age" of files to be removed (set by MEDIA_CLEAN).
Possible values: "no" or some positive numeric value (in minutes)
Default value: "no"
Example: MEDIA_CLEAN="240"

NFSD
Enables or disables NFS services on the IPBox. This is ONLY required if you want to access the files which are located on the IPBox from another device using NFS protocol. This option is NOT needed for NFS recording (see below).
Possible values: "yes", "no"
Default value: "no"
Example: NFSD="yes"

NTP_SYNC
Enables or disables time synchronisation with an NTP server. The synchronisation will be performed only ONCE during receiver power up.
Possible values: "no", name or IP address of an NTP server
Default value: "no"
Example: NTP_SYNC="ntp2.fau.de"

PICONS
Sets the path containing e2 compatible picons. Cuberevo software requires the PNG files to be 24bit with transparency (alpha) channel. 8bit PNG files WILL NOT WORK! Picon file names must be in the following format: 1_0_STYPE_SID_TSID_ONID_SATPOS0000_0_0_0.png
Default value: "/var/picons"
Example: PICONS="/media/picons"

PPP
Set the name for the USB modem configuration file to be used by the pppd service. This parameter is required to enable USB 3G/UMTS/CDMA/PPPoE connection automatically during startup. The file specified by this option must exist in /var/etc/ppp/peers directory.
For more information refer to a separate NETWORK_en.txt document
Possible values: "none" or custom name
Default value: "none"
Example: PPP="3g-on-demand"

SAMBA
Enable or disable the Samba service. This is ONLY required if you want to access the files which are located on the IPBox from another device using Windows File Sharing (SMB) protocol.
Possible values: "yes", "no"
Default value: "no"
Example: SAMBA="yes"

SKIN
Sets an alternative skin. The value should be the FULL ABSOLUTE PATH of the directory containing the skin (often in /var/skins) directory. The name is CASE-SENSITIVE!!! You can put your skins into the /var directory or to the HDD (/media directory).
Default value: "default" (built-in skin)
Example (for a skin in /var): SKIN="/var/skins/MySkinName"
Example (for a skin on HDD): SKIN="/media/skins/MySkinName"
Example (for a skin on USB Flash): SKIN="/mnt/usb/sda2/MySkinName"

WEBTV
Enables or disables PERMANENT Web-TV / VLC streaming. Normally only required when you do NOT use IPBox web interface for watching Web-TV (for instance, when watching directly with VLC player). The web interface should automatically start streaming when required
Possible values: "yes", "no"
Default value: "no"
Example: WEBTV="yes"


Have fun,
PGI Team

**** READ THIS README BEFORE FLASHING THE NEW IMAGE *****

THIS SOFTWARE AND README IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. UNDER NO CIRCUMSTANCES WILL THE RECCONV SOFTWARE AUTHOR BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR EXEMPLARY DAMAGES, DATA LOSS OR HARDWARE MALFUNCTION, ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE UNDER NEGLIGENCE OR EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BY INSTALLING AND USING THE SOFTWARE YOU ACCEPT ALL THE TERMS AND CONDITIONS OF THIS AGREEMENT.

README for converting old format movies to new format movies.

Whenever the readme speaks of old (format) recordings, this means: Recordings made with PGI 0.7.2a or before (or any DGS R12413 and before)
Whenever the readme speaks of new (format) recordings, this means: Recordings made with PGI 0.8 or later (or any DGS R13078 and later untill they change the format again)

This readme describes the converter that gives the option to convert old recordings to the new format.

Recconv 1.0 Final
=================
This will be the last version of the recording converter, as after a couple of months with the newer images everyone should have converted their recordings, either
with 0.8, 0.8.1 or with 1.0. The s/w changes everytime and it is a lot of work to keep a one time tool up to date (this is for example the reason the converter failed in 0.9).
Except the improvements below, nothing changed in the way to use it, so see below.

Improvements
============
- Now handles special characters correctly
- The restarting of the conversion has been improved, the broken off conversions will be deleted prior to converting them again
- recconv will now be daemonized after starting and answering the questions. Wait till recconv says: You can now close this telnet session. You can turn off you pc as well after doing this
- Converted recordings will be appended with _c in the file name so you can recognize them easily. Recordings that were converted succesfully with the older versions of recconv will not be converted again.

Extra remarks:
==============
- After booting PGI 1.0 wait at least 5 minutes before starting the conversion
- READ THE REST OF THE README!!!


Prerequisites:
--------------
Before Flashing the new image:
If you use post descrambling, turn it off and make sure all old recordings are descrambled before flashing the image. Scrambled recordings cannot be converted.
If you have timeshift on, turn it off, just to be safe.
If you have any timers set, delete those timers as they might boot up the box while converting the recording.
As converting is at realtime speed, you might want to consider deleting unneeded recordings prior to flashing.

You can now safely flash the image.

After flashing the image, do not open the mediafile list prior to running the converter, or before manually deleting the /media/filelist.meta file. If you open the mediafile list before doing this, the box will panic and might corrupt your db.dat

Features/remarks
----------------
The converter converts the old recordings at about the same speed as that a post descrambling, so the best time to run it will be at times when noone is using the box.

All previous bookmarks, skips and repeats are lost during conversion. This is due to the new file formats and it isn't possible to easily convert the bookmarks etc.

The converter will show its progress on the VFD on at least the 9000 and CubeRevo models, the VFD option is not tested on other boxes, so it might just as well show garbage, but at least it will change every second.

The VFD will show the following:
| 1/10 20%
The first character (in this case | )will make a step every 1 seconds this way you can see that the application is still running. Next you will see the recording being converted as in "1 of 10". As the last info you get an indication of how far the conversion is for this specific recording. This is just an indication, not exact.

To prevent overheating of the box, the fan will be turned on during conversion, keep this in mind when choosing the time at which you want to convert (for example if the box is in the bedroom).

The converter can be restarted after a reboot and will skip already converted recordings, please see conversion step 9

The box MUST be rebooted after conversion, even after breaking off a conversions.

During the converion, a log file is generated: /media/converter.log This log shows what is happening and if any failures occured if a failure occurs, the old format recording won't be deleted.

Requirements:
-------------
- a network connection and a pc with putty or another telnet client. Do NOT use web interface to execute Telnet commands!
- Diskspace should be at least 1.5 times the size of your longest recording. If you plan to keep the old format recordings, make sure you have at least 52% of free diskspace (see Conversion step 4).
- If you have enough diskspace, keep the old format recordings and delete them manually after checking the converted recording.

Conversion steps:
-----------------
Steps to convert the recordings (all after flashing the new image):
1) the box needs to be in stand by mode (WARM OFF), to get it there, press the power button on the remote briefly so that you get the powerdown menu (you might need to enable the menu if you have disabled it in the PGI settings). Choose the option Standby (the bottom one).

*** If the box isn't in standby mode, the conversion will fail!
If you have forgotten, the converter will automatically switch the box into standby mode before step 8.

2) The box will go into standby mode now.
3) telnet to your box
4) Check your free diskspace by typing:
'df'
and look for the line containing /dev/sda2
You need at least 1.5 times the free disk space as your longest recording. A value of 20 GB would suffice in most cases. If you plan to keep the old format recordings, you need at least 52% free disk space. The converter application doesn't check the available diskspace, so your are on yourself here, running out of diskspace during conversion will cause problems that looses the specific recording it is converting.
5) start the converter by typing:
'recconv'
(without the quotes and press enter)
6) The application will now ask you whether or not to keep the old format recordings, type either Y or N. Best would be to keep them after converting them, unless you plan to switch back to a previous (0.7.2a and before) version of PGI. Besides that, if conversion fails and isn't handled correctly, you can always rerun it
7) If you selected N at step 6, the converter will ask you to type the word 'delete' (without quotes) to make sure that you really want to delete them. Anything else then 'delete' will exit the converter.
The conversion will now start.
The box will automatically switch to warm off, then after 5 seconds the conversion will start (in case you wonder if anything happens, there is a 5 second delay before starting the conversion).
During conversion you can see the progress on the VFD.
9) If you want to break off the conversion (for example in the morning and the conversion isn't finished yet). Make a second telnet connection to your box and run 'stopconvert.sh' without the quotes.
The box will reboot now. The conversion can be restarted by starting at step 1 again any previous converted recordings will be skipped.
10) When the conversion is finished, the VFD will show Finished
11) When finished, the box will reboot itself automatically.

The conversion is now finished, after the reboot, your recordings will show up in the mediafile list (might be that they don't show up at opening the list the first time, but they will when closing the list and reopening it after a few minutes, populating the list is done in the background and might not have finished yet when you open it the first time).

If you have any questions (even before converting), please post them at denktenk.com


Manually deleting the old format recordings:
--------------------------------------------

If you decided to keep the old recordings and want to remove them after checking the converted recordings, you can do the following
telnet to your box
File by file:

WARNING: take a good look at the file name, old recording directory starts with ~ this is no typo!!! forgetting it will delete the new recording without a possibility to recover!!!!

cd /media
rm -r ~recordingname
rm recordingname.ifo
rm recordingname.dgsifo
rm recordingname.extinfo

You can also use the above to create diskspace

If you feel daring and want to to them all at the same time:

WARNING: take a good look at the commands below, the ~ is not a typo, leaving this one out erases you entire harddisk!!!!

cd /media
rm -r ~*
rm *.ifo
rm *.dgsifo
rm *.extinfo

Reconverting an already converted recording:
--------------------------------------------
If you find a recording that hasn't converted correctly (for example filesize is 0) you can do the following:
cd /media
rm -r name_of_recording

WARNING: the name_of_recording is the new one, don't delete ~name_of_recording as that is the old format version!!! The difference is the ~ this is not a typo.

Hard Disks, Flash Media, Formatting and Swap Space
===============================================================================

0.0 Storage device initialisation in PGI differs from other software images. The differences DO NOT AFFECT the devices in a standard configuration which is the following: ONE storage device (external USB or internal SATA) which has already been formatted by one of the DGS based images and was used for making the recordings before. If your configuration differs from the described or you are having troubles connecting some new device or you have custom partitions layout (for multiboot, skins or EPG storage only on USB sticks, etc.), then you should take your time and read the notes below.

0.1 PGI WILL NEVER FORMAT YOUR DISKS OR FLASH MEDIA BY ITSELF. Which means that if you want to connect new storage device like USB Flash or new SATA disk that has never been used before by the receiver, they will NOT be formatted and recognised automatically. This decision was deliberate and the main reason behind it was that while automated formatting may make life easier for some people, it may destroy valuable data for others who wish to use their connected devices for more than just pure PVR functionality. Since the software cannot magically guess what you intend to do with your storage device, you will have to choose device formatting option by hand when desired. Luckily, with PGI that procedure is quite straightforward.

0.2 In contrast with other images, the OSD menu called "HDD Settings" ALWAYS stays active. Therefore, if you want to format newly installed (or even an existing) device, you can do it at any time from that menu. Please pay attention to the message that is displayed once you choose the formatting option. The message will display the actual information about the device that will be formatted. If that device is not what you expect it to be, read the next paragraph.

0.3 What exactly will be formatted? This question may seem strange at first but only to those who have only one storage device connected. If you have more than one device connected (like SATA and USB together), then you have to be sure you are formatting the right disk. As a general rule, the disk which contains your /MEDIA partition will be formatted. Note that the whole disk with ALL(!) of its partitions be erased, not just the /media partition, so if you have non-standard disk layout with multiple partitions (used for multiboot, etc) you should never format your disk using receiver's OSD menu. In detail, the following occurs during format: first, ALL PARTITIONS will be deleted from the device that contains your /media partition and 2 new partitions will be created after that. The first partition (for example, /dev/sda1) will always be 256MB in size and will be used as a swap space (equivalent of the Windows' page file). The second partition (for example, /dev/sda2) will take the rest of the available disk space and will be used for the /media partition (i.e., PVR functions such as timeshift and channel recording). By default the ext3 file system will be used to format the /media partition. If you prefer ext2 instead, you can set the HDD_FS parameter in pgi.conf accordingly (see HDD_FS description below as well as the next paragraph)

0.4 Which file system is better: ext2 or ext3? The answer will be "it depends". ext2 performs slightly faster than ext3 which may become a crucial point for some devices with slower write speed. At the same time, ext3 handles errors much better since it is a journaling file system (and that makes it slightly slower). You have to try it for yourself. If your setup can handle ext3 it is better to stick with it rather than with ext2. If the write speed is not enough you will get "freezes" and "hiccupping" during timeshift and recording, especially with the high bitrate HD channels. For most SATA devices ext3 is fine.

0.5 Can I use another file system (not ext2 and not ext3) on my storage device? The short answer is no, not for recording. The longer answer is that you can only use ext2 or ext3 for recording but PGI images also understand FAT and NTFS file systems in the "read-only" mode, i.e. you can play media from USB flash formatted as FAT or connect your NTFS formatted HDD with the media files to view them but you will not be able to use devices with such format for channel recording. Why ext2 or ext3? Because they are native Linux file systems and are optimised for speed and error handling. For this very reason you cannot read the disks that you use for recording with Windows, if you decide to connect them to a PC later. There is some third-party Windows software available (some free and some not) to be able to read Linux file system like ext2 or ext3 under Windows. Why IPBox does not use more advanced Linux file systems such as ext4 or xfs? Because they require too much resources than what's available on IPBox and will be very slow or will not work at all.

0.6 If you have more than one storage device connected or you wish to use some non-standard disk layout with multiple partitions, you can select which partition should be used for /media via the MEDIA_DEVICE setting in pgi.conf. To make proper use of MEDIA_DEVICE setting it is mportant to determine the names of your storage devices. If you have only ONE device connected (does not matter if it's a SATA or a USB device) then that device will be named /dev/sda (and the partitions on it will be named /dev/sda1, /dev/sda2, etc.) If you have more than one storage device connected, SATA device will always have higher priority in terms of naming and usually will be called /dev/sda while any additional external USB disks will be then named /dev/sdb, /dev/sdc and so on. Finally, if you have several external USB devices connected at the same time, the order of their naming could change unpredictably from one boot to another (depending on how fast they reset during boot). In such (rare) situations you can use device's UUID (unique identifier) to specify the required partition for /media. To obtain UUID for all your existing EXT2/EXT3/FAT partitions you can execute "blkid" command in the Telnet session (also explained below in the MEDIA_DEVICE description).

0.7 PGI 1.x software uses most of the receiver's free RAM, especially when working with lots of EPG data. Therefore, it is highly recommended to have swap space enabled for the image to work properly. PGI will automatically detect all of the swap partitions that you may have and will make use of them without any additional configuration. For example, if you have internal HDD or external USB storage attached and formatted using receiver's OSD menu "Format HDD", then the swap space will be allocated as the 1st partition on the disk (and 2nd partition will be used as /media). If you have custom disk layout, you can allocate ANY partition for your swap space (you need to run mkswap command on that partition to mark it as swap) and it will be automatically detected and mounted during boot without changing any settings, no matter which partition it is going to be. Additionally, PGI image allows to use any ordinary file as a swap space. This means that if you want to have custom disk layout, you do not necessarily need to make a dedicated swap partition but can use an empty file on any other partition instead. If you decide to go ahead with a file as your swap space, you need to specify its full path in the SWAP_FILE parameter in pgi.conf (see its description below). WARNING: NEVER EVER use receiver's flash memory for swap, i.e. never assign files in /var directory for such purpose! It is also not recommended to use /media partition to hold your swap file because HDD health check that runs once in a while during boot may fail due to the fact that /media needs to be unmounted before checking (which means swap file cannot be used, which means you may run out of memory if the /media partition is too large in size).

0.8 If your receiver does not have ANY storage device attached internally or externally (usually the case with Cuberevo Mini/250/200 models), it is highly recommended to connect any USB stick (the faster speed, the better) and use it as a swap device. As an added bonus you will have possibility to store things like persistent EPG data, skins and picons on the same device. The USB stick does not need to be huge size if you are not planning to use it for channel recording; even 1GB stick would be more than enough to hold your swap space, EPG data, picons and skins. There are two possibilites with regards to how format such USB stick. One is to format it using receiver's "HDD Setup" menu, just like you would do it with a hard disk for PVR functions. In this case you will not need to change any default parameters in pgi.conf as both your swap and your /media partitions will be now on your USB stick (just don't forget to disable the Timeshift in the PVR options as soon as you have formatted the stick!) Alternatively, you can use ordinary FAT32 formatted USB stick with 1 partition on it, without reformatting it. In this case you need to change the following pgi.conf settings: SWAP_FILE, EPG_DATA_DIR and, if required, PICONS, SKIN and BACKUP_DIR to point to "/mnt/usb/sda1/...". The preferred way is the first one, because Linux native EXT3 file system will perform better than FAT32 in most scenarios.

0.9 To see the list of all partitions and/or files which mounted as swap you can use the following Telnet command: "cat /proc/swaps", to check the swap space usage you can use the following Telnet command: "free" (commands need to be typed it without quote marks). The "free" command shows more than just swap usage information, but you are only interested in the last line of the output that starts with "Swap:". It should contain three numbers. The first one is the total amount of swap memory (should be greater than 0 if swap is enabled) the second number is the amount of swap memory used at the moment (ideally it should be as low as possible), the last number is the amount of free swap space.



My Disk IS Not Being Recognised!
===============================================================================

1.0 You can always see some information about why your /media partition is not being recognised. The information is available in the "HDD Info" OSD menu and you should always start any troubleshooting from that screen. Most of the times it will be immediately apparent what went wrong just from the status message in that screen. If that information is not enough then you can enable debugging in pgi.conf (DEBUG="yes") and check the /var/log/hdd.log file after the reboot for most detailed information. Below you will find the description of most common errors and messages that you can see in the "HDD Information" menu.

1.1 Very often people think that their HDD has not been recognised, while actually it is simply being checked for errors during startup. The error checking may take a long time if you have many files (or many errors) on your disk and during this time the HDD will be "unavailable". You can see the disk checking progress in the "HDD Information" menu. The procedure of disk checking has 5 stages (and EACH stage goes from 0 to 100%). The disk checking can be enabled and disabled via the "HDD Settings" menu. It is a very good idea to check your disk once in a while to avoid data loss or corruption which could come from an unexpected reboot or panic. Generally speaking, the error checking is performed MUCH faster on ext3 file systems.

1.2 If you see the error that says "/dev/sda2 cannot be detected and no NFS is set" it means that the receiver cannot actually detect ANY storage devices connected to it (and you are not using NFS recording). There are 2 most common reasons for this:

1.2.1 If you get this message after you have installed new SATA disk, then chances are that the actual hardware is simply incompatible. Some people had success when they switched the HDDs from SATA 2 into SATA 1 mode by using a special jumper on their HDD.

1.2.2 If you get this message while using a USB HDD, the reason for the failure could be that it takes longer for the HDD to "spin up" after the cold start and the receiver checks for this device "too early". To overcome this problem you can force device detection (the device timeout will be longer) by setting HDD_USB_DETECT parameter in pgi.conf as follows: HDD_USB_DETECT="force" (see detailed description of this parameter below). If the device cannot be initialised even with such option, then you will see an error "/dev/sda detection timeout" in the "HDD Information" menu. In such case the only thing left to do would be to try another USB HDD model or provide external power to your USB disk if you have not done so.

1.3 If the error message says "/dev/sda2 does not exist", it means that your HDD *is* being detected, but is not partitioned the way IPBox expects it, i.e., second partition, is normally expected to be used for PVR tasks and it does not exist. There are two possible situations that may cause the error:

1.3.1 You device has never been used before for PVR functionality so it does not have correct partition layout. If you DO want to use this device for recording or timehift, you should simply reformat it using standard OSD menu option (see the beginning of this document).

1.3.2 You have a single USB device connected but do NOT wish to use it for PVR functions. Receiver would normally assume that the first detected device (sda) should be used for recording and will try to detect 2nd partition which is normally used for such purpose. Since in "receiver's opinion" your device is not partitioned the "right way" for PVR, you will get an error. In such case it is recommended to set the HDD_USB_DETECT parameter in pgi.conf as follows: HDD_USB_DETECT="no". This will prevent your receiver from trying to use your device for PVR functions.

1.4 If the error message says "/dev/sda2 has FAT file system" (or "NTFS file system" or "unknown system") that means that the device *is* detected, *has* the second partition, but the partition is not formatted using ext2 or ext3 file system. In such a case you need to format the device (see the beginning of this document).

1.5 If the error message says "/dev/sda2 cannot be mounted" that means that the device has correct format but due to some inconsistency or data corruption cannot be mounted. In such case it is best to attempt to run disk error checking by selecting this option from the "HDD Settings" menu and rebooting (you can watch the progress as described in 1.1 above). If that does not help, then reformat may be the only option.

1.6 The error "Cannot create tv/radio/multi dir" means that the device has been mounted, but no data can be written to it. Most often this happens with incorrectly set up NFS share used for recording when the /media device is mounted in a read only mode.

1.7 If the error message has something like "fdisk failed" or "mkfs failed" or "mkswap failed", that means that the HDD format was attempted but failed. You can try formatting one more time and if that still fails then it is worth checking the full log file as described in 1.0 above.

1.8 If the error is "NFS attempted but failed", then the connection to NFS recording share was attempted but failed. It is best to try to manually mount the same share from the Telnet session to see why it is not working. You should also check the correctness of your NFS path in MEDIA_DEVICE parameter (note that the colon sign is used twice for NFS paths).



Storage Device Related Parameters for pgi.conf
===============================================================================

In addition to the parameters listed in the REAMDE_en.txt file, there are some more HDD related options that can be set if required. It is best to only use them when you fully understand what you are about to do. As always, if the changes to these parameters cause non-booting receiver or data loss, it is your own problem.

HDD_AWAKE
By default, the shutdown sequence will try to spin down HDD shortly before shutting down power. If this feature is problematic for your configuration (some externally powered USB disks do not wake up until their power is reset), you can disable it by setting this parameter to "yes" in which case no command to spin down HDD will be sent.
Possible values: "yes", "no"
Default value: "no"
Example: HDD_AWAKE="yes"

HDD_FS
The name of the file system to use for /media partition formatting. Setting this option WILL NOT re-format the existing system and will not magically convert from one file system to another. You will have to manually invoke format from the OSD menu to change the file system (and lose all your data with it)! If this option is not set, "ext3" will be used the next time you format the storage device.
Possible values: "ext2", "ext3"
Default value: "ext3"
Example: HDD_FS="ext2"

HDD_SLEEP
The time in MINUTES after which the HDD should start sleeping, if inactive for that amount of time. "Inactive" means: there is no channel recording going on, timeshift is off and no EPG data, skins or picons is being accessed at the moment.
Possible values: 0 (no sleeping), 1 .. 20 and then 30, 60, 90, 120... etc.
Default value: "10"
Example: HDD_SLEEP="3"

HDD_USB_DETECT
Helps to solve problems with USB HDD detection in certain configurations. Normally receiver tries to autodetect external USB storage device automatically but sometimes autodetection does not work as expected. If your USB HDD does not get recognised at all during boot sequence you can try to set this parameter to "force" to enable alternative detection procedure. Also, if you have only 1 storage device permanently connected to your receiver but do NOT want to use it for PVR functions set this parameter to "no" to avoid false alarms related to "incorrect disk partitioning". However, for most configurations the "auto" setting works just fine. If you have problems recognising SATA drives, this is NOT the parameter that is going help and you should leave it at "auto" (see 1.2.1 above).
Possible values: "auto", "force", "no"
Default value: "auto"
Example (for problematic USB HDD that does not get detected nicely): HDD_USB_DETECT="force"
Example (if the *only* device is USB storage device and is *not* being used for PVR functions): HDD_USB_DETECT="no"

SWAP_FILE
Allows to specify a file that should be used as a swap space. The file MUST already exist (will not be created automatically) and it MUST be marked as a swap space. Both actions (creating an empty file of required size and marking it as swap) can be done using Telnet commands. For instance, the following commands will create 128 MB empty file in /mnt/usb/sda3 called pgi.swap and then it will be marked as swap space:
mkfile 128m /mnt/usb/sda3/pgi.swap
mkswap /mnt/usb/sda3/pgi.swap
Afterwards this file name can be specified as SWAP_FILE and it will be used IN ADDITION to all autodetected swap partitions on all connected disks. See 0.7-0.9 above for more information on swap space.
Default value: "none" (i.e. no special file used for swap, only the autotedected real swap partitions will be used)
Example (swap file on one of the partitions of an internal SATA disk): SWAP_FILE="/mnt/usb/sda3/pgi.swap"
Example (swap file on an external USB stick): SWAP_FILE="/mnt/usb/sdb1/myswap.tmp"

MEDIA_DEVICE
Allows to specify partition on SATA/USB device or NFS share which will be used as the /media folder (i.e. PVR functions such as channel recording and timeshift).
There are TWO possible ways to specify the SATA/USB device: using /dev/sdxX syntax and using device's UUID (see examples below). To see device UUID you can use 'blkid' command in the Telnet session.
There are TWO possible ways to specify an NFS share: when your NFS server uses UDP the path should start with nfs:// and when the server uses TCP the path should start with nfs-tcp:// (see the examples below).
A tip: you do NOT need to set NFSD="yes" in pgi.cong for NFS recording to work!
Default value: "/dev/sda2"
Example (SATA or USB storage device): HDD_MEDIA="/dev/sda3"
Example (SATA/USB storage device UUID): HDD_MEDIA="b7dfba7e-0e6b-4066-8906-d344e5a43912"
Example (NFS share using UDP protocol): HDD_MEDIA="nfs://192.168.1.2:/myshare"
Example (NFS share using TCP protocol): HDD_MEDIA="nfs-tcp://192.168.1.3:/myshare"

WARNING! If you change the default MEDIA_DEVICE setting and then format your HDD via the standard "HDD Setup -> HDD Format" menu, you have to remember 2 things:
1) Not only /media partition will be formatted, but the complete disk which contains media partition will be erased with ALL of its partitions!
2) The layout of such formatted disk will always be standard: 1st partition will be used for swap space, 2nd for media.
If you require different layout, never format your disk using the "HDD Setup -> HDD Format" menu and do it manually instead.


Enjoy your recordings,
PGI Team