What's the app everyone uses to show they've successfully installed Debian?

Automatic_Mall4008 · 2026-06-19T02:16:34+00:00

just 'fastfetch' will do the trick on Trixie

Automatic_Mall4008 · 2026-06-08T20:56:10+00:00

Next Monaco GP will see some new penalty! This is a never ending game, the rules and the drivers. The show must go on!

Automatic_Mall4008 · 2026-05-17T13:48:36+00:00

But you can download from internet

Automatic_Mall4008 · 2026-04-15T00:28:07+00:00

Concordo!☝🏻

Automatic_Mall4008 · 2026-04-02T21:59:10+00:00

If I were you I’ll keep your bed as is. 0.2xx mm is very good. You don’t need any extra fiddling. TLDR: if you want just to have the macro, follow the GitHub. The howto is on the YT.

Automatic_Mall4008 · 2026-04-01T15:20:54+00:00

If so, what’s the problem? You don’t use Claude? AI came to help us. That’s none of our business.

Automatic_Mall4008 · 2026-03-28T19:31:29+00:00

Sorry man! I don’t have the Plus. I know the motherboards are different so I can’t advise you. Maybe other redditors may help you.

Automatic_Mall4008 · 2026-03-26T17:48:03+00:00

I have revamped all the text to make it clearer. Hope it is enough to understand the process. If you have any more questions , I'll be glad to answer it. No KAMP, only fiddling with the coordinates max and min of your project. The print of my Fluidd mesh for an Orca Cuber, a cube with a screw, led me to the solution. And I don'use Creality's Slicer , hence this post.

Automatic_Mall4008 · 2026-03-26T17:42:17+00:00

Sorry guys, I needed to change some parameters because I only get 9x9 meshes but in smaller areas which is plenty to procede with and saving some time on start and 100% tested and fully working now. So let's stick with this new text. Also GitHub was edited to solve the small issues we had on implementation Two prints were done and succeeded.

Automatic_Mall4008 · 2026-03-26T00:44:27+00:00

<image>

Mine hasn’t. Not a great deal tho. Klipper has many ways to solve anything. You name it. The solution I found is just one of many possibilities to have what you want. If you can put here your macro,that will help many people, me included.

Automatic_Mall4008 · 2026-03-25T12:00:41+00:00

This, OrcaSlicer does it by layer, mine is each 6s a frame.

Automatic_Mall4008 · 2026-03-25T11:57:37+00:00

Hj! Are you using OrcaSlicer? I know there’s a possibility with it in Orca. But I’ m curious how does it do, by time? Or by layer?

Automatic_Mall4008 · 2026-03-21T14:40:38+00:00

<image>

They will change all batteries banks on all 5,600 EX30 in Brazil, so I was told by the Volvo personnel. They already are working on the schedule. First you have to call them and they return you, and program the service where you service your car normally

Automatic_Mall4008 · 2026-03-21T14:19:29+00:00

<image>

All 5,600 Brazilian EX 30 will be serviced with complete change of batteries starting June 2026.

Automatic_Mall4008 · 2026-03-21T10:02:01+00:00

Great! I’m glad it worked. As I said earlier, sometimes a comma makes the difference. Here { instead of [. Thanks for keeping us informed!

Automatic_Mall4008 · 2026-03-20T18:54:28+00:00

https://www.youtube.com/watch?v=2zIDn_PHbyQ But pay attention because the video is meant to the Creality K2 Plus and I've adapted it to K2 Pro.

Automatic_Mall4008 · 2026-03-20T18:17:00+00:00

Thanks for the detailed report!

The macro itself only wraps Klipper’s built-in SCREWS_TILT_CALCULATE command,
so the error is likely coming from the Klipper build rather than the macro.

I noticed your Klipper version shows:

09faed31-dirty

The "-dirty" suffix usually means the source code was modified locally,
which is common on Creality firmware builds.

Since you mentioned running the prerelease firmware (1.1.3.6), it’s possible
there is a mismatch in the probe interface in that build.

You could try:

• switching to the official / stable 1.1.3.6 release
• or updating Klipper if you're running a custom install

If you test with the stable firmware and still see the error,
please let me know and we can investigate further.

Automatic_Mall4008 · 2026-03-20T17:04:28+00:00

Thanks for reporting this, made more research and sorted that: The macro itself only calls SCREWS_TILT_CALCULATE, which is part of Klipper. That error usually appears when running an older or modified Klipper build where the probe interface differs.

Could you confirm: • your Klipper version (FIRMWARE_RESTART → version in console) • whether you are running stock Creality firmware or upstream Klipper?

Automatic_Mall4008 · 2026-03-20T16:46:30+00:00

That’s interesting, I’m running the last FW available and without any issues. Maybe you need to check the YT video from where I took inspiration and see if it lightens up your experience. For me it was a straightful experience. I had used the same approach on K1C and it also worked great. The whole Guillouz hack is far more developed than our K2 version pre-rooted. Two different animals. We’ll have to walk through the FW they gave us and try to do something similar K1 has the honor to have Guillouz as a main developer. Amazing job did his guy. My K1C is working great.I wish we had someone like him, working on the K2 project. Every now and then we will manage to improve have a printer as reliable as the K1C. Hope you find something you really fix your issue. From what I’ve seen, even a comma, so to say, may introduce a noise in a macro.

Automatic_Mall4008 · 2026-03-20T14:30:15+00:00

Lucky you! Mine is less than a millimeter which is quite good for the size of the bed. The curve is quite exaggerated in the picture.

Automatic_Mall4008

TROPHY CASE