Page 2 of 3 FirstFirst 123 LastLast
Results 21 to 40 of 41

Thread: Install E2 on USB and leave dom untouched

  1. #21
    Member
    Join Date
    Mar 2010
    Posts
    28
    Thanks
    0
    Thanked 0 Times in 0 Posts
    with AzUp work, ftp o.k. with telnet no

  2. #22
    V.I.P leerock's Avatar
    Join Date
    Dec 2008
    Posts
    315
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Ti di***o aoratos eimai vre antoni?
    read my post above...

  3. #23
    Member
    Join Date
    Mar 2010
    Posts
    28
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I try nothing

  4. #24
    Senior Member
    Join Date
    Jan 2009
    Posts
    219
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by antonis13 View Post
    user: root
    pass: dreambox

    wrong!
    user: root
    pass: azbox

    thnx papito

  5. #25
    Junior Member
    Join Date
    Aug 2010
    Posts
    8
    Thanks
    0
    Thanked 0 Times in 0 Posts

  6. #26
    Member
    Join Date
    Mar 2010
    Posts
    28
    Thanks
    0
    Thanked 0 Times in 0 Posts
    aa
    Last edited by antonis13; 29-10-2010 at 11:54 AM.

  7. #27
    Junior Member
    Join Date
    Oct 2008
    Posts
    9
    Thanks
    0
    Thanked 0 Times in 0 Posts
    If I would put on usb original fw is is possible ? In this way a change the USB (E2, Original) to switch S.O., only reboot should be performed.

    To procedure to apply it is the same of
    "#####FIRST TIME FLASHING E2######" but the the patch.bin in USB must be Original and not e2 ?

    Thanks
    Pippapeppa

  8. #28
    Senior Member
    Join Date
    Jan 2009
    Posts
    219
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by antonis13 View Post
    it work with putty but :

    Powered by The Ripper, telesat && MickeySa
    Linux/mips 2.6.22.19-19-the_ripper

    (none) login: root
    Password:
    # dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs
    mkdir /patch
    mount -o loop patch_cramfs.bin /patch
    sfdisk -f -uM /dev/sdb < /patch/hda.out
    mkfs.ext3 /dev/sdb1
    mkfs.ext2 /dev/sdb2
    umount /MMP
    mount /dev/sdb1 /MMP
    cd /patch
    tar -cf - . | tar -C / -xpf -
    826294+1 records in
    826294+1 records out
    46272512 bytes (44.1MB) copied, 56.612581 seconds, 79
    # mkdir /patch
    # mount -o loop patch_cramfs.bin /patch
    mount: mounting patch_cramfs.bin on /patch failed: No
    # sfdisk -f -uM /dev/sdb < /patch/hda.out
    -sh: can't open /patch/hda.out: no such file
    # mkfs.ext3 /dev/sdb1
    mke2fs 1.41.12 (17-May-2010)
    Filesystem label=
    OS type: Linux
    Block size=4096 (log=2)
    Fragment size=4096 (log=2)
    Stride=0 blocks, Stripe width=0 blocks
    61568 inodes, 245944 blocks
    12297 blocks (5.00%) reserved for the super user
    First data block=0
    Maximum filesystem blocks=255852544
    8 block groups
    32768 blocks per group, 32768 fragments per group
    7696 inodes per group
    Superblock backups stored on blocks:
    32768, 98304, 163840, 229376

    Writing inode tables: done
    Creating journal (4096 blocks): done
    Writing superblocks and filesystem accounting informa

    This filesystem will be automatically checked every 3
    180 days, whichever comes first. Use tune2fs -c or -
    # mkfs.ext2 /dev/sdb2
    mke2fs 1.41.12 (17-May-2010)
    mkfs.ext2: No such device or address while trying to
    # umount /MMP
    umount: can't umount /MMP: No such file or directory
    # mount /dev/sdb1 /MMP
    mount: mounting /dev/sdb1 on /MMP failed: No such fil
    # cd /patch
    # tar -cf - . | tar -C / -xpf -

    but finaly again nothing, after reboot is rescue mode
    You dont look wether commands are executed right or not?

    mount -o loop patch_cramfs.bin /patch --> should be --> mount -o loop /mnt/root/patch_cramfs.bin /patch

    @papito

    Should be possible but i dont know the device name of the harddisk, and you will loose all data

  9. #29
    Junior Member
    Join Date
    Aug 2010
    Posts
    8
    Thanks
    0
    Thanked 0 Times in 0 Posts
    the device name is hda for HDD

    BR
    PaPiTo

  10. #30
    Junior Member
    Join Date
    Aug 2010
    Posts
    8
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Could this work? for HDD

    dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs.bin bs=56 skip=1
    mkdir /patch
    mount -o loop /mnt/root/patch_cramfs.bin /patch
    umount /MMP
    mount /dev/hda /MMP
    cd /patch
    tar -cf - . | tar -C / -xpf -

  11. #31
    Senior Member
    Join Date
    Apr 2010
    Posts
    191
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Guys, here is booting from usb1, hehehehe

    You must create the dir /MMP because it does not exist.

    After that is working

  12. #32
    V.I.P 4@@@@'s Avatar
    Join Date
    Mar 2010
    Posts
    106
    Thanks
    0
    Thanked 0 Times in 0 Posts
    The error is here
    @antonis13
    dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs
    you missed bs=56 skip=1
    So use
    dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs bs=56 skip=1

    @PaPiTo2:
    The internal HDD is /dev/hdb
    hda is the DOM.

  13. #33
    V.I.P 4@@@@'s Avatar
    Join Date
    Mar 2010
    Posts
    106
    Thanks
    0
    Thanked 0 Times in 0 Posts
    For those of you with console access - AND ONLY FOR THOSE!

    Put the patch.bin to your HDD or usb stick as described here. Or do the whole thing on a linux box (Windows User can use WUBI - Ubuntu on Windows).

    Fetch this with right click and save as - it is a rar archive.

    Put setxenv to /bin on your Original and E2 device.

    Put vme2hdd.bin to your tftp directory
    192.168.1.2 is the IP of your tftp server.
    With telnet on the original booted box
    # For E2 from HDD
    setxenv -f /dev/mtdblock0 -k y.start -v "net init;net initpci;net up; load -b tftp://192.168.1.2/vme2hdd.bin 0x90020000; go 0x90020000"
    setxenv -f /dev/mtdblock0 -k a.linux_cmd -v "console=ttyS0,115200 root=/dev/hdb1 rw rootdelay=5 mem=108m"

    If the extracted patch.bin is on the /dev/sda1 change hdb1 to sdb1.

    Reboot
    If bootet in E2 you should put setxenv to /bin and now to go back use this

    setxenv -f /dev/mtdblock0 -k y.start -v "xrpc 0xac080090; load zbf 0xb3000000; go"
    setxenv -f /dev/mtdblock0 -k a.linux_cmd -v "console=ttyS0,115200 root=/dev/hda1 rw rootdelay=5 mem=108m"

    There is some work to be done, that the kernel (vme2hdd.bin) can be loaded from devices like HDD.
    There is also the command "disk" in yamon which could be used to boot from the first partition of the internal disk, if it is divided in two partition. I haven't tryed this yet.
    The_Ripper will implement kexec into the kernel which will makes things easyer. But this is another story and will be shown when done.

  14. #34
    Senior Member
    Join Date
    Apr 2010
    Posts
    191
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Went back to original, and no problem.

    Thanks Sattommy

  15. #35
    Member
    Join Date
    Sep 2010
    Posts
    30
    Thanks
    0
    Thanked 0 Times in 0 Posts
    All steps done ok, but when I try to reboot it returns to the "rescue mode" and nothing else.

    Any ideas?

  16. #36
    Member
    Join Date
    Sep 2010
    Posts
    30
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Now it's working...
    I just have to wait a longer time.

  17. #37
    V.I.P Smudger's Avatar
    Join Date
    Dec 2004
    Location
    UK & Spain
    Posts
    759
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Just a thought how do we handle an update to next release? when available.
    Last edited by Smudger; 31-10-2010 at 12:12 PM.

  18. #38
    Senior Member
    Join Date
    Apr 2010
    Posts
    191
    Thanks
    0
    Thanked 0 Times in 0 Posts
    when new update comes, you have to repeat all steps to install again on the usb.

  19. #39
    Member
    Join Date
    Sep 2010
    Posts
    30
    Thanks
    0
    Thanked 0 Times in 0 Posts
    lets dream....

    maybe a liveCd booting from usb, without change the kernel....

    yeah, it's a dream....

  20. #40
    V.I.P hfmls's Avatar
    Join Date
    May 2009
    Location
    Portugal
    Posts
    1,819
    Thanks
    0
    Thanked 0 Times in 0 Posts
    pff dual boot would be (flash original) enigma2 usb would be heaven (in test phase).
    after that i would prefer in flash (DOM)

Page 2 of 3 FirstFirst 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •