Closed 7aku8 closed 2 weeks ago
Can you try without the fkms
change? Could be that no longer works on Pi 5, though it shouldn't be necessary anymore anyway.
If the issue persists, can you post the output of the raspinfo
command?
Sure, so I reinstalled OS to make sure that other changes I did will not affect it. I went through the setup process once again, skipping fkms
change. Finally I ran into exactly same issue as before.
@ardera FYI I tried to use Pi4 with 64-bit Raspbian Bullseye instead of Pi5 and it works perfectly fine.
running it on a rpi5 with a 3.5 inch tft display getting this same error
modesetting.c: Could not set DRM client universal planes capable. drmSetClientCap: Operation not supported
flutter-pi.c: Could not create drmdev from device at "/dev/dri/card0". Continuing.
flutter-pi.c: Device "/dev/dri/card1" doesn't have a display connected. Skipping.
Segmentation fault
@anirudh-walia That's not the same error. How is your TFT display connected to the Pi? What model?
My bad just saw the first few lines it's a 3.5-inch TFT display connected via GPIO pins the display is working fine with touch and everything.
LCD Type
TFT
Interface
SPI
Touch Screen Type
Resistive Screen
Touch Controller
XPT2046
Colors
65536
Backlight
Yes, LED
Resolution (Pixel)
320*480
Aspect Ratio
8:5
Hey, I'm kinda noob in embedded programming so sorry if that's a trivial issue. I've been struggling for few hours, trying to run Flutter app with
flutter-pi
on Raspberry pi 5 [4gb and Debian GNU/Linux 12 (bookworm)] with official touch screen display.I skipped 4. step from "Configuring your Raspberry PI" as I wasn't able to find this setting in
raspi-config
. I also wasn't able to find GL driver settings so I enabled fake KMS manually by changingdtoverlay=vc4-kms-v3d
todtoverlay=vc4-fkms-v3d
inconfig.txt
file.Display itself works fine.
I built an app with this command:
And then tried to run it with command:
And I ended up with that error:
I tried several different config.txt changes without any success. Setting option
display_auto_detect
to0
disables whole screen. What I can add is that it used to work just fine with HDMI display.Do you guys have any ideas whether that's a library issue or I'm doing something wrong?