@pitch64 Fantastic, thanks for confirming!

I still can't get it to work. I bought a different Bluetooth Stick (CSL nano V4), but same result: it finds the controller as "Pro controller", when selected it says "in progress" for a long time until the controller stops his pairing mode. Then it takes even some time for the message "unable to pair controller to appear.

I'm totally out of ideas. (said so before, I know)

@bemandrill To disable ertm it is easier to change the value of the line in recalbox.conf:
controllers.bluetooth.ertm=1

to

controllers.bluetooth.ertm=0

@Zing i tried that one it works, i'll just use it

@gfisher Actually I was looking for it myself a few hour ago 🙂

@Zing Thanks for the help/direction. I will give it a try and report back as soon as I can.

@Zing Thats okay bud. I appreciate your efforts all the same.

Thanks again.

Dell seems to have made the leap of faith and did away with legacy boot.

From what you are saying, the problem is the BIOS incompatibility, so if there is any solution, it is the one you mentioned yourself:

Suggestions exist on how to "hack" GRUB to force the system to boot seems to exist

I may be mistaken, but it will be difficult for someone to help you in this case, you have already found the source of the problem and a possible solution, there is no more that can be done ...

@the_clansman_fr version téléchargée sur notre site ?

Quelle marque de carte SD ?

@nindzaki please don't post any link to copyrighted content

Bonjour,

Je relance ce topic car j'ai exactement le même problème. J'ai flashé un dd avec la 6.1.1, le premier boot se passe parfaitement puis le second reste bloqué a l’écran de démarrage.
En mode verbose, j'ai le message d'erreur suivant: xinit: giving up xinit: unable to connect to x server

J'utilise un HP hp t610 thin client - APU T56N AMD avec carte graphique Radeon HD 6320

J'ai essaye de flasher la version x86 et x64, même résultats...

@beatlesdbp Your pi boy came with a pre installed version as you said (with roms which is illegal by the way, as it the reselling/commercial use of recalbox and most if not all emulators).

There is no way to know what this os is exactly, how much customization was applied to it, or even what version of recalbox it really uses, and what they possible broke.

There is no support on this forum and/or from the dev team for such versions, as there is already more than enough work on the official version support

So if you want help, you need to install the official version, at the risk of your piboy not working anymore if your vendor/builder heavily modified things without documenting them.

ARGH!

thanks for the update 😉

I put my old odroid XU4 back on, it still has an old recalbox install from november 2016 and it works with the nfs mount like this :

sharedevice=NETWORK sharenetwork_nfs1=SHARE@192.168.1.82:/export/Recalbox

Can't understand why it doesn't with the latest recalbox version.

@oyyodams said in Unable to "save config", no update available, etc...:

Oui ton problème est là.

Bon !

Je confirme que les systèmes, malgré l'intelligence artificielle qui progresse et qui atteindra probablement un jour la singularité technologique qui signera la fin de l'humanité, ont pour le moment d'un DNS pour savoir comment traduire un nom de domaine 🙂

Plus sérieusement, en ajoutant un DNS dans le fichier /etc/resolv.conf, le script demandé donne une meilleur résultat :

COMMAND=canupgrade [[ -z canupgrade ]] BINDIR=/recalbox/scripts/upgrade/ SYSTEMSETTINGS='python /usr/lib/python2.7/site-packages/configgen/settings/recalboxSettings.pyc' RECALBOX_SYSTEM_DIR=/recalbox/share/system
++ cat /recalbox/recalbox.version INSTALLED_VERSION=18.03.30
++ cat /recalbox/recalbox.arch ARCH=rpi3
++ python /usr/lib/python2.7/site-packages/configgen/settings/recalboxSettings.pyc -command load -key updates.type UPGRADETYPE=stable SERVICE_URL=https://recaleur-archive-prod.recalbox.com:9443
++ /recalbox/scripts/upgrade//../system/uuid.sh --uuid-file /recalbox/share/system/uuid UUID=8be1dd7f-d418-4866-aaad-c912137a8291 [[ stable == \b\e\t\a ]] [[ stable == \u\n\s\t\a\b\l\e ]] '[' canupgrade == canupgrade ']' [[ stable == \s\t\a\b\l\e ]] /recalbox/scripts/upgrade//recalbox-canupgrade.sh --from-version 18.03.30 --service-url https://recaleur-archive-prod.recalbox.com:9443 --arch rpi3 --uuid 8be1dd7f-d418-4866-aaad-c912137a8291
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 36 100 36 0 0 38 0 --:--:-- --:--:-- --:--:-- 44
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 9 100 9 0 0 9 0 0:00:01 --:--:-- 0:00:01 11
https://lb-archive-prod.recalbox.com exit 0

Mais :

toujours pas d'update et toujours le problème de sauvegarde impossible des paramètres.

Allez, zou, ne perdons pas plus de temps : je réinstalle tout propre.

En revanche... il faudra bien, amha, mettre un DNS dans la couche réseau, sinon elle aura du mal à faire son job : ne manque-t-il pas quelque chose dans la procédure indiquée ici ? On fixe l'@IP, le masque, la passerelle, mais... pas le(s) DNS. Mais je me trompe peut-être ?

Merci en tous cas 🙂