Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Section 'shaketune' is not a valid config section #28

Open
Megastrong1 opened this issue Dec 7, 2024 · 22 comments
Open

Section 'shaketune' is not a valid config section #28

Megastrong1 opened this issue Dec 7, 2024 · 22 comments

Comments

@Megastrong1
Copy link

Hi! After installing the firmware it gives the following error, did I do something wrong or is this a feature?
image

@deveth0
Copy link

deveth0 commented Dec 11, 2024

See #20, you need to update all packages first.

@frap129
Copy link
Owner

frap129 commented Dec 12, 2024

Like deveth0 said, updating packages should solve this.

@frap129 frap129 closed this as completed Dec 12, 2024
@Megastrong1
Copy link
Author

This doesn't really solve the problem. Only after I commented out [shaketune] did it work.
image

@frap129
Copy link
Owner

frap129 commented Dec 12, 2024

In the updates section of Fluidd, did you update everything? Disabling shaketune only hides the error

@frap129 frap129 reopened this Dec 12, 2024
@Megastrong1
Copy link
Author

In the web interface, Fluidd performed all updates and Klipper still did not start. I had to copy q1.cfg and add it to the parent directory and comment it out [shaketune]
image

@frap129
Copy link
Owner

frap129 commented Dec 12, 2024

How did you restart klipper? It would need to be manually restarted after the shaketune update was applied, which moonraker does not do.

@Megastrong1
Copy link
Author

I tried to restart using the "RESTART FIRMWARE" button

@Megastrong1
Copy link
Author

And also "RESTART KLIPPER"

@Megastrong1
Copy link
Author

I can demonstrate it on video. Perhaps I'm doing something wrong.

@frap129
Copy link
Owner

frap129 commented Dec 12, 2024

I tried to restart using the "RESTART FIRMWARE" button

That does not restart klipper, that restarts the MCU firmware. The only way to restart from Fluid is using the menu button in the top right, then click services, then the circle arrow next to klipper

@Megastrong1
Copy link
Author

Let me try your method and then it will be clear.

@frap129
Copy link
Owner

frap129 commented Dec 12, 2024

In the web interface, Fluidd performed all updates and Klipper still did not start. I had to copy q1.cfg and add it to the parent directory and comment it out [shaketune]

Copying q1.cfg to the parent directory doesn't do anything. I think when you restarted to apply the new config, you inadvertently restarted and solved your issue already.

@Megastrong1
Copy link
Author

image

In printer.cfg I changed the path

@Megastrong1
Copy link
Author

https://disk.yandex.ru/i/B9UTcPHtAmaWHg
Here's a video of what it all looks like.

@frap129
Copy link
Owner

frap129 commented Dec 12, 2024

If you've updated everything and that is still happening, something must have gone wrong with the update. You can reinstall shaketune by following the instructions here: https://github.com/Frix-x/klippain-shaketune

or, your fix works fine if you dont plan on using shaketune

@Megastrong1
Copy link
Author

My fix works and that's enough for me. I just decided to immediately notify you that something is broken somewhere.

@Megastrong1
Copy link
Author

I tried reinstalling and it worked.

@messschuh
Copy link

i stuck at same issue today. reinstall with wget -O - https://raw.githubusercontent.com/Frix-x/klippain-shaketune/main/install.sh | bash solve the problem for now.

@Megastrong1
Copy link
Author

Thank you!

@aidan-gibson
Copy link
Contributor

Confirmed also got this issue on a fresh install

@frap129
Copy link
Owner

frap129 commented Jan 29, 2025

Confirmed also got this issue on a fresh install

Yep, the base image needs to be rebuilt, but the upstream repo mine was based on was rebased, so that requires a bit of rework and testing to do.

@frap129 frap129 reopened this Jan 29, 2025
@frap129
Copy link
Owner

frap129 commented Jan 29, 2025

Leaving this open for visibility to others

@frap129 frap129 pinned this issue Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants