Understanding the DM7020 - a build-it-from-source exploration of the new Dreambox

[karlmoran]

thanks to all
I made all the steps , every thing went smoothly , but at the end Igot this error

--10:37:42-- http://www.treke.net/oe/source/apps....0040928.tar.gz
=> `/home/karl/pro/sources/apps.misc.libs_cvs.tuxbox.org__20040928.tar.gz'
Resolving link.net... 213.131.64.64
Connecting to link.net[213.131.64.64]:8080... connected.
Proxy request sent, awaiting response... 404 Not Found
10:37:43 ERROR 404: Not Found.

NOTE: Fetch cvs://anoncvs@cvs.tuxbox.org/cvs/tuxbox;module=apps/misc/libs;method=ext
connect to address 82.149.243.100: Connection refused
Trying krb4 rsh...
connect to address 82.149.243.100: Connection refused
trying normal rsh (/usr/bin/rsh)
cvs.tuxbox.org: Connection refused
cvs [checkout aborted]: end of file from server (consult above messages if any)
NOTE: Task failed: Fetch failed: apps/misc/libs
ERROR: package tuxbox-libs-1.0-r1: task do_fetch failed
ERROR: TaskFailed event exception, aborting
ERROR: package tuxbox-libs: build failed
ERROR: Build of dreambox-image failed

any idea plz
thanks

[noggie]

Originally Posted by karlmoran

any idea plz
thanks

This one looks to be the same as the one described by "mikev" here: http://sat-industry.net/forums/showt...0&page=5&pp=10

[karlmoran]

thanks a lot noggie
I tried again but at the end I got a different error

01:00:35 (7.82 KB/s) - `/home/karl/pro/sources/libc_sources.redhat.com__20040726.tar.gz' saved [18,965,958/18,965,958]
NOTE: Fetched libc_sources.redhat.com__20040726.tar.gz from tarball stash, skipping checkout
NOTE: package glibc-initial-2.3.2+cvs20040726-r13: task do_fetch completed
NOTE: package glibc-initial-2.3.2+cvs20040726-r13: task do_unpack started
NOTE: Unpacking /home/karl/pro/sources/libc_sources.redhat.com__20040726.tar.gz to /home/karl/pro/build/tmp/work/glibc-initial-2.3.2+cvs20040726-r13/
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers

gzip: stdin: invalid compressed data--crc error

gzip: stdin: invalid compressed data--length error
tar: Read 5444 bytes from /home/karl/pro/sources/libc_sources.redhat.com__20040726.tar.gz
tar: Child returned status 1
tar: Error exit delayed from previous errors
NOTE: Task failed:
ERROR: package glibc-initial-2.3.2+cvs20040726-r13: task do_unpack failed
ERROR: TaskFailed event exception, aborting
ERROR: package glibc-initial: build failed
ERROR: Build of dreambox-image failed

any idea plz
thanks

[noggie]

Originally Posted by karlmoran

any idea plz
thanks

Never seen (or heard about) this before, but judging by the error messages there's a couple of things you may want to check:

1) Make sure you're not running out of disk space. That can cause strange things to happen. Check that you have free space on /tmp also.
2) Maybe your download of libc_sources.redhat.com__20040726.tar.gz is bad. The md5sum of my copy is 099c09cffbb87e498f00086d4885c62f. If it's different in your copy, delete the file and try again.

[karlmoran]

thanks a lot noggie for great help and advice
finally I did it
I don know what was the problem ?!!
all what I did is that I deleted the whole {tuxbox-oe} directory and started from the begininig , everything went smoothly and I got the ¨nfi¨ file

please noggie :
how can I decopress the boot.jffs2 and the rootfs.jffs2 parts which are found in /...../build/tmp/deploy/images

also if I want to make a new img which contains some modifications , what could I do ?

thanks a lot my friend

[noggie]

Originally Posted by karlmoran

please noggie :
how can I decopress the boot.jffs2 and the rootfs.jffs2 parts which are found in /...../build/tmp/deploy/images

I have posted (here on SI) earlier some scripts (for running on your Linux PC) and programs (for running on the dreambox) to do that. They start from the .nfi file, extracts the jffs2 images from the nfi file, and does some strange stuff to get these file system images mounted. Alternativeley, the miniroot7020 also contains this functionality, and the sources for that have also been posted here on SI. One way to (ab)use the miniroot7020 is to use it just to do the unpacking for you. Install it, run it once to unpack the image you want to peek inside, and then uninstall it.

But actually, I don't think you need any of this for your own build. In .../build/tmp/rootfs you will find an exact copy of what's in root.jffs2, so why unpack it? Unfortunately, the files that are put into boot.jffs2 are deleted before the rootfs.jffs2 is made, but if you look into the log and run files (in .../build//tmp) you will see where in the .../build/tmp/work directory tree they came from, and since there's only a handful of files in the boot.jffs2 image, it's not big deal to reconstruct it.

also if I want to make a new img which contains some modifications , what could I do ?

There's a right way to do this, by changing the build rules etc. Sorry, I don't have a good description of that, it's not something I do myself.

There's also a quick-and-dirty way... Just replace the files you want to in the .../build/tmp/rootfs directory, and repack the .nfi. Again, the log and run files in .../build/tmp is your friend, they tell what commands to run and what options to use in order to repack the .nfi.

So when can we expect the karlmoran image for the 7020?

[karlmoran]

Originally Posted by noggie

There's also a quick-and-dirty way... Just replace the files you want to in the .../build/tmp/rootfs directory, and repack the .nfi. Again, the log and run files in .../build/tmp is your friend, they tell what commands to run and what options to use in order to repack the .nfi.

thanks noggie

can you please give some more explaination on how to use these files to repack the .nfi

thanks a lot

[noggie]

Originally Posted by karlmoran

can you please give some more explaination on how to use these files to repack the .nfi

What I meant was that by reading through these files, you will see the commands that are used by the OE build environment to pack the .nfi. Knowing that, you will be able to use the same commands to pack your own .nfi after applying any changes that you want.

[karlmoran]

hi noggie
sorry for bothering you

I found these commands

mkfs.jffs2 --root=/home/karl/tuxbox/build/tmp/rootfs/boot --faketime --output=/home/karl/tuxbox/build/tmp/deploy/images/dreambox-image-dreambox-20050418050724.boot.jffs2 --eraseblock=0x4000 -n -b ; rm -rf /home/karl/tuxbox/build/tmp/rootfs/boot/*; mkfs.jffs2 --root=/home/karl/tuxbox/build/tmp/rootfs --faketime --output=/home/karl/tuxbox/build/tmp/deploy/images/dreambox-image-dreambox-20050418050724.rootfs.jffs2 --eraseblock=0x4000 -n -b ; buildimage /home/karl/tuxbox/build/tmp/staging/powerpc-linux/lib/dreambox-secondstage/main.bin.gz /home/karl/tuxbox/build/tmp/deploy/images/dreambox-image-dreambox-20050418050724.boot.jffs2 /home/karl/tuxbox/build/tmp/deploy/images/dreambox-image-dreambox-20050418050724.rootfs.jffs2 > /home/karl/tuxbox/build/tmp/deploy/images/dreambox-image-dreambox-20050418050724.nfi

but when I tried these command I got somthing like this:

bash :mkfs.jffs2 no such command

any idea plz

thanks

[noggie]

Originally Posted by karlmoran

any idea plz

That one's easy

Check the path that is reported in the log file, and make sure the directory where the mkfs.jffs2 lives is included in your own path when you run the command.