Recently I acquired a Fujitsu Futro S740. Its sold as a thinclient, but is technically a full blown pc with a small SSD (8 or 16GB). I replaced it with a M.2 2280 B+M Key SSD and planned to use it as “Retrostation”. I tried recalbox, however the S740 only allows GPT/EFI boot, there is no legacy mode anymore. So I tried batocera. It boots well from the USB Stick but after installing to the SSD from the Menu it doesn’t boot.
You can fix this by booting a Live Linux Distribution of your choice. I used Ubuntu MATE, can be downloaded here and burned to an USB Flashdrive. Afterwards boot with the USB Flashdrive and then you just register it to the BIOS via Terminal:
efibootmgr -c -d /dev/sda -p 1 -L "Batocera" -l '\EFI\BOOT\bootx64.efi'The command won’t work from within Batocera, using a bootable linux of an USB stick is mandatory.
Reboot and have fun.
Hi,
could you give me more information for the terminal command?
efibootmgr -c -d /dev/sda -p 1 -L “Batocera” -l ‘\EFI\BOOT\bootx64.efi’
I got an error after enterimg this -> command not found.
Do you create an extra partition for EFI or rename the Batocera partition to this “efi system partition” label?
Hello,
efibootmgr is not part of batocera. You’ve to boot for ex. Ubuntu or any other linux dist you like via USB to execute the command. Additionally you should mark the Partition with GParted, as the post mentions.
I renamed the partition because some BIOS/EFI require this to be named correctly. This is documented on batocera wiki as well.
Hope this helps!
Cheers
Hi,
I tried Fujitsu Futro S740 8GB memory + 16GB SDD with Batocera from USB stick booting, but is was not working. UI came up, but running a game did not work. As you provided how to boot from SSD I changed this also and was booting from SDD(thanks for the commands), but same issue, games are not running, I just get the first screen to start the game.
Is there anything to change in bios or settings? Linux system is in general is running, I can switch to console, but it seems the UI is somehow frozen.
Recalbox from USB stick booting was fine. Games can be started without any changes applied. (never tried to boot Recalbox from SSD).
I’m not having any issues. Have you installed latest BIOS and disabled SGX + set Graphics to MAX?
Sometimes I’ve to switch source on tv from hdmi away and back again.
Which games are you trying to run?
Yes, latest Bios was installed.
Now also disabled SGX + Graphics to MAX. Still no success.
I have tried to start first game in C64 which was already on. “Fix It Felix Jr” was the game.
Tried also some Nintendo games already on it, did not work.
Never had Batocera before running on my Pi, just wanted to switch from Recalbox which was running fine on Pi to Batocera. So maybe best to go back to Recalbox.
Sounds strange to me. Batocera v35? Works absolutely flawless on mine.
Recalbox won’t work with the guides provided as it boots MBR and the S740 only supports EFI.
Now I reset Bios to default and did not change anything.
Tried with latest greatest Batocera v35 20220917. Booting from USB stick worked, starting default games which comes with Batocera did not work.
Also tried with latest greates Recalbox 8.1.1. Booting from USB stick worked, starting of some default games worked. No changes applied, worked out of the box.
Next I will analyse logs and try to get support from Batocera team.
Same for me, Batocera not working on Futro S740. Booting ok, but stuck as soon as i launch a game. Any further ideas?
I think you (Dom and mhmuc) should try batocera v34 not v35. Thats what I wrote the guide for and updated to v35 afterwards. I think this is not an issue of the Futro.
Hi, tried v34, unfortunately same behavior
Solution for Futro S740:
Connect to a Monitor with sound (HDMI). I connected to DP Monitor without sound – then it stucks when loading a game. Connecting to my TV with HDMI and sound – everything is ok.
Additionally – disable SGX in Futro BIOS makes booting Batocera 20x faster.
A few seconds instead of 2-3 minutes
Thanks for the update. I do use DP to HDMI on my TV, so I didn’t had that issue.
Thanks for your hints. Now it is also working for me. Had the same issue with a monitor without sound. Now connected to television with SGX disabled, bootup is really fast and games can be played. Will try to use Batocera as an replacement for my Recalbox Pi.
Still strange, when connected to monitor without sound, bootup takes up to some minutes.
You guys may try latest BIOS which has been released on 14th of October 2022.
“V5.0.0.13 – R1.13.0”
“Fix: Non-Existent audio output was available”
I have been using an internal SSD to run Batocera v36 for about 9 months. I created two partitions on my SDD to host the /boot and /userdata partitions and used dd to copy the partitions from my v36 boot USB to the HDD partitions. This worked well until I updated from v36 to v37 – I then had the boot disk not found issue from my Dell UEFI bios boot sequence. I was able to boot from a new v37 USB (which also uses the v36 /userdata partition somehow) and tried setting boot flags on the new v37 non-booting SSD partition – but it did not work. I have a feeling it is related to the label you set in your efibootmgr example which I will fiddle with next time. In the end I just did a dd of the v37 USB /boot partition to the SSD /boot partition and that fixed the issue.
Hello Mark,
I can not confirm loosing the boot entry on Futro S740 after update from v36 to v37.
I removed the advisory changing the flags on the partition, its not necessary. You can just run the EFI Bootmanager command. The Label is only for EFI Boot Entry and has no impact on booting.
However if you change partitions you need to make sure -p matches the boot partition.
Cheers
Thank you for the additional help. I did a bit more digging and I was able to define a UEFI boot entry directly in the Dell BIOS setup by searching the Batocera boot partition for the bootx64.efi file. Once I did this, I was able to boot the upgraded partition without dd’ing it first. I still suspect there is something not quite right about how the Batocera upgrade no longer boots using the old UEFI boot entry, but the fix to create a new BIOS entry is trivial (and there is less possibility of error than resorting to dd!)