Search results

I'm not sure I will have success with mipsel. I need to get kexec working. However it take a lot of effort

Update on mipsel: - vusolo2: kexec don't work with 3.13 kernel - vusolo2: tried to boot a 5.19 kernel, flash not recognized - vuzero: tried to boot a 5.19 kernel, flash not recognized, modified some stuff, flash now is recognized, but partitions not... Notes: the 5.19 kernel couldn't be used...

This isn't the final solution yet. Is still an hack so I wouldn't spend to much time on a work in progress solution

I was trying to get the TFT of my vuultimo4k to be active while booting the slot.. the idea was to show "booting slot X" I spent lot of time but I'm unable to get it to wake on.

if with the first method you mean the echo xxxx > STARTUP, is outdated.

Blackhole menu never supported multiboot. If someone will develop a plugin I can try to inject it from the multiboot itself. About the kernel overritten, blackhole have by default openmultiboot... probably you messed with the omb menu.

that patches are already included in the binary provided with this installer package It happens if you have usb slots slot["kernel"] = "%sp%s" % (device.split("p")[0], int(device.split("p")[1]) - 1) the string that they are trying to split /dev/mmcblk0p? as you can see they are trying to...

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