## TLXOS 5 upgrade problems Unfortunately our first attempts at TLXOS 5 in February this year had some pretty serious bugs, especially for x86-based editions (RePC and SFF) and especially 5.2.0, that may have either prevented you from installing in the first place, or that might affect your ability to upgrade to 5.0.1 or 5.2.1. We performed emergency re-releases of TLXOS 5.0.0 and 5.2.0 with corrections for the most critical bugs on 14 March (everything) and 27 March (RePC and SFF only), but if you downloaded the original February release you may need to apply hotfixes. ## The tms_client "checksum mismatch" bug (5.2.0 only) Due to a coding error, the initial release of tms_client 8.4.2 was unable to correctly verify MD5 checksums using OpenSSL v3, i.e. on TLXOS 5.2.0. This bug was fixed in the 14 March re-release. If you find that you cannot install updates of any kind (firmware upgrades, hotfixes, or tms_client updates) because TMS or Tlxconfig reports that the update has an incorrect checksum, please apply the hotfix named "bogus checksum mismatch fix", and then reattempt whatever you were doing. You'll be able to install this particular hotfix because it deliberately has the incorrect-but-expected checksum in its metadata. The hotfix will replace tms_client with a patched version. ## The "stops at (initramfs) prompt" bug (RePC and SFF only) This problem only occurs when attempting to boot from an unpartitioned device, and therefore only affects installation of RePC and SFF via USB stick, since RPi and RePC Live are provided in a "preinstalled" format using a partitioned disk. ISO installers are not affected. This bug was fixed in the 27 March re-release of SFF and RePC 5.0.0, and RePC 5.2.0. If you encounter this bug, either re-download your 5.0.0 / 5.2.0 USB installer image and rewrite your USB stick with it, or install RePC 5.0.1 / 5.2.1 or SFF 5.0.1 instead. ## The other "stops at (initramfs) prompt" bug (RePC 5.2.0 only) This problem occurs when booting a RePC 5.2.0 USB installer on a system that already contains RePC 5.0.x or earlier. The initramfs repeatedly attempts to mount the Reiser4 root filesystem of the older release, which is not possible because the 6.1 kernel lacks Reiser4 filesystem support, and eventually fails with a fatal error. The ISO version of the RePC 5.2.x installer does not have this bug. This bug was fixed in the 27 March re-release of RePC 5.2.0. If you encounter this bug, either re-download your 5.2.0 USB installer image and rewrite your USB stick with it, or install RePC 5.2.1 instead. ## The "Fatal error in gpu init" bug (RePC and SFF only) This bug only affects devices with AMD GPUs (and will therefore only occur on SFF or RePC). Any attempt to boot an installer or enter Maintenance Mode will get permanently stuck, such that you are unable to install or upgrade to TLXOS 5.x at all. We provided some unofficial fix attempts to select customers, but this bug wasn't properly fixed until TLXOS 5.0.1 / 5.2.1. Since most customers won't have been able to install TLXOS 5.x on devices with AMD GPUs, and customers using RePC Live are likely only doing so for evaluation purposes and will never upgrade it, we don't intend to release 5.0.0 and 5.2.0 hotfixes for the bug. If you have managed to install TLXOS 5.x on a device with an AMD GPU and need to upgrade rather than reinstall it, please contact us for a workaround. Everyone else can just reattempt their install using a 5.0.1 or 5.2.1 installer. ## The "Integrity checking config filesystem ... failed" bug (RePC and SFF only) This problem occurs when attempting to perform a "TMSless" upgrade by entering Maintenance Mode on a system that already has the same edition of TLXOS installed, and that has a newer copy of the O/S available to it. In other words, when booting TLXOS 5.x USB or ISO installers or performing a Provisioning mode PXE boot, on a system that contains TLXOS 4.x or an older version of TLXOS 5.x (e.g. a 5.0.0 to 5.2.0 upgrade). It can also occur when using the AoE-assisted-but-not-PXE-boot upgrade method described in https://help.thinlinx.com/knowledgebase.php?article=68. The only available fix for this is to boot a 5.0.1 or 5.2.1 installer instead. This means that if you are attempting to upgrade from 5.0.0 or 5.2.0 to a later version using Provisioning mode PXE boot or similar, you will first have to upgrade your PXE server to 5.0.1 or 5.2.1 by some destructive means (e.g. re-imaging / forced re-installation).