2014.0/Release Notes

From Wiki [en] OpenMandriva
< 2014.0
Revision as of 18:21, 28 March 2014 by TPG (Talk | contribs) (ATI Graphics Cards)

Jump to: navigation, search

It is recommended that you read the latest release notes on our wiki.

2014.0 Beta Release

The OpenMandriva Lx teams are pleased to announce the availability of the 2014.0 beta release!

Detailed are some of the changes that the OS has undergone since OpenMandriva Lx 2013.

Available Media

This release is available as a live media DVD, downloadable in ISO format. They are available on our downloads page.

Live media means you're able to run OpenMandriva Lx straight from the DVD and try it before installing it. You may also install the system to hard disk either from the running live cd or from the boot manager. You may also from a USB memory stick (See Below).

Recommended Hardware

Please note the recommended hardware requirements have changed; To run the installed distribution, we recommend 1 GB of memory (min 640MB), at least 10 GB of hard drive space (see below for known issues with partitioning), and for best compositing performance a suitable accelerated 3D graphics card.

To run the live distribution (Grub Option 1) The minimum memory requirement is 1.5GB of memory but 2GB is recommended. Releases are available for the i586 and x86_64 architectures. ARM architectures are not available for this release.

The same hardware requirements apply when running in virtual machines

Booting from USB

It is possible to boot this release from a USB. You may use ROSA Image Writer available from our repos:

urpmi rosa-imagewriter

as a static binary:
Linux 32-bit
Linux 64-bit

There is also a Windows binary, working out of box. Just download it and write iso. with a download of the OpenMandriva Lx ISO for your system to make your USB bootable. At least 2GB of flash drive capacity is recommended. Persistent storage is not necessary. Note that this will erase everything on your USB! It is also possible to use the dd command to image the iso to an USB Drive e.g "dd if=<iso_name> of=/dev/sd<x> bs=4M" .

Booting with KVM

Please use the QXL or VMWare video driver to avoid any problems booting OpenMandriva LX with kernel 3.11.5 or higher.

Booting with VirtualBox

Please note that there is an increased memory requirement for successful booting in this VM manager. The virtual machine should be set up with a minumum of 1536mb.

Due to a recent API change, 4.2.x series of vboxadditions will not work. Instead, use 4.3.x series which is known to work with this release Bug small.png Bug #204

Workaround: Upgrade to VirtualBox 4.3 or later

New Features and Major Changes

The introduction of OpenMandriva 2014.0 represents a major update from the previous version of OpenMandriva Lx, and is also the third release under the community of the OpenMandriva Association. With that in mind, here are some of the new features:


OpenMandriva Lx features new kernel called NRJ as for energy!

With the "NRJ" configs the CPU and RCU are configured with full Pre-emption enabled and in full Boost mode, while the "QL" mode adds the CK1 and BFQ patchsets which combine to provide further optimisations, including better CPU load scheduling (BFS) and improved disk I/O scheduling (BFQ), Improved memory managment is present with the provision of UKSM and TOI for better suspension and hibernate functionality, each designed with desktop system performance and responsiveness in mind.

KDE 4.12.3

KDE 4.12.3 provides a clean, unified desktop for OpenMandriva. It has all the tools required to be productive whilst providing a pleasant, functional environment.

This release provides a KDE 4.12 installation featuring homerun launcher, new artwork and plasma-mediacenter!.

Upgrading to 2014.0

Upgrading between releases of Mandriva always has the potential to cause some problems. Upgrading is supported and we do test upgrades, but due to the huge range of packages and hardware configurations possible, it is always the case that in your particular situation, the upgrade may cause a problem we did not anticipate. Therefore we recommend that you always back up your system prior to upgrading.

Upgrading between OpenMandriva releases should be less problematic in the future.

In particular, upgrading between MDV-based packages and OMV-based packages may cause problems.

Upgrading from 2013.0

Please use below commands:

urpmi.removemedia -a
urpmi.addmedia --distrib --mirrorlist 'http://downloads.openmandriva.org/mirrors/openmandriva.2014.0.ARCH.list'

Substitute ARCH with your architecture, e.g. i586 or x86_64.

Then run the following commands, as root:

urpmi --auto --auto-select --replacefiles 2>&1 | tee upgrade.log

Upgrading from 2011.0

We do not currently have an official way to update this from the GUI, as our tool is not ready yet.

With the caveats mentioned above, you can still accomplish this upgrade from the command line. To do this, first ensure your system is entirely up-to-date with the latest updates for your current version of the distribution (using either MandrivaUpdate, Mandriva Online (Mandriva update notification applet) or urpmi --auto-update}}.

Then remove your existing repositories, either using the graphical repository configuration tool or the urpmi.removemedia command. urpmi.removemedia -a will remove all repositories. Then you should add repositories for this release. Run a command like this:

urpmi.addmedia --distrib --mirrorlist 'http://downloads.openmandriva.org/mirrors/openmandriva.2014.0.ARCH.list'

Substitute ARCH with your architecture, e.g. i586 or x86_64.

Then run the following commands, as root:

urpmi --auto --auto-select --replacefiles 2>&1 | tee upgrade.log

You may see an error "unknown option --replacefiles" when you first run this, but don't worry, that's normal: older urpmi versions do not have this option, but our urpmi does, and it will be passed along to our urpmi when the urpmi process is restarted after the package has been updated. This will save the output of the process to the file upgrade.log, in case you need to check it later, or you have any problems. Once the process completes, you should reboot immediately, and you should find the system has been fully updated to this version.

Media "restricted"

Here are some non free libraries that aren't installed by default. For example, playing mp4 videos with VLC needs libfaad2_2 which can be installed after having added all set of media.


DrakX Installer

The DrakX Installer is not included in this release. We hope to include it (or a new installer that brings back its features) in later releases.

Please note though that the various tasks that installed batches of software that were available in the old installer may still be used either through the OpenMandriva Tools or though the command line with urpmi. The tasks available can be listed by running 'urpmq --fuzzy task-'. Use these tasks at your own risk as they are not all currently maintained.

Changes to Hardware Support

Graphics Support

Graphics support has improved with the latest drivers however there are still issues with some hardware.

NVIDIA Graphics Cards

Note that older NVidia graphics cards FX series and before are not currently supported by the XFDrake, the DrakX video configuration tool. Older drivers are available from the OpenMandriva repositories and should be installed directly with urpmi: your mileage may vary. The reverse engineered nouveau driver gives moderately good support for these older cards.

ATI Graphics Cards

The latest ATI graphics cards are supported; however, we have not had any concrete feedback about its usage. Your mileage may vary.

If you are using Radeon HD7770 please add below command in grub2 cmdline:


Intel Graphics Cards

Intel graphics cards are supported with the latest kernel we have, including newer 4th generation Intel graphics cards.


We have not had any other feedback from users.

Ethernet Support

Changes to Installation

Unused Hardware & Language Removal

Previously, when running the installer, you would not be prompted to remove any hardware or languages that the system did not use. However, this did lead to numerous false-positives (and even in some cases, destruction of the installed system). We have disabled the removal step until the problem can be remedied or a choice given to the user (unselected by default).

Changes to the DrakX suite of tools


Changes to Software Support

Booting with systemd

Switching runlevels has changed. Instead of adding the target runlevel, as before, there are now specific boot options. Namely, the following options must be appended to the kernel command line:

  • Rescue Mode: systemd.unit=rescue.target
  • Text Mode: systemd.unit=multi-user.target
  • Graphical Mode: systemd.unit=graphical.target

Other Changes



As with any release, there are still issues and bugs that have not been resolved. This page attempts to document the ones that may cause inconvenience.

Booting Live DVD/USB

This software is BETA quality. There seem to be an issue booting the live image with some hardware. Please report a bug detailing your hardware and any observations that you make if you are affected by this problem. Please also see Black Screen at Boot

Usage of Mandriva in System Tools

There are still usages of Mandriva in the system tools. They are being remedied.

Workaround: Check for updates periodically, and report bugs for any occurrences that you still see.

Partitioning with Small Disks

When using the custom partitioning tool to divide up the hard disk/s be aware that there is a minimum size requirement a root partition that contains the /usr directory of at least 5.0Gb. If the partition is made smaller that this the partition manager will not function correctly.

Due to the adoption of systemd the use of a separate /usr partition is no longer possible. 
It is still permissible to have a separate /usr/local partition.

Workaround: If you receive an error message stating that the partition is smaller than the minimum requirement then do not try to resize it as this will fail; instead, use the auto-allocate function which will automatically create a partitioning scheme for you, which you may then delete or change to suit your own requirements. This will clear the error.

Black Screen at Boot

Graphics Drivers:

There is an issue with systems that have two different graphics adapters but only one of them is operational. Typically this is a Nvidia GPU combined the either Intel or AMD/ATI. Due to the automated nature of driver selection in modern systems if the non-functional GPU is automatically selected then X will load the matching driver. Thus the working GPU never gets setup resulting in a black screen. We have recently added a new boot command line option to allow an Xorg driver to be blacklisted thus allowing the correct driver to be detected.

To use this feature you must edit the grub2 command line. You can do this by selecting your desired boot option and then pressing TAB. To the end of the line add the following:-

xorg.blacklist=<driver to blacklist>

To determine which driver needs to be blacklisted is probably best achieved by booting the system to a text mode and checking which driver has been loaded at boot time. A procedure for doing this is detailed below. In some circumstances this may not be possible and you will need to resort to your motherboard/Graphics card specifications or trial and error. It will be necessary to permanently add the line to the grub2 command line that boots the installation. This is described below.

There are other circumstances where a black screen may be encountered. In these circumstances adding




to the kernel command line will normally be enough to allow installation of the OS. If necessary the command may be added permanently by editing /etc/default/grub at the GRUB_CMDLINE_LINUX_DEFAULT label and adding the required command. Then run update-grub2

To boot to text mode:-

1: Boot from the DVD/USB stick and at the grub selection screen select the livecd option and press TAB. Edit the grub command line by and add the command

"systemd.unit=multi-user.task nomodeset" 

to the end and boot the machine. This will bring you to a command prompt where you can login.

2: Login as root and then type lsmod | less and observe the output. Look for the loaded graphics driver by finding the drm entry the graphics driver will be listed here. It will be typically nouveau, radeon or i915 (there may be others). The name used here will be the name to add to the xorg.blacklist= parameter

Backlight Issues

There are some machines with Intel GPU's (Netbooks particularly) may still give a black screen. This may be fixed by adding i915.invert_brightness=1 parameter to the boot command line. This may be needed in addition to the xorg.blacklist= parameter.

Incorrect tty

On boot it may be found that you are presented with terminal screen rather that the normal graphical login, In this case you may need to switch ttys (terminal); you can do this by pressing alt+ctrl+F7 if you still have no graphical login try using the same key cobination but with a different function key. Key F1-F7 are all different ttys (terminals). Please report a bug for this problem noting your what hardware you are running on.

Contact, Bug Reporting, Discussion

You are invited to discuss this release on:

Please report bugs to our bugtracker. Please give as much information as you can in your report.


Currently we are having problems importing our CA Cert into our web browser configurations. When you go to openmandriva.org pages you will get a security exception which you can safely ignore. We hope to address this problem very soon.

Helping the Project

As always, the OpenMandriva development teams (Cooker & QA) are always looking for contributors to assist in bugfixing, and so we invite you to join us and help tackle issues that might arise!

Also, the OpenMandriva Workshop, which contains Artwork, Documentation, and Communication teams, is always open to new submissions for artwork and translations!

See our wiki (wiki.openmandriva.org) for more details, and to learn how to join!.