Recalbox 6.0 is OUT! Codename: Dragonblaze

[Garu]

@scavy Thanks for your friendly reply! I appreciate it!

[HauruIchidaru]

Hello and thanks guys for the tremendous amount of work ! You are awesome !

I don't know if you have opened a subject on bugs of the 6.0, but I wanted to submit two little problems that I encountered :

• When you set the audio output to "auto", EmulationStation does not play any sound. I switched to "HDMI" and it worked. That leads to the second point...
• MP3 support for custom musics in EmulationStation is broken. I had to convert them to OGG to see if that worked.

(I'm on Pi 3B, I also have a 3B+ and the same problems occurs on it)

If you need the logs, I'll upload them.

[Zing]

@hauruichidaru About the MP3, it is intentional, until there is an entry in the wiki:
https://github.com/recalbox/recalbox-os/wiki/Add-Custom-Music-to-EmulationStation-(EN)

[Alex_123]

Thanks for this new Recalbox version. I like this OS a lot compared to others due to its ease of use and simplicity.

Raspberry 3B+ user

[nwildner]

I'm now a 3B+ user, and i can say this release is awesome. Everything runs clean and smooth, MegaPI case working with latching on/off switch, and found a performance gain on some N64 games. Yay. Only minor issues i had:

• ES crashes if you try to pair a bluetooth device with Wifi disabled. It was a honest mistake right after trying to pair a device on a fresh image install. Maybe a warning that wifi needs to be enable when you try to pair through ES would do the trick
• When using 2 usb Xbox 360 gamepads, and turning on a 3rd PS3 bluetooth controller(already paired), the PS3 controller gets recognized as player 3(and the controller index lights indicate so), but as soon as i select a game, it gets remaped/reindexed as player 1.
• If I configure ES to use static gamelist.xml only to improve load performance(and since i add romsets once), ES will crash.

I can provide further logs if needed

[caxelair]

Hi guys,
Great work my Rpi3b+ thanks you. PS4 controller recognized right away, no major issue with Kodi.
I just face the black screen with the pacman ghosts, recalbox logo when I press F4 to reach the terminal.
Any idea why?

[isaacnailor]

This post is deleted!

[caxelair]

As I can edit my previous message, I've got new issues:

1. Wifi is not working when I "reboot" from Putty. Then I need to manually go into the menu, disable and enable the wifi to have a connected status and get my IP.

2. My 2.4g keyboard is not detected by the RPi. I looked at lsusb and /dev/input/ as mentioned here https://github.com/recalbox/recalbox-os/wiki/Keyboard-encoder-configuration-(EN)
   My keyboard (no name purchased on https://www.aliexpress.com/item/Desxz-Original-H9-2-4G-Mini-Wireless-Game-Keyboard-RGB-Backlit-With-7-Colorful-Backlight-Touchpad/32923551234.html) is not listed here: https://github.com/recalbox/recalbox-os/wiki/Compatibility-(EN) but works with Raspbian/Windows/Android TV...
   Any help?

3. Scrapper doesn't work, it goes back to black screen with pacman ghosts and recalbox logo

[NeXuS]

Hello guys, thank you for this release and for all the good work! I have some problems with N64 though that I never experienced on the older versions. From the gamelist menu, when I run any N64 game, I get the screen "recalbox'" and then it comes back to the menu. It's the same for all the N64 games whatever the file extension. I didn't modify anything, just installed the latest version, put a ps4 controller and added some games... Do you know what is going on? Thanx a lot

[RecalManc]

Hi, this new release looks awesome but I am having an issue with the x64 build. I have tried on 2 separate machines and 2 separate hard drives. It all starts well, I get my roms copied over and games play. Then randomly it reboots and I've lost everything. It seems like the main partition is being lost. All the config and log files show 0bytes size. I've tried everything I can to resolve this but I'm not a Linux guy or a developer so I'm kinda lost now. Any help would be very much appreciated.

[RecalManc]

I managed to get this from a log.

May 1 13:17:17 RECALBOX user.err kernel: [ 11.849940] EXT4-fs (sda3): error loading journal
May 1 13:17:17 RECALBOX user.info usbmount[554]: /dev/sda does not contain a filesystem or disklabel
May 1 13:17:17 RECALBOX user.info usbmount[570]: executing command: mount -text4 -onoexec,nodev,noatime,nodiratime /dev/sda3 /media/usb0
May 1 13:17:17 RECALBOX user.err kernel: [ 11.980833] EXT4-fs (sda3): couldn't mount as ext3 due to feature incompatibilities
May 1 13:17:17 RECALBOX user.err kernel: [ 11.981109] EXT4-fs (sda3): couldn't mount as ext2 due to feature incompatibilities
May 1 13:17:19 RECALBOX user.err kernel: [ 14.385032] JBD2: Invalid checksum recovering block 22 in log
May 1 13:17:20 RECALBOX user.warn kernel: [ 15.521924] JBD2: recovery failed
May 1 13:17:20 RECALBOX user.err kernel: [ 15.521928] EXT4-fs (sda3): error loading journal

[paradadf]

@recalmanc try flashing your sd card again and wait patiently when booting up recalbox the first time until you reach ES. Otherwise partitions won’t be created properly.

[RecalManc]

@paradadf Thanks for the reply - I have done this several times. It completes and the larger drive is there; I get it loaded up with ROMS and then randomly it looses that partition and goes back to basic settings.

I'm running this on a 240gb SSD, i7 with 4GB RAM.

[paradadf]

@recalmanc can you give me the output of df -h?

[RecalManc]

@paradadf

df -h

Filesystem Size Used Available Use% Mounted on
none 1.9G 0 1.9G 0% /dev
/dev/sda2 1.9G 1.6G 206.6M 89% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 1.9G 12.0K 1.9G 0% /tmp
tmpfs 1.9G 5.1M 1.9G 0% /var
tmpfs 1.9G 300.0K 1.9G 0% /run
/dev/sda1 63.0M 10.0M 53.0M 16% /boot
/dev/sda3 217.0G 39.5G 166.5G 19% /recalbox/share
/dev/sda3 217.0G 39.5G 166.5G 19% /media/usb0

[paradadf]

@recalmanc it looks good to me. Sadly, I don’t know what’s happening.

[garmadon]

@recalmanc , this also happened to me several times.
I think, it may happened because you don't shutdown recalbox properly.
Do not shutdown using the PC power ON/Off button, but use software "Shutdown" in the recalbox menu instead. If you not shutdown properly, the "share" partition will not be unmounted properly, and recalbox will not be able to mount it again at the next boot because the partition will have errors.
If it happened, unplug your hard disk and plug it under a linux system, then use "fsck" command to repair the faulty partition, it worked for me.

[RecalManc]

@garmadon That makes sense as I just noticed that the "Skraper" app I was using was restarting my recalbox machine after each system was complete. I guess it doesn't shut it down correctly. I have stopped using it and I've been stable for a lot longer than I have so far.

Thank you for your help.

[RecalManc]

@paradadf No worries, I think I worked it out (see below). Thanks for trying to assist though!

[garmadon]

@recalmanc , yes i think you're right. Skraper may be responsible.
It happened to me just yesterday at the end of a scrap using the same software.
Skraper reboot the whole operating system after each scrap. It should restart only "emulation station".