I have both HDMI and DSI connected, neither work. DSI shows just black screen. HDMI shows desktop background like extended monitor. This is with a 3b+, does this only work with a 4?

OK. so now bookworm loads and I have the board connected. When the Duet2 board runs 3.4.6 it gives an error that the versions are incompatible. When I update the board with Bossa to 3.5r3, it says it can't find the host. What can I do to get you access to take a look....

ready to test when you have something to try

counter is at 115.
Feb 16 11:01:48 duet3 systemd[1]: Stopped duetcontrolserver.service - Duet Control Server.
Feb 16 11:01:48 duet3 systemd[1]: duetcontrolserver.service: Consumed 3.238s CPU time.
Feb 16 11:01:48 duet3 systemd[1]: Starting duetcontrolserver.service - Duet Control Server...
Feb 16 11:01:49 duet3 DuetControlServer[11638]: Duet Control Server v3.5.0-rc.3
Feb 16 11:01:49 duet3 DuetControlServer[11638]: Written by Christian Hammacher for Duet3D
Feb 16 11:01:49 duet3 DuetControlServer[11638]: Licensed under the terms of the GNU Public License Version 3
Feb 16 11:01:49 duet3 DuetControlServer[11638]: [info] Settings loaded
Feb 16 11:01:50 duet3 DuetControlServer[11638]: [info] Environment initialized
Feb 16 11:01:50 duet3 DuetControlServer[11638]: [info] Connection to Duet established
Feb 16 11:01:50 duet3 DuetControlServer[11638]: [info] IPC socket created at /run/dsf/dcs.sock
Feb 16 11:01:50 duet3 systemd[1]: Started duetcontrolserver.service - Duet Control Server.
Feb 16 11:01:50 duet3 DuetControlServer[11638]: [fatal] Abnormal program termination
Feb 16 11:01:51 duet3 DuetControlServer[11638]: [fatal] SPI task faulted
Feb 16 11:01:51 duet3 DuetControlServer[11638]: System.InvalidOperationException: Stack underrun on channel File2
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 16 11:01:51 duet3 DuetControlServer[11638]: [fatal] SPI task faulted
Feb 16 11:01:51 duet3 DuetControlServer[11638]: System.InvalidOperationException: Stack underrun on channel File2
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 16 11:01:51 duet3 DuetControlServer[11638]: at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 16 11:01:51 duet3 DuetControlServer[11638]: [info] Application has shut down
Feb 16 11:01:51 duet3 systemd[1]: duetcontrolserver.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 16 11:01:51 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'exit-code'.
Feb 16 11:01:51 duet3 systemd[1]: duetcontrolserver.service: Consumed 3.190s CPU time.
Feb 16 11:01:56 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 116.
Feb 16 11:01:56 duet3 systemd[1]: Stopped duetcontrolserver.service - Duet Control Server.
Feb 16 11:01:56 duet3 systemd[1]: duetcontrolserver.service: Consumed 3.190s CPU time.
Feb 16 11:01:56 duet3 systemd[1]: Starting duetcontrolserver.service - Duet Control Server...
Feb 16 11:01:56 duet3 DuetControlServer[11717]: Duet Control Server v3.5.0-rc.3
Feb 16 11:01:56 duet3 DuetControlServer[11717]: Written by Christian Hammacher for Duet3D
Feb 16 11:01:56 duet3 DuetControlServer[11717]: Licensed under the terms of the GNU Public License Version 3
Feb 16 11:01:57 duet3 DuetControlServer[11717]: [info] Settings loaded
Feb 16 11:01:58 duet3 DuetControlServer[11717]: [info] Environment initialized
Feb 16 11:01:58 duet3 DuetControlServer[11717]: [info] Connection to Duet established
Feb 16 11:01:58 duet3 DuetControlServer[11717]: [info] IPC socket created at /run/dsf/dcs.sock
Feb 16 11:01:58 duet3 systemd[1]: Started duetcontrolserver.service - Duet Control Server.
Feb 16 11:01:58 duet3 DuetControlServer[11717]: [fatal] Abnormal program termination
Feb 16 11:01:58 duet3 DuetControlServer[11717]: [fatal] SPI task faulted
Feb 16 11:01:58 duet3 DuetControlServer[11717]: System.InvalidOperationException: Stack underrun on channel File2
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 16 11:01:58 duet3 DuetControlServer[11717]: [fatal] SPI task faulted
Feb 16 11:01:58 duet3 DuetControlServer[11717]: System.InvalidOperationException: Stack underrun on channel File2
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 16 11:01:58 duet3 DuetControlServer[11717]: at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 16 11:01:58 duet3 DuetControlServer[11717]: [info] Application has shut down
Feb 16 11:01:59 duet3 systemd[1]: duetcontrolserver.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 16 11:01:59 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'exit-code'.

doesn't like to run on duet2 ethernet board in sbc mode here is putty response from journalctl

rface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 16 11:01:19 duet3 DuetControlServer[11300]: at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 16 11:01:19 duet3 DuetControlServer[11300]: at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 16 11:01:19 duet3 DuetControlServer[11300]: [info] Application has shut down
Feb 16 11:01:19 duet3 systemd[1]: duetcontrolserver.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 16 11:01:19 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'exit-code'.
Feb 16 11:01:19 duet3 systemd[1]: duetcontrolserver.service: Consumed 3.165s CPU time.
Feb 16 11:01:24 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 112.
Feb 16 11:01:24 duet3 systemd[1]: Stopped duetcontrolserver.service - Duet Control Server.
Feb 16 11:01:24 duet3 systemd[1]: duetcontrolserver.service: Consumed 3.165s CPU time.
Feb 16 11:01:24 duet3 systemd[1]: Starting duetcontrolserver.service - Duet Control Server...
Feb 16 11:01:24 duet3 DuetControlServer[11382]: Duet Control Server v3.5.0-rc.3
Feb 16 11:01:24 duet3 DuetControlServer[11382]: Written by Christian Hammacher for Duet3D
Feb 16 11:01:24 duet3 DuetControlServer[11382]: Licensed under the terms of the GNU Public License Version 3
Feb 16 11:01:25 duet3 DuetControlServer[11382]: [info] Settings loaded
Feb 16 11:01:26 duet3 DuetControlServer[11382]: [info] Environment initialized
Feb 16 11:01:26 duet3 DuetControlServer[11382]: [info] Connection to Duet established
Feb 16 11:01:26 duet3 DuetControlServer[11382]: [info] IPC socket created at /run/dsf/dcs.sock
Feb 16 11:01:26 duet3 systemd[1]: Started duetcontrolserver.service - Duet Control Server.
Feb 16 11:01:26 duet3 DuetControlServer[11382]: [fatal] Abnormal program termination
Feb 16 11:01:26 duet3 DuetControlServer[11382]: [fatal] SPI task faulted
Feb 16 11:01:26 duet3 DuetControlServer[11382]: System.InvalidOperationException: Stack underrun on channel File2
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 16 11:01:26 duet3 DuetControlServer[11382]: [fatal] SPI task faulted
Feb 16 11:01:26 duet3 DuetControlServer[11382]: System.InvalidOperationException: Stack underrun on channel File2
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 16 11:01:26 duet3 DuetControlServer[11382]: at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 16 11:01:26 duet3 DuetControlServer[11382]: [info] Application has shut down
Feb 16 11:01:27 duet3 systemd[1]: duetcontrolserver.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 16 11:01:27 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'exit-code'.
Feb 16 11:01:27 duet3 systemd[1]: duetcontrolserver.service: Consumed 3.220s CPU time.
Feb 16 11:01:32 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 113.
Feb 16 11:01:32 duet3 systemd[1]: Stopped duetcontrolserver.service - Duet Control Server.
Feb 16 11:01:32 duet3 systemd[1]: duetcontrolserver.service: Consumed 3.220s CPU time.
Feb 16 11:01:32 duet3 systemd[1]: Starting duetcontrolserver.service - Duet Control Server...
Feb 16 11:01:32 duet3 DuetControlServer[11461]: Duet Control Server v3.5.0-rc.3
Feb 16 11:01:32 duet3 DuetControlServer[11461]: Written by Christian Hammacher for Duet3D
Feb 16 11:01:32 duet3 DuetControlServer[11461]: Licensed under the terms of the GNU Public License Version 3
Feb 16 11:01:33 duet3 DuetControlServer[11461]: [info] Settings loaded
Feb 16 11:01:34 duet3 DuetControlServer[11461]: [info] Environment initialized
Feb 16 11:01:34 duet3 DuetControlServer[11461]: [info] Connection to Duet established
Feb 16 11:01:34 duet3 DuetControlServer[11461]: [info] IPC socket created at /run/dsf/dcs.sock
Feb 16 11:01:34 duet3 systemd[1]: Started duetcontrolserver.service - Duet Control Server.
Feb 16 11:01:34 duet3 DuetControlServer[11461]: [fatal] Abnormal program termination
Feb 16 11:01:34 duet3 DuetControlServer[11461]: [fatal] SPI task faulted
Feb 16 11:01:34 duet3 DuetControlServer[11461]: System.InvalidOperationException: Stack underrun on channel File2
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 16 11:01:34 duet3 DuetControlServer[11461]: [fatal] SPI task faulted
Feb 16 11:01:34 duet3 DuetControlServer[11461]: System.InvalidOperationException: Stack underrun on channel File2
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 16 11:01:34 duet3 DuetControlServer[11461]: at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 16 11:01:35 duet3 DuetControlServer[11461]: [info] Application has shut down
Feb 16 11:01:35 duet3 systemd[1]: duetcontrolserver.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 16 11:01:35 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'exit-code'.
Feb 16 11:01:35 duet3 systemd[1]: duetcontrolserver.service: Consumed 3.838s CPU time.
Feb 16 11:01:40 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 114.
Feb 16 11:01:40 duet3 systemd[1]: Stopped duetcontrolserver.service - Duet Control Server.
Feb 16 11:01:40 duet3 systemd[1]: duetcontrolserver.service: Consumed 3.838s CPU time.
Feb 16 11:01:40 duet3 systemd[1]: Starting duetcontrolserver.service - Duet Control Server...
Feb 16 11:01:41 duet3 DuetControlServer[11559]: Duet Control Server v3.5.0-rc.3
Feb 16 11:01:41 duet3 DuetControlServer[11559]: Written by Christian Hammacher for Duet3D
Feb 16 11:01:41 duet3 DuetControlServer[11559]: Licensed under the terms of the GNU Public License Version 3
Feb 16 11:01:42 duet3 DuetControlServer[11559]: [info] Settings loaded
Feb 16 11:01:42 duet3 DuetControlServer[11559]: [info] Environment initialized
Feb 16 11:01:42 duet3 DuetControlServer[11559]: [info] Connection to Duet established
Feb 16 11:01:42 duet3 DuetControlServer[11559]: [info] IPC socket created at /run/dsf/dcs.sock
Feb 16 11:01:42 duet3 systemd[1]: Started duetcontrolserver.service - Duet Control Server.
Feb 16 11:01:43 duet3 DuetControlServer[11559]: [fatal] Abnormal program termination
Feb 16 11:01:43 duet3 DuetControlServer[11559]: [fatal] SPI task faulted
Feb 16 11:01:43 duet3 DuetControlServer[11559]: System.InvalidOperationException: Stack underrun on channel File2
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 16 11:01:43 duet3 DuetControlServer[11559]: [fatal] SPI task faulted
Feb 16 11:01:43 duet3 DuetControlServer[11559]: System.InvalidOperationException: Stack underrun on channel File2
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 16 11:01:43 duet3 DuetControlServer[11559]: at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 16 11:01:43 duet3 DuetControlServer[11559]: [info] Application has shut down
Feb 16 11:01:43 duet3 systemd[1]: duetcontrolserver.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 16 11:01:43 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'exit-code'.
Feb 16 11:01:43 duet3 systemd[1]: duetcontrolserver.service: Consumed 3.238s CPU time.
Feb 16 11:01:48 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart

F

OK. so now bookworm loads and I have the board connected. When the Duet2 board runs 3.4.6 it gives an error that the versions are incompatible. When I update the board with Bossa to 3.5r3, it says it can't find the host. What can I do to get you access to take a look....

this makes the dsi screen work...

placing the directive in boot/confix.txt

dtoverlay=vc4-kms-dsi-7inch,invx,invy

and disabling the entry:

display_auto_detect=1

putting the hash sign # at the beginning

#display_auto_detect=1

@printerguy3d also of note, if i unplug the DSI monitor, the HDMI screen is also blank after boot.

I have both HDMI and DSI connected, neither work. DSI shows just black screen. HDMI shows desktop background like extended monitor. This is with a 3b+, does this only work with a 4?

I am struggling to try and combine some commands.

Can I use G32 to call bed.g and inside my bed.g file call G29 to get the bed mesh?
Is this creating a recursive loop and kicking it out?

Here is the start of my sequence.

G90
M83
M106 S0
; reset filament monitor
M42 P63 S0
G4 P100
G4 P50
M42 P63 S1
;
M104 S0 ;cancel S3D set temp
G21 ; set units to mm
G90 ; use absolute coordinates
T0 ; select tool 0
G92 E0.0 ; reset e count
M220 S100 ; reset speed multiplier
M140 S45 ; set bed temp and do not wait
G32 ; probe bed
M190 S45 ; set bed temperature and wait
M109 S230 ; set print head temperature and wait
; === pause for heating ===

But it seems that when G32 runs, nothing happens.
Here is the bed.g file called by G32

M83 ; set extruder to relative mode
G29 S2 ; clear any existing height map
M557 X7:353 Y11:354 P2:2 ; Define G29 grid. Done here so we don't have to modify config.g

; heat and home
M104 S260 ; set head temperature and do not wait
G28 ; home all axes
G28 Z ; home Z again in case it was bottomed out
M109 S260 ; set head temperature and wait

; Probe sequence
G29 ; probe bed

G1 X1 Y1 Z10 F4000 ; move to home position

Is there a better way to do this?

Could I please have a private chat to discuss paying for some firmware updates for a custom feature set for a machine we are building as and OEM? We are a long time customer using only Duet 2 Ethernet boards. Thank you.