HJ Jansen

The file " 40_custom" in the grub menu then looked like this (this worked before I entered developer mode and before I enabled Andoid Subsystem): menuentry "Fydeos" { set root='(hd0,6)' set img=/fydeos/fydeos_dual_boot.img search --label --set root FYDEOS-DUAL-BOOT loopback loopdev $img linux (loopdev,gpt12)/syslinux/vmlinuz.A init=/sbin/init root=/dev/sda6 boot=local rootwait noresume noswap ro loglevel=7 console= i915.modeset=1 cros_efi fydeos_dualboot initrd /boot/dual_boot_ramfs.cpio } After...

Note that I tried this. And it worked. Until it didn't work anymore. What happens is: you make an entry for Fydeos in the Efi-partition. This entry will do. Or you can make it easier, skipping the multi-boot. However, when you do either of two things on Fydeos the efi partition information will be altered by Fydeos itself. And when the grub-information is still the same and doesn't change, strange things will happen to your system. So when does this happen: a. When you enter "developer mode" in Fydeos...

Note that I tried this. And it worked. Until it didn't work anymore. What happens is: you make an entry for Fydeos in the Efi-partition. This entry will do. Or you can make it easier, skipping the multi-boot. However, when you do either of two things on Fydeos the efi partition information will be altered by Fydeos itself. And when the grub-information is still the same and doesn't change, strange things will happen to your system. So when does this happen: a. When you enter "developer mode" in Fydeos...