Rebuild v1.0.1 - Revision history

Elias: /* Known issues */

2024-06-12T17:31:20Z

‎Known issues

Elias: /* SSH access */

2024-06-11T19:53:28Z

‎SSH access

Elias: /* SSH access */

2024-06-11T19:52:21Z

‎SSH access

Elias: /* SSH access */

2024-06-11T19:50:52Z

‎SSH access

Elias: /* SSH access */

2024-06-11T19:50:35Z

‎SSH access

Elias: /* Known issues */

2024-06-11T19:48:43Z

‎Known issues

Elias: /* Enable host mode on the USB-C connector */

2024-06-11T19:47:29Z

‎Enable host mode on the USB-C connector

Elias: /* Enable host mode on the USB-C connector */

2024-06-11T19:46:17Z

‎Enable host mode on the USB-C connector

Elias: /* Running Toggle */

2024-06-11T19:44:19Z

‎Running Toggle

Elias: /* Recore booting */

2024-06-11T19:44:09Z

‎Recore booting

← Older revision		Revision as of 17:31, 12 June 2024
Line 308:		Line 308:

	== Known issues==		== Known issues==
		+	===Having both Ethernet and Wi-Fi creates problems with mDNS===
		+	When having both ethernet and Wi-Fi connected there can be a problem with hostname resolution.
		+	The workaround is to either remove Wi-Fi or ethernet.

@@ Line 86: / Line 86: @@
 # You can choose "enable SSH on new image" in the Reflash user interface
 # You can start the SSH service from Mainsail/Fluidd
-# You can start the ssh service from the serial port. ```systemctl start ssh```. The ssh service will then be persistent on next boot.
+# You can start the ssh service from the serial port. The ssh service will then be persistent on next boot. <pre>systemctl start ssh</pre>.
 SSH access is only enabled for user '''debian''' using the password '''temppwd'''.
 The first time you log in, you will be prompted to change the password. After the password has been changed, you will need to log in again. If you do not log in within an hour of enabling SSH, '''the SSH access will be disabled'''. This is for security reasons, it's not good to have an open SSH port with the default password. If the SSH access is disabled, it can be enabled again from the user interface.

@@ Line 86: / Line 86: @@
 # You can choose "enable SSH on new image" in the Reflash user interface
 # You can start the SSH service from Mainsail/Fluidd
-# You can access the terminal of the board via USB-C or via the "DBG" connector and a USB to TTY adapter.
+# You can start the ssh service from the serial port. ```systemctl start ssh```. The ssh service will then be persistent on next boot.
 SSH access is only enabled for user '''debian''' using the password '''temppwd'''.
 The first time you log in, you will be prompted to change the password. After the password has been changed, you will need to log in again. If you do not log in within an hour of enabling SSH, '''the SSH access will be disabled'''. This is for security reasons, it's not good to have an open SSH port with the default password. If the SSH access is disabled, it can be enabled again from the user interface.

@@ Line 86: / Line 86: @@
 # You can choose "enable SSH on new image" in the Reflash user interface
 # You can start the SSH service from Mainsail/Fluidd
-# You can access the terminal of the board via USB-C or vioa the "DBG" connector and a USB to TTY adapter.
+# You can access the terminal of the board via USB-C or via the "DBG" connector and a USB to TTY adapter.
 SSH access is only enabled for user '''debian''' using the password '''temppwd'''.
 The first time you log in, you will be prompted to change the password. After the password has been changed, you will need to log in again. If you do not log in within an hour of enabling SSH, '''the SSH access will be disabled'''. This is for security reasons, it's not good to have an open SSH port with the default password. If the SSH access is disabled, it can be enabled again from the user interface.

@@ Line 83: / Line 83: @@
 ==SSH access==
-Most of the configuration for Klipper can be handled via the UI, but sometimes it is necessary to have SSH access to the board. By default, the SSH access is disabled, but it can be enabled in two ways.
+Most of the configuration for Klipper can be handled via the UI, but sometimes it is necessary to have SSH access to the board. By default, the SSH access is disabled, but it can be enabled in three ways.
 # You can choose "enable SSH on new image" in the Reflash user interface
 # You can start the SSH service from Mainsail/Fluidd
 SSH access is only enabled for user '''debian''' using the password '''temppwd'''.
 The first time you log in, you will be prompted to change the password. After the password has been changed, you will need to log in again. If you do not log in within an hour of enabling SSH, '''the SSH access will be disabled'''. This is for security reasons, it's not good to have an open SSH port with the default password. If the SSH access is disabled, it can be enabled again from the user interface.

← Older revision		Revision as of 19:48, 11 June 2024
Line 307:		Line 307:

	== Known issues==		== Known issues==
−	~~=== Error message: Unable to retrieve Moonraker service info ===~~
−	~~<div class="res-img">~~
−	~~[[File:Error msg Unable to retrieve Moonraker service info.png]]~~
−	~~</div>~~
−	~~Error message is observed on first boot after flashing rebuild-fluidd-v1.0.0.img.xz on a Recore A7.~~
−
−	~~Issue seems to be related to that moonraker starts before the ssh service is registered by systemd (Linux service manager).~~
−	~~[https://github.com/intelligent-agent/Rebuild/issues/27 Github Issue 27]~~
−	~~<pre>~~
−	~~Unable to retrieve Moonraker service info. Service file must be updated manually.~~
−	~~</pre>~~
−	~~Workaround 1: Reboot the recore.~~
−	~~Workaround 2: Restart moonraker.~~
−
−	~~=== Wifi Access Point does work ===~~
−	~~'''Fixed in Rebuild v1.0.1'''~~
−
−	~~On Rebuild v1.0.0 there is an issue with setting up Wifi as a hotspot/Access Point. There are three issues preventing this.~~
−	# The kernel has trouble with the RTW88 driver causing the AP to connect/disconnect continously. The workaround to that is to downgrade a legacy kernel. The "current" kernel is Linux 6.6.x, while the legacy is 6.1.x as of this writing.
−	~~# There is a missing binary dnsmasq. The can be installed by writing <pre>apt install dnsmasq-base</pre>~~
−	~~# The default channel for the AP is set to 0 which is not a valid channel for an AP. The workaround is to specify which channel to use.~~
−	It is not expected that the user should implement these changes, since the main benefit of having a working AP when setting up a board for the first time, is to be able to use the board without a network cable. There is a PR with these changes implemented, so it will become a part of a future patch version of Rebuild v1.0.x.

@@ Line 101: / Line 101: @@
 === Enable host mode on the USB-C connector ===
 On Recore A7, the host mode for the USB C connector is activated using a device tree overlay. On A8, this is handled automatically.
-To enable the host mode on Recore A7 write the following on the command line. First SSH into the board.
+To enable the host mode on Recore A7 write the following on the command line. First SSH into the board. Recore A6 and A5 can not operate in host mode with +5V output.
 <pre>
 sudo mount -o remount,rw /boot

@@ Line 106: / Line 106: @@
 sudo armbian-add-overlay /boot/overlay-user/sun50i-a64-usb-host.dts
 sudo mount -o remount,ro /boot
 </pre>

← Older revision		Revision as of 19:44, 11 June 2024
Line 259:		Line 259:

	See the Ubuntu documentation for valid rotations: [https://manpages.ubuntu.com/manpages/jammy/man5/weston.ini.5.html weston.ini]		See the Ubuntu documentation for valid rotations: [https://manpages.ubuntu.com/manpages/jammy/man5/weston.ini.5.html weston.ini]
		+	== Recore booting ==
		+	There are several stages to booting Recore, and depending on which media is installed, the boot process will
		+	try and boot either from eMMC, USB host or USB device (FEL).
		+
		+	The board can be booted by either pressing the "BOOT" button for 2 seconds or by applying power to either the 24V connector or the USB C connector. To shut down the board, either use the "shutdown" button from the UI or press the "BOOT" button once. It's not ideal to shut off the board by removing power directly as this can cause a corrupted file system.
		+
		+	<tabs>
		+	<tab name="From eMMC">
		+	===Booting Recore from eMMC (the normal way)===
		+	# Turn on power
		+	# The BROM will load u-boot SPL from eMMC
		+	# The u-boot SPL will load u-boot
		+	# u-boot will load Linux
		+	# Linux will load the rootfs from eMMC.
		+	</tab>
		+	<tab name="From USB">
		+	===Loading u-boot from eMMC but load kernel and rootfs from USB===
		+	Starting with Rebuild v1.0.0, u-boot will do a scan for a USB mass storage device and if a working version of Reflash or Rebuild or Refactor is found, it will boot to that image.
		+	# Download Refactor/Rebuild/Reflash and flash it to a USB drive.
		+	# Insert the USB drive in the board.
		+	# Boot the board normally (Use the Boot button/apply power)
		+	The board should now be have the kernel/rootfs from the USB drive.
		+	</tab>
		+	<tab name="From FEL">
		+	===Boot Recore from a USB stick using the FEL button===
		+	If u-boot should be loaded from a host computer and kernel and rootfs is loaded from a USB drive:
		+	# Flash the [[Reflash]] Linux distro to a USB drive.
		+	# Insert the USB drive in the Recore board in one of the two host connectors close to the HDMI.
		+	# Hold down the FEL button while applying power to the board via the USB-C connector.
		+	# Download the Recore repository https://github.com/intelligent-agent/Recore
		+	# Install the sunxi-tools program
		+	# Run the fel command ('''make fel''') from the host computer. All the necessary binarys are in the Recore repository:
		+	You can read more about the steps needed to boot aboard in FEL mode on the Sunxi wiki: https://linux-sunxi.org/FEL
		+
		+	'''Note:''' Depending on what linux platform you're running from, sunxi-tools will require the following dependencies to compile properly:
		+	* libftd-dev
		+	* libusbx-dev
		+	* libudev-dev
		+	(These are Debian/ubuntu names. For Fedora, change -dev to -devel)
		+
		+	This should upload u-boot from the host computer to the board via the USB cable. u-boot will then boot from the connected USB drive.
		+	Please note that in some instances, the USB drive is not detected as a mass storage device without also having the VIN power connector inserted. See more in [[Recore_A6#USB_connectors_not_discovered_when_powered_by_USB_device\|in the "known errors" section of Recore A6]]
		+	</tab>
		+	</tabs>

	===Running OctoPrint===		===Running OctoPrint===

← Older revision		Revision as of 19:44, 11 June 2024
Line 81:		Line 81:

	</div>		</div>
−
−	~~== Recore booting ==~~
−	~~There are several stages to booting Recore, and depending on which media is installed, the boot process will~~
−	~~try and boot either from eMMC, USB host or USB device (FEL).~~
−
−	The board can be booted by either pressing the "BOOT" button for 2 seconds or by applying power to either the 24V connector or the USB C connector. To shut down the board, either use the "shutdown" button from the UI or press the "BOOT" button once. It's not ideal to shut off the board by removing power directly as this can cause a corrupted file system.
−
−	~~<tabs>~~
−	~~<tab name="From eMMC">~~
−	~~===Booting Recore from eMMC (the normal way)===~~
−	~~# Turn on power~~
−	~~# The BROM will load u-boot SPL from eMMC~~
−	~~# The u-boot SPL will load u-boot~~
−	~~# u-boot will load Linux~~
−	~~# Linux will load the rootfs from eMMC.~~
−	~~</tab>~~
−	~~<tab name="From USB">~~
−	~~===Loading u-boot from eMMC but load kernel and rootfs from USB===~~
−	~~Starting with Rebuild v1.0.0, u-boot will do a scan for a USB mass storage device and if a working version of Reflash or Rebuild or Refactor is found, it will boot to that image.~~
−	~~# Download Refactor/Rebuild/Reflash and flash it to a USB drive.~~
−	~~# Insert the USB drive in the board.~~
−	~~# Boot the board normally (Use the Boot button/apply power)~~
−	~~The board should now be have the kernel/rootfs from the USB drive.~~
−	~~</tab>~~
−	~~<tab name="From FEL">~~
−	~~===Boot Recore from a USB stick using the FEL button===~~
−	~~If u-boot should be loaded from a host computer and kernel and rootfs is loaded from a USB drive:~~
−	~~# Flash the [[Reflash]] Linux distro to a USB drive.~~
−	~~# Insert the USB drive in the Recore board in one of the two host connectors close to the HDMI.~~
−	~~# Hold down the FEL button while applying power to the board via the USB-C connector.~~
−	~~# Download the Recore repository https://github.com/intelligent-agent/Recore~~
−	~~# Install the sunxi-tools program~~
−	~~# Run the fel command ('''make fel''') from the host computer. All the necessary binarys are in the Recore repository:~~
−	~~You can read more about the steps needed to boot aboard in FEL mode on the Sunxi wiki: https://linux-sunxi.org/FEL~~
−
−	~~'''Note:''' Depending on what linux platform you're running from, sunxi-tools will require the following dependencies to compile properly:~~
−	* libftd-dev
−	* libusbx-dev
−	* libudev-dev
−	~~(These are Debian/ubuntu names. For Fedora, change -dev to -devel)~~
−
−	~~This should upload u-boot from the host computer to the board via the USB cable. u-boot will then boot from the connected USB drive.~~
−	Please note that in some instances, the USB drive is not detected as a mass storage device without also having the VIN power connector inserted. See more in [[Recore_A6#USB_connectors_not_discovered_when_powered_by_USB_device\|in the "known errors" section of Recore A6]]
−	~~</tab>~~
−	~~</tabs>~~

	==SSH access==		==SSH access==