Search results

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

I'm working at it

I think you can directly wrote; cp -f /boot/STARTUP_RECOVERY /boot/STARTUP ; reboot

you need to start flashing always from slot0... download error is download error... try different image or double check that the downloaded file is good

It is partially compatible, if your box have just an usb stick it should work for daily use. if you have both an hdd and a stick then some guest images crash on start because they don't recognize a slot in /dev/sdb1. we need the team accept the solution and start modifying their images.

i cant reproduce the issue on vusolo4k..

maybe we can discuss later/in another thread... this is the default current behaviour and is outside the scope of this project

Atv Version?

Pli fixed in v0.2.2. boot into recovery and update

which box? wich kexec-multiboot version? how many devices you have? the STARTUP_RECOVERY have to be on the first partition of the usb disk

no serve se vuoi provare un altra immagine senza dover reinstallare da capo. provi non ti piace butti via

published v.0.2.1 now is quite usable it works on duo4k/se and zero4k but to change slot you need an usb stick with a magic file vuplus, and vti should work now

va bene anche telnet o ssh... quello che riesci

se sai come si fa, hai modo di provare a collegarti con putty al box e digitare i seguenti comandi? opkg update opkg upgrade e incolli qui l'output?