docs: update distribution/releases/omlxrolling/notes
This commit is contained in:
parent
5fe023d731
commit
d6722e94ef
|
@ -2,7 +2,7 @@
|
||||||
title: OpenMandriva Lx ROME Release Notes
|
title: OpenMandriva Lx ROME Release Notes
|
||||||
description:
|
description:
|
||||||
published: true
|
published: true
|
||||||
date: 2022-09-13T21:03:40.378Z
|
date: 2022-09-13T21:50:13.678Z
|
||||||
tags: rolling, rome
|
tags: rolling, rome
|
||||||
editor: markdown
|
editor: markdown
|
||||||
dateCreated: 2021-04-24T05:53:55.903Z
|
dateCreated: 2021-04-24T05:53:55.903Z
|
||||||
|
@ -14,6 +14,7 @@ The OpenMandriva Lx teams are pleased to announce the availability of OpenMandri
|
||||||
## **This page is currently a Work_In_Progres!** Updated 2022-09-13
|
## **This page is currently a Work_In_Progres!** Updated 2022-09-13
|
||||||
|
|
||||||
The OpenMandriva Lx teams are pleased to announce the availability of **ROME** an OpenMandriva *rolling* release meant for majority of users.
|
The OpenMandriva Lx teams are pleased to announce the availability of **ROME** an OpenMandriva *rolling* release meant for majority of users.
|
||||||
|
<br>
|
||||||
|
|
||||||
**Available Media**
|
**Available Media**
|
||||||
|
|
||||||
|
@ -24,6 +25,7 @@ This release is available as a live media USB flash drive (memory stick), downlo
|
||||||
\- *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.
|
\- *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)
|
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**
|
||||||
|
|
||||||
|
@ -32,18 +34,22 @@ ROME requires at least 2048 MB of memory and at least 10 GB of hard drive space
|
||||||
*Important Note: Graphics Hardware:*
|
*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.
|
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.
|
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.
|
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.
|
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**
|
||||||
|
|
||||||
|
@ -56,24 +62,28 @@ 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.
|
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)
|
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. ***Example***:
|
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.
|
||||||
|
|
||||||
`btrfs` and `xfs` are working in recent tests but these are much less often tested. We rely on user feedback for this.
|
`btrfs` and `xfs` are working in recent tests but these are much less often tested. We rely on user feedback for this.
|
||||||
|
|
||||||
Other files system types in the list are not recommended.
|
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.
|
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.
|
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**
|
||||||
|
|
||||||
|
@ -92,10 +102,12 @@ Please share your experiences on the forums so that we may improve this aspect o
|
||||||
|
|
||||||
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.
|
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.
|
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.
|
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**
|
||||||
|
|
||||||
|
@ -117,15 +129,18 @@ You may alternatively dd the image to your USB stick:
|
||||||
Replace <iso_name> with the path to the ISO and <usb_drive> with the device node of the USB drive, i.e. /dev/sdb.
|
Replace <iso_name> with the path to the ISO and <usb_drive> with the device node of the USB drive, i.e. /dev/sdb.
|
||||||
|
|
||||||
- SUSE Studio ImageWriter has also been tested and works for burning ISO images to USB storage device.
|
- 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.
|
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.
|
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 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.
|
||||||
|
<br>
|
||||||
|
|
||||||
**How to install and remove packages**
|
**How to install and remove packages**
|
||||||
|
|
||||||
|
@ -142,6 +157,7 @@ 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>`
|
`sudo dnf --refresh install <package_name_1> <package_name_2> <package_name_3> <package_name_4>`
|
||||||
|
|
||||||
More about package management with dnf [here](https://dnf.readthedocs.io/en/latest/command_ref.html).
|
More about package management with dnf [here](https://dnf.readthedocs.io/en/latest/command_ref.html).
|
||||||
|
<br>
|
||||||
|
|
||||||
**Recommended update procedure**
|
**Recommended update procedure**
|
||||||
|
|
||||||
|
@ -150,29 +166,29 @@ More about package management with dnf [here](https://dnf.readthedocs.io/en/late
|
||||||
`sudo dnf clean all ; sudo dnf dsync`
|
`sudo dnf clean all ; sudo dnf dsync`
|
||||||
|
|
||||||
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".
|
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 OMLx 4.3rc.
|
In order to keep current with latest changes in Linux, computer security issues, and computer code writing there are major changes in ROME.
|
||||||
|
|
||||||
*Major changes*:
|
|
||||||
|
|
||||||
- The kernel has been updated to 5.19.8
|
- The kernel has been updated to 5.19.8
|
||||||
- KDE products have been updated: Frameworks 5.98.0, Plasma Desktop 5.25.5, KDE Gear
|
- KDE Frameworks 5.98.0
|
||||||
22.08.1
|
- KDE Plasma Desktop 5.25.5
|
||||||
|
- KDE Gear 22.08.1
|
||||||
- Qt 5.15.6 with all patches proposed by KDE
|
- Qt 5.15.6 with all patches proposed by KDE
|
||||||
- Mesa 22.2.0
|
- Mesa 22.2.0
|
||||||
- FFMPEG to 5.1
|
- FFMPEG to 5.1
|
||||||
Upgraded also some cool stuff not on the ISO but available in our repositories:
|
|
||||||
-AMDVLK 2022.Q3.3 official AMD Vulkan driver. It is an alternative driver and can be installed at same time with RADV. It can be used to improve performance or stability in some games on Linux
|
Upgraded also some cool stuff not on the ISO but available in our repositories
|
||||||
-OBS-Studio 28.0.1 software for video recording and live streaming; it finally supports wayland session. It also supports recording h264 with VAAPI (hardware accelerated video encoding) and we also patched it to support HEVC-x265 with HW VAAPI
|
- AMDVLK 2022.Q3.3 official AMD Vulkan driver. It is an alternative driver and can be installed at same time with RADV. It can be used to improve performance or stability in some games on Linux
|
||||||
-Blender 3.3.0
|
- OBS-Studio 28.0.1 software for video recording and live streaming; it finally supports wayland session. It also supports recording h264 with VAAPI (hardware accelerated video encoding) and we also patched it to support HEVC-x265 with HW VAAPI
|
||||||
-GIMP 2.10.32
|
- Blender 3.3.0
|
||||||
-Audacity 3.1.3
|
- GIMP 2.10.32
|
||||||
-Firefox 104.0
|
- Audacity 3.1.3
|
||||||
-Steam 1.0.0.75
|
- Firefox 104.0
|
||||||
-LXQt 1.1.0
|
- Steam 1.0.0.75
|
||||||
|
- LXQt 1.1.0
|
||||||
|
<br>
|
||||||
|
|
||||||
**Default sound server switched to Pipewire**
|
**Default sound server switched to Pipewire**
|
||||||
|
|
||||||
|
@ -182,6 +198,7 @@ PipeWire has become our default sound server in the current system release, thus
|
||||||
|
|
||||||
|
|
||||||
[*Pipewire*](https://pipewire.org/)
|
[*Pipewire*](https://pipewire.org/)
|
||||||
|
<br>
|
||||||
|
|
||||||
**Clang compiled kernel**
|
**Clang compiled kernel**
|
||||||
|
|
||||||
|
@ -190,13 +207,16 @@ The standard kernel for ROME is clang compiled. Should user want a gcc compiled
|
||||||
**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).
|
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).
|
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!
|
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!
|
||||||
|
|
||||||
**Please read also [ROME Errata](https://wiki.openmandriva.org/en/distribution/releases/omlxrolling/errata)**.
|
**Please read also [ROME Errata](https://wiki.openmandriva.org/en/distribution/releases/omlxrolling/errata)**.
|
||||||
|
<br>
|
Loading…
Reference in New Issue