update to 2.1 RC3 gives configuration error: 'allow_unknown_gcode_generator' is not valid
Recently installed RatOS 2.1 RC2.
Updated RatOS to RC3 via mainsail. Subsequently updated RatOS Configurater upon which I now get the error shown in the image.
How does one clean this up? Do I need to run configuration again?
23 Replies
debug.zip please
how do i generate that?
should be on the lefthand side of the nav
https://discord.com/channels/582187371529764864/1233461645167169576/1300167486624235564
I don't see that in any of your configs which is confusing...
yeah - but it does show up in the klippy log - i'm just not sure which file it's being pulled from
how familiar are you with linux and command line? You could try SSHing into the pi and searching in
/home/pi/printer_data/ with grep for allow_unknown_gcode_generator
something like grep -rl allow_unknown_gcode_generator /home/pi/printer_data/quite familiar actually... i'll do that this afternoon... taking a break for a bit
found it in ~/printer_data/config/RatOS/printers/base.cfg
took out the offending line and now seeing the following warnings:
feels like the update maybe didn't clean some things up properly?
indeed, there is no '.git' folder where that macro is looking
plenty of others:
try running
ratos-doctorSolution
sorry
ratos doctor
here's the output from ratos doctor:
definitely did something
well, stuck at the above - seems like these shouldn't be problems - not sure what to do at this point... maybe just burn RC2 again and start from there?
hold on - klipper now showing it needs an update... let's see where that goes...
RatOS Core now showing dirty due to modifying base.cfg... what is the difference between soft recovery and hard recovery? will either restore the file?
Both will break things and you'll need to do the doctor again
ran soft recovery and seems fine now... i think the initial error was due to klipper needing an update
same with the subsequent error... running the klipper update seems to have solved both problems
yeah, you aren't supposed to edit those files yourself
as TheTik said, soft and hard recovery mess things up. Cover your bases and re-run
ratos doctoryes, i know... but was trying to dig into the issue stopping klipper from running... i think i understand why... a bit surprised that ratos doctor didn't identify that klipper needed an update
it isn't checking for updates, it is just restoring things to how they should be
I see
I think I'm ok now
I'll mark this solved