drmModeGetResources failed: Invalid argument about flutter-pi HOT 4 CLOSED

The v3d driver is the open source OpenGL driver for the VideoCore 4 made by Eric Anholt, that's the GL driver you're activating when choosing full-kms or fake-kms. If it's set to legacy, the broadcom one is used.

Ah, so you're using a Pi 4! I actually don't have a Pi 4, I'm testing on a Pi 3A+. In that case, the fix is simple. /dev/dri/card0 is not the device flutter-pi should use on the Pi 4. it's /dev/dri/card1. For now, you could simply look for the line inside flutter-pi.c where it says

. . . = open("/dev/dri/card0", O_RDWR);

and change the path to /dev/dri/card1.

I really thought the drm device would be the same on the 4, but I was wrong as it seems. I'm currently working on an update where flutter-pi will automatically choose it's devices, seems like I need to add capability for automatically selecting the correct DRM device too.

from flutter-pi.

did you activate the v3d OpenGL driver in raspi-config?
i.e.
sudo raspi-config --> Advanced --> GL Driver --> Fake-KMS

If you have activated the v3d driver, or it already was activated, and the error still ocurrs, could you please tell me what files there are inside /dev/dri/? flutter-pi by default uses /dev/dri/card0 as its DRM device.

There's actually not much that is leading up to drmModeGetResources, flutter-pi just opens /dev/dri/card0 and then calls drmModeGetResources on it.

from flutter-pi.

Yes, I did enabled Fake-KMS as a GL driver.

I do see /dev/dri/card0 (card1 and renderD128). What is v3d driver, I've just installed gldriver-test and xinv3d packages but they didn't fixed this issue. Any other hints?

from flutter-pi.

Yes, I do have Pi 4. Changing card to card1 did helped!! Thanks!

Now I'm having different problem with flutter binary format :| Will open another issue for it.

from flutter-pi.