[Devilfish]

How to build a complete image for your dreambox

Choosing your Platform

First of all, you will need a platform to create your image. There are many versions of linux that you can use, I have used VMWare with Ubuntu and also a dedicated linux PC running Ubuntu. Both variations will work just as well.

If you want to use VMWare, you can download it at http://www.vmware.com/download/player.

If you want to use a dedicated PC, either with Ubuntu as the main OS or as a dual-boot system, you can download Ubuntu for free at http://www.ubuntu.com.

The VMWare method is probably easier if you are trying it out for the first time. You can always uninstall it if it's not for you.

Configuring your Ubuntu

The following packages need to be installed in your ubuntu before you start creating any images.

Click on System, Administration, Synaptic Package Manager.

You will need to search for the following packages and install them:

- cvs
- autoconf
- automake
- libtool
- gettext
- make
- makeinfo (texinfo)
- tar
- bunzip2 (bzip2)
- gunzip (gzip)
- patch
- infocmp (ncurses-bin / ncurses-devel)
- gcc
- g++
- flex
- bison
- pkg-config
- wget
- libpng2 or libpng3 (DirectFB)
- ftpd (or other ftp server)

The latest versions of these packages should work ok. Click Apply to install them.

There is a pre-configured environment that you can download from here:

http://rapidshare.com/files/19433800...art01.rar.html
http://rapidshare.com/files/19438947...art02.rar.html
http://rapidshare.com/files/19443643...art03.rar.html
http://rapidshare.com/files/19447782...art04.rar.html
http://rapidshare.com/files/19451240...art05.rar.html
http://rapidshare.com/files/19454408...art06.rar.html
http://rapidshare.com/files/19457852...art07.rar.html
http://rapidshare.com/files/19460565...art08.rar.html
http://rapidshare.com/files/19462848...art09.rar.html 

If you have installed the necessary packages, you don't need to download the pre-configured environment.

Compiling an Image

Now we'll move on to downloading and compiling our image. Most of this will be copy and paste but you'll get used to the commands.

Open a terminal window and paste the following commands:

Creating a working directory

mkdir tuxbox-cvs

Change into the working directory

cd tuxbox-cvs

The following can now be copied and pasted in, line by line. Wait for the command prompt to be displayed before pasting the next line.

export CVS_RSH=ssh

 cvs -d anoncvs@cvs.tuxbox.org:/cvs/tuxbox -z3 co -P -rdreambox .

### Note the dot at the end of the command, this is important ###

cd cdk

chmod 755 prepare

Now we need to alter the 'prepare' file to personalise our image

Go to /tuxbox-cvs/cdk and open the 'prepare' file with the text editor. It should look like this:

#!/bin/bash
cd .. && CURRENT_PATH=`pwd`;
cd cdk
./autogen.sh;
# boxtype dm500 dm56x0 or dm7000
TYPE=$1
if test -z "$TYPE"; then
    TYPE=dm7000                   //change to box type
fi
./configure \
    --with-boxtype=$TYPE \
    --with-webif=standard \       //change to webif=expert
    --prefix=$CURRENT_PATH/root \
    --with-cvsdir=$CURRENT_PATH \
    --with-cpu=405 \
    --enable-maintainer-mode \
    --with-targetruleset=flash \
    --with-epg=private \          //change to -epg=standard
    --with-mhw-epg=no \           //change to -epg=yes
    --with-flashtool=standard \
    --with-reiserfs=no \
    --with-ext-flashtool=yes \
    --with-enigma-debug=yes

Change the lines in red. Save the file and return to the terminal window.

Back to the copy and pasting.

./prepare dm500

make checkout

make dreamboximage_root

The last command will take a long time to complete, depending on the speed of your PC and internet; up to about 2 hours.

The following command creates the folders that you normally see on your box, i.e. /bin, /etc, /var, /var_init, etc.

make rebuild-flash

The following command compresses all your folders into an .img file.

make flash-compress

If all has gone ok and you didn't get any errors, you should have a file called complete.img in /tuxbox-cvs/root/cdkflash. This is your actual image file that you flash to your box. There will be two other .img files but don't worry about them.

Now this will be a basic image, no addons or emu managers or anything. It will be like the dream original image only up-to-date.

Next you need to modify it to your needs.

Good luck!

[osborne82]

just to add about the prepare file

#!/bin/bash
cd .. && CURRENT_PATH=`pwd`;
cd cdk
./autogen.sh;
# boxtype dm500 dm56x0 or dm7000
TYPE=$1
if test -z "$TYPE"; then
    TYPE=dm7000                   //change to box type
fi
./configure \
    --with-boxtype=$TYPE \
    --with-webif=standard \       //change to webif=expert
    --prefix=$CURRENT_PATH/root \
    --with-cvsdir=$CURRENT_PATH \
    --with-cpu=405 \
    --enable-maintainer-mode \
    --with-targetruleset=flash \
    --with-epg=private \          //change to -epg=normal
    --with-mhw-epg=no \           //change to -epg=yes
    --with-flashtool=standard \
    --with-reiserfs=no \
    --with-ext-flashtool=yes \
    --with-enigma-debug=yes

not needed to change box type here as the ./prepare dmxxxx will sort it (defalut is dm7000)

also --with-epg=private \ again not really needed to change but can use either private OR standard

--with-reserfs=no if u change to yes it gives few more hard drive options (mainly for dm7000 and above)

cheers

osborne82

ohh might have a play with this when ive got some time to sit down on it. always wanted a go but never knew how.


wonder if someones going to make a digital-kaos image

[Devilfish]

Thanks for the additional info osborne82, you always keep me right!

Get stuck in thommo.

[Devilfish]

One other thing to note...

When you create an enigma image, all your files go in /var_init; /var is always empty.

The reason for this is, when the image boots for the first time, it copies everything from /var_init to /var. It only does this on first boot or if you have selected the 'factory reset' option.

You should be asked to select the language, timezone and PAL. This is the image configuring the /var/tuxbox/config/enigma/config file.

The config file is useful for setting default options.

When you select Menu > Setup > Expert Setup, you have a few options that you can 'tick'. These are defined in the config file. To find out what each line does by comparing the file before and after you change an option. Reboot to take effect.

[Devilfish]

UK Infobar 'Now and Next' EPG Modification

UK cable doesn't conform to the dvb-c standard. So we need to modify the source code so that it displays the now and next program information on the infobar. Without this mod, there will be no now and next epg.

Download the attached txt file and extract the contents to your 'tuxbox-cvs' directory.

In a terminal window, change into the tuxbox-cvs directory.

cd tuxbox-cvs

Copy and past this command:

patch -p1 < infopmt.diff

If it patches ok you shouldn't get any errors and you should see a prompt again.

Now you need to copy and paste the following commands:

cd cdk

 rm .enigma

 make .enigma

 make rebuild-flash

 make flash-compress

The image will compile into .img as in the first post. Now and next epg should now work.

[Devilfish]

How to create your own startup, shutdown, radio, scan and mp3 logos
The dimension of these pictures must be 720×576 pixels in PAL format.

Path where the boot image is stored is /root/platform/kernel and is called bild.
Path where the other pictures are stored is /var/tuxbox/config/enigma/pictures.

The program we will use to create the pictures is called TMPGEnc.

1. Download TMPGEnc from official site
2. Unzip the file to your chosen destination.
3. Double click the ‘TPMGEnc.exe MPEG Encoder’ file and click ‘OK’ on the small pop up window. Then click ‘Cancel’ on the ‘Project Wizard (1/5)’ window that appears.
4. Next screen, bottom right…’Stream type’, check the box ‘ES (Video only)’.
5. Next, bottom left…’Video source:’ click on ‘Browse’ and select the background/photo that you want as your new logo.
6. Next, bottom left… ‘Output file name:’ click on browse and choose the path for your finished ‘new’ boot background/photo and edit the name to ‘bild’ (minus the ‘….’ and in lower case) ie: the line that apperars in the ‘Output file name:’ should read similar to C:\Documents and Settings\Whatever\My Documents\bild ( the actual name of the photo does NOT appear).
7. Next, bottom right…click on ‘Setting’ and check that the value settings are:

…..’Stream type:’ = MPEG-1 Video
…..’Size’ = 720 x576 pixels
…..’Aspect ratio:’ = 1:1 (VGA)
…..’Frame rate:’ = 25 fps
…..’Rate control mode:’ = Constant bitrate (CBR)
…..’Bitrate:’ = 12000
…..’Motion search precision:’ = Normal

When checked, click ‘OK’ to exit the screen.

Top left click ‘Start’, if all is goes well, the ‘100%’ bar appears and your completed ‘bild’ file is in your chosen ‘Output…’ location.

*** If You want to change the boot picture before compressing the image (after the ‘make rebuild-flash’ command ) , just copy it into /tuxbox-cvs/root/cdkflash/boot/root/platform/kernel before executing the ‘make flash-compress’ command.

Thanks to Fergy for initial guide

[virus]

I am here again, I would like to know a good and simple way of getting a skin as default and delet those that come from home, I think that only lack here in this same section of development

[Devilfish]

To make a certain skin default, you can edit the setup_skin.cpp file to reflect this.

Or add this line to the bottom of the /var_init/tuxbox/config/enigma/config file.

s:/ezap/ui/skin=/share/tuxbox/enigma/skins/SKIN_NAME.esml

You can also remove any skins you don't want from /share/tuxbox/enigma. Remember to remove the skins and pictures files.

[virus]

Originally Posted by Devilfish To make a certain skin default, you can edit the setup_skin.cpp file to reflect this. Or add this line to the bottom of the /var_init/tuxbox/config/enigma/config file. s:/ezap/ui/skin=/share/tuxbox/enigma/skins/SKIN_NAME.esml You can also remove any skins you don't want from /share/tuxbox/enigma. Remember to remove the skins and pictures files.

thankd for reply


I get to another skin as the default file setupskin.cpp

I must add here?

CONFIGDIR "/enigma/skins/virus.esml", TUXBOXDATADIR "/enigma/skins/virus.esml",

after adding a skin that commands can I do for the skin is in the picture???

make rebuild-flash
make flash-compress
????????


very grateful for your help

[Devilfish]

After you adjust any src files you need to remake enigma.

rm .enigma
make .enigma
make rebuild-flash
make flash-compress

[rolks]

newbe here. tryed different linuxes to use for copile but result allways same:
nable different security models (SECURITY) [N/y/?] n
*
* Cryptographic options
*
Cryptographic API (CRYPTO) [N/y/?] n
make[2]: Leaving directory `/tuxbox-cvs/cdk/linux-2.6.9'
make -C linux-2.6.9 include/linux/version.h \
ARCH=ppc
/tuxbox-cvs/cdk/linux-2.6.9/scripts/gcc-version.sh: line 11: powerpc-tuxbox-linux-gnu-gcc: command not found
/tuxbox-cvs/cdk/linux-2.6.9/scripts/gcc-version.sh: line 12: powerpc-tuxbox-linux-gnu-gcc: command not found
make[2]: Entering directory `/tuxbox-cvs/cdk/linux-2.6.9'
CHK include/linux/version.h
UPD include/linux/version.h
make[2]: Leaving directory `/tuxbox-cvs/cdk/linux-2.6.9'
ln -sf /tuxbox-cvs/cdk/linux/include/asm-ppc /tuxbox-cvs/cdk/linux/include/asm
touch .linuxdir
make[1]: Leaving directory `/tuxbox-cvs/cdk'
( rm -rf binutils-2.15.91.0.2 || /bin/true ) && bunzip2 -cd Archive/binutils-2.15.91.0.2.tar.bz2 | tar -x && ( rm -rf build || /bin/true ) && mkdir build
cd build && \
CC=gcc \
CFLAGS="-g -O2" \
../binutils-2.15.91.0.2/configure \
--target=powerpc-tuxbox-linux-gnu \
--prefix=/tuxbox-cvs/root/cdk \
--disable-nls \
--nfp && \
make all all-gprof && \
make install
creating cache ./config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... config.sub: invalid option --targetpowerpc-tuxbox-linux-gnu
Try `config.sub --help' for more information.
checking build system type... i686-pc-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for gcc... gcc
checking whether the C compiler (gcc -g -O2 ) works... yes
checking whether the C compiler (gcc -g -O2 ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for gnatbind... no
checking whether compiler driver understands Ada... no
checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1 $$f2
checking for correct version of gmp.h... no
checking for bison... bison
checking for bison... bison -y
checking for gm4... no
checking for gnum4... no
checking for m4... m4
checking for flex... flex
checking for flex... flex
checking for makeinfo... makeinfo
checking for i686-pc-linux-gnu-ar... no
checking for ar... ar
checking for i686-pc-linux-gnu-as... no
checking for as... as
checking for i686-pc-linux-gnu-dlltool... no
checking for dlltool... dlltool
checking for i686-pc-linux-gnu-ld... no
checking for ld... ld
checking for i686-pc-linux-gnu-nm... no
checking for nm... nm
checking for i686-pc-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-linux-gnu-windres... no
checking for windres... windres
checking for i686-pc-linux-gnu-objcopy... no
checking for objcopy... objcopy
checking for i686-pc-linux-gnu-objdump... no
checking for objdump... objdump
checking for --targetpowerpc-tuxbox-linux-gnu-ar... no
../binutils-2.15.91.0.2/configure: line 4183: test: too many arguments
checking for --targetpowerpc-tuxbox-linux-gnu-as... no
../binutils-2.15.91.0.2/configure: line 4255: test: too many arguments
checking for --targetpowerpc-tuxbox-linux-gnu-dlltool... no
../binutils-2.15.91.0.2/configure: line 4327: test: too many arguments
checking for --targetpowerpc-tuxbox-linux-gnu-ld... no
../binutils-2.15.91.0.2/configure: line 4399: test: too many arguments
checking for --targetpowerpc-tuxbox-linux-gnu-nm... no
../binutils-2.15.91.0.2/configure: line 4471: test: too many arguments
checking for --targetpowerpc-tuxbox-linux-gnu-ranlib... no
../binutils-2.15.91.0.2/configure: line 4543: test: too many arguments
checking for --targetpowerpc-tuxbox-linux-gnu-windres... no
../binutils-2.15.91.0.2/configure: line 4615: test: too many arguments
checking whether to enable maintainer-specific portions of Makefiles... no
checking if symbolic links between directories work... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
sed: file conftest.s1 line 64: unterminated `s' command
make[1]: Entering directory `/tuxbox-cvs/cdk/build'
make[1]: *** No rule to make target `all'. Stop.
make[1]: Leaving directory `/tuxbox-cvs/cdk/build'
make: *** [.binutils] Error 2
[root@localhost cdk]#

maybe some know what i did wrong or what packages i missed. thank you

[rolks]

tried with english interface and endup with another error:
Location: http://switch.dl.sourceforge.net/sou...-4.1.3.tar.bz2 [following]
--2008-07-26 12:46:30-- http://switch.dl.sourceforge.net/sou...-4.1.3.tar.bz2
Connecting to switch.dl.sourceforge.net|130.59.138.20|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://prdownloads.sourceforge.net/l...ourceforge.net [following]
20 redirections exceeded.
--2008-07-26 12:46:30-- http://tuxbox.berlios.de/pub/tuxbox/...-4.1.3.tar.bz2
Resolving tuxbox.berlios.de... 195.37.77.138
Connecting to tuxbox.berlios.de|195.37.77.138|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2008-07-26 12:46:30 ERROR 404: Not Found.

make: *** [Archive/libungif-4.1.3.tar.bz2] Error 1
[root@localhost cdk]# make dreamboximage_root

[Devilfish]

It looks like libungif-4.1.3.tar.bz2 file is missing.

You can download it from here...

http://downloads.sourceforge.net/gif...0&big_mirror=0

..put it int he Archive folder along with all the other .tar.bz files and do a make dreamboximage_root again.

[rolks]

how to tell to "make dreambox_image" to get it from what mirror or it can be indalled before? thanks