Multiboot on Dream ONE/TWO

[Captain]

here you can download

ZIP Files in the Current Folder
ZIP Files in the Current Folder

copy file to usb or hdd and flash from local

[frankviana]

here you can download

ZIP Files in the Current Folder
ZIP Files in the Current Folder

copy file to usb or hdd and flash from local

Both links appear same dream"one" images and not dream"two".

Thx

[Captain]

ah ok one of the mirror server have a issue, in 15min its fixed please wait

[frankviana]

How to access using ftp or sftp (dreamOs images)? I tried several times and passwords (including blank/removed passwords) but no access... I do everything only using telnet (including password changes), but no luck for ftp/sftp

Thx

[Captain]

dreamos . you must add a passwort in e2 to access ftp and telnet

[frankviana]

dreamos . you must add a passwort in e2 to access ftp and telnet

Yes... I did several times... using e2 (all options) and telnet (passwd root)..... using telnet, access OK, but problem is ftp/sftp

[Captain]

dreamos you must use ftp, sftp must install from feed

[frankviana]

Sample Setup:

200920086156_55

Slot 1: OpenATV (nov, 2023)
Slot 2: Peter Pan (DreamOS 5)
Slot 3: Gemini 4.2 (DreamOS 5)

https://youtu.be/7FZ9xYlriw4

[mihaip]

Frank , I've follow with attention your clip ! what I've remarked
... you can move step by step into GPT Boot Menu ... I use
BL106 , as anyone , and the cursor is jumping unpredictable !
thru the choice elements !

[Captain]

the jumping in the u-boot menu cannot be fixed. no source and Dream has stopped development. so there are no more bug fixes.

[mihaip]

Hi @Captain ! your mailbox is full !

[mihaip]

Hi @Captain !
If I load PeterPan AIO or ... let say Gemini AIO ...,
and run it , do you think that "rescue image 110" will work !

[frankviana]

After run this commands using AIO image:

echo "deb [trusted=yes] https://repo.fury.io/aio/ ./" > /etc/apt/sources.list.d/aio.list
apt-get update
apt-get upgrade
apt-get install rescue-image

I have bootloader v106-v3 and not v110 anymore, but works too (same as 110). No problems here.

But if I want v110 again, I just need:

dpkg -i rescue-image_110_arm64.deb

[Captain]

flash image with 110 from web browser works too openatv ?

[frankviana]

flash image with 110 from web browser works too openatv ?

Yes... This was my first step (only after v110, now I see v106 using feed). After install using dpkg, I did a update OpenATV from v110... and after, other 2 slot images.

Both: 106 and 110 works as before (slot 1: openatv, slot 2: Peter Pan and slot 3: Gemini 4.2 AIO (DreamOs 5.0)

I tried several times upload OpenATV using webbrowser (v110), but backup don't recognize... only clean image. My first test was: openatv-7.3-dreamtwo-20231106_mmc.zip. After this image, I restore my backup and works very fine.

EDIT: Need only upload your rootfs.tar.gz (backup or clean image)

[mihaip]

Well ... I don't understand ! dpkg is just extrecting from .deb archive to ...

\usr\share\rescue-image\dreambox\dreambox-rescue-image-dreambox-20231106.img

when this image become BL110 ?

[frankviana]

Now, tests using v111 (4 partitions).

Restoring my rootfs (OpenATV) from last image backup.

LOG:

Code: Alles auswählen

dreambox
Firmware upload

   
      [*] Creating directory '/data'
[*] Mounting '/dev/disk/by-partlabel/dreambox-data' to '/data'
[*] Unmounting '/data'
[*] Creating partition table
[*] Creating GPT for multiboot u-boot
[*] Creating ext4 filesystem 'dreambox-data' on /dev/disk/by-partlabel/dreambox-data
mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks:    4096/1652992 528384/16529921052672/16529921576960/1652992               done                            
Creating filesystem with 1652992 4k blocks and 413712 inodes
Filesystem UUID: 26bcd112-e30f-48b0-b14e-581aac215b1a
Superblock backups stored on blocks: 
   32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables:  0/51     done                            
Writing inode tables:  0/51     done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information:  0/51     done

[*] Creating ext4 filesystem 'dreambox-rootfs1' on /dev/disk/by-partlabel/dreambox-rootfs1
mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks:   4096/524288             done                            
Creating filesystem with 524288 4k blocks and 131072 inodes
Filesystem UUID: a005e00b-cf54-4440-90b4-cf49674ccc53
Superblock backups stored on blocks: 
   32768, 98304, 163840, 229376, 294912

Allocating group tables:  0/16     done                            
Writing inode tables:  0/16     done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information:  0/16     done

[*] Creating ext4 filesystem 'dreambox-rootfs2' on /dev/disk/by-partlabel/dreambox-rootfs2
mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks:   4096/524288             done                            
Creating filesystem with 524288 4k blocks and 131072 inodes
Filesystem UUID: 52dd168d-13f8-4840-aa66-50dd56aa0534
Superblock backups stored on blocks: 
   32768, 98304, 163840, 229376, 294912

Allocating group tables:  0/16     done                            
Writing inode tables:  0/16     done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information:  0/16     done

[*] Creating ext4 filesystem 'dreambox-rootfs3' on /dev/disk/by-partlabel/dreambox-rootfs3
mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks:   4096/524288             done                            
Creating filesystem with 524288 4k blocks and 131072 inodes
Filesystem UUID: d83bd505-850a-43c6-905d-b1965091ae11
Superblock backups stored on blocks: 
   32768, 98304, 163840, 229376, 294912

Allocating group tables:  0/16     done                            
Writing inode tables:  0/16     done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information:  0/16     done

[*] Mounting '/dev/disk/by-partlabel/dreambox-data' to '/data'
[*] Creating ext4 filesystem 'dreambox-rootfs' on /dev/disk/by-partlabel/dreambox-rootfs
mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks:   4096/524288             done                            
Creating filesystem with 524288 4k blocks and 131072 inodes
Filesystem UUID: 44b1fff9-0a66-4c93-b53e-69be25107e61
Superblock backups stored on blocks: 
   32768, 98304, 163840, 229376, 294912

Allocating group tables:  0/16     done                            
Writing inode tables:  0/16     done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information:  0/16     done

[*] Mounting '/dev/disk/by-partlabel/dreambox-rootfs' to '/mnt'
[*] Extracting '/tmp/mHHdFO' to '/mnt'
[*] Mounting '/dev' to '/mnt/dev'
[*] Mounting '/proc' to '/mnt/proc'
[*] Mounting '/run' to '/mnt/run'
[*] Mounting '/sys' to '/mnt/sys'
[*] Mounting '/tmp' to '/mnt/tmp'
[*] Mounting '/data' to '/mnt/data'
Warning: Could not read CA!
Warning: Please consider updating your rescue loader!
mktemp: No such file or directory
Fatal: Failed to create working directory
Fatal: Failed to run dreambox-bootlogo-u-boot.postinst
[*] Unmounting '/mnt/data'
[*] Unmounting '/mnt/tmp'
[*] Unmounting '/mnt/sys'
[*] Unmounting '/mnt/run'
[*] Unmounting '/mnt/proc'
[*] Unmounting '/mnt/dev'
[*] Unmounting '/mnt'
[*] Unmounting '/data'

[frankviana]

But , after restart, OpenATV show only same 3 partitions and, new v111 is for 4 partition tables.

Der Dateianhang startup.jpg existiert nicht mehr.

new bootconfig.txt (after repartition table):

details=0
timeout=5
fb_pos=100,400
fb_size=1080,300
[Dreambox Image]
cmd=ext4load mmc 1:5 1080000 /boot/kernel.img;bootm;
arg=${bootargs}
[Dreambox Recovery]
cmd=imgread kernel recovery ${loadaddr} 0; bootm ${loadaddr};
arg=${bootargs}


Old bootconfig.txt:

default=3
details=0
timeout=2
fb_pos=100,400
fb_size=1080,300
[BuildIn Slot 1]
cmd=ext4load mmc 1:5 1080000 /boot/kernel.img;bootm;
arg=${bootargs} logo=osd0,loaded,0x7f800000 vout=1080p50hz,enable hdmimode=1080p50hz fb_width=1280 fb_height=720 panel_type=lcd_4
[BuildIn Slot 2]
cmd=ext4load mmc 1:6 1080000 /boot/kernel.img;bootm;
arg=${bootargs} logo=osd0,loaded,0x7f800000 vout=1080p50hz,enable hdmimode=1080p50hz fb_width=1280 fb_height=720 panel_type=lcd_4
[BuildIn Slot 3]
cmd=ext4load mmc 1:7 1080000 /boot/kernel.img;bootm;
arg=${bootargs} logo=osd0,loaded,0x7f800000 vout=1080p50hz,enable hdmimode=1080p50hz fb_width=1280 fb_height=720 panel_type=lcd_4
[ Recovery ]
cmd=imgread kernel recovery ${loadaddr} 0; bootm ${loadaddr};
arg=${bootargs} logo=osd0,loaded,0x7f800000 vout=1080p50hz,enable hdmimode=1080p50hz fb_width=1280 fb_height=720 panel_type=lcd_4

[frankviana]

I think need now update the "bootargs" using 4 slots and discovery this address: loaded,0x7f800000

[frankviana]

Waiting for OpenATV update using new partition tables: 4 slots + recovery.

Der Dateianhang 1_0_1_EBC0_75E_75E_B530000_0_0_0_20231111115932.jpg existiert nicht mehr.

After update this options, need reflash or only a opkg upgrade?