Software
/
wiki
mirror of https://github.com/OpenMandrivaSoftware/wiki.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: update distribution/releases/omlxrolling/notes

This commit is contained in:
ru ru 2022-10-19 08:07:44 +01:00 committed by omakuta
parent aa4364b603
commit 76b12a8df2
1 changed files with 29 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

57
distribution/releases/omlxrolling/notes.md
View File

@ -2,7 +2,7 @@
title: OpenMandriva ROME Release Notes
description:
published: true
date: 2022-10-13T22:27:33.209Z
date: 2022-10-19T07:07:40.020Z
tags: rolling, rome
editor: markdown
dateCreated: 2021-04-24T05:53:55.903Z
@ -11,21 +11,21 @@ dateCreated: 2021-04-24T05:53:55.903Z
# OpenMandriva ROME Release Notes
The OpenMandriva teams are pleased to announce the availability of **ROME** an OpenMandriva *rolling* release meant for majority of users.
The OpenMandriva teams are pleased to announce the availability of **ROME** the OpenMandriva *rolling* release meant for majority of users.
<br>
**Available Media**
## Available Media
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 are:
\- *x86_64 KDE Plasma desktop* full featured (includes the most common used functionalities, multimedia and office software).
\- *znver1 KDE Plasma desktop*: we have also built a version specifically for current AMD processors (Ryzen, ThreadRipper, EPYC) that outperforms the generic (x86_64) version by taking advantage of new features in those processors. znver1 is for the listed processors (Ryzen, ThreadRipper, EPYC) only, do not install on any other hardware.
**Available ISO files:**
- *x86_64 KDE Plasma desktop* full featured (includes the most common used functionalities, multimedia and office software).
- *znver1 KDE Plasma desktop*: we have also built a version specifically for current AMD processors (Ryzen, ThreadRipper, EPYC) that outperforms the generic (x86_64) version by taking advantage of new features in those processors. znver1 is for the listed processors (Ryzen, ThreadRipper, EPYC) only, do not install on any other hardware.
Installable images are offered for the Pinebook Pro, Raspberry Pi 4B, Raspberry Pi 3B+, Synquacer, Cubox Pulse and generic UEFI compatible devices (such as most aarch64 server boards)
<br>
**System requirements**
## System requirements
ROME requires at least 2048 MB of memory and at least 10 GB of hard drive space (see below for known issues with partitioning).
@ -34,22 +34,22 @@ ROME requires at least 2048 MB of memory and at least 10 GB of hard drive space
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.
<br>
**Internet Connection**
## Internet Connection
Calamares Installer checks if an Internet connection is available, but ROME 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.
<br>
**Virtual Machines**
## Virtual Machines
At this time the only virtualization software that ROME 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 ROME 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.
<br>
**Calamares installer**
## Calamares installer
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.
<br>
**Partitioning**
## Partitioning
At this time partitioning LVM and Raid setups with Calamares installer are not supported.
@ -62,12 +62,12 @@ The following applies to all partitioning of all installations on hardware: If y
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.
<br>
**Upgrading OMLx 4.3 system to ROME**
## Upgrading OMLx 4.3 system to ROME
See [Upgrading OMLx 4.3 system to ROME](https://forum.openmandriva.org/t/how-to-upgrade-rock-omlx-4-3-to-rome-rolling/4470)
<br>
**File system type**
## File system type
In the Calamares installer for ROME 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 `boot/efi`. `f2fs` *currently does not work* we hope to fix this in the future.
@ -78,12 +78,12 @@ 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 whatever you use for your root partition.
<br>
**NVME SSDs**
## NVME SSDs
NVME SSDs are normally recognized by ROME 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.
<br>
**Installer and EFI Support**
## Installer and EFI Support
This release of ROME supports booting and installation with and without UEFI.
@ -102,12 +102,12 @@ If you are installing beside Windows 8, 8.1, 10 or similar EFI booted OS as a pr
We would welcome any feedback in this area.
<br>
**Changing Partition Type**
## Changing Partition Type
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.
<br>
**Booting from USB**
## Booting from USB
It is possible to boot this release from a USB storage device. To transfer the live/installation image you may:
@ -129,18 +129,19 @@ Replace <iso_name> with the path to the ISO and <usb_drive> with the device node
- SUSE Studio ImageWriter has also been tested and works for burning ISO images to USB storage device.
<br>
**Booting from DVD**
## Booting from DVD
Booting from DVD is deprecated.
For all OMLx ISOs there are workarounds in [Booting OM Lx 4.3 ISO from DVD](https://forum.openmandriva.org/t/booting-om-lx-4-3-iso-from-dvd/4377) that should enable one to boot from DVD. Even though the forum post refers to OMLx 4.3 the instructions should work for ROME.
<br>
**About Repositories**
## About Repositories
We now have the 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 ROME system. If you use Rock, use Rock repositories only. This is explained in more detail in [OpenMandriva Release Plan and Repositories](https://wiki.openmandriva.org/en/policies/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.
We have [om-repo-picker](policies/repositories-tldr) 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 ROME system. If you use Rock, use Rock repositories only. This is explained in more detail in [OpenMandriva Release Plan and Repositories](https://wiki.openmandriva.org/en/policies/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.
<br>
**How to install and remove packages**
## How to install and remove packages
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:
@ -157,7 +158,7 @@ One may in install or remove a string of packages. Example:
More about package management with dnf [here](https://dnf.readthedocs.io/en/latest/command_ref.html).
<br>
**Recommended update procedure**
## Recommended update procedure
***Do not use Discover or dnfdragora to upgrade your ROME system***. The command they use is for Rock release and is not correct for ROME. This is very easy, just copy and paste this command string:
@ -166,7 +167,7 @@ More about package management with dnf [here](https://dnf.readthedocs.io/en/late
Then press Enter key and when prompted enter your root (superuser) password. We recommend this 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".
<br>
**New Features and Major Changes**
## New Features and Major Changes
In order to keep current with latest changes in Linux, computer security issues, and computer code writing there are major changes in ROME.
- The kernel has been updated to 5.19.8
@ -188,7 +189,7 @@ Upgraded also some cool stuff not on the ISO but available in our repositories
- LXQt 1.1.0
<br>
**Default sound server switched to Pipewire**
## Default sound server switched to Pipewire
PipeWire has become our default sound server in the current system release, 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:
@ -198,21 +199,21 @@ PipeWire has become our default sound server in the current system release, thus
[*Pipewire*](https://pipewire.org/)
<br>
**Clang compiled kernel**
## Clang compiled kernel
The standard kernel for ROME is clang compiled. Should user want a gcc compiled kernel for their desktop install `kernel-desktop-gcc`. Then find this and boot from it under 'Advanced Options' in the Grub2 Menu.
**What to do if I have a problem**
## What to do if I have a problem
Should you have problems please report in the [English Support forum](https://forum.openmandriva.org/c/en/support) with a descriptive title and enough of a description and information for someone to be able to help you. If your issue is a serious technical issue then please [file a bug report](https://github.com/OpenMandrivaAssociation/distribution/issues).
<br>
**Helping the project**
## Helping the project
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](https://forum.openmandriva.org).
<br>
**Donate to the project**
## Donate to the project
It also costs time and money to keep our servers up and running. If you can, please [donate](https://www.openmandriva.org/en/Donate) to keep the lights on!