The OpenMandriva Lx teams are pleased to announce the availability of OpenMandriva Lx 5.0.
This release is available as a live media USB flash drive (memory stick), downloadable in ISO format. These are available on our downloads page. USB flash drive installation is usually noticeably faster. As always speed depends on many factors. Live media means you are able to run OpenMandriva Lx straight from a memory stick (see below) and try it before installing it. You may also install the system to hard disk either from the running live image or from the boot manager.
Available ISO files:
Installable images will be available for the Pinebook Pro, Raspberry Pi 4B, Raspberry Pi 3B+, Synquacer, Cubox Pulse and generic UEFI compatible devices (such as most aarch64 server boards)
OpenMandriva Lx 5.0 requires at least 2048 MB of memory and at least 10 GB of hard drive space, 20 GB recommended for a Plasma desktop full installation.
Important Note: Graphics Hardware:
The KDE Plasma Desktop requires a 3D graphics card that supports OpenGL 2.0 or above. We recommend using AMD, Intel, Adreno or VC4 graphics chips.
Calamares Installer checks if an Internet connection is available, but OpenMandriva 5.0 will install just fine even without. It is perfectly OK to simply install as you normally would and proceed to use your new system as normal. Updating such a system would require being temporarily connected to the internet or downloading the packages elsewhere and transferring them to the installed system and installing the updated packages. But as you are not connected to the internet you could simply use the system and not update for how ever long you see fit.
At this time the only virtualization software that OpenMandriva 5.0 ISOs are tested on is VirtualBox. The same hardware requirements apply when running in virtual machines. For VirtualBox you must always have at least 2048 MB of memory or OMLx 5.0 will fail to boot. Also for VirtualBox it is advisable to install to a fresh virtual machine, as trying to install to an existing one may occasionally fail.
The Gnome ISO may need setting VMSVGA graphics controller to display correctly and properly boot in VirtualBox, as well as the most recent install images might.
Calamares is an installer framework. By design it is very customizable in order to satisfy a wide variety of needs and use cases. It aims to be easy, usable, beautiful, pragmatic, inclusive and distribution-agnostic. Calamares includes an advanced partitioning feature, with support for both manual and automated partitioning operations. It is the first installer with an automated “Replace Partition” option, which makes it easy to reuse a partition over and over for distribution testing. Many Linux distros use Calamares installer and each has its own implementation and standards. The user may notice some small differences but it does not mean this is a bug.
At this time partitioning LVM and Raid setups with Calamares installer are not supported.
The following applies to all partitioning of all installations on hardware: If you have a UEFI/EFI computer and your BIOS offers a choice when you boot installation media between for example:
USB some Flash Drive
UEFI USB some Flash Drive
You have to choose the UEFI option and boot that. But know also that not all computers will do this. Some with more spartan FIRMWARE or BIOS will offer only the one option and almost always it is the correct one. So for instance if on a notebook you don't see the above choice no worries. If you have multiple storage drives enabled they all need to have the same partition table type. They either need to all be GPT or all MBR for everything to work properly. On UEFI computers in multi-boot situation with multiple storage drives if you already have an existing
/boot/efi partition you should use that. The partitioner will not create another
/boot/efi with proper flags and installation will result in error with no bootloader installed. Do not format you just set the mount point to
/boot/efi and select the
boot flag. One can have many different boot loaders for different operating systems in the same
/boot/efi partition. If there is any need to switch boot loaders that is done in FIRMWARE or BIOS settings.
In the Calamares installer for OpenMandriva 5.0 the file system list includes all file systems the operating system recognizes for a host of reasons. This does not mean one should use anything in the list for your root (
/ ) partition.
ext4 is the official recommendation for root,
fat32 is the recommendation for
xfs are working in recent tests but these are much less often tested. We rely on user feedback for this. Based on recent testing
btrfs is not a good choice for multi-boot scenario.
Other files system types in the list are not recommended.
No official recommendation is made at this time for storage partitions or for a seperate
/home partition. It is expected the users using seperate storage partitions or a seperate
/home partition know what they are doing. For
/home the easy way is to use
ext4 (recommended) or whatever you use for your root partition.
NVME SSDs are normally recognized by OpenMandriva 5.0 Live ISO. If for some reason they are not we have couple of workarounds under 'Troubleshooting' in the ISO Grub2 Menu that may work. They are (PCIE ASPM=OFF) and (NVME APST=OFF). We hope this works for most peoples hardware. See more in Errata/NVME SSDs. This issue is of course very hardware specific.
This release of OpenMandriva 5.0 supports booting and installation with and without UEFI.
Note that secure boot is NOT supported.
Note it is NOT recommended to mix MBR and GPT partitions.
If you wish to perform an EFI installation on an existing MBR disk it will be necessary to convert the disk partition table to the newer GPT partitioning scheme. To do this you need to use the gdisk tool. A typical invocation would be gdisk /dev/sda: the existing partition table will be converted in memory to the GPT scheme. Warnings will be issued about potential data loss, the disk will not be altered until you write the partition table by pressing w. You are advised to back up any important data.
There may be occasions where the conversion cannot be performed, this will usually be due to insufficient space at the beginning or end of the disk to write the partition table. It may be necessary to delete or resize a partition to create the needed space, gparted is your friend in these circumstances.
There is still a need to create a
/boot/efi partition to contain the boot equipment and this must be created while running the Calamares installer. When the installer reaches the partitioning stage the
/ (root) partition should be removed and a small (300 MB) fat32 partition created at the start of the drive. The partition must be named
/boot/efi and the
boot flag set. If diskspace is critical then a smaller partition may be used, but be sure to set it as fat32 in Calamares otherwise the installation will fail. If you fail to observe these steps the installation of the boot loader will fail. Subsequently partition the disk in the normal way.
Please share your experiences on the forums so that we may improve this aspect of the installation.
If you are installing beside Windows 8, 8.1, 10 or similar EFI booted OS as a precaution please ensure that you have recovery disks and you have backed up any important data. Our testing has been limited with this configuration, but successful installations have been performed with no issues.
We would welcome any feedback in this area.
Please note that Calamares cannot convert one partition type to another and preserve partition data. If you run Calamares to change an existing partition type you must first delete the partition and recreate it as the type that you wish.
It is possible to boot this release from a USB storage device. To create the live/installation media you may:
sudo dnf --refresh install rosa-imagewriter
Or, if you do not have OpenMandriva Lx yet, you can get rosa-imagewriter download links at this page.
At least 4 GB of flash drive capacity is recommended. Persistent storage is not necessary. Note that this will erase everything on your USB!
Please do not use other usb-writing tools as some Windows tools (e.g. Rufus) truncate the volume name. This breaks the boot process.
sudo dd if=<iso_name> of=<usb_drive> bs=4M conv=fdatasync status=progress
Replace <iso_name> with the path to the ISO and <usb_drive> with the device node of the USB drive, i.e. /dev/sdb.
Booting from DVD is deprecated, still OpenMandriva 5.0 ISOs boot from DVD using Legacy or UEFI boot. Should you encounter difficulties there are 2 workarounds here that should enable one to boot from DVD. In testing booting OMLx 5.0 from DVD took 5-6 minutes. This may take longer on some hardware. Using a DVD for this purpose is a lot slower than using a USB flash drive.
We have om-repo-picker aka Software Repository Selector to select additional repositories for more package availability.
Do not mix the repositories from different release versions/update channels. This means, as an example, do not use Cooker repositories on a OMLx 5.0 system. If you use Rock, use Rock repositories only. This is explained in more detail in OpenMandriva Release Plan and Repositories. If you mix different release/update channel repositories and you break your computer the solution is to do a fresh install. After that fresh install do not do this again.
While graphical tools (Discover, dnfdragora, etc.) are useful to find out available extra software, we recommend users to install and remove packages from command line:
sudo dnf --refresh install <package_name>
To remove a package:
sudo dnf remove <package_name>
One may in install or remove a string of packages. Example:
sudo dnf --refresh install <package_name_1> <package_name_2> <package_name_3> <package_name_4>
More about package management with dnf here.
This is very easy, just copy and paste this command string:
sudo dnf clean all ; sudo dnf --allowerasing distro-sync
Then press Enter key and when prompted enter your root (superuser) password.
We recommend it because we see a lot of problem reports that begin with "I updated my system with Discover updater" or "I updated my system with dnfdragora".
Pipewire has become our default sound server together with WirePlumber, thus replacing PulseAudio.
However, PulseAudio is still in our repository and you can return to it at any time. To do that use this command string:
sudo dnf remove pipewire-pulse ; sudo dnf install pulseaudio-server
The standard kernel for OpenMandriva Lx 5.0 is clang compiled.
There are kernel-desktop-gcc and kernel-server-gcc versions available in the rare instance they are needed.
This is discussed in OpenMandriva Lx 5.0 Errata page
Should you have problems please report in the English Support forum with a descriptive title and enough description and information for someone to be able to help you. Or for possible faster results contact us at OpenMandriva Chat . If your issue is a serious technical issue then please file a bug report.
Please read also OpenMandriva Lx 5.0 Errata
You may want to have a look at the latest changes
The OpenMandriva development teams (Cooker & QA) are always looking for new contributors to assist in creating and maintaining packages and to assist bugfixing and testing. You are welcome to join us and help us in this work which is not only rewarding but also tremendous fun! If you feel that your talents do not lie in the realm of software, then the OpenMandriva Workshop group, which is made up from the artwork, documentation, translation and Communication teams, is always open for the submissions of artwork and translations. New contributors who would like to help with these wide-ranging tasks should see the wiki for more details, and to learn how to join! Alternatively you may use our forum.
It also costs time and money to keep our servers up and running. If you can, please donate to keep the lights on!