Code:
kernel=/linuxrootfs4/zImage root=/dev/sdb1 rootsubdir=linuxrootfs4
Vu+ Real Multiboot Now Available
- Thread starter Ev0
- Start date
Helo
I installed openbh-5.1.012 in flash and did only the basic settings, then I installed kexec-multiboot, the receiver restarts and I insert the usb with the backup image and start installing the backup image in partition 1, after that Enigma crashes, I tried several clean images but the same thing happens, receiver vu duo 4k se and solo 4k. However, on solo 4k, the first version of kexec-multiboot works without problems. Where am I going wrong with this new version of kexec-multiboot
I installed openbh-5.1.012 in flash and did only the basic settings, then I installed kexec-multiboot, the receiver restarts and I insert the usb with the backup image and start installing the backup image in partition 1, after that Enigma crashes, I tried several clean images but the same thing happens, receiver vu duo 4k se and solo 4k. However, on solo 4k, the first version of kexec-multiboot works without problems. Where am I going wrong with this new version of kexec-multiboot
Attachments
Last edited:
essencestudios1956
Member
The same problem with vu duo 4k instead I solved the problem by first installing kexec-multiboot-duo4k-v0.2.2.zip reboot and then I installed kexec-multiboot-duo4k-v0.2.3.zip and it no longer crashes enigma2
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)
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
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?@Liquid
The flash drive was mounted because I have picon and config on it and camd for oscam and everything else worked I gave up for now, I guess I'll wait for the final version
I also did that on solo 4k, did I have the old version, but for duo 4k there is no old version
Digit
Code:
mountAaaaahhhh
The startup_4 must be at the same level of other startup files... Not on usb
darog69
Active member
As I have dealt with the slots, now I have a crashlog when installing the image to STARTUP_1
Welcome to openbh for vuultimo4k openbh 5.1 vuultimo4k vuultimo4k login: root Password: clear root@vuultimo4k: clear [H[Jroot@vuultimo4k: m o u n t rootfs on / type rootfs (rw) /dev/mmcblk0p4 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 type tmpfs (rw,relatime) tmpfs on /proc/cmdline type tmpfs (rw,relatime) /dev/mmcblk0p4 on /boot type ext4 (rw,relatime,data=ordered) devtmpfs on /dev type devtmpfs (rw,relatime,size=800752k,nr_inodes=85500,mode=755) tmpfs on /media type tmpfs (rw,relatime,size=64k) /dev/sda1 on /media/hdd type ext4 (rw,relatime,data=ordered) /dev/sdb1 on /media/usb type ext4 (rw,relatime,data=ordered) debugfs on /sys/kernel/debug type debugfs (rw,relatime) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) /etc/auto.network on /media/autofs type autofs (rw,relatime,fd=6,pgrp=2133,timeout=5,minproto=5,maxproto=5,indirect) root@vuultimo4k
I can't use a spoiler or insert a crashlog file, so I'm providing a link
Crashlog
Welcome to openbh for vuultimo4k openbh 5.1 vuultimo4k vuultimo4k login: root Password: clear root@vuultimo4k: clear [H[Jroot@vuultimo4k: m o u n t rootfs on / type rootfs (rw) /dev/mmcblk0p4 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 type tmpfs (rw,relatime) tmpfs on /proc/cmdline type tmpfs (rw,relatime) /dev/mmcblk0p4 on /boot type ext4 (rw,relatime,data=ordered) devtmpfs on /dev type devtmpfs (rw,relatime,size=800752k,nr_inodes=85500,mode=755) tmpfs on /media type tmpfs (rw,relatime,size=64k) /dev/sda1 on /media/hdd type ext4 (rw,relatime,data=ordered) /dev/sdb1 on /media/usb type ext4 (rw,relatime,data=ordered) debugfs on /sys/kernel/debug type debugfs (rw,relatime) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) /etc/auto.network on /media/autofs type autofs (rw,relatime,fd=6,pgrp=2133,timeout=5,minproto=5,maxproto=5,indirect) root@vuultimo4k
I can't use a spoiler or insert a crashlog file, so I'm providing a link
Crashlog
Attachments
Last edited:
You have to flash the slot from Recovery Image!
So:
1) boot to recovery image
2) Flash the slot from OpenBh 5.1.012 ( recovery image )
You must allways install from recovery image!
MENU > STANDBY & RESTART > RECOVERY MODE
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 later or tomorrow
Component, not converter.
Last edited: