E2 on HDD instructions

How to install Enigma2 to boot from the internal SATA harddisk:

1. Startup with original firmware

2. Informative:
     The box partitions a harddisk as follows:
         /dev/sda1    FAT12 ( 1)      (1 GB)
         /dev/sda2    Linux (83)      (Remaining space)

         The /dev/sda2 is then mounted under /media

   Since /dev/sda1 is not used in any way, we will be using this
   partition to store the Enigma2 image to it.

   It is probably a good idea to check if /dev/sda1 is not used,
   and to check if the partition is what we expect:
   Using Telnet:
    -sh-3.00# df                         (displays the active filesystems)
    -sh-3.00# fdisk -l /dev/sda          (displays the partitions on /dev/sda)

   Now the actual formatting:
    -sh-3.00# mkfs.ext2 /dev/sda1        (format the partition)

3. Mount the first partition.
   Using Telnet:
     -sh-3.00# mkdir /mnt/part1               (create a subdirectory)
     -sh-3.00# mount /dev/sda1 /mnt/part1     (mount the first partition under
                                               the just created subdirectory)

4. Copy 'enigma2_cuberevo.tar.gz' (or the file of interest) to the harddisk.
   We don't do this on the first partition (size is limited to 1GB), but
   do this on the second partition. This one is mounted on the /media
   subdirectory.
   Using FTP, copy the file to the '/media' directory.

5. Unpack the file
   Using Telnet:
    -sh-3.00# cd /mnt/part1
    -sh-3.00# tar -xzf /media/enigma2_cuberevo.tar.gz
    -sh-3.00# mv ./release/* .

   Note: If you use 'CIe2T_ALL.tar.gz' you can skip the 'mv' step,
         since the files in the package are already in their correct
         location.

6. Unmount
    -sh-3.00# cd /
    -sh-3.00# umount /mnt/part1

7. Remove the file (optional)
    -sh-3.00# rm /media/enigma2_cuberevo.tar.gz

8. Modify the environment settings of the bootmanager. Hook up a serial
   connection to the box (null-modem). Settings: 115200, 8 bit, no flow control.
   Using a terminal program, enter into the bootmanager console by pressing CTRL-Z
   during the first seconds of booting the box.
   The item to start from harddisk is the 'menu_5' line.
   Note that the IP addresses here can be adapted to make them match
   your own situation. In this case '192.168.1.90' will be the IP address of the
   box, and '192.168.1.64' is the IP address of the server (typically your PC).
   For normal use these settings are not that important. The operating system
   that is being booted up typically has it's own settings anyway ....
     cuberevo> setenv menu_1 'setenv ipaddr 192.168.1.90;setenv serverip 192.168.1.64;setenv gateway 192.168.1.1;setenv netmask 255.255.255.0;setenv bootargs "console=ttyAS1,115200 panic=3 bigphysarea=10240 root=/dev/nfs nfsroot=/root/Desktop/root rw rootpath=/root/Desktop/root ip=$ipaddr:$serverip:$gateway:$netmask mem=128m coprocessor_mem=4m@0x10000000,4m@0x10400000 init=/bin/devinit";setenv bootcmd "nfs a5ff0000 192.168.1.64:/root/Desktop/root/boot/uImage;bootm a5ff0000";saveenv;boot'
     cuberevo> setenv menu_2 'setenv ipaddr 192.168.1.90;setenv serverip 192.168.1.64;setenv gateway 192.168.1.1;setenv netmask 255.255.255.0;setenv bootusb  "run bootargsusb;usb reset;ext2load usb 0:1 a5ff0000 boot/uImage;bootm a5ff0000";setenv bootargsusb "setenv bootargs console=ttyAS1,115200 panic=3 bigphysarea=10240 root=/dev/sda1 rw rootdelay=10 init=/bin/devinit ip=$ipaddr:$serverip:$gateway:$netmask mem=128m coprocessor_mem=4m@0x10000000,4m@0x10400000";setenv bootcmd "run bootusb";saveenv;boot'
     cuberevo> setenv menu_3 'setenv ipaddr 192.168.1.90;setenv serverip 192.168.1.64;setenv gateway 192.168.1.1;setenv netmask 255.255.255.0;setenv bootusb  "run bootargsusb;usb reset;ext2load usb 0:1 a5ff0000 boot/uImage;bootm a5ff0000";setenv bootargsusb "setenv bootargs console=ttyAS1,115200 panic=3 bigphysarea=10240 root=/dev/sdb1 rw rootdelay=10 init=/bin/devinit ip=$ipaddr:$serverip:$gateway:$netmask mem=128m coprocessor_mem=4m@0x10000000,4m@0x10400000";setenv bootcmd "run bootusb";saveenv;boot'
     cuberevo> setenv menu_4 'setenv ipaddr 192.168.1.90;setenv serverip 192.168.1.64;setenv gateway 192.168.1.1;setenv netmask 255.255.255.0;setenv bootargs "console=ttyAS1,115200 panic=3 root=/dev/mtdblock3 bigphysarea=1500 ip=$ipaddr:$serverip:$gateway:$netmask quiet";setenv bootcmd "bootm a0060000";saveenv;boot'
     cuberevo> setenv menu_5 'setenv ipaddr 192.168.1.90;setenv serverip 192.168.1.64;setenv gateway 192.168.1.1;setenv netmask 255.255.255.0;setenv boothdd  "run bootargshdd;ide reset;ext2load ide 0:1 a5ff0000 boot/uImage;bootm a5ff0000";setenv bootargshdd "setenv bootargs console=ttyAS1,115200 panic=3 bigphysarea=10240 root=/dev/sda1 rw rootdelay=1 init=/bin/devinit ip=$ipaddr:$serverip:$gateway:$netmask mem=128m coprocessor_mem=4m@0x10000000,4m@0x10400000";setenv bootcmd "run boothdd";saveenv;boot'
     cuberevo> saveenv

   Note: Some flash images (like NLB), when updating, also update/reset/restore
         these environment settings. In such a case you should modify the
         settings again.

8. Reboot, and when rebooting press the '5' on the remote control
   during the first 5 seconds, to activate the boot from harddisk.
   (when using '4' instead of '5' you will switch back to starting
   from flash).
   Note: This procedure only needs to be done once (and not during
         every boot), since the bootup procedure stores the last selection.

   The first boot after a new install typically takes longer
   because of first time initialization procedures (about 1.5 minutes
   longer). So, be patient.
   If you want to know what is going on then use the serial connection,
   which gives out debug information about what is going on.
   If installing fails for some reason, then try re-installing it. It
   might help ....



Hints/Notes:
. When at the bootmanager console you can check if the harddisk is
  recognized and accessible:

  cuberevo> ide reset               <- initializes the interface
  cuberevo> ext2ls ide 0:1          <- displays the directory


. In Enigma2 you can/should:
   . change '/etc/fstab' such that '/dev/sda2' is mounted on 'hdd'


. If you have no video then the video mode is probably wrong.
  For SCART, replace in the file '/etc/videomode' the first line
  so it only contains:
    576i50

. You can create a 'clean' harddisk by removing all partitions
  (and data!!) and then rebooting the box. The box will then create
  the required partitions for you.
  For this you have to switch off timeshifting (reboot?) and then
  using Telnet:
    -sh-3.00# umount /media
    -sh-3.00# fdisk /dev/sda
              Command (...): d
              Command (...): 1
              Command (...): d
              Command (...): 2
              Command (...): w
    -sh-3.00# reboot


. During testing I have had different results when using the same
  procedure. This only applies to the initial, first, boot after
  installing Enigma2. At one time the kernel would not boot,
  at other times an error was generated (could not load library).
  There was no real 'consistance' on this behaviour. Maybe it had
  to do with me not unmounting /dev/sda1 before rebooting...
  It could also have to do with the implicit delay of 1 minute
  during the first boot, which might be just too small .....
  Anyway, if in error, just retry.