update to 2.1 RC3 gives configuration error: 'allow_unknown_gcode_generator' is not valid | Rat Rig Community [Unofficial] | Page 1

zealous flume Apr 23, 2025, 2:51 PM

#

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?

echo quarryBOT Apr 23, 2025, 2:51 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

glacial dust Apr 23, 2025, 3:15 PM

#

debug.zip please

zealous flume Apr 23, 2025, 3:25 PM

#

how do i generate that?

glacial dust Apr 23, 2025, 3:34 PM

#

should be on the lefthand side of the nav

#

#1233461645167169576 message

zealous flume Apr 23, 2025, 3:36 PM

#

📎 ratos-debug.zip

glacial dust Apr 23, 2025, 3:46 PM

#

I don't see that in any of your configs which is confusing...

zealous flume Apr 23, 2025, 3:47 PM

#

yeah - but it does show up in the klippy log - i'm just not sure which file it's being pulled from

glacial dust Apr 23, 2025, 3:52 PM

#

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/

zealous flume Apr 23, 2025, 3:56 PM

#

quite familiar actually... i'll do that this afternoon... taking a break for a bit

zealous flume Apr 23, 2025, 5:48 PM

#

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:

#

glacial dust Apr 23, 2025, 5:54 PM

#

try running ~~ratos-doctor~~

#

sorry ratos doctor

zealous flume Apr 23, 2025, 5:56 PM

#

#

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?

hybrid walrus Apr 23, 2025, 6:15 PM

#

Both will break things and you'll need to do the doctor again

zealous flume Apr 23, 2025, 6:16 PM

#

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

glacial dust Apr 23, 2025, 6:26 PM

#

zealous flume RatOS Core now showing dirty due to modifying base.cfg... what is the differenc...

yeah, you aren't supposed to edit those files yourself

glacial dust Apr 23, 2025, 6:27 PM

#

zealous flume ran soft recovery and seems fine now... i think the initial error was due to kl...

as TheTik said, soft and hard recovery mess things up. Cover your bases and re-run ratos doctor

zealous flume Apr 23, 2025, 6:30 PM

#

glacial dust yeah, you aren't supposed to edit those files yourself

yes, 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

glacial dust Apr 23, 2025, 6:31 PM

#

zealous flume yes, i know... but was trying to dig into the issue stopping klipper from runni...

it isn't checking for updates, it is just restoring things to how they should be

zealous flume Apr 23, 2025, 6:46 PM

#

I see

#

I think I'm ok now

#

I'll mark this solved

#update to 2.1 RC3 gives configuration error: 'allow_unknown_gcode_generator' is not valid