PC is no needed for choosing, copying booting.

All takss of multiboot are available in an addon plugin within enigma enigma and can be done there.

Even CSV images can be downloaded with the remote control in the meantime.

PC with FTP is more or less only needed to FTP new Images to /MB_Images directory and maybe for copying settings and plugins not available by online update or BP if your image has one (but this is not discussed here)

ciao
thowi

Zitat

Originally posted by thowi

I think we have a misunderstanding here:

First I'm also using the same tools from nfi2cf (just to the multiboot image directories, instead of a plain single second partition after the FAT Boot partition)

Second I don't use the link approach as FWZ does (only Harddisk only Installations are raping the /boot in Flash to then boot from Harddisk - and maybe later from USB if it will work more stable). On a CF Installation the bootloader directly finds a bootable FAT partition on CF card and then boots from there !

So seddi is wron, you even can delete the flash with Multiboot (copy 0 0 erases /boot and / ) and still boot from CF card as long as the scondstage bootloader in Flash is alive !

You then can even copy back from an Multiboot Image to flash if you want (copy 0 ) from eitehr an nfi, a MB Image file or another partition.

So basically mutliboot does the same then the manual booting on an Image on CF, with the only diference to have a nice userscript and gui and the possibility to have multiple independent Partitons with up to 12 Images.

Hence multiboot is mainly targetted for the non-technical user who needs all the funtionality nicely wrapped, but it does nothing not available standalone or manually !

So you could say I didn't invent the engine, I just built it together so
that everybody finds the steering wheell and gear stick

Ciao
thowi

Alles anzeigen

OK, Im wrong
I didnt look at your multiboot tool, because I never use any multiboot on any box. I only have one image on the box and this one is in the flash
So sorry, I thought you do it the same way as the multiboot solutions on the other boxes like fw and so on ...

Seddi - I wasn't upset or something, I simply wanted to correct it.

And like muscbob said 'multiboot et una otre systema' sorry for my italian

Hi guys,

I'm a quite newbie with Dreambox so I need a bit of your help.

I've used this program for my 7020 and doesn't work. The boot seems to start from CF (I see in my TV the logo of the image I converted and placed to CF with the prog) but the boot starts from the internal flash.

Into the first post of the 3ad is written that probably I've to patch the kernel to be able to use this with 7020.

Could someone of you tell me what I need to do for boot an image with my 7020.

Thank you very much in advance.

Please take the following with a pinch of salt. I don't own a 7020, and the current sources for the bootloader is not public. In other words: I'm guessing...

As far as I know, there has been certain improvements in the bootloader from the lastest 7020 version to the current 7025 version. One of the improvements concerns the possibility to transfer parameters to the linux kernel that you want to boot. This is possible to do in the 7025 version, but probably not in the 7020 version. When you boot a standard kernel from the CF on a 7020, the kernel will be loaded from the CF, but the hard-wired root file system will still be flash. (On the 7025, you can use a kernel parameter to intruct the linux kernel to use a partition on CF or HDD as the root file system).

To get around this problem on the 7020, you would need to patch the kernel, to change the hard-wired root file system. More guessing: you can probably do this using a binary editor on a kernel, find the "root=" string, and patch the path to the root file system. Or you could change the kernel configuration and make your own kernel...

is there a way to use this tools on a dm800 ?

i get KeyError: 'dm800'

and when i lock in ripimage.py
i can only see

endianess = {"dm7025": "1234", "dm7020": "4321"}

would it be posibly to just add this

endianess = {"dm7025": "1234", "dm7020": "4321", "dm800": "1234"}

sems to work did just unpack a dm800 firmware

but i cant run buildimage always get error not a executive files or something.
tested on 2 computers, one with slackware and the other with debian

Zitat von t3ch

is there a way to use this tools on a dm800 ?

i get KeyError: 'dm800'

and when i lock in ripimage.py
i can only see

endianess = {"dm7025": "1234", "dm7020": "4321"}

would it be posibly to just add this

endianess = {"dm7025": "1234", "dm7020": "4321", "dm800": "1234"}

sems to work did just unpack a dm800 firmware

but i cant run buildimage always get error not a executive files or something.
tested on 2 computers, one with slackware and the other with debian

Alles anzeigen

Your change to ripimage.py looks valid.

About running buildimage: please remember that this package is over two years old, before the dm800 was introduced. Your best bet is probably to find the current sources for buildimage, and use those instead.

hello!

is it posibly to add support for dm8000 in this script?

FOR DM8000 IMAGE
machine   type: dm8000
extracting secondstage.gz
extracting boot
unpacking   2 (ignore errors about mknod, chown)
  ** wrong data crc **
  **   wrong data crc **
  ** wrong node crc **
Segmentation fault
Traceback   (most recent call last):
  File "./unpack_nfi.py", line 42, in   <module>
    raise "unpacking jffs2 failed!"
TypeError:   exceptions must be classes or instances, not str

b.r

Zitat von gutemine

selber ins nfidump 6.0 gemacht.

Bitte nfidump 6.0 hier anbieten/anhängen

Zitat von gutemine

Sicher nicht - tmbinc wollte es nicht haben

Nah so was...warum will tmbinc es nicht, nfidump ist doch sehr gut bzw. das Beste...
Wenn du es nicht anhängt dann hat dein Bericht mit lzo support doch kein Zweck.

gibt es auch wieder eine .exe Datei, also für windows?
und auch für ix86 (linux) pc...?
Version von 09-05-2012 läuft nur auf mips(el)