19 Replies
optimistic-gold•12mo ago
This means that the linux kernel was built with local changes which haven't been commited to the branch
This happens if someone/something has made local changes to klipper (ie, on your pi). If klipper isn't dirty in your update manager, run "flash all connected MCU's" in the configurator, to recompile and flash everything.
It appeared like a week ago, after an update.
Probably just a klipper migration thing. In either case i told you how to fix it if it's annoying you.
i have the same thing could this cause some problems ? like z offset not saving
Please check the status of Klipper in your update manager
like z offset not savinNo Unless you manually broke the z-offset code and thats why it's "dirty" "dirty" means the code has been modified locally the klipper code itself Not ratos
ok. i dont think i have i only done the normal z-offset calibration
ah ok
thanks alot
did that but it still says dirty
im just going to do a fresh install
that won't do much
Again, what does the update manager say in the machine tab in mainsail? Send me a screenshot
@miklschmidt
it says dirty again XD
So nothing here is dirty. It doesn't make much sense that the flashed firmware would be dirty 🤨
update manager or the MCU status?
Host(armv7l, 32bit)
Version: v0.11.0-221-g6ce2bd61-dirty
Just happened on my machines too when updating to the latest klipper
Something probably changed in the linux service compilation process that causes the repository to be temporarily dirty
I wouldn't worry about it
ok well hoped it would fix my issue.
There's no way it's related, it's only the raspberry pi process which is only used (by default) on the v-minion for dual accelerometers, nothing else is using the pi linux process.
ok well time to do a nightshift i guess