@oyyodams said in v6 - roms + kodi won't start when samba share activated:

/recalbox/scripts/recalbox-support.sh

Damn ! thanks !

I ran the script. It failed and the last line was

/recalbox/scripts/recalbox-support.sh: line 116: /recalbox/share/saves/recalbox-support-20190514153203.tar.gz: Permission denied

The share/save folder didn't have the writing permission on for guest.

Kodi and Games run fine now. So thanks for the tip :D

However, maybe some more logging could be made available for more self diagnose? Maybe it's somewhere else and I didn't look properly.

Cheers

It works after having deleted all gamelist file...

some other error log found on es folder

es_launch_stdout.log
Powering on HDMI with explicit settings (CEA mode 4)
Powering on HDMI with preferred settings
/usr/bin/retroarch -L /usr/lib/libretro/fbalpha_libretro.so --config /recalbox/share/system/configs/retroarch/retroarchcustom.cfg /recalbox/share/roms/fba_libretro/gunbird2.zip
running command: /usr/bin/retroarch -L /usr/lib/libretro/fbalpha_libretro.so --config /recalbox/share/system/configs/retroarch/retroarchcustom.cfg /recalbox/share/roms/fba_libretro/gunbird2.zip
mkdir(/recalbox/share_init/cheats/cht/FB Alpha/) error: Read-only file system.
Failed to create directory: "/recalbox/share_init/cheats/cht/FB Alpha/".
mkdir(/recalbox/share_init/cheats/cht/FB Alpha/) error: Read-only file system.
Failed to create directory: "/recalbox/share_init/cheats/cht/FB Alpha/".

and in es_launch_stderr.log
ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory

Would that means something for you ?

@soundmanx2 To find out all systems that need BIOS, read the Wiki:
https://github.com/recalbox/recalbox-os/wiki/Add-system-bios-(EN)
Inside each emulator folder, there is a .txt file that tells you the correct ROMS format and tells you if you need a BIOS.
About SNES ... have you tried changing the emulator / emulation core?

@leosabino Upgrade to the latest stable version (currently Recalbox 6.0 Dragonblaze):
https://archive.recalbox.com/
You will have to back up your files and start from a clean install because the updater will not be able to upgrade from such an old version (there were many changes).
After that, test and return here to say if it solved.

@mrayzarc
Maybe the german versions have copy-protection and that's why they do not work?
For some games, that have LibCrypt protection, you need the corresponding .sbi files
https://github.com/recalbox/recalbox-os/wiki/Definitive-PSX-Guide-(EN)
https://retropie.org.uk/forum/topic/2970/psx-games-with-lybcript

Bonjour @Micman @Scavy @voljega

ce site est une bible sur l'amiga : http://hol.abime.net/hol_search.php
et certains jeux ont le manuel de disponible, téléchargeable au format zip, peut être que ça peut aider.

@schattenwesen could you please open an issue reporting this problem here:

https://gitlab.com/recalbox/recalbox/issues

Please, try to be precise and only explain ehat’s happening.

I leave the information here if somebody has the same issue:

FIXED turning off 'service mode' on 'dip switches' from the mame menu in that screen.

Next time I'll give more information, sorry!

@zing yep, it will more be an issue of drivers (and linux kernel I suppose) than anything else.
What I meant is that, contrary to arm board it doesn't require any porting or specific development, at least theorically, and has a better chance of beeing supported by recalbox one day than any arm board

@mattmame i don't see any bios for gamecube in recalbox needings. Do i need it? Which is the filename?

@sebastien-brossard "en remontant / en écriture" mount -o remount, rw /

@cristiano-marçal said in Some issue after start Pi 3B + Recalbox with PS3 Sixaxis:

It's normal with the Official driver not turn on the 1 led and still flashing, even after pairs?

Thank chinese controllers manufacturers that partly changed the protocol. If they had properly reversed engineered the sixaxis protocol and not change some parts, they'd work flawlessly

@chris27 Dans le jeu rentre dans retroarch en faisant hotkey+a (croix avec ta manette ps4) puis vas dans control et regarde à quoi la touche start est attribuée.
Reconfigure si besoin.

Mais effectivement c’est chelou. La manette ps4 est reconnue et configurée directement normalement. Et par défaut le bouton start est le bouton option si je n’m’abuse.

Ça fonctionne bien avec un autre périphérique usb sinon?

@gaetan thank you very much to ask a so noob question. I put some roms and it work. Thanks for the patiance.

Regards.

@zing Yeah a clean install did the trick. No issues whatsoever. Thanks!