Rebuild v1.2.0 - Revision history

Elias: System updates in Fluidd/Mainsail with tested kernel releases; install with Reflash v1.2.0 or newer

2026-10-01T16:37:07Z

System updates in Fluidd/Mainsail with tested kernel releases; install with Reflash v1.2.0 or newer

@@ Line 18: / Line 18: @@
 The tools have moved from <code>/usr/local/bin</code> to <code>/usr/bin</code>. On a board that is upgraded in place, the old paths keep working: they become links to the new ones. The files the old image had copied in are kept in <code>/var/backups/rebuild-legacy</code>.
 ==Security==
@@ Line 78: / Line 90: @@
 =Getting started=
 ==Building firmware on the printer==

Elias: Image sizes: download, unpacked and used on the Recore, v1.1.0 against the v1.2.0 development build

2026-10-01T15:00:07Z

Image sizes: download, unpacked and used on the Recore, v1.1.0 against the v1.2.0 development build

@@ Line 59: / Line 59: @@
 * '''Input shaper graphs are no longer drawn on the printer by default.''' <code>python3-matplotlib</code> is not installed, which saves 242 MB. Klipper itself never used it. See [[#Input shaper graphs|Input shaper graphs]] below.
 * The ARM compiler no longer carries libraries for Cortex-A and Cortex-R processors, which Klipper never builds for, and the firmware package no longer carries firmware for Qualcomm processors. Together these save about 630 MB. Every Cortex-M variant is kept, so firmware for any microcontroller Klipper supports can still be built on the printer, with any options (CAN bus, USB to CAN bridge, and so on).
 =Getting started=

Elias: Klipper v0.13.0-786 with the AR100 changes merged; AR100 step rate and top speed per microstep setting on a Voron 2.4

2026-10-01T14:55:44Z

Klipper v0.13.0-786 with the AR100 changes merged; AR100 step rate and top speed per microstep setting on a Voron 2.4

@@ Line 23: / Line 23: @@
 ==Klipper and the AR100==
-* Klipper is updated to '''v0.13.0-777'''.
+* Klipper is updated to '''v0.13.0-786'''. This version includes the AR100 improvements made for this release, which are now part of Klipper itself: the timer and message handling rework from Klipper's maintainer, faster serial handling, and building at <code>-O2</code> with a correct size check. The AR100 firmware is built from an unmodified Klipper.
 * The AR100 compiler is updated from GCC 15.1.0 to '''GCC 16.1.0''', which includes fixes for code generation errors on OpenRISC (64-bit and 16-bit shifts, and branch placement).
 * Each firmware file in <code>/opt/firmware</code> now has the exact configuration it was built with next to it (<code>ar100.config</code>, <code>stm32.config</code>, <code>stm32-32KB.config</code>, <code>rp2040.config</code>), and <code>klipper-version</code> records the Klipper version they were built from.
 ==Fixes==

Elias: Draft: Klipper 777 with the pending AR100 changes, GCC 16.1 toolchain, Moonraker stop fix

2026-09-30T14:51:46Z

Draft: Klipper 777 with the pending AR100 changes, GCC 16.1 toolchain, Moonraker stop fix

← Older revision		Revision as of 14:51, 30 September 2026
Line 21:		Line 21:
	==Security==		==Security==
	* The '''printer''' account is now a service account. It has no password, is not in the <code>sudo</code> group, and cannot log in over SSH. Klipper, Moonraker and KlipperScreen keep working: the rights they need are given to them explicitly. Log in as '''debian''', and use <code>sudo -u printer -i</code> to work in Klipper's files, as before.		* The '''printer''' account is now a service account. It has no password, is not in the <code>sudo</code> group, and cannot log in over SSH. Klipper, Moonraker and KlipperScreen keep working: the rights they need are given to them explicitly. Log in as '''debian''', and use <code>sudo -u printer -i</code> to work in Klipper's files, as before.

			==Klipper and the AR100==
			* Klipper is updated to '''v0.13.0-777'''.
			* The firmware for the AR100 is built with AR100 improvements that are still on their way into Klipper: the timer and message handling rework from Klipper's maintainer, and building at <code>-O2</code> with a correct size check. The changes are kept in <code>/usr/share/rebuild/klipper-patches</code>, and are dropped from Rebuild as they are merged into Klipper. They only affect the AR100 firmware; Klipper itself on the board is an unmodified upstream checkout.
			* The AR100 compiler is updated from GCC 15.1.0 to '''GCC 16.1.0''', which includes fixes for code generation errors on OpenRISC (64-bit and 16-bit shifts, and branch placement).
			* Each firmware file in <code>/opt/firmware</code> now has the exact configuration it was built with next to it (<code>ar100.config</code>, <code>stm32.config</code>, <code>stm32-32KB.config</code>, <code>rp2040.config</code>), and <code>klipper-version</code> records the Klipper version they were built from.

			==Fixes==
			* A reboot shortly after the board has started no longer hangs for 90 seconds. Moonraker is given 10 seconds to stop.

	==A smaller image==		==A smaller image==
Line 44:		Line 53:
	A Recore without a fan can reach its critical temperature with all four cores compiling, and it then powers itself off. Build with <code>make -j2</code> or plain <code>make</code>, not <code>make -j4</code>.		A Recore without a fan can reach its critical temperature with all four cores compiling, and it then powers itself off. Build with <code>make -j2</code> or plain <code>make</code>, not <code>make -j4</code>.
	</div>		</div>


			===AR100 toolchain===
			The AR100 firmware is compiled with an OpenRISC GCC toolchain installed in <code>/opt/or1k-elf</code>. v1.2.0 uses GCC 16.1.0, binutils 2.46 and newlib 4.6, built for the Recore from OpenRISC's own build scripts. The build and the changes made for Rebuild are in [https://github.com/intelligent-agent/or1k-toolchain-build/tree/rebuild intelligent-agent/or1k-toolchain-build] (branch <code>rebuild</code>), and the toolchain is downloaded from http://feeds.iagent.no/toolchains/.

	==Input shaper graphs==		==Input shaper graphs==

Elias: Draft of the v1.2.0 release page (not released; unlinked)

2026-09-30T11:45:49Z

Draft of the v1.2.0 release page (not released; unlinked)

New page

__NOINDEX__
<div class="alert alert-danger">
===='''Draft - Rebuild v1.2.0 has not been released'''====
This page collects the documentation for the next release while it is being built. The changes it describes are on development branches and may still change. For the current release, see [[Rebuild v1.1.0]].
</div>

[[File:Rebuild header.png|center]]
Rebuild is a complete Linux image for [[Recore A8|Recore]] 3D printer controller boards. Rebuild comes with Klipper installed and the choice of either [https://docs.mainsail.xyz/ Mainsail], [https://docs.fluidd.xyz/ Fluidd] or [https://octoprint.org/ OctoPrint].

=What is new in v1.2.0=

==Rebuild's own files are Debian packages==
Everything Rebuild adds to the base system is now installed from two packages, rather than copied into the image by the build scripts:
* '''rebuild-recore''', on every image including barebone: the board tools (<code>get-serial-number</code>, <code>get-recore-revision</code> and friends), the USB-C serial console, and the Wi-Fi hotspot fallback.
* '''rebuild-printer''', on the Fluidd, Mainsail and OctoPrint images: the tools that flash the AR100, STM32 and RP2040 firmware, the configurations that firmware is built from, first boot, SSH auto-disable, the boot splash, and the system settings the printer images share.

This means that a fix to any of these files can reach a board through <code>apt upgrade</code>, instead of requiring a new image and a reflash.

The tools have moved from <code>/usr/local/bin</code> to <code>/usr/bin</code>. On a board that is upgraded in place, the old paths keep working: they become links to the new ones. The files the old image had copied in are kept in <code>/var/backups/rebuild-legacy</code>.

==Security==
* The '''printer''' account is now a service account. It has no password, is not in the <code>sudo</code> group, and cannot log in over SSH. Klipper, Moonraker and KlipperScreen keep working: the rights they need are given to them explicitly. Log in as '''debian''', and use <code>sudo -u printer -i</code> to work in Klipper's files, as before.

==A smaller image==
* '''Input shaper graphs are no longer drawn on the printer by default.''' <code>python3-matplotlib</code> is not installed, which saves 242 MB. Klipper itself never used it. See [[#Input shaper graphs|Input shaper graphs]] below.
* The ARM compiler no longer carries libraries for Cortex-A and Cortex-R processors, which Klipper never builds for, and the firmware package no longer carries firmware for Qualcomm processors. Together these save about 630 MB. Every Cortex-M variant is kept, so firmware for any microcontroller Klipper supports can still be built on the printer, with any options (CAN bus, USB to CAN bridge, and so on).

=Getting started=

==Building firmware on the printer==
The configurations Rebuild uses for its own firmware are installed with the image, in <code>/usr/share/rebuild/firmware</code>. To rebuild the STM32 firmware for a Recore A8 (32 KB flash):
<pre>
sudo -u printer -i
cd ~/klipper
cp /usr/share/rebuild/firmware/stm32f031-32KB-serial.config .config
make olddefconfig
make
exit
</pre>
The same directory has <code>stm32f031-serial.config</code>, for the 16 KB STM32 on earlier boards, and <code>ar100.config</code>. Flashing works as described in [[Rebuild v1.1.0#Flashing STM32 firmware|v1.1.0]].

<div class="alert alert-warning">
===='''Use one or two build jobs'''====
A Recore without a fan can reach its critical temperature with all four cores compiling, and it then powers itself off. Build with <code>make -j2</code> or plain <code>make</code>, not <code>make -j4</code>.
</div>

==Input shaper graphs==
Klipper's resonance measurement does not need anything extra. <code>SHAPER_CALIBRATE</code> runs inside Klipper, measures both axes, recommends a shaper for each and saves it with <code>SAVE_CONFIG</code>. That works on v1.2.0 exactly as before.

The '''graphs''' are optional. They are drawn by Klipper's scripts (<code>scripts/calibrate_shaper.py</code>, <code>scripts/graph_accelerometer.py</code>), which need the Python plotting library <code>matplotlib</code>. v1.2.0 no longer installs it. There are two ways to get graphs.

===Draw the graphs on your computer (recommended)===
The picture is looked at on a computer anyway, so draw it there. First measure on the printer, from the console in Fluidd or Mainsail:
<pre>
TEST_RESONANCES AXIS=X
TEST_RESONANCES AXIS=Y
</pre>
Klipper writes the measurements to <code>/tmp/resonances_x_*.csv</code> and <code>/tmp/resonances_y_*.csv</code> on the printer. Copy them to your computer:
<pre>
scp debian@recore.local:/tmp/resonances_*.csv .
</pre>
Then, on the computer, with Python 3 installed:
<pre>
git clone https://github.com/Klipper3d/klipper
python3 -m pip install numpy matplotlib
python3 klipper/scripts/calibrate_shaper.py resonances_x_*.csv -o shaper_calibrate_x.png
python3 klipper/scripts/calibrate_shaper.py resonances_y_*.csv -o shaper_calibrate_y.png
</pre>

===Install matplotlib on the printer===
If you would rather draw the graphs on the printer, as described in [https://www.klipper3d.org/Measuring_Resonances.html Klipper's documentation], install matplotlib first, logged in as '''debian''':
<pre>
sudo apt update
sudo apt install python3-matplotlib
</pre>
This takes about 240 MB. Klipper's scripts then work as described in its documentation.

Plugins that draw these graphs themselves, such as Shake&Tune, install their own copy of matplotlib and do not need either step.