Hi again,

i solved my probleme, i was coming from my swap partition.
As explained here, recalbox expect to have 3 partitions : / in the middle, /boot first, and /share last (). So with my swap partition, boot was not mounted and recalbox-boot.conf not available of course.

So here is my new setup

sda (ssd)
sda1 500M BOOT
sda2 5G RECALBOX
sda4 55G archlinux

sdb (hd)
sdb1 500G SHARE

the systemd-boot entrie for recalbox

title recalbox
linux /bzImage
initrd /initrd.gz
options root=UUID=[UUID] rw label=RECALBOX

and my /boot/recalbox-boot.conf

sharedevice=DEV [UUID]
sharewait=30

every thing is running well now, with no hack at all

Hi,

I'm new with recalbox but not with linux. i'm trying to installe recalbox in dual boot with archlinux booting with systemd-boot.
I have a few questions and i wanted to know what you think about it, if it will stand on the long run.

The box is a vorke v1 with a 64Go ssd and a 500Go hd
I installed the systems on the ssd, and used the hd as storage for roms

Partitionning (labels are important) :

sda (ssd)
sda1 500M BOOT
sda2 4G swap
sda3 20G RECALBOX
sda4 35G archlinux

sdb (hd)
sdb1 500G DATA

First I installed archlinux as usual, mounting the boot partition in /boot and installing systemd-boot as bootloader (https://wiki.archlinux.org/index.php/Systemd-boot)

Then i flashed an usbkey with the recalbox x86_64 img, pluged it in the vorke (sdc), and dd the main partition on sda3
dd if=/dev/sdc2 of=/dev/sda3 bs=4M status="progress"

Then i mounted the recalbox boot partition, copied bzImage and initrd.gz over to /boot and added an entry on systemd-boot /boot/loader/entries/recalbox.conf

title recalbox
linux /bzImage
initrd /initrd.gz
options root=UUID=...... rw label=RECALBOX sharewait=30

and finally i selected DATA as storage through recalbox interface

my two problems for now :
1 recalbox don't want to record my hd DATA as storage media, event with sharewait option
2 boot partition is not mounted on /boot and i can't figure out yet why

what do you think ?