2024-01-03, 12:05 AM
A very impressive start on the road to Pi5 migration.
A couple of early observations in case others who are more knowledgeable can replicate or solve what I'm seeing.
1. In headless mode the VNC runs really (unusably) slow. The Pi4 solution of commenting out two lines in the /boot/config.txt file
#dtoverlay=vc4-kms-v3d
#max_framebuffers=2
causes no image to be presented by VNC on the Pi5.
2. SignalK seems a little unstable. I have a a pretty KIP dashboard which is solid on the Pi4 (not disconnects/reconnects) but is constantly glitching on the Pi5.
Currently testing on the bench but hope to get the Pi5 connected to some real data, afloat later this week.
A couple of early observations in case others who are more knowledgeable can replicate or solve what I'm seeing.
1. In headless mode the VNC runs really (unusably) slow. The Pi4 solution of commenting out two lines in the /boot/config.txt file
#dtoverlay=vc4-kms-v3d
#max_framebuffers=2
causes no image to be presented by VNC on the Pi5.
2. SignalK seems a little unstable. I have a a pretty KIP dashboard which is solid on the Pi4 (not disconnects/reconnects) but is constantly glitching on the Pi5.
Currently testing on the bench but hope to get the Pi5 connected to some real data, afloat later this week.