Raspberry 4 seems to not be supported #16
Comments
|
Hmm, that's weird. In your previous issue you said you're running Raspbian Buster Lite, so I assume you're not running a desktop environment, is that correct? The thing is, I don't have a Pi 4 to test so it's just luck if something works on the 4 out of the box. Getting OpenGL to work without X or Wayland is just that buggy. You mess up one thing, maybe some buffer is not in the right format, and it just outputs nothing without throwing any errors.
Yeah, I know about that one. Seems to be a bug in the engine, I'm not sure whats causing it. |
Yes, I'm not running X.
No worries, I'm not blaming you nor I'm upset that it doesn't work. Lets try to figure why it isn't and make
I've installed How can I help to make |
Thanks!
There are many things we could try. In the meantime I'll try making I also had to apply some hacks to |
|
Here is the output with all the debug flags set. Kinda interesting is that DRI configuration seems to be not found, also libEGL complains about some optional missing extensions and not supported formats. Other than that output looks completly normal for me. I'll also switch to |
|
Yeah, it looks pretty much the same for me, except for the lines that start with I just now pushed a new commit to devel-pi4 that contains some more verbose modesetting. The DRM device is now chosen automatically, so you now longer need to patch the Could you try and run that? You no longer need to specify the GL ES version override environment variable, the appropriate |
|
Still no luck :| I don't see any errors, also checked |
|
Pushed another small update. flutter-pi should now be doing exactly the same things that kmscube is doing to initialize the display. If this doesn't work, maybe the problem isn't in display initialization after all. By the way, the native resolution of your display is 1366x768, right? At least that's the one flutter-pi chooses (because it has the May I ask what App you are trying to run using flutter-pi? Just the example |
Yes, the native resolution should be 1366 x 768
I'm running Still it doesn't work. The screen not even flickers, it stays black all the time :( Here is the output. |
|
There one more thing we can try, we can disable all GL ES extensions and override the GL version to 2.0 (using the environment variable you used before). Maybe the V3D driver reports some things as working even though they aren't, similiar to the VideoCore IV driver. I'm afraid simple debugging ends after that though. EDIT: Just pushed the commit. |
Just tired it and it didn't worked :| I can give you ssh access to my PI4 if you would like. Also you could send/push your |
That would certainly allow me to test all the things, but how are we gonna tell if something actually works? There seems to be no remote viewing solution for headless linux. There used to be dispmanx_vnc, but that's probably not working anymore, now that dispmanx is obsolete. I also just bought a Raspberry Pi 4 (2GB version), it will arrive tomorrow. My asset bundle is this: https://1drv.ms/u/s!AsNHmDqMr-aVgcgAhAGjCx7T2nkrmw?e=j8HLkR |
Well... we can get creative, eg. I can start a YT stream and point camera to the other monitor :D But since you are getting your own PI 4 it probably won't be necessary.
Cool! Can't wait for it! Thank you!
This doesn't improve the situation, still nothing is shown :| |
|
In case it helps, I run on raspberry pi 4 only change in flutter-pi.c snprintf(drm.device, sizeof(drm.device), "/dev/dri/card1"); and make again. Work perfectly. |
Yeah, I already fixed that one in the
Thanks! That's valuable information. That means the issue is probably not in flutter-pi, but somewhere else. Would you mind if you both @dluksza @akilinomendez run Also @dluksza, do you maybe have some other display lying around you can test? Maybe flutter doesn't like 1366x768. And I suppose you've already done that, but if you haven't, could you please do a full system upgrade using |
|
Here output from I did upgraded raspbian a few days ago, will do it right now. Upgrading didn't fix the issue. Unfortunately I don't have any other display at hand, but will try to find another one in couple of days and will inform if it did worked.
The command is Also @akilinomendez, which version of raspbian are you using, did you installed X server or any other development libraries? Maybe I've installed something inappropriate some kind of package, a lib or lib-dev that is making flutter upset. BTW. I wanted to start today from scratch with new install of raspbian base, then give it a try to raspbinan with X pre-configured, but since we want to test the resolution, I'll hold of until I got a spare monitor to test on. |
|
BTW. is it possible that flutter doesn't render the UI because of unsupported touchscreen input device? |
|
Upload my raspinfo.txt. |
|
There must be something with the display I'm using. I've connected Pi to another monitor and was able to see kernel buffer, when on mine it isn't showing anything while system is starting. Didn't had any input device at hand therefore was not able to start I wonder if using raspbian with configured X environment could improve things and show kernel buffer and/or flutter. |
Thanks!
No, input devices are handled by flutter-pi. The flutter engine only sees the input events flutter-pi sends to it.
Yeah, sorry about that, running flutter-pi without input devices should really be allowed. I'm gonna fix that in the next update.
Weird, but the kernel buffer is the only thing you're not seeing right? So the whole Raspbian startup is visible on screen? BTW: which HDMI connector are you using? The one nearest to the USB-C (HDMI0) or the other one (HDMI1), or have you tried both? HDMI0 seems to be the more capable. |
No, I see completely nothing on my screen, no kernel buffer/messages, no raspbian startup, anything. The only think I can see is the
Yes, I'm using HDMI0, one next to the usb-c power cable. Any hints? Or should I ditch this installation and start new one from scratch? BTW. this is the monitor I'm using. |
Yeah, that's definitely not normal. Could really be a Raspbian or firmware bug. If you look at the firmware and raspbian repos, there are many people reporting some kinds of graphics problems/bugs. Maybe this is one of them. Monitors with a native 1366x768 resolution aren't that common, so it's possible that you're just the first one to notice it. But to be sure I'd start completely from scratch. You could also try hardcoding 1080p in Just got my Pi 4. Works fine for me too regardless of firmware, raspbian & kernel version |
|
OK, I've found two options that shows kernel buffer: and
Any other hints? |
|
BTW. When I start either |
|
I've managed to make This also requires: in There are two downsides:
|
|
The package that you can install to upgrade you raspbian lite to a raspbian desktop is called
That means there must be a bug somewhere. The Raspberry Pi doesn't have the ability to switch off the HDMI signal, even if it wanted to. (It says so on this page under the
If splash screen is enabled, that behaviour is normal (up to the point where the display has no signal anymore). I too see only 4 raspberry's (no kernel buffer or raspbian startup log) and then the splash screen on startup, if I have splash screen enabled. I think it's best to report this & all the things we've found out as a bug report on https://github.com/raspberrypi/linux. I'd especially mention that your screen shows no signal, since that for sure means something is wrong. |
Don't know what I'm missing right now. After modifying source code to use
card1, downgrading my local flutter to 1.9.1 I still can't see the demo app.It seems that app is running,
flutter-pidoesn't exit it just stops, but nothing is visible on the monitor. I've checked both HDHMI outputs, also activatedfake_KMS, for now I run out of ideas what could be wrong.Also seems that flutter engine arguments are not respected, as you can see in the output I'm setting
observatory-host, but later on flutter still prints127.0.0.1as observatory host.The text was updated successfully, but these errors were encountered: