[Drastic / nds] spamming error msgs (solved)

nemo93

Hi! I gave a try to the Nintendo DS emulation and I'm quite surprised by how well it runs with Drastic. I've noticed an issue in the logs though which is not critical as it doesn't impact the emulation. I just wanted to mention it in case someone knows a workaround or a fix. I'm aware Drastic is closed source (as of typing) hence I don't expect any update to the binary in the short term.

TL;DR: launch a game and check in dmesg after a few minutes of gameplay. There will be an overwhelming amount of messages stating:

...
[drm:vc4_fkms_page_flip [vc4]] *ERROR* Async flips aren't allowed
[drm:vc4_fkms_page_flip [vc4]] *ERROR* Async flips aren't allowed
...

Pi Model: Pi4 4GB
Power Supply used: original Pi
RetroPie Version Used: 4.7.17
Built From: official Retropie Image
USB Devices connected: powered USB hub w/ 4TB HDD and keyboard/mouse
Controller used: Xbox One S (bluetooth)
Emulator: Drastic 2.5.0
OS/kernel: 32bit RaspiOS with fKMS (fake mode) / 5.10.52-v7l+

How to replicate the problem:
Simply run any game either 2D or 3D.

Thanks.

mitu

What's in your /boot/cmdline.txt ?

nemo93

@mitu that's a very quick answer ;-) Thanks for jumping in. Here you go:

$ cat /boot/cmdline.txt
console=serial0,115200 console=tty3 root=PARTUUID=e22bcd10-02 rootfstype=ext4 elevator=deadline fsck.repair=yes quiet
rootwait loglevel=3 consoleblank=0 logo.nologo plymouth.enable=0 vt.global_cursor_default=0

mitu

The errors/messages are from the Linux kernel. The level of debug/info can be set via the kernel command line, looks like your cmdline.txt ~~contains~~ does not contain any customizations to increase the logging (not sure if loglevel=3 is default or not).

The messages aren't errors per-se, some application (DraStic probably) tries to use use a feature that's not available/supported in the vc4 driver and the kernel logs this.

nemo93

@mitu thanks for the hint. I've used the values from the docs as I'm hiding anything at boot time :-) I've reduced loglevel to 2 (perhaps I'll try 0). This case can be considered closed.

Thanks again.