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...
• UEFI: 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 will be 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) .

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.

Check the hardware with Labtix
To start, you should check a donated computer. After all, it makes no sense to send a laptop to hot countries that already overheats in cool regions. Or if the hard drive is already "crumbling", how is it supposed to survive transport and operation in hot regions? That's why Labtix comes with useful tools to check not only the hard drive, but also speakers, temperature sensors under load and much more. more to check, if necessary to clean fan, to renew thermal paste or foil.

BIOS settings
Some laptops require changing BIOS settings:

Recommended hardware checks

If you already have a bootable CD or USB Stick with our Labtix installation environment and Laboo Images for cloning, you can skip this chapter.

Thanks to the Labtix tool (LiveCD), all pre-installed learning content in labdoo systems can be "cloned" quickly and easily to new computers using the so-called images.
These images are available in 4 languages (English, Spanish, German, French). So you can select the language in the target country of the IT donation depending on the language and manually upload further learning contents in further languages.

You need two things for that:
Labtix bootable media: this can be a CD or USB stick, that you use to boot the Laptop you want to have restored, into the Labtix einvironment.
External USB hard drive: to store the cloning images and other learning content from our FTP server (Labdoo also provides an already prepared USB Drive to the volunteers, please contact your local Hub).

Labtix: The Labdoo installation environment

To be able to install older and newer computers with a license-free tool, Labdoo.org has a small solution (live-image) based on the Linux-Version Antix which we have called Labtix (a combination of Labdoo and Antix).

In Labtix you will find everything you need to delete old data on a donated computer or laptop, for fast and automated installation proceses in order to obtain a ready-to-ship computer. Additionally, Labtix provides many tools to diagnose hardware, to analyze and solve problems (CPU/processor, temprerature problems, damaged hard drives, etc.)

You can download the iso file for Labtix from our FTP server
here (MD5SUM).

Once you have downloaded the file, you can create a boot media (CD or USB) from the iso file, which you will use to start and prepare (Sanitation process) donated computers

Creating a bootable USB or CD/DVD from the Labtix ISO

The next thing to do is to convert the ISO file into a bootable CD or USB bootstick (simple copying is not enough!). This often works with file managers of your favorite operating system or with additional tools. For further questions consult the web (search for "cd / USB stick create ISO" and your operating system).

A blank 750 MB CD is sufficient for one CD (DVD is not necessary), USB sticks go from 1 GB (but usually 4 GB is the smallest size you can get). Note for technicians: Labtix has a persistence mode, with which you can save your desired configuration. However, this takes up more space, therefore 4 GB or more is better.

WINDOWS:
- Download and run a program for creating bootable media. For example, Rufus: https://github.com/pbatard/rufus/releases/download/v3.4/rufus-3.4p.exe (link is external) or another alternative https://alternativeto.net/software/rufus/
(link is external)
- Run Rufus, select the USB device, click on the "Select" button and select the labtix.iso file, then click on ''Start''.

LINUX:
you will find many useful tools for Linux in the following link: https://wiki.ubuntuusers.de/Brennprogramme/
(link is external)

But the easiest and fastest way is using dd. Once you know the device path to your USB key (in the example /dev/sdb) run:
dd if=Labtix.iso of=/dev/sdb bs=1M; sync
(see details explained under: https://antixlinux.com/forum-archive/writing-antix-iso-image-on-usb-flas...)

MAC OS:
You can use the following procedure: [https://osxdaily.com/2015/06/05/copy-iso-to-usb-drive-mac-os-x-command ]
(Here we refer to Internet and search engines).

Labdoo-Cloning images method and additional content

For the Fast Restoration method, you need to clone the Labdoo Images. For cloning, you have to download the images first. Images are copies of a complete, pre-installed system (of already sanitized laptops). Linux has a great feature that other operating systems don't have. You can transfer a system from computer A to computer B - and it runs!

You will find these images online in our Labdoo FTP server http://ftp.labdoo.org/download/install-disk/.
You can also download these images from the web browser by selecting the image you want to download, right-click on it, and then select "save link as".

This does not work for folders or for many files! These have to be downloaded individually and of course, this is a lot of work.
Simple methods for downloading multiple files for all common operating systems can be found at https://www.labdoo.org/de/content/zugang-zum-ftp-server

Images are large and the download takes a long time, so If you are familiar with FTP clients, we recommend downloading them directly via FTP (sftp, userlabdoo and password labdoo).

Labdoo Images for Cloning

When deciding what image is best for you, you should consider the following aspects:

• The CPU/processor architecture of the computer you are currently working on (32 bit or 64 bit). You can easily figure this out with the Labtix environment. It will be displayed in the upper right corner of your desktop (see also the video above).
• The target language you want to install.
• The size of the hard disk in the computer to be refurbished. This size is displayed e.g. in the BIOS or after booting Labtix.

The name of an image on the FTP server shows:

• There are 4 directories for the 4 available languages:
  • English (EN): http://ftp.labdoo.org/download/install-disk/EN_English_images/ : includes versions for 80, 160 and 250 GB Hard drives.
  • German (DE): http://ftp.labdoo.org/download/install-disk/DE_German_images/ : requires a minimum of 80 GB HardDrive.
  • Spanish (ES): http://ftp.labdoo.org/download/install-disk/ES_Spanish_images/ : requires a minimum of 80 GB HardDrive.
  • French (FR): http://ftp.labdoo.org/download/install-disk/FR_French_images/ :(requires a minimum of 80 GB HardDrive)
• PAE32 = for 32 Bit-CPUs ; PAE64 = for 64 Bit-CPUs
• Other 18.04 images Different sizes for 32 BIT-CUPs and 64 Bit-CPUs: http://ftp.labdoo.org/download/archive/18_04_archive/
• xx_04_LTS = version of Lubuntu it is based on, either 16.04 LTS (kept for legacy), or 18.04 LTS (to be used from 2018 on).

imagesThe French and Spanish images occupy 80 GB because they already have the learning content in these languages (Wikis, OER Open Educational ressources,...). The German image is additionally played with German courses, dictionaries in many refugee languages etc..

The English images of 80 Gbs as well, but the larger images (160,250 Gbd) include even more learning contents

Additional learning content

Additional learning content can be added after the installation process if you are not using the autodeploy.sh method that allows you to add additional content during installation. We will come back to this later...

External USB hard disk preparation (1+ TB)

The downloaded images are already unpacked and ready to use. Copy 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 filesystem for an external hard disk.

The automated installation scripts require to be saved to an external hard disk without a parent directory, as they are stored on the FTP server. For further details please refer to the manual http://ftp.labdoo.org/download/install-disk/labdoo%20autodeploy%20and%20...

This section describes how to use the file manager SpaceFM (Labtix 1) or zzzFM (Labtix 2) to clone images with just 2 clicks.

Labtix 2

https://youtu.be/Q7WMvF1QXX8

Labtix 1

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

For Labtix 2: 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 SpaceFM (Labtix 1) oder zzzFM (Labtix 2).
• Mount the drive on which the images for cloning are located.
• für Labtix 1 und 2: 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 "+".
• Labtix 1: On a server: Plugins→MountShare→Scan and manually enter the IP address of the server, if necessary select Share from the list, User and Passwort→Mount.
• Labtix 2: 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 1: Labdoo Image Installer
• Labtix 2: labdoo-legacy-installer or labdoo-UEFI-installer (depending on system settings and boot)
• in the next window
• Labtix 1: leave the "shred sda" tick (disk will be overwritten 3 times) or remove it (disk will not be deleted),
• 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.

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.

Helpful comnands (shell, terminal)

To open a terminal click on the terminal icon in the menu bar or press the keys Ctrl and Alt and t.

If access to a command is denied ("permission denied") or root rigts are needed, add "sudo" in front of the command to be used, e.g. "sudo zzzfm"

For more information use the --help option e.g. "apt --help"

======================================================================
acpi (-V) >> information about the powersystem like battery-state, battery-condition etc.

======================================================================
(sudo) apt >> package manager

Usage:

sudo apt update >> create the needed package database
sudo apt install mousepad >> installs the program "mousepad"

Only usefull in the persistence mode. The device must be connected to the internet.

======================================================================
eject -T >> ejects CDs or DVDs

======================================================================
grep >> filters the output of commands

acpi -V | grep -i battery >> shows only the lines of acpi -V wich contain the term "battery"

======================================================================
(sudo) inxi >> system information

sudo inxi -v 5 >> informations with verbosity level 5 (1-8 possible)
inxi -B >> battery information
sudo inxi -M >> informations about the system
inxi -m >> informations about the memory

Sudo is only needed if informations inxi gathers need root permissions

======================================================================
iwconfig >> shows informations about wireless connections

======================================================================
lsblk >> lists blockdevices like harddisks

======================================================================

======================================================================
lspci >> lists all recognized pci-devices

lspci | grep -i Network ( or Wireless or WLAN ) >> shows Wifi-devices

======================================================================
lsusb >> lists all recognized USB-devices

======================================================================
rfkill >> tool for radio devices

rfkill list all >> lists the states of all radio devices
rfkill unblock all >> unblocks all softblocked devices

To unblock a hardblocked device:

- look for a hardware switch
- look for a keyboard function/binding
- look if the device is blocked in the UEFI/BIOS

======================================================================
(sudo) shred >> tool to securely delete devices or partitions

Usage:

sudo shred /dev/sdX -v -f -n 2 >> overwrites sdX 2 times

Shred will overwrite each single byte of the target device, so it might take a long time.

BE CAREFUL !!! BE SURE TO USE THE PATH TO THE DEVICE/PARTITION YOU REALLY WANT TO CLEAN !!!

======================================================================
sudo >> command to get root permissions

In labtix no sudo-password is installed, so typing in a password is not needed

======================================================================
wipefs >> tool to delete filesystems

Usage:

sudo wipefs -a -f /dev/sdX >> wipes the filesystem of sdX

BE CAREFUL !!! BE SURE TO USE THE PATH TO THE DEVICE / PARTITION YOU REALLY WANT TO CLEAN !!!

This is not a secure method of deleting any devices, it's the quick and dirty solution if you want to get rid of an installed system. For safe deletions use the command "shred"

======================================================================
xkill >> tool to kill windows that are not responsible

Usage:

Open a terminal, type "xkill" and press "Enter". The mousepointer will be shown as a skull. Leftclick with the skull inside the window you want to close. Xkill will only close windows. In some cases processes started by the killed window might still run in the background.

Do not click on the Desktop, it is a window too !!!

======================================================================
xrandr >> tool to manipulate the graphical-(x-)server

xrandr --output eDP-1 --scale 0.5x0.5 >> reduces the height and width resolution of output eDP-1 by the factor 0.5 . Very useful if the screen has a very high resolution.

To get the name of the actual output:

xrandr | grep primary

======================================================================

[This page explains a solution in case a donated computer can only boot with UEFI or the BIOS is locked (password unknown) and UEFI is set as the boot option. If your computer can boot in legacy mode, you can skip this page].

Back in 2013/2014, there was a technical and legal discussion about SecureBoot and UEFI. The manufacturers argued that only UEFI boot on their computer provides security and therefore must only be used. However, the EU and NGOs went to court and the judges decided that the computer manufacturers had to re-open the BIOS settings so that users could choose whether to use the UEFI boot, the legacy boot (the "old" boot) or both as boot options. Computers that were produced before the "UEFI only" decision and after the old flexibility decision have no problem installing with Labtix and prepared Labdoo images.

However, if the computer was manufactured in the "UEFI only" period in 2013/2014, this may cause problems when installing a Lubuntu-based installation. Our Labdoo images are set up for legacy boot, not for UEFI boot (although Lubuntu could). We have described a solution for these specific UEFI-only machines here.

Another use case is a locked BIOS. A computer has been donated, but a BIOS password has not been removed and is unknown. If the boot option in the BIOS is set to "UEFI / Secure Boot Only" and cannot be switched to "Legacy Boot" because of the password lock, you can run the installation process described below and then use the computer for Labdoo.

If our solution is too difficult for you, please contact Labdoo helpers or hubs in your country / region and ask them for support.

You can use the installation tool Labtix (recommended, supports UEFI-Boot) or Parted Magic. PXE is not possible because you have to select certain options during the installation process and PXE does not allow access to these settings.

The installation sequence is rough:

• First install a small Xubuntu based image via cloning in a partition (Xubuntu is able to UEFI boot); a prepared image is available on FTP server http://ftp.labdoo.org/download/install-disk/special_images/,
• Next ,install in a second partition of one of our Labdoo images with slightly different settings than usual.
• Change the grub boot file.
• After that, the system will boot and a user will not even notice that this is a special "UEFI only" laptop.
• This solution only works for 80 GB disc-drives or bigger.

So here are the steps in details:

1. Download the special UEFI-Boot image, available on our FTP-Server http://ftp.labdoo.org/download/install-disk/special_images/ and copy it to a local USB-drive or any local server.
2. Start Labtix, run the Clonezilla tool (icon on the Labtix desktop) and make the drive with the special UEFI image available - Important: Use "expert mode" and "restoredisk", mark the option -icds . For experts: Or install Xubuntu (I think all other UEFI based * buntu do it too) in UEFI mode on the device.
3. If you use the prepared UEFI image, the size of the partition sda2 is set to 80 GB by default. A Labdoo image for 80 GB fits. If you want to install an image for a 160 GB or 250 GB hard drive, you have to enlarge the partition sda2 with GParted.
4. Shut down the computer and restart it with Labtix.
5. Start Clonezilla to replace sda2(!) of the installed UEFI-Boot image / Xubuntu by replacing "restoreparts" with sda1 of the Labdoo-image you want to install. Make sure you choose the target-partition sda2 when asked and the "-icds"-option in "Clonezilla advanced extra parameters". Make sure the option "-k Do NOT create a partition table..." is checked.
6. After installing sda2, use GParted to maximize sda2. Check if the "boot"- and "esp"-flags are set to sda1. To retrieve the UUID of sda2 right-click on it and select "Information". Mark the UUID and copy it with "Ctrl" + "C" to the clipboard.
7. Edit /EFI/ubuntu/grub.cfg in the EFI-bootpartition ( usually sda1, the small partition with 512MB ) with the editor Geany and replace the given UUID with the UUID of sda2 you copied by GParted. E.g. open SpaceFM -> sda1 -> navigate to /EFI/ubuntu/grub.cfg -> right mouse click -> open > Geany editor -> in line 1 you will see a UUID -> mark and paste the new UUID from the clipboard. Don't forget to save the file before closing Geany editor.
8. Shut down and restart the computer. Now it should start in UEFI mode and users will see the Labdoo login after a short time.

This description is very technical, but it works. If you know a simpler solution, please feel free to contact us.
A special thank you goes to helpers from hub Rhein-Ruhr (Germany) for noticing and solving this specific problem.