only the command that starts the ui inside the vnc desktop, it works as in it finishes booting and you can use it musically, but it’s not a proper workaround, its a workaround we tested, you’re the one who shared it I’m using the hdmi to vga adaptor at the moment as a fully practical workaround, as stated above.
I see, that’s whats going on with the plugin displays, interesting
@riban I’m happy to raise an issue tracker ticket but I’m not even sure what I’m agreeing to!
If you want to provide some direction, I can learn something new.
@riban for the Noob like me, where/when are you running this code. Are you running in the webconf terminal following booting or are you adding it to the custom boot command?
@RMunn so the trick we used allowed the pi to finish its boot process, I wouldn’t call it a perfect environment because there’s no way to not display the plugins that have desktop displays, which is a very useful way to save resources that would become unavailable, but other than that it did appear to work, it got me out of a sticky situation where I would have had to hang it off of my screen again to get it back on during an audio interface change
hi, i’m new here.
i have same situation but on a pi4: connected with hdmi to a large display (no touch), it works with raspbian, i also can see the display working when removing the sd, but with zynthian i get a black screen, even after 15 minutes. I tried both stable and “testing”, tried changing hdmi port, web interface and ssh are working.
My display is a 4K, and i tried adding to cmdline.txt the following
video=HDMI-A-1:1024X760M@60D
video=HDMI-A-1:1920X1080M@60D
video=HDMI-A-1:3840X2160M@60D
my goal is to be able to try zynthian before buying the kit (when it will be available), don’t really mean to use it with this display.
Hi @rejetto welcome aboard and glad to hear you that have solved your issue.
You may mark and edit the topic as [SOLVED] and detail the solution you have ended with.