Getting steadily more disillusioned with the whole MM project. :(

Twice recently it’s crashed, at 01:09, and 21:44
When it boots back up again, the screen flashes blank a few times before it settles.

Pi feels warm, temp shows 63.4C - despite making the changes to the Pi config.

I tend mostly to view MM on a browser away from the host Pi.
Would running MM in ‘server mode’ avoid the Electron browser temp problem?

But if it keeps crashing like this, I think I might abandon the whole thing, and use the Pi for something else.

Done through raspi-config, seems ok, boots and runs fine.

sudo vcgencmd measure_temp

shows 56.9C

Ok, when I get time, I’ll create a backup of the MM SD card first, and then try the GUI config tool.

Thanks.

No, because if that kills it, I don’t know how to bring it back - what file to edit etc…?

Stuck time might be the sunset time. Mine is 21:17, so not stuck al all.

That doesn’t work for me, MM boots to a few lines about blocks, then nothing else.

display_rotate = 1 - is commented out (I’m happy with MM in landscape mode)
avoid_warnings = 1 - line doesn’t exist.

Or…, is it best to use the sudo raspi-config /Advanced/… route?

Comment out the dtoverlay=vc4-kms-v3d change, and Pi boots, MM starts OK.

Does it matter where in config.txt that the new line is placed?

Update to 2.4.0, and made the sudo nano /boot/config.txt dtoverlay=vc4-kms-v3d change.

Shut down Pi, powered Pi back on, and now fails to boot, showing just a cursor top left of monitor.