592 replies to this topic

[Huevos]

SRC_URI = " \
	file://kernel_auto.bin \
	file://STARTUP_cpio.bin \
"

S="${WORKDIR}/vuplus-kexec-${MACHINE}"

do_install() {
	install -d ${D}${bindir}
	install -m 0755 ${S}/kernel_auto.bin ${D}${bindir}/kernel_auto.bin
	install -m 0755 ${S}/STARTUP_cpio.bin ${D}${bindir}/STARTUP.cpio.gz

Maybe this SRC_URI wrong?

 

https://github.com/o...6b9522858R9-R20

[neo]

Has been addressed.

[Dimitrij]

I'll ask again. You can get detailed instructions on how to get out of the installed image without multibut support, for example, openATV.

 

The file system of a flash drive / disk and what's next ...

So far, I get only through the firmware of the original /vuplus/duo4k/kernel_auto.bin(not support kexes).

Edited by Dimitrij, 6 April 2023 - 05:32.

[Huevos]

I'll ask again. You can get detailed instructions on how to get out of the installed image without multibut support, for example, openATV.

 

The file system of a flash drive / disk and what's next ...

So far, I get only through the firmware of the original /vuplus/duo4k/kernel_auto.bin(not support kexes).

I don't understand this question.

[Dimitrij]

This is the only thing that helps me

 

If the STARTUP_RECOVERY isn't enough to recover your slot0, you can flash a kernel aligned to your slot0 sing an usb stick usb (vuplus/boxname/kernel_auto.bin)..if you don't put the rootfs it just flash the kernel.

 

 

STARTUP_RECOVERY does not help, the current image is always loaded.

[cobus]

 

When will the first version be ready to try?

 

I will restart the develop build in a minute. So when that build is finished .

 

Thanks
 

 

 

[littlesat]

The enigma2 part of 8.3 is merged... but as far I can see there is no bsp part merged yet on stable 8.3.

[neo]

That is not needed, the only requirement was the ability to select another slot. Not to be able to flash 8.3-release as the "slot 0" image.

[Dimitrij]

That is not needed, the only requirement was the ability to select another slot. Not to be able to flash 8.3-release as the "slot 0" image.

Please update ofgwrite for 8.3

https://github.com/O...orefs.conf#L176

-SRCREV_pn-ofgwrite ??= "f45fe98197a0c34f4011878d2f5978e6e67dea7c"
+SRCREV_pn-ofgwrite ??= "07e156f2064a9b6d5d15b0773be85ea8221af54d"

 

[Huevos]

@Dimitrij, have you successfully flashed PLi to slot 0? Did you have any problems?

[neo]

Please update ofgwrite for 8.3

 

https://github.com/O...orefs.conf#L176

-SRCREV_pn-ofgwrite ??= "f45fe98197a0c34f4011878d2f5978e6e67dea7c"
+SRCREV_pn-ofgwrite ??= "07e156f2064a9b6d5d15b0773be85ea8221af54d"

 

Done.
 

[Dimitrij]

@Dimitrij, have you successfully flashed PLi to slot 0? Did you have any problems?

Not any problem.Add multiboot in openPLi develop.

Install in  slot 1 openATV

Install in  slot 2 openPLi 8.3

 

I connected a USB flash drive (I tried different ones, including with different file systems).

Add file STARTUP_RECOVERY in to the root of the flash drive.

Welcome to openATV for vuduo4k
openatv 7.2 vuduo4k

vuduo4k login: root
Password:
root@vuduo4k:~# mount
/dev/mmcblk0p9 on /boot type ext4 (rw,relatime,data=ordered)
/dev/mmcblk0p9 on / type ext4 (rw,relatime,data=ordered)
tmpfs on /var/volatile type tmpfs (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
proc on /proc type proc (rw,relatime)
tmpfs on /sys/firmware/devicetree/base/chosen/bootargs type tmpfs (rw,relatime)
tmpfs on /proc/cmdline type tmpfs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=274560k,nr_inodes=26641,mode=755)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /media type tmpfs (rw,relatime,size=64k)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
/dev/sda1 on /media/hdd type ext4 (rw,relatime,data=ordered)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/etc/auto.network on /media/autofs type autofs (rw,relatime,fd=6,pgrp=1810,timeout=5,minproto=5,maxproto=5,indirect)
root@vuduo4k:~# ls -la /media/hdd/
drwxr-xr-x    5 root     root          4096 Apr  6 20:14 .
drwxrwxrwt    4 root     root            80 Apr  6 20:20 ..
-rw-r--r--    1 root     root             0 Apr  6 20:14 STARTUP_RECOVERY
drwx------    2 root     root         16384 Apr  6 20:00 lost+found
drwxr-xr-x    2 root     root          4096 Apr  6 20:06 movie
drwxr-xr-x    2 root     root          4096 Apr  6 20:06 timeshift
root@vuduo4k:~#

 

Power off box.

Boot again openATV.

KEXEC-1ST STAGE: /dev/sda is not a block device... skip
KEXEC-1ST STAGE: /dev/sda1 is not a block device... skip
KEXEC-1ST STAGE: /dev/sdb is not a block device... skip
KEXEC-1ST STAGE: /dev/sdb1 is not a block device... skip
KEXEC-1ST STAGE: /dev/sdc is not a block device... skip
KEXEC-1ST STAGE: /dev/sdc1 is not a block device... skip
KEXEC-1ST STAGE: /dev/scdd is not a block device... skip
KEXEC-1ST STAGE: /dev/sdd1 is not a block device... skip
KEXEC-1ST STAGE: loading STARTUP from /dev/mmcblk0p9...
KEXEC-1ST STAGE: STARTUP: kernel=/linuxrootfs1/zImage root=/dev/mmcblk0p9 rootsubdir=linuxrootfs1
KEXEC-1ST STAGE: Found kernel /linuxrootfs1/zImage
KEXEC-1ST STAGE: Found root /dev/mmcblk0p9
KEXEC-1ST STAGE: Found rootsubdir /linuxrootfs1
KEXEC-1ST STAGE: WAITING

KEXEC-1ST STAGE: ##############################################################################
KEXEC-1ST STAGE: booting kernel: /newroot//linuxrootfs1/zImage
KEXEC-1ST STAGE: booting initrd: /newroot/STARTUP.cpio.gz
KEXEC-1ST STAGE: ##############################################################################
KEXEC-2ND STAGE: loading STARTUP from /dev/mmcblk0p9...
KEXEC-2ND STAGE: STARTUP: kernel=/linuxrootfs1/zImage root=/dev/mmcblk0p9 rootsubdir=linuxrootfs1
KEXEC-2ND STAGE: Found kernel /linuxrootfs1/zImage
KEXEC-2ND STAGE: Found root /dev/mmcblk0p9
KEXEC-2ND STAGE: Found rootsubdir linuxrootfs1
KEXEC-2ND STAGE: WAITING
KEXEC-2ND STAGE: Mount bind linuxrootfs1
KEXEC-2ND STAGE: ##############################################################################
KEXEC-2ND STAGE: Hack to override vuplus static cmdline
KEXEC-2ND STAGE: ##############################################################################
KEXEC-2ND STAGE: kernel v4

KEXEC-2ND STAGE: ##############################################################################
KEXEC-2ND STAGE: Mounting /newroot to /newroot_subdir/boot to expose STARTUP_RECOVERY
KEXEC-2ND STAGE: ##############################################################################
KEXEC-2ND STAGE: mount -o move /newroot /newroot_subdir/boot/

 

[dpeddi]

 

@Dimitrij, have you successfully flashed PLi to slot 0? Did you have any problems?

Not any problem.Add multiboot in openPLi develop.

Install in  slot 1 openATV

Install in  slot 2 openPLi 8.3

 

I connected a USB flash drive (I tried different ones, including with different file systems).

Add file STARTUP_RECOVERY in to the root of the flash drive

KEXEC-1ST STAGE: /dev/sda is not a block device... skip
KEXEC-1ST STAGE: /dev/sda1 is not a block device... skip
KEXEC-1ST STAGE: /dev/sdb is not a block device... skip
KEXEC-1ST STAGE: /dev/sdb1 is not a block device... skip
KEXEC-1ST STAGE: /dev/sdc is not a block device... skip
KEXEC-1ST STAGE: /dev/sdc1 is not a block device... skip
KEXEC-1ST STAGE: /dev/scdd is not a block device... skip
KEXEC-1ST STAGE: /dev/sdd1 is not a block device... skip

Kexec multiboot scan just the unpartitioned device and the partitioned from sda to sdd

The device should be  fat formatted..someone reported that ext3 should work.

[Ev0]

 

 

@Dimitrij, have you successfully flashed PLi to slot 0? Did you have any problems?

Not any problem.Add multiboot in openPLi develop.

Install in  slot 1 openATV

Install in  slot 2 openPLi 8.3

 

I connected a USB flash drive (I tried different ones, including with different file systems).

Add file STARTUP_RECOVERY in to the root of the flash drive

KEXEC-1ST STAGE: /dev/sda is not a block device... skip
KEXEC-1ST STAGE: /dev/sda1 is not a block device... skip
KEXEC-1ST STAGE: /dev/sdb is not a block device... skip
KEXEC-1ST STAGE: /dev/sdb1 is not a block device... skip
KEXEC-1ST STAGE: /dev/sdc is not a block device... skip
KEXEC-1ST STAGE: /dev/sdc1 is not a block device... skip
KEXEC-1ST STAGE: /dev/scdd is not a block device... skip
KEXEC-1ST STAGE: /dev/sdd1 is not a block device... skip

Kexec multiboot scan just the unpartitioned device and the partitioned from sda to sdd

The device should be  fat formatted..someone reported that ext3 should work.

 

Fat32 on usb in front of the box or Ext4 on mounted usb or mounted hdd both work for me.

Edited by Ev0, 6 April 2023 - 22:11.

[Abu Baniaz]

Maybe fat32 should be excluded as it is likely going to cause issues with symlinks?

[Ev0]

Maybe fat32 should be excluded as it is likely going to cause issues with symlinks?

What do you mean ?

Fat32 is needed, as most will only need this if the box is stuck on the splash screen due to something they did, in which case they will have no access to ftp the file to the internal hdd or mounted ext4 usb stick.

[Dimitrij]

I tried different flash drives, different file systems, but  always writes 'KEXEC-1ST STAGE: /dev/sda1 is not a block device... skip'.

 

By the way, if you format any flash drive in fat32 and add the /vuplus/duo4k/* folder, then it can be used for firmware.

 

Maybe this is a problem only DUO4K?

Maybe a long delay is needed 5-6 sec?

https://github.com/B...it-kexec.sh#L68

 

What is this parameter?

https://github.com/O...elector.py#L213

Edited by Dimitrij, 7 April 2023 - 05:48.

[Dimitrij]

self["description"].setText(_("Attention - forced loading recovery image!\nCreate an empty STARTUP_RECOVERY at the root of your hard drive and hold the Power button for more than 12 seconds!"))

Please edit the text to make it more understandable.

My english is equal to google translator .
 

[Abu Baniaz]

Maybe fat32 should be excluded as it is likely going to cause issues with symlinks?

What do you mean ?

Fat32 is needed, as most will only need this if the box is stuck on the splash screen due to something they did, in which case they will have no access to ftp the file to the internal hdd or mounted ext4 usb stick.

What happens when a symlink is needed? E.g for openssl.

[Ev0]

I tried different flash drives, different file systems, but  always writes 'KEXEC-1ST STAGE: /dev/sda1 is not a block device... skip'.

 

By the way, if you format any flash drive in fat32 and add the /vuplus/duo4k/* folder, then it can be used for firmware.

 

Maybe this is a problem only DUO4K?

Maybe a long delay is needed 5-6 sec?

https://github.com/B...it-kexec.sh#L68

 

What is this parameter?

https://github.com/O...elector.py#L213

The rootwait, is for when using usb 3.x devices, the Duo4K and Duo4KSE need longer to initialise usb 3.0 ports than usb 2.0