Search results

If it hung with starting enigma the issue is in enigma, which slot? Which image is hanging? Please attach the debug log.

Just flashing the stock kernel should be enough to restore the slot0. Just removinv oldroot or newroot with FTP could bring nefast results Try to paste the output of blkid command

The slot0 is special and have kernel=zImage (without the slot directory)

it seems that ofgwrite failed, then it left mount the /newroot file system... however the posted log doesn't have the error in ofgwrite. you should do a box reboot, then init 2 enigma2 and after that start flashing..

Started few tests doesn't mean that I have something working . Vusolo2 status: -Kernel build with Kexec support, flashed.. -Rebooted box... Soft bricked. -Rebuilt and reflashed more and more time the ramdisk... Kexec doesn't like the missing of device tree on these boxes doesn't start -patched...

This seems to be an error of ofgwrite....since. The previous flashing failed it didn't cleanup it's environment

Can't tell you what the error is..in this case probably is better to do: init 2 enigma2 So you will se the verbose output of enigma. I'm interested by the output o ofgwrite

started few tests on solo2

just updated to v0.2.4.. i did a mistake with the installer script and the SystemInfo.py was copied to the wrong path. Sorry

You can see the source on GitHub...

Component, not converter.

Ok I can see that now you have the extra slot. About the crash, It seems that the System info.py files havent been updated correctly. Will check. It seems that it doesn't read the following change: https://github.com/BlackHole/enigma2/commit/8a3ae673dc835b981501c8af09e0adabc99ba7a0 Will check...

Digit mount And paste the output Aaaaahhhh The startup_4 must be at the same level of other startup files... Not on usb

The device name in the startup match the one you have in the mount output? You have the kexec multiboot 0.2.3? You are installing into the usb from the recovery?

It seems the installer replaced the obh plugin file, while the backup replaced an old version of SystemInfo.py file in /usr/lib/enigma2/Components. I don't know why it happen, but it should explain that reinstalling kexec-multiboot fixed... Because it restore some python files needed

Digit the command mount And paste the output. Maybe you usb device is not mounted or recognized as another device (es /dev/sdb1 or /dev/sdc1)

At the moment is not so user friendly yet. If your usb is ext3 or ext4 formatted it should be ok. You have to check if the decoder locate it as sda1 or sdb1. You have to create a new startup file in the root directory of your decoder. You should name it with a consecutive number after the...

Maybe if kexec multiboot would work on mipsel coul we consider for these boxes a recovery in flash and all slot on usb?

I have to check the size of the kernel partition, if the kernel+initrd will fit. But there are difficulties... Kexec on mipsel had issue in the past. It will need time.

si potrà installare in flash e su usb, ed è più veloce di omb