Solved

When I downgraded VLC to have faster video previews, it created the problem. Just re-use the script proposed by RapidEdwin08

wget https://raw.githubusercontent.com/RapidEdwin08/RetroPie-Setup/master/vlc-downgrade.sh -P ~/ chmod 755 ~/vlc-downgrade.sh ~/vlc-downgrade.sh

And select option 2 to re-install the original VLC version. Now you can re-install EmulationStation

https://retropie.org.uk/forum/topic/35717/emulationstation-video-previews-on-raspberry-pi-5/22?_=1728574374997

@mitu said in Trouble with RetroPie after updating from Stretch to Buster:

@keks24 said in Trouble with RetroPie after updating from Stretch to Buster:

Could you elaborate this and provide some references, please?

I think every new Raspberry Pi OS (was Raspbian once) mentions this in their release notes. For instance, for the Buster release:

We do not recommend upgrading an existing Stretch (or earlier) system to Buster – we can’t know what changes everyone has made to their system, and so have no idea what may break when you move to Buster. However, we have tested the following procedure for upgrading, and it works on a clean version of the last Stretch image we released. That does not guarantee it will work on your system, and we cannot provide support (or be held responsible) for any problems that arise if you try it.

Ah, thank you for the link!

In my opinion, they are making it a little bit easy on themselves here, but I guess, that they do not want to let the (normal) user go through the entire partitioning resizing process of /boot/ here.

They also increased the partition of their official images, due to the large kernel files of Debian Buster:

$ fdisk --list * | grep "Device\|img1" | column -t Device Boot Start End Sectors Size Id Type 2020-12-02-raspios-buster-armhf-full.img1 8192 532479 524288 256M c W95 FAT32 (LBA) Device Boot Start End Sectors Size Id Type 2020-12-02-raspios-buster-armhf.img1 8192 532479 524288 256M c W95 FAT32 (LBA) Device Boot Start End Sectors Size Id Type 2020-12-02-raspios-buster-armhf-lite.img1 8192 532479 524288 256M c W95 FAT32 (LBA) (retropie) $ df --human-readable /boot Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p1 512M 47M 466M 10% /boot

Hey,

it's me again.
I guess I am a bit closer. I was wondering why my custom gamepad driver which generates a uinput device is not working. By incident I started the game directly without the start script, so I could see the information output. One of the very first lines was "couldn't find keyboard event file". I recognized that my custom driver creates a eventX in /dev/input but not in the subdirectories by-id or by-path.
So I tried to create a symbolic link in by-id, pointing at my event.

Now the keyboard-emulating gamepad worked in the game!

Playing that a bit further I went back to my gamepad driver which behaves like a gamepad without keyboard emulation. Running on top xboxdrv with mouse and keyboard emulation. again with a symlink in by-id.

Now the regular gamepad-driver with xboxdrv on top worked in the game!

Only point is, that no regular keyboard is allow to be connected (maybe be game only uses the first keyboard?).

BR
Florian