Posts made by Danixu86

@Scavy said in Bios hash in 7.2 are correct?:

@Danixu86 where did you notice the bios changes concerning GB, GBC ?

Hello @Scaivy,

On Recalbox 7.1.1 I have all the bios as correct (green). After upgrading to 7.2 I have noticed that some bios were marked as orange with a CRC error so I have started to search the correct file on internet. After taking a look into Google I have seen that there is no way to find those bios, and the only page where that CRC exists is just the commit where was changed on Recalbox gitlab. Is that why I have this doubt about if they are correct, because on all the sites I have found those files, the crc is the old one (or completly different to both).

Best regards.

Hello,

I have noticed a change in some bios related with GB, and GBC for example, where the hash has changed. Searching on internet for the correct file I have noticed that there is no way to find the new hash file, and the old one is everywhere in at least all the emulators I have seen.

Is the hash correct? (is not critical because still working with the old file).

Best regards.

@Zing Oh, thanks,

I've not received any message and I didn't see your response, sorry. I'll try in Recalbox 7.2 and if still failing I'll post there too.

Thanks again!

Hello @Zing,

Sorry for take so long to test it but I was a bit busy. I've looked into the guide that you sent and I've not found a way to configure the video mode, because I think that the display is a TFT display conected through GPIO ports and then it has no modes. I've tried to get the supported modes but nothing is reported, and I only I'm able to get the resolution:

# tvservice -s
state 0x400000 [LCD], 320x240 @ 0.00Hz, progressive

I've tried some configurations to check if maybe works, but same behaviour. Is there any way to set mode to custom?, because the smallest mode is DMT 4 which has the double of resolution.

Thanks!!

@Zing said in PSX games always freezes on GPi case:

@Danixu86

also the bios report of recalbox is green

If you checked the Recalbox's internal BIOS checker and received a green thumbs up, then your BIOS is not the problem.

Every time the game starts I get the same errors of this thread

Have you tried to set up the videomode?

• https://recalbox.gitbook.io/documentation/tutorials/video/display-configuration/complete-guide-on-video-configuration

I'll take a look to see if I can find the way to make it work.

Thanks!

@Zing said in Audio channels selector in audio menu (Stereo or mono):

@Danixu86 I recommend that you open an issue in gitlab:
https://gitlab.com/recalbox/recalbox/-/issues

Ok, thanks!! I'll do it

Sorry for triple post... I'm not able to edit the above messages.

Looks like I've found the problem, and is related to the way the Safe Shutdown script powers off the RPi.

On the SS script located in /recalbox/system/hardware/case/installers/gpi/assets/recalbox_SafeShutdown_gpi.py there is a line that reboots the RPi when ES is killed:

os.system("reboot -f")

With this the shutdown is much faster because doesn't wait until the SO is ready (is like pressing the reset button, so I don't know if is dangerous), but looks like some things are not saved correctly. Changing this line to the original shutdown command is a bit slower (but much less than retropie ), but all seems to works fine.

os.system("shutdown -h now")

I've tried several times to power off using the Switch to see if fails again, and now seems to be working fine.

I don't know if I have to report this problem on the Gitlab repository...

Best regards.

Hello,

Is strange, because I've took a look into the safe shutdown script and is improved compared to the original script, and this script seems to quit ES first:

                # Tell EmulationStation to quit demo/mode and/or to exit gracefully
                try:
                        import os
                        try:
                                os.makedirs("/tmp/externalnotifications")
                        except: pass
                        with open("/tmp/externalnotifications/emulationstation.quitnow", "w") as sf:
                                sf.write("exit")
                                sfush()
                                sf.close()
                except IOError:
                        pass  # Can't wait or retry

                # Quit emulationstation gracefully
                parent.terminate()
                print("Emulationstation terminated")

So now I'm not sure why is failing and why if I power off the ES manually works, and with the SS script some weird things happen...

Best regards.

Hello!, thanks for your response.

Not really. The safe shutdown button of the back just enable or disable the safe shutdown feature when you switch off the top power button. If it is disabled, the top button just power off the RPi like a normal switch (which can lead to filesystem corruption), but when is enabled (like I have it), it calls an script that must be installed trough a signal to a GPIO pin, and this script executes a "Safe Shutdown" just running the command "shutdown -r now" if I'm not wrong. On Recalbox this script is already installed so I don't have to install it, and I'm sure that is almost working because recalbox is shutted down before the console is powered off.
The problem is that there is something in the method that recalbox is closed that doesn't allow it to save some things, like for example the wifi configuration. Maybe related with linux shutdown method that closes some programs without wait (an example is Chrome, if you have chrome in a linux system opened and you poweroff the computer, linux doesn't wait to Crome to close and just kill it). That's why I was asking if there is any way to close the ES saving its configuration, or at least force it to save it, to modify the "Safe Shutdown" script and run it before the shutdown command.

Thanks!!

Hello,

I write because I don't know what to do to make it work... I've tried a lot of games on the GPi case using the latest version of recalbox (7.1.1). Every time the game starts I get the same errors of this thread:
https://forum.recalbox.com/topic/19155/gpi-case-psx-crash/2

The entire SO is freezed and I have to disconnect the power to shutdown the RPi.

I've searched and in some posts talks about the bios, but I've checked all files hash and is correct (also the bios report of recalbox is green):

# md5sum scph*
dc2b9bf8da62ec93e868cfd29f0d067d  scph1001.bin
6e3735ff4c7dc899ee98981385f6f3d0  scph101.bin
8dd7d5296a650fac7319bce665a6a53c  scph5500.bin
490f666e1afb15b7362b406ed1cea246  scph5501.bin
32736f17079d0b2b7024407c39bd3050  scph5502.bin
1e68c231d0896b7eadcad1d7d8e76129  scph7001.bin

Testing the Supreme GPI V2 I've seen that the pcsx rearmed emulator built in that image works better than I've expected from a RPi Zero, emulating some games that I've tested at full speed. I've tried to copy the binary file and games has started to boot in recalbox, but buttons are not working (surely any integration).

Is there any way to fix this problem?, because the libretro is slow and is impossible to play.

Thanks!

Hello,

I've installed a clean Recalbox 7.1.1 image and after the first boot installation I've entered into Network Settings and I've configured the Wifi connection. Later I've just powered off the GPi case using the switch, and after recalbox boots I've enter into network settings. The wifi is "On" but not connected, and if I disable and reenable the Wifi it connects as usual. If I power off the GPi case using the switch the problem is always there until I enter into the Quit menu and use the "Shutdown System" option. Powering off the console using the Quit menu solve the problem and then the Wifi is activated automatically on next boots. Also the "Fast Shutdown" option seems to works and of course the reboot option.

The same happens if I disconnect the Wifi. I have to power off the console using the menu option at least the first time to save the Wifi status. Of course, I don't know if something else is not saved using the switch, so I'm using always the quit menu.

Best regards.

Hello,

Thank you for your response.

My Recalbox version is 7.1.1. Was installed using the oficial image and is almost clean (I just added some bios and roms, but no much more). Is the latest and was reinstalled a few days ago, but I'll try to create a new one with just the Recalbox clean installation.

Best regards.

Hello,

I've seen that GPi case is configured on downmix mode by default. Is correct because the speaker only uses the right channel and the best is to mix both into mono. The problem comes when I use headphones, the audio still on downmix mode and sounds strange.

For now I'm using this options in /etc/asound.conf:

pcm.monocard{
        slave.pcm "hw:0"
        slave.channels 2
        type route
        ttable {
                # Copy both input channels to output channel 1 (Right).
                0.1 1
                1.1 1
                # Copy both input channels to output channel 0 (Left).
                0.0 1
                1.0 1
        }
}

pcm.stereocard{
        slave.pcm "hw:0"
        slave.channels 2
        type route
        ttable {
                1.1 1
                0.0 1
        }
}

pcm.!default monocard

I change the default route between monocard and stereocard, but is very annoying because I have to connect to the RPi through ssh, mount the root as RW and change that file every time I want to change between modes, so I want to know if is possible to add an option in Audio menu to allow the user to change between mono and stereo sound.

Thanks!

Hello,

I've noticed some problems with the safe shutdown used in the GPi case. When I power off the Recalbox using the console switch, looks like some options are not saved correctly and fails. For example, If I deactivate the Wifi and then I shutdown the console, then on startup the Wifi option is "Off", but the wifi connection is enabled and connected. This doesn't happen if I shutdown the console using the "Shutdown" option in Recalbox and then I power off the switch.

I've seen that the shutdown command in the python script is "shutdown -r now", so I want to know if there is any way to do a normal recalbox shutdown from command line to allow it to save all the options before power off all.

Thanks!!

Hola de nuevo,

Por si ayuda con la solución del problema, he visto que al hacer un "fast shutdown" las configuraciones son obviadas, por ejemplo, subía el volumen del alsamixer y al reiniciar estaba otra vez igual. Teniendo esto en cuenta he decidido probar y efectivamente, tras desactivar el wifi y apagar de forma normal, este no se vuelve a activar de nuevo.

¿Es posible cambiar la ejecución del safe shutdown del rápido al normal al usar el botón de apagado?. Total, el apagado rápido me tarda como el normal, por lo que no me aporta ninguna ventaja y sin embargo muchas desventajas.

Un saludo y gracias.

Hola,

Recientemente he adquirido una caja para las Raspberry Pi Zero: Retroflag GPi. Me he inclinado por Recalbox porque la configuración es mucho más simple y funciona correctamente, pero me he dado cuenta de que la gestión del Wifi no la está haciendo correctamente.
Cuando cambio la opción de Activar Wifi a Off para intentar ahorrar batería, el Estado se mantiene como "Conectado" y sólo desaparece la dirección IP. No sé si esto quiere decir que no se apaga el Wifi lo cual sería un fastidio cuando quieres ahorrar batería.
Dejando de lado eso que quizá es simplemente que no se actualiza el texto del estado, la razón principal por la que escribo es porque tras el reinicio de la consola, el Wifi siempre se activa y se conecta, aunque el botón de Activar Wifi ponga claramente Off. Esto hace que gaste batería innecesariamente si no te interesa que esté activo, y tienes que andar entrando en la configuración de red cada vez que la enciendes para Activar el Wifi y luego Desconectarlo, ya que al estar la opción en Off la primera vez que le das se activa.

Actualmente estoy usando la caja Recalbox GPi como comenté arriba, con una Raspberry Pi Zero W, y la fuente de alimentación es por pilas. La versión de Recalbox que estoy usando es la última, que actualmente es la 7.1.1.

¿Puede ser porque tenga las actualizaciones activas?. EDIT: No parece serlo, porque hace lo mismo al quitar las actualizaciones.

Un saludo.