All Labtix versions can be downloaded from the FTP server
current version: http://ftp.labdoo.org/download/install-disk/
older version (archive): http://ftp.labdoo.org/download/archive/Labtix_former_releases/

Labtix 2 (from 2022)

Since its launch in 2017, Labtix has become the most popular installer and remover tool within the Labdoo project. Labtix Release 1 is based on a 32-bit Antix 17 (2017) kernel. Labtix 2 is based on a 64-bit Antix 21 (2021) kernel.

Don't put Labtix 1 too far away as this "old" version works well with "old" hardware. And the new Labtix version 2 fits the more modern your donated laptop is, which requires current drivers that are only available in 2. And cloning images of 22.04 LTS and higher Labtix 2 is mandatory.

Ubuntu 22.04 LTS introduced a new boot partition format (grub2 core.img). Labtix 1 and also older Clonezilla versions do not know this format and therefore cannot clone current images on Ubuntu 22.04 and higher! Please try whether Labtix 2 starts with a setting such as failsafe or safe graphics if there is a problem. Then there would be Parted Magic as another installation tool on the web. Or you would have to take Labtix 1 and an image based on 20.04 LTS.

However, we recommend using Labtix 2 by default as it comes with many improvements and features:

• Labtix 2 is based on Antix 21 and is only available in a 64-bit version. There is no longer a 32-bit version (sorry). Users who require a 32-bit version must use the earlier Labtix 1.
• The images provided by Labdoo on our FTP server can be processed with either Labtix 1 or Labtix 2.
• You need for Labtix 2
• At least one 2GB USB key (recommended) or DVD to install and run Labtix 2 on. It is not possible to install Labtix 2 on a CD or a 1GB stick (too small).
• min. 1.5 - 2 GB RAM in the computer to be installed.l
• Labdoo team has changed the user interface as little as possible, so you don't need long training. Some changes were mandatory, e.g. Labtix 2 comes with the file manager zzzFM (Fork of SpaceFM). And 4 years of software development have passed...
• Standard installation from the context menu of zzzFM with the Labdoo installer which performs a legacy and UEFI bootable (hybrid) installation,
• Legacy installation with the Labdoo legacy installer from the zzzFM context menu for devices that cannot boot with Labdoo's hybrid installations.
• The images provided by Labdoo on our FTP server can be processed with Labtix 1 up to 20.04 LTS and with Labtix 2 from 22.04 LTS.
• From summer 23, only Labtix 2 will allow you to install the new smaller BASIC images and the desired content at the same time. If installed otherwise, the content can be added in Labdoo using the script.
• UEFI (only for technicians): The number of IT donations with UEFI will increase. Normally you turn off UEFI and Secure Boot in the BIOS and enable Legacy Boot. However, there may be reasons why this is not possible (e.g. BIOS locked by unknown password; no legacy support implemented, etc.). There was already a manual UEFI procedure in Labtix 1, in Labtix 2 it is now largely automated. Labtix shows which mode (Legacy or UEFI) was booted in and you select the appropriate installation script in the 2-click installer in the file manager. If you select the UEFI Sprit, this happens: On the installation medium, the folder /UEFI with the UEFI image must be in the top folder. This small UEFI image is automatically installed first, followed by the actual image you want. After the installation, the UUID of the 2nd partition is entered in the grub file so that the computer starts up correctly. Labdoo had to decide to either maintain 2 complete sets of images (UEFI and legacy), which would have taken a lot of time and storage space on our servers. Or to have only one set of images (legacy) with the above solution, which is still started correctly in connection with an upstream UEFI image. Sounds more complicated than it is, everything is set automatically during installation.
• Improved user support and more tools available:
• Remaining battery capacity: Labtix shows the percentage (%) of the remaining battery capacity (life cycle), e.g. 20% means that only ⅕ of the original battery capacity is available and a new battery should be considered.
• Better support for SSDs
• New driver for current hardware (graphics card, interfaces, LAN/WiFi etc.).
• Additional tools: Speaker test, Live USB Maker, Avahi network scan, StressCPU (°C/°F check), DiskCheck and much more.
• Images for Cloning:
• A new set of images for cloning based on Ubuntu 22.04 LTS was made available and uploaded to our FTP server in mid-2022,
• the 20.04 LTS based images are moved to the /archives directory on the FTP server,
• The 18.04 LTS images need to be removed from the FTP server due to the capacity of the FTP server (those were the last images that could run on a 32-bit CPU; thus ending the 32-bit range for the Labdoo project) .
• From summer 2023, only small “BASIC” images will be used for the respective languages. The content is then installed in Labtix by the installers. The large images that contain content will continue to be created for a while, but will be phased out in the long term.

Any image release can be processed with any Labtix release, fully compatible.

Labtix 1 (2017 - 2021)

Based on Antix 17 (2017) you get a complete set of refurbishment and installation tools. Labtix 1 runs on 32-bit and 64-bit CPUs. The drivers included in Labtix 1 work best on older hardware (approx. 2008 - 2018, difficult to define exactly, it's best to try it).

for Labtix

• At least one 2GB USB stick or CD to install and run Labtix 1 on.
• 1GB RAM.

Looking through a donated laptop

In order to start Labtix or Labdoo, settings in the UEFI may need to be changed. UEFI has replaced the old BIOS system, but can usually still be used in the same way as the old BIOS interfaces.

UEFI Settings

On some laptops it is necessary to change UEFI settings:

BIOS settings
On some laptops it is necessary to change BIOS settings:

Check the hardware with Labtix

System requirements (currently on https://www.labdoo.org/deu/en/faq#FAQ04)

• min. 120 GB disk capacity,
• min. 3 GB RAM, better 4 GB,
• if the laptop is max. 12 years old, it should fit (usually with Windows 7 / 8 / etc. seal.

Does the donated device meet our minimum requirements (3-4 GB RAM, max. 12 years old, min Windows 7 or higher upon delivery)? https://www.labdoo.org/deu/en/faq#FAQ04

You should look through a donated computer before installing it. It makes no sense to give a laptop that overheats in cool regions to hot countries. Or if the hard drive is already "crumbling", how will it survive transport and operation in hot regions? That's why Labtix comes with useful tools for not only the hard drive, but also speakers, temperature curves under load, and much more. more to check.

Recommended hardware checks

If you already have a bootable CD or USB stick with the Labtix installation environment and Laboo Images for Cloning, you can skip this chapter.

Using the Labtix tool as a live CD/DVD or USB stick (recommended), Labdoo systems prepared by our helpers and equipped with learning content can be easily and quickly transferred ("cloned") to new computers , using so-called Images. As of Labtix 2.09 there are 4 BASIC images in 4 languages (English, Spanish, German, French). Depending on the language in the target country of the IT donation, you can select the language and upload additional learning content in other languages using control files. Local teams maintain additional images, e.g. in Catalan.

You need 2 things:
Labtix on a bootable medium: this can be a DVD (from Labtix 2.xx, from 2022) or a CD (Labtix 1.xx, 2017-2021) or a USB stick (recommended, 2 GB or larger) with which you can boot a computer into the Labtix environment.
External USB hard drive: for storing the Cloning Images and other learning content from our FTP server (Labdoo Hubs in Germany can be obtained from Labdoo.org e.V. Retrieve donated, pre-recorded boot media and USB hard drives.)

---------------------------------------------------------------------------------------------------------------------------

Labtix: The Labdoo installation environment

In order to be able to install older and newer computers yourself with a license-free tool, Labdoo.org has put together a small solution based on the Linux version Antix, which we called Labtix (composed of Labdoo and Antix).

In Labtix you will find everything you need - for deleting old data on a donated computer, for quick and automated installation of finished systems. In addition, you will find many tools on Labtix to diagnose hardware and analyze and solve problems (CPU/processor, thermal problems (°C), detect damaged drives, battery status, etc.)

You could download the iso files for Labtix from the folder of our FTP server. You could check the correct download using checksums (MD5 or sha512).

Once you have downloaded the file, you can create a boot medium from the iso file (CD or USB stick). This is the boot medium with which you can start and prepare donated computers.

Create a boot medium (CD or USB stick) from the Labtix ISO

Next, convert the ISO file into a boot CD or USB boot stick (simple copying is not enough!). This can often be done with the file manager of the operating system you trust or with additional tools. Below you will find some suggestions. For more, consult the web (search for "create CD / USB stick iso" and your operating system).

Requirements for Labtix 2:

• Installation on DVD possible, a simple CD is no longer sufficient
• USB stick with at least 2 GB of storage space. If Labtix is to be expanded using the persistence mode, it may make sense to use a larger stick.

WINDOWS:

• Install and start a program for creating start media, e.g. Rufus: https://github.com/pbatard/rufus/releases/download/v3.4/rufus-3.4p.exe or alternatives https://alternativeto.net/software/rufus/.
  Start Rufus, select the USB device, click on the "Select" button, select the labtix.iso file, then click on Start.

LINUX:

• In Labtix there is the tool Live USB Maker as well as the tool ISO-Snapshot with the help of which you can create an ISO file from the existing system (recommended).
• At https://wiki.ubuntuusers.de/Brennprogramme/ you will find a range of Linux tools that you can use to burn CDs/DVDs, e.g. Xfburn or Brasero,
• zto create bootable USB sticks: Unetbootin, boot media creator, Yumi, drive management etc. As a rule, every distro/desktop environment has a corresponding program installed
• With dd, enter the following in the terminal: dd if=/Path/to/Labtix.iso of=/dev/target partition bs=1M
  But beware: Persistence cannot be set up on USB sticks created with dd! Further details at : https://antixlinux.com/forum-archive/writing-antix-iso-image-on-usb-flas...

MAC OS:
The balenaEtcher tool at https://www.balena.io/etcher/ creates the boot medium in a simple way after installation: select the image file, specify the target drive and the medium is flashed.

---------------------------------------------------------------------------------------------------------------------------

Labtix 2

https://youtu.be/oCJ84kMxjg4

---------------------------------------------------------------------------------------------------------------------------

Labdoo Clone Images and additional learning content

You must download the images beforehand for cloning. Images are copies of a complete, pre-installed system. Linux has a great feature that other operating systems do not have. You can transfer a system from computer A to computer B - and it will run!

You can find these images online on our Labdoo FTP server http://ftp.labdoo.org/download/install-disk/.

You can download individual files via the browser by clicking on them with the right mouse button and then selecting "save link as".

However, this does not work for folders or for many files! These have to be downloaded individually and this is of course not convenient.
Simple methods for downloading multiple files for all common operating systems can be found at https://platform.labdoo.org/content/connecting-labdoo-ftp-server
Images sind groß und der Download dauert lange. Wenn ihr euch mit FTP-Clients auskennt, empfehlen wir daher sie direkt per FTP herunterzuladen (sftp, user labdoo und Passwort labdoo).

Labdoo BASIC Images for Cloning

Images and learning content have been decoupled since summer 2023. Previously, there were turnkey images, e.g. EN_40, EN_80, EN_160, EN_250 etc. Learning content was already pre-installed in these images, but this bloated the images, led to redundancy and long download times.
You can quickly download BASIC images with approx. 16 GB and then complete them with the desired content either during cloning with Labtix 2 or after rebooting. This is much faster, more flexible and saves time and resources.

In order to decide which image and which content is/are best for you, you would have to take the respective framework conditions into account:

• The CPU/processor architecture of the computer you are currently working on (only 64-bit has been supported since 2018). Current images from 2020 are only available as 64-bit versions.
• The language(s) in the target country for which you want to install.
• The size of the hard disk in the computer to be refurbished. The size of the hard disk is displayed e.g. in the BIOS or after booting Labtix.

The name of a BASIC image on the FTP server says:

• xx_04_LTS = Version on which Ubuntu is based, e.g. 22.04 LTS (older versions are in the archive)

There are standard directories for each available BASIC image and user language.

• English (EN): http://ftp.labdoo.org/download/install-disk/EN_English_images/
• German (DE): http://ftp.labdoo.org/download/install-disk/DE_German_images/
• Spanish (ES): http://ftp.labdoo.org/download/install-disk/ES_Spanish_images/
• French (FR): http://ftp.labdoo.org/download/install-disk/FR_French_images/

...and more to come.

Additional learning content
Additional learning content can be combined with the BASIC images. The content must be available locally on a local storage medium or on a local server. Downloading from the FTP server during installation is deliberately not supported (overloading the FTP server and taking a long time).

• Either during installation with Labtix. content: none is preset in the mask. If you click on it, you will be redirected to the folder with prepared control files. The names provide information about the content and required disk size, e.g. EN_SW_250 installs English and Swahili content and requires a 250 GB disk.
• Or after the installation process with the script installscript-content.sh, which can be found on the desktop in the /scripts folder. The process is the same as before, only you have to manually navigate to the folder with the control files for the content (usually on install-disk/wiki-archives/content_list

).

Preparation of the external USB hard drive (1+ TB)

The downloaded images are already unpacked and ready for immediate use. Copies them to an external hard drive or a local server. The USB disk must be formatted to store large files. For example, FAT32 is not possible because FAT32 can only handle files smaller than 4GB. NTFS is the recommended file system for an external hard drive.

Labtix 2

https://youtu.be/oCJ84kMxjg4

Sometimes the screen is very dark after booting and the screen cannot be brightened or darkened using the function keys. Then move the mouse to the upper left corner, if necessary "flying blind", click there and then tap on the arrow key to the right. Each time you press the arrow key, the monitor should get a little brighter.

• Double-click to start the file manager zzzFM (Labtix 2).
• Mount the drive on which the images for cloning are located.
• For external USB drives: plug it in, the drive appears with a - in front of it, then click on the entry and the "-" becomes a "+".
• Connect to the network, via LAN it is sufficient to plug in the LAN cable, for WLAN with Connman system tray, then open file manager zzzFM → in the input area (preset /home/labdoo/) den Enter the path to the server, e.g. smb://192.168.1.1/install-disk, if necessary enter the password in the terminal window. smb is the protocol required for Windows servers.
  First it tries to establish a connection for the user guest, then for the user ladboo. Or you can enter a local user like this: smb://user@192.168.1.1/install-disk and then the password in the terminal window.
• The drive / server is now mounted, i.e. the computer has access to it.
• Open the folder with the images.
• Right click on the folder containing the image to be installed.
• Click the displayed functions list on
• Labtix 2: labdoo-legacy-installer or labdoo-UEFI-installer (depending on system settings and boot)
• in the next window
• Labtix 2: Enter the path to the target disk, e.g. sda, nvmep1n or similar → set the number of delete runs,
• optional: enter the host ID if you already know it (otherwise it can be changed after the restart)
• The image will now being copied to the internal hard disk sda.
• At the end GParted opens for control to display the finished partition on sda. The whole hard disk should be available. Close GParted. In rare cases the automatic adjustment of the partition does not work. Then it can be adjusted manually.
• The window with the installation's confirmation will appear, confirm with "ok" and close.
• The installation will be confirmed in the terminal, then close with ''Enter''.
• The installation is complete. Labtix can be shut down with "Poweroff" or "Save Poweroff" and the computer can be restarted.

Select your BASIC-image and content package
Select the content package
(Example) Content package chosen and power off after installation activated

Labtix comes with a number of useful tools preinstalled:
(partly smaller deviations between the Labtix versions possible)

For more information, please use the man pages of the help function in the terminal (e.g. "man gparted" or
type "psensor --help" there and press (enter)) or use the Internet.

Desktop Settings:
The Labtix desktop environment is based on openbox with the additional lxpanel. If you right-click on the desktop, you can select "Desktop Settings" to make changes to the desktop. To install new program launchers on the desktop, copy them from /usr/share/applications to the desktop. To move icons on the desktop, use "Shift + Drag". Please note that in some cases SpaceFM moves the items out of the folder. If so, please copy it back.

We may need some tools for troubleshooting that make it easier for us to fix errors when installing or starting computers:

• Labtix on a USB stick :-) ,
• Labtix on USB stick, installed with "dd" with the Live USB Maker,
• Labtix on DVD,
• a finished standard Labdoo installation on a hard drive to test whether a device can / wants to boot with Labdoo,
• a finished legacy Labdoo installation on a hard drive to test whether a device can / wants to boot with Labdoo legacy,
• Super Grub 2 Disk (link) as a starting aid for Labtix or Labdoo,
• Clonezilla-Live or Parted Magic to install if nothing else works,
• Boot Repair Disk ( link ) to fix boot problems with Labdoo.
• optional: USB adapter for SATA to be able to "plug in" a hard drive externally,
• optional: USB hub for USB / USB-C slots if a laptop doesn't have enough slots

You don't have to create all of these tools directly. It is enough to create them when needed. But the more problem cases you have worked on, the more complete this tool collection becomes.

The easiest way can often be to install a hard drive with a finished Labdoo installation in a "problem" computer. This saves time and nerves!!!

Computer remains "dead":

When plugging in the power supply, the DC indicator light does not light up or the computer beeps:

• Power supply defective or not suitable? Make sure you have the correct DC plug.
• No RAM memory installed?
• Battery deeply discharged? If possible, try starting without a battery or powering the computer for a while. Depending on the device, it can take a few minutes to an hour until the device is bootable!

UEFI not accessible:

• Win 10 or 11 is started in installation mode and the UEFI is not accessible: remove the hard drive and delete it externally.
• If Windows is already installed and boots to the login screen: Click the power icon, click the "Restart" option with Shift/Shift key >>"Advanced options">> "Troubleshoot" >> "UEFI settings" . In the UEFI then put the Labtix stick first in the boot settings, deactivate secureboot if necessary.
• Common keys to get into UEFI: ESC, F1 (Lenovo), F2, F10, F12 (Dell), Del . Depending on the setting in the UEFI, the "Fn" key must be pressed at the same time.
• Some devices (some Lenovo or Sony) have their own button to boot into UEFI, sometimes quite hidden. A search on the Internet can be informative.
• If Labtix boots into the UEFI boot menu: Boot Rescue Menus >> Reboot into BIOS/UEFI Setup. Labtix may have to be booted via the computer's boot menu.
• If you have one, try a Labtix DVD and boot into the UEFI using the Boot Rescue Menu (see above).
• Boot into the UEFI boot menu with a Xubuntu USB Live stick. This contains the “UEFI Firmware Settings” option. Is also possible with some other *buntus. You may have to boot via the computer's boot menu.
• Sometimes it helps to consistently remove all drives and don't overlook the SD card slot.
• On some devices, removing the CMOS battery can force an error message from which access to the UEFI is often possible. Similarly, some devices have a reset button on the bottom that can be reached through a small hole.

Labtix does not boot into the Grub boot menu:

• Secureboot switched off in UEFI?
• USB boot not possible, e.g. by excluding USB boot in UEFI
• Some devices only boot Labtix in UEFI mode, others only in legacy mode, so it makes sense to try it out. The same applies to the installed images.
• "USB-always power on" activated in UEFI?
• A common problem is the poor connectivity of some USB sticks in USB sockets. If you pull the stick approx. 1mm outwards, the stick may have better contact. If the LED on the stick (if present) lights up or flashes, the contact should be OK.
• Use Labtix DVD?
• Use Labtix on a stick installed in Labtix with the Live USB Maker with the "dd" option?
• The device simply does not want to start with the bootloader used by Labtix or ignores it due to the computer firmware used (e.g. on some Acer laptops). If the device accepts the SuperGrub2Disk bootloader (from USB or CD), Labtix can be started using SuperGrub2Disk. https://www.supergrubdisk.org
• If all else fails, you can install a hard drive in the device on which you have installed Labdoo.
• If only Win 10 or 11 stubbornly boots, the only solution is to remove the hard drive to start Labtix and/or get into the UEFI. The hard drive should then be erased using an external USB adapter and checked for errors using DiskCheck in Labtix.
• (for Labdoo Germany) ...and if all else fails, then send the IT donation to the central post office https://platform.labdoo.org/de/hub?h=119075

Labtix hangs when booting:

• If Labtix hangs when booting, it is worth trying out the boot options “failsafe” (driver problems), “nomodeset” (graphics driver problems) or acpi=off (power management problems),
• A network search with the computer type, "Linux" and "Boot options" can lead to success in special cases,
• If the boot process hangs with the message "waiting for devs to be fully populated ..." you can cancel this process with Ctrl + C,
• sometimes a device just won't boot with Labtix. Alternatively, an image can be installed with Parted Magix or Clonezilla Live. The content can then be installed from Labdoo.
• There is always the option of installing a hard drive pre-installed with Labdoo.

Installation aborts:

• Destination disk damaged? Check with check disk.
• Contact to the install disk or the server used is not stable? Or files do not exist on the specified paths?
• The Labdoo images use a block size of 4096 bytes. This can cause problems with a few SSDs/NVMEs. Unfortunately, the only solution is to replace the hard drive.
• The target hard drive could be too small for the selected image and content.
• In general you should carry out an installation with a freshly booted Labtix. If the installation scripts were aborted or hard drives or shares were added or deleted in Labtix, artifacts in the operating system may prevent the installation scripts from running correctly.
• Some hard drives have write and/or read protection. The values in Disk-Check then look normal, but no partitions can be deleted or created. The only quick solution here is to replace the hard drive.

MacBooks:
Note: Labdoo Germany accepts MacBooks as IT donations. Labdoo Switzerland does not.

• If Labtix does not boot (which is the rule), hold down the Alt key immediately after pressing the power button until a selection of bootable media appears.
• The computer's NVRAM may need to be deleted first:
• Power button, then hold down "Alt", "P", "Cmd", "R" at the same time for approx. 30 seconds,
• In Labtix, pay attention to the clock frequency, if necessary limit it to approx. 2 Ghz with Cpupower-Gui to avoid overheating during the installation of Labdoo. Use the temperature_workaround in Labdoo!
• MacBooks with the T2 chip are unfortunately not compatible with Labdoo. The same applies to the new MacBooks with ARM processors.

Labdoo does not boot:

• Try booting via the computer's boot menu. Common keys: Esc, F9, F12 on tablets/convertibles Power + Vol"+" or Vol"-". If necessary, together with the Fn key.
• Use Gparted in Labtix to check whether the installation on the hard drive looks correct:
• Standard installation: grub2core.img, efi partition and Linux partition present and extended to the entire drive?
• Legacy installation: Linux partition present and extended to the entire drive?
• "Boot flag" and efi flag (standard installation only) set?
• Check the hard drive again with Disk Check in Labtix. By deleting hard drives with "shred" when installing Labdoo, they can be damaged if they were already on the brink anyway.
• The boot mode may need to be changed in UEFI. Sometimes Labtix only boots in UEFI mode on the same device, but Labdoo boots in Legacy or CMS mode or vice versa
• Move Labdoo up in the boot order in the UEFI,
• look in the boot menu of the computer to see whether the Labdoo installation appears there and whether it can be started from there,
• Start Labdoo using Super Grub 2 Disk (https://www.supergrubdisk.org). Connect to the Internet. Open a terminal with "Ctrl" + "Alt" + "T" and reinstall the bootloader with the command "sudo grub-install". This may cause Labdoo's bootloader to be entered into the computer's firmware.
• Start the computer with "Boot Repair Disk" ( link ), establish an internet connection and follow the instructions. Can solve one or two UEFI problems.

Get more messages:
In its default setting, Labdoo does not display the kernel boot messages during booting, but rather the Mate boot logo ("plymouth"). However, if booting or shutting down hangs or takes a long time, you can use the boot messages to diagnose possible sources of error.
To display the boot messages while Plymouth is displayed: press "ESC" + "F1"

If you want to show all messages:

• After switching on, use the shift key to make Grub's boot menu visible. If necessary, try several times, the default time window is 3 seconds!
• If you are in the boot menu and the first entry is activated, press the "E" key to enter editor mode.
  Find the line with linux /boot/vmlinuz.... and replace quiet splash with noplymouth. The American keyboard layout applies!
• Boot with F10.

The most recent boot messages can be used to search for errors on the Internet. When searching, always specify the device used.
The changed settings only apply once, so they have to be changed every time you boot.
When the computer boots into Labdoo, the "dmesg" command in the terminal displays the boot messages. Problems are usually displayed in red.

Secure boot activated and cannot be deactivated
Important note: Labtix does not boot with Secureboot!!! However, the Grub boot menu appears and the message “secureboot” appears at the bottom left. However, it is often possible to access the UEFI in order to deactivate Secureboot via the Boot Rescue Menus >> Reboot into BIOS/UEFI Setup entries.

On some computers, Secureboot can only be deactivated if an administrator password has previously been set in the UEFI.

There is a small trap with some Acer computers: if you deactivate Secureboot and set the boot mode to "UEFI", Secureboot is automatically activated again!

If the computer's UEFI is protected with an unknown password and Secureboot is activated, it is still worth trying to install. As a rule, all *buntus like Ubuntu Mate, the basis of the Labdoo images, can be installed easily with Secureboot.

Since Labdoo images are installed through cloning, the installation step in which the Ubuntu secureboot certificate is entered into the computer's firmware is no longer necessary. This means that, depending on the computer firmware or the secure boot settings, the computer is prevented from booting Labdoo. Nevertheless, it is worth a try to have the certificates subsequently entered into the firmware. Unfortunately, this doesn't always work.

Installation of Labdoo:

• The quickest way to work is to install a hard drive pre-installed with Labdoo.
• Does the computer still have to be installed, e.g. because of a soldered hard drive
• Installation with Clonezilla in Parted Magic, then install contents in Labdoo.
• If the Labdoo installation does not boot: see "Labdoo does not boot".

Once Labdoo has been made to boot (unfortunately this is not always possible), an update must be carried out:

• Connect to the Internet and open a terminal with "Ctrl" + "Alt" + "T" and enter the following commands one after the other:
• sudo apt update >>> check for updates,
• sudo apt upgrade >>> run the updates.
• If asked, answer yes and provide the Labdoo admin password.
  During the update you should be asked whether you want to create a secureboot password. This must be answered in the affirmative and entered accordingly. Write on a piece of paper and keep it safe :-)) . It may be that if there are changes to the hardware (e.g. new WiFi card) the password will be requested!
• Restart Labtix once, then enter sudo apt autoremove >>> in the terminal to remove unnecessary files.

For very inflexible devices:
Unfortunately, this type of installation is not trivial, which is why the procedure can only be outlined superficially. If you really want to give it a go, you'll have to search online from time to time to get further:

• Install a hard drive pre-installed with Labdoo in the device,
• Install Xubuntu on the device in parallel. During the installation, the kernel or its secure boot certificate is entered into the UEFI partition and the firmware of the computer.
• In the corresponding window, select the option "Install Xubuntu alongside Ubuntu",
• during Xubuntu installation, set the partition size for Xubuntu to approximately 12 Gb,
• After installation, set the default boot entry of the Grub bootloader to the partition with Labdoo. Unfortunately it's not entirely trivial; it's best to use the Internet to find out,
• After booting into Labdoo for the first time, update the system once as described above.

...and if nothing works, send the IT donation to the central post office... ;) (Labdoo Germany only)

Labtix has two boot menus. Once the menu for legacy boot and the menu for UEFI boot. Whether you boot into the legacy or UEFI boot menu depends on the settings in the UEFI. On many devices, both options can be selected via the computer's boot menu.

Legacy boot menu from Labtix:
Set the desired options using the corresponding function keys (e.g. F2 for language or F4 for kernel boot options) and, if desired, set them up permanently with F8. A reset is possible at any time with F8 > Reset. Alternatively, you can also enter it directly in the “Boot Options” line. After the next reboot, the boot menu contains the menu entry "Custom..."

Labtix UEFI boot menu:
The UEFI boot menu contains the “Advanced Options” entry through which options can be set up and saved using submenus.

Persistence mode

In persistence mode, all your changes are saved, such as . Network connections, Firefox bookmarks, changes within the Labtix environment, etc. . Installing programs and saving files is also possible.

• To do this, press F5 in the Labtix grub menu in legacy mode and select "persist_all",
• then press F8 and select "save",
• then you boot e.g. "antix-21 x64-base ...",
• When asked for the rootfs persistence file, press "Enter" for the default size,
• When asked for the homefs persistence file, press "Enter" for the default size,
• If you are asked for the live USB swap file, select "n" for "no",
• The question "Do you want to copy the files to the home persistence device?" answered with "y" for "yes",
• The question "Please choose auto-save mode" answered with "2" for semi-automatic,

If you wanted to use changes via persistence, you should not boot toram and remove the stick, because then Labtix cannot save your changes when you shut down.
Using the ISO Snapshot and Live USB Maker tools in Labtix, a new bootable stick can be created that includes all changes. The Unetbootin we previously recommended for creating live USB sticks uses the fat32 file system, which limits the maximum persistence size to 4 GB. The Live USB Maker uses ext4 as the file system and therefore allows for greater persistence. If the Live USB stick was created with the dd program or the "dd" option of the Live USB Maker, it is not possible to permanently set up boot options and set up persistence. The corresponding options do not appear in the boot menus.l

Helpful terminal commands

Even if, contrary to popular opinion, the use of a terminal in Linux is not absolutely necessary, it does offer some advantages. Terminal commands give you output faster than pushing the mouse. Terminal commands can be controlled and linked in a variety of ways using arguments and are therefore the method of choice for more complex problem solving.

To open a terminal, click on the icon at the bottom left of the bottom menu bar or press Ctrl + Alt + t on the keyboard.

If a command is refused with the note "permission denied" or root rights are required, type "sudo" before the command used, e.g. "sudo zzzfm"

For further information use the --help option e.g. "apt --help" or the man pages "man apt"

The Labtix 1 version of the Labtix installation tool is no longer being developed. For current images Labdoo recommends the current version Labtix 2 https://platform.labdoo.org/de/content/installation-mit-labtix.

Labtix 1 is still able to process older 32 bit images. However, these are no longer maintained.

Based on Antix 17 (2017), you get a complete set of refurbishment and installation tools. Labtix 1 runs on 32 bit and 64 bit CPUs. The drivers included in Labtix 1 work best on older hardware (ca. 2008 - 2018, difficult to delimit exactly, best you try it out).
You need for Labtix 1

• at least a 2 GB USB stick or a CD (750 MB) to install and run Labtix 1 on it,
• 1 GB RAM (besser mehr, speziell wenn ihr den Persistenzmodus nutzen möchtet).

Version	until Ubuntu 20.04 LTS	from Ubuntu 22.04 LTS
Labtix 1
Labtix 2

Labtix comes with various tools and installation tools https://platform.labdoo.org/de/content/vorinstallierte-tools-labtix.

Most of them can be found directly on the desktop. You have to decide for yourself which tool suits you best:

• "2-click" installer - from the file manager SpaceFM (up to Labtix 1.02) / zzzFM (from Labtix 2.0) clone images with 2 clicks. From Labtix 2.0 the standard installation procedure.
• Labdoo Installer - with graphical user guidance (only Labtix 1)
• autodeploy and content installer - comprehensive, terminal-based installation tool that also automates the deployment of additional content in multiple languages

On the Labtix desktop, you will find a Docs folder containing manuals in PDF format. However, we recommend that you first watch the individual steps and tools as a YouTube video tutorial.

Labtix 1

https://www.youtube.com/watch?v=DkmrV3tvt-U

Nur für Labtix 1

Labdoo Installer - the compact installation tool with graphical user interface (English)

• Start by double click Labdoo Installer,
• 2 windows open; the terminal shows whether it is 32 and/or 64 bit CPU; the 2nd window shows the hard disk on which is installed (in most cases. sda. Confirm by ok.
• in the next window:
• shred = Number of deletion runs (from 0 to 3 possible, 3 preset)
• Target Disc sda (may not be mounted)
• Display the size of the hard disk (just for info, to better choose the appropriate image)
• Choose Image → click on the triangle next to home → Select Other... → then navigate to(!) the folder where the unpacked image is located (just marking the folder is not enough); confirm with "Open".
• optional: Enter Host_ID, if already known (but can also be entered after restarting the computer)
• click "OK" to start the installation.

In Labtix 2 this function has been integrated into the file manager zzzFM. A separate script could be dispensed with.

[Archiv, outdated / veraltet]

autodeploy and content installer - the comprehensive, terminal-based, script-driven installation tool (German)
the new version (since September 2018 part of Labtix,) also automates the deployment of learning content to multiple language (not seen in video)

Manual (pdf) http://ftp.labdoo.org/download/install-disk/labdoo%20autodeploy%20and%20...

Requirements

1. A 4GB or larger USB flash drive to create a bootable image
2. (Optional but recommended) Another 4+GB USB drive or external HD to store the files that you will download later
3. At least 40GB free on the Mac HD

Downloading Files
Download the following files from labdoo@ftp.labdoo.org:/macOS-ubuntu:

• refind-bin-0.12.0
• ubuntu-mate-20.04-desktop-amd64.iso
• unetbootin-mac-681.dmg

It is strongly recommended that you install and use a download manager software (e.g. FileZilla) to download the files since the iso file is huge, and the download manager can resume the download just in case you lost the connection. Save the files to a USB drive or external HD. Below is a screenshot using FileZilla:

Create Bootable USB
Do the following on a working Mac. Otherwise, complete “The Mac Side” section and come back here.

1. Insert a blank USB
2. Double click on the file unetbootin-mac-681.dmg that you downloaded earlier



3. Right-click and select Open
   
4. Click the Open button
   
5. Enter the password if prompted. The UnetBootin application will open. Select “Disk Image” option and the Ubuntu ISO file you downloaded earlier
   
6. Click OK. UnetBootin will extract and copy a bunch of files to the USB drive.
7. When it’s done, eject the USB drive by clicking on the Eject icon:
   

The USB drive now can be used to boot any Mac.

If MacOS is missing
You will need to have Wifi and internet access to reinstall macOS.

1. Booting the laptop.
2. If it prompts you to install a new OS, simply connect to your WiFi and follow the screen
3. Otherwise, reboot the laptop, holding both the Command and R keys until you see the Apple logo. Then select “Reinstall macOS” from the menu

If MacOS is present
If you know the password of the admin user, congratulations!. Otherwise, follow these steps to reset the password:

1. Reboot the laptop, hold the Command + R keys until the Apple logo appears.
2. Select Utilities -> Terminal to launch a terminal.
3. Type resetpassword (yes, one word) at the terminal. Follow the screen to reset the password for each existing account.
4. Restart and log in using the new password

“Labdooing” the Mac
Create Labdoo Accounts
You will use the existing admin account to create two new accounts: “student” and “labdoo” and then remove all non-labdoo accounts.

1. Log in as the current admin account
2. Select “System Preferences” -> “Users & Groups”
3. Click the lock icon to unlock. Type password when prompted
4. Click ‘+’ to add a new account. A new account form will pop up
5. Create “labdoo” account - fill in the form with the following values:
1. New Account: Administrator
2. Full Name: labdoo
3. Account Name: labdoo
4. Password: labdooadmin
5. Verify: repeat the password
6. Password hint: can leave blank
6. Create “student” account - fill in the form with the following values:
1. New Account: Standard
2. Full Name: student
3. Account Name: student
4. Password: labdoo
5. Verify: repeat the password
6. Password hint: can leave blank

Delete Non-labdoo Accounts

1. Log in as “labdoo”
2. Select “System Preferences” -> “Users & Groups”
3. Click the lock icon to unlock. Type password when prompted
4. Select a non-labdoo account, click the ‘-’ to remove the account
5. Select “delete user directory” option. Confirm deletion when prompted
6. Repeat step 4 and 5 for all remaining non-labdoo accounts

Change the Computer Name:
We will change the computer name to the labdoo Tag ID:

1. Generate a tag ID for this computer if it doesn’t have one yet
2. Click “System Preference” -> “Sharing”
3. Change the computer name to labdoo-000xxxxxx, where xxxxxx is the tag ID.

Create a Partition for Ubuntu

1. Run Disk Utility: Select Go -> Utilities -> Disk Utility
   
2. Disk Utility screen
   
3. Click “Partition”. A dialog box will pop up. Click Partition again
   
4. Click the ‘+’ sign. A new partition will be added. We now have 2 partitions, each occupies 50% of the disk space. Name the new partition “UBUNTU” and set its format to MS-DOS(FAT).
   
5. Click Apply
   
6. Click Partition
   
7. Click Continue. The process may take a while.

We are now ready to install Ubuntu on the new partition. But there is one task left: to install a boot manager.

Install rEFInd Boot Manager
Disable SIP (System Integrity Protection)
SIP protects critical areas on the disk from being altered, and rEFInd needs to write to one of those areas. Thus, we need to disable SIP before installing rEFInd

1. Check to see if SIP is enabled or disabled. Open a Terminal and type “csrutil status”
   

If it says “enabled” like in the capture above, follow the steps below to disable it

2. Reboot and hold the Command + R key until you see the Apple logo. It will boot into Recovery mode.
3. Select “Utilities” -> “Terminal”
4. At the terminal, type csrutil disable
5. Reboot and log back in as labdoo

Installing rEFInd

1. Open a Terminal
2. Open the folder where you downloaded the files earlier
3. Arrange the Terminal window and the folder window so you can see both at the same time:
   
4. Drag and drop the “refind-install” file into the Terminal folder
5. In the Terminal window, hit Enter or Return key to execute the command. Enter the password when prompted
   

We are now ready to install Ubuntu.

1. Insert the bootable USB drive that you created earlier
2. Reboot. The rEFInd boot menu will show
3. Select EFI\BOOT\grubx64.rfi from {your USB drive name} and hit Enter
4. Select “Try Ubuntu MATE without installing”
5. After a few minutes or so, you should see the Ubuntu desktop
6. Click on Install Ubuntu MATE 20.04LTS
7. Follow the screens to complete the installation. IMPORTANT:
1. Under the “Updates and other software” screen, make sure you select “Install third-party software for graphics and WiFi hardware and additional media formats”. Click Continue. Then connect to your WiFi network when prompted.
   
2. Under the “Installation Type” select “Something else” option
   
3. Select the partition with format fat32 which we created earlier using Disk Utility
   
4. Double-click the highlighted entry. A dialog box will pop up. Select:
   Ext4 journaling file system
   Check “Format the partition”
   Mount point: /
   
8. Click OK
   
9. Click “Install Now” and follow the screens to complete the installation. At the “Who are you” screen, create the labdoo account and use the tagID for the hostname:
   
10. When the installation completes, click restart to reboot the system. Hold the Option key while the system reboots until you see the original boot menu

    IMPORTANT NOTE:
    The installation of Ubuntu overwrites the EFI boot area that we created earlier in the “Installing rEFInd” section. But without the EFI boot area, the Ubuntu installation would fail for some reason that I haven’t figured out. Thus, we’ll have to install rEFInd again.

11. Select booting from macOS partition and hit Enter key
12. Repeat the steps in the Installing rEFInd section again

Enable SIP

1. Reboot into recovery mode: hold Command + R key while rebooting until the Apple logo appears
2. Select Utilities->Terminal to open a terminal
3. Type “csrutil enable” and hit Enter key
4. Reboot