multiboot setup?

  • Please provide some information about the hard- and software used.


    Box type: DB7025
    GUI (enigma1/enigma2): Enigma2
    Firmware version: Latest DMM build as of 06022006


    your question Is there a tutorial on how to build a multi boot environment? I'd like to have a Compact Flash in my DB and be able to boot with different images to try out various things, but keep the original DMM image intact as a reference. I searched the board, but maybe I have missed it.

    2 Mal editiert, zuletzt von nattar ()

  • Is this becasue of the Compact Flash driver? Or a different reason?


    I have a hard drive in my DB? Can I use that?

    Einmal editiert, zuletzt von nattar ()

  • Booting from CF is supported by DMM, no extra software needed. What you need:
    1) A CF that has at least two partitions, one for boot and one for root
    2) The boot partition must be the first partition on the CF, and must be formatted as a FAT partition.
    3) The root partition can not be FAT, but could be e.g. ext3
    4) A file on the the boot partition called "autorun.bat" that loads the boot screen image and the kernel. Kernel options are allowed, and must be used to change the root partition from flash (a default that is compiled into the kernel) to the root partition on CF.
    5) Obviously all the needed boot files on the boot partition, and all the rest of the files in the image on the root partition.


    Here's a small script (to be run on the 7025) to partition and format the CF. Change to fit your own needs.


    (Please excuse my python code, I'm still learning...)
    The script assumes that you have the dosfstools package installed, it contains the "mkdosfs" program. You will also need a directory for the root partition on CF. The script assumes that this directory is /media/cf2


    A simple way to make an image on CF is to mount the CF on your Linux PC and copy the files from your OE build environment. You could also make a copy of the existing files on flash, so that the CF contains a backup. The following script could perhaps be a starting point:


    You could also unpack nfi files on your Linux PC if you have the required mtd and jffs2 modules for your kernel. Doing the same thing on the 7025 is possible, but it requires some extensive kernel patching, and you probably don't want to do that. I've got my own scripts to unpack nfi-files on my PC, but they are quite dependant on my own Linux setup and probably won't run on any other machine without some modifications. I don't have a problem posting them, but I kinda doubt that anybody would find them very interesting. Let me know if I'm wrong.

  • Hi noggie,


    yes, i'd like to know the way to mount the .nfi images on my linux pc, because I'm also interested to boot from CF images :). And, there is a way to change files on the unpacked .nfi and pack it again?


    Thanks!

  • Well, let it not be said that I didn't warn you... These scripts have been written for my own private use, reflecting my Linux environement, with no attempt at making them generic and usable for anybody else. I can almost guarantee that they will need changes to run on any other machine but my own.


    Just to make it clear, these scripts are used on my PC, not on the 7025. On the PC, each image for the 7025 is stored in a separate directory.


    There are four different scripts:
    1) Backup_cf, to copy the existing image from CF to the PC disk.
    2) Unpack_image, to unpack an nfi file to PC disk
    3) Update_files, to copy config files etc. from one image to another (still on the PC)
    4) Copy_image_to_cf, to copy an image to the CF


    Those four scripts would typically be run one after the other when I test a new image. The new image on CF would then contain all my up-to-date configuration files, and I would have a backup of my last working image on disk in case the new one fails for whatever reason.


    Notably missing is a script to install extra ipkg-packages offline on an image. This script would also make it easier to update single packages (think CVS versions of enigma2) from OE. Maybe this week-end... Currently, I keep a collection of ipkg-files in a directory on the harddisk on the 7025, and install them on any new image from the 7025 itself.