Printer Model: Sovol SV04
MCU / Printerboard: Octopus Pro klippy.log
Describe your issue:
I haven’t got it to work with BLtouch and it just sat there for a couple of weeks. I have read every post I can found to no avail.
Today I started it and the updater in mainsail wanted to update everything but mainsail so I let it do that. When it was done it said that there isn’t possible to log in and look at the log files. But I can’t get the log files since neither Putty or WinSCP can log in.
So the built in updater totally destroyed the instal and finished with locking me out from it. I am shocked over how bad this is. Why is Klipper like this? What to do?
This has nothing to do with Klipper. If you hit update all in Mainsail, also your Linux packages will get updated (one of the reason why I do not use this functionality).
Apparently this Linux update did something with your ssh daemon. Connect the RPi to a monitor and check if you ssh is running and allowing logins.
Most are configured by default, not to allow root as user.
Ok, but since I updated from within Klipper it in part is a Klipper problem. I have seen that this has happened before so why allow that update from Klipper? Why not warn that it may fail?
Anyway, I have a monitor and after it has loaded it starts shutting of and on about 1Hz. There are all that text but no way to see.
I do find it strange that the default user Id and password have been erased though.
I guess then that the only way is to do another install from the start or go with Marlin. Bummer.
Regards
Johan
Not being a Mainsail expert, I would think that it just calls apt update / apt upgrade to update the Linux OS. If such an operating system update causes issues, it is likely that the issues would have also came up when doing a “manual upgrade” from the shell.
Not sure who is to “blame” here. Definitively not Klipper
Ok, then I now know that it is mainsail to blame.
I did a new install and that worked without problem, well except BLTouch that is, but that is another story.