Batocera 34 Vanilla Installation Slow Startup and Exit from Emulation

Muckypaws

[SOLVED]

Hi All,

I have Batocera 32 up and running pretty well.

This evening I installed 34 on a fresh SD Card, default installation and inserted into my RPi4. Default installation no changes (yet)

Whilst startup goes through the collections it takes up to two minutes.

There’s some included games in Build 34, so I start C64 Fix It Jr, which works, then exiting from the emulator, it takes up to two minutes to return to the Emulation Station screen.

I’ve checked the ES Logs, no real hint what’s going on.

Controller is a generic Dragon Rise USB Controller.

I’ve repeated the same with another fresh SD Card and the results are the same.

Unplug the USB controller and reboot a couple of time, still the same.

I’ve read the articles on the Wiki about slow performance and DMESG and lsusb -t doesn’t reveal anything exciting.

Connecting the RPi to the same 1080P TV I’ve been using for build 32 and haven’t added any ROMS yet.

Anyone else experience this with the default installation from the Image provided on the Batocera website?

Cheers

Muckypaws

Seems that there remains issues with

dtoverlay=vc4-kms-v3d

Which is enabled by default, switching back to dtoverlay=vc4-fkms-v3d solved the issue with the long delays between Collections message finished on ES to returning back to ES.

Atari

fkms “solves” a lot of problems. At the cost of 3D acceleration…

I mean, if that doesn’t bother you, then yeah that’s a viable solution.

Megig

I had before a problem like that too and figure out this happen Because my flash drive had a too slow write speed

you need a least sd card with a 20 MB write speed to run Batocera normally

Atari

That is demonstrably false and misleading. Batocera can be run on storage speed as slow as 1 MB/s without noticeable slowdown.

What’s usually killer is when you are using faulty storage, and that usually comes along with slow write speeds.

Correllation does not mean causation.