Is it possible to boot elive on a second disk if I'm on systemd-boot on first linux and my esp is on the first disk ???
I'm quite puzzled since documentation is rather confusing on that aspect of systemd-boot.
I have installed elive on a second disk (on an mmc disk device). All installation went well but I cannot boot on it since on boot it seems the other disk is not there even if it is.
Can I add manually an entry in systemd to "chain load" the Elive on the other disk ???
I haven't figure a way to do so yet. Help appreciated!
Seems like the best ways to boot multiple distros in UEFI mode is by running their own grub themselves, instead of using a single grub for all which can cause many issues booting the other systems (basically they don't knows how to boot them correctly / which boot parameters to use), so the best way to do that is by booting their own grub independently, for example by using a boot manager like refind, which is like a previous-boot system which allows you to pick which os-grub to boot next
the next updates on the elive installer will include installing this software (customized to look better and being more friendly) by default
Yes its a 64G small SD card that was in an old phone as extra memory.
The installation went well with no error message. The SD card is formatted with 3 partitions.
First one the EFI, second one boot, third one a vg with the root and the swap.
I'm not 100% sure how it should be done (my Eeepc died a long time ago) but if at all you'll need a kernel up and running to recognize the SD card, the BIOS/firmware doesn't do that.
I do know that you cannot boot an SD card with normal installation methods so, if at all it'll have to be from EFI on the HD.
The PinebookPro and also Raspberry Pi have their own special way of booting ..... I advise to do a search on that.
Looking at your 'inxi' output from Arch, I do notice that it defines your sd-card as '/dev/sda' where I dpubt that the installed Elive follows the same scheme.
I'm not surprised ..... I think your laptop treats the (second mmc) as a USB device which either requires a running system (kernel) or ... that the BIOS or Firmware recognizes the hardware and is prepared to boot from it.
I'd go with the first option .... get Arch to start booting, recognize the SD card and hand over the boot process from there to that SD card, if possible. Else try using 'chroot".... where both cases will require an adapted kernel in Arch.
I'm sorry that my 'solutions' are only theoretical as I don't have the same hardware nor do I use systemd-boot often enough to practically roubleshoot your issue/question.
I would instead try to install simply on the second disk very "normally" (maybe disconnecting the first hard disk for that) and everytime you boot the computer you press F12 or the equivalent select-boot bios key to select which disk you want to boot from, this should work pretty good IMHO
On the other hand I don't suggest you to install Elive on a SD card, these devices are limited in RW and break soon when installing an OS on them (an OS requires loots of RW all the time), Instead I will suggest to use it as a Live system (just like when you record your USB's, but recording your SD) and enabling persistence on it
The first hard disk is the laptop disk and I'm not in favor of disconnecting anything since the SD card doesn't seem to be seen by the bios at boot time. But I will eventually reinstall Elive on an external disk or USB key. But by the mean time I need to read a bit more on UEFI. I want to understand how it works.
Also on that laptop (Asus Vivobook), I haven't found any way to disable UEFI and activate legacy boot.
It does indeed appear to be a bug, so might be a work around for now.
Methinks it would be good if @PerfMonk (or anyone else with one of these netbooks) enabled reporting the logs when trying an install again. That way we can check if these glitches are 'elive-installer' induced or down to the partitioner itself not working correctly.
Even on the new 'Bullseye' based version, this kind of stuff needs checking.
All things considered, if @e-Solutions is prepared to spend some more time double checking, we could DM a link to the latest Bullseye version download for testing. @e-Solutions just say the word.