docs: update releases/omlx41/errata

This commit is contained in:
ru ru 2020-04-26 09:01:52 +01:00 committed by omakuta
parent f8458ab6f8
commit db90faf5b8
1 changed files with 16 additions and 1 deletions

View File

@ -2,7 +2,7 @@
title: OpenMandriva Lx 4.1 Errata
description:
published: true
date: 2020-04-24T16:47:03.336Z
date: 2020-04-26T08:01:51.123Z
tags: 4.1
---
@ -78,6 +78,21 @@ $ sudo pkcon refresh force
```
If you want to explore also additional repositories packages you will need to enable them by mean of [Software Repository Selector](/en/doc/repositories-tldr) and refresh cache again.
## Multiboot
In the 'real world' multiboot works well most of the time but when there are problems sometimes the solution is a workaround rather than a fix. These are just realities of multiboot.
Also it is not currently possible for OpenMandriva QA to test our bootloader with every file system type on every Linux distro, or even on "Top 10" Linux distros. The fact is that whether multi-booting with Windows or other Linux distros we rely exclusively on users' reports to know what does and what does not work regarding multi-booting.
One known problem encountered with OM Lx bootloader is that OM Lx grub2 does not create boot entries for openSUSE systems that use btrfs file system. OM Lx grub2 does work with openSUSE systems that use ext4 file system.
This is because openSUSE uses custom syntax for their btrfs patches for openSUSE os-prober and grub2 packages that are not compatible with OM Lx code. It is not presently known if OM Lx bootloader does/does not work with openSUSE with any other file system types such as XFS or F2FS.
The workaround is for users to switch boot-loaders in UEFI firmware settings or BIOS.
Alternative may be to use openSUSE bootloader if it recognizes your OpenMandriva system.
As users report multiboot issues we will fix what we are able to. Issues we are unable to fix we will report in Errata for our OM Lx Releases.