Difference between pages "Package:NVIDIA Linux Display Drivers" and "FLOP:FFmpeg"

(Difference between pages)
m (note use of vesa is also acceptable, add console for nvidia-xconfig so the command can be pulled out of Video)
 
(add technical details to the FLOP)
 
Line 1: Line 1:
{{Ebuild
+
{{FLOP
|Summary=NVIDIA accelerated graphics driver
+
|Created on=2015/01/31
|CatPkg=x11-drivers/nvidia-drivers
+
|Summary=Funtoo Linux prefers FFmpeg. Some enlightenment about our choice and why we prefer this  or could switch to alternative in future.
|Repository=Funtoo Overlay
+
|Author=Oleg, Mgorny
|Overlay=Funtoo
+
|Maintainer=Oleg, Mgorny
 +
|Reference Bug=FL-844
 
}}
 
}}
 
== Introduction ==
 
== Introduction ==
NVIDIA have proprietary graphics drivers for Linux under binary blob. The alternative open source driver is {{Package|x11-drivers/xf86-video-nouveau}}.
+
FFmpeg and Libav are library sets for multimedia decoding (and more). Both libraries expose similar API and features.
  
== Preparing to Install ==
+
Both project have common origins and diverged only recently. The developers share the same bad coding practices causing permanent lack of API and ABI stability, therefore requiring frequent rebuilds of reverse dependencies.
=== Hardware compatibility and driver versions ===
+
Currently, there are five versions of meta NVIDIA Linux drivers, each of which supports a specific group of GPUs. To check the type of driver that is related to your video card, check out the official page of the NVIDIA [http://www.nvidia.com/object/IO_32667.html complete list of supported GPUs].
+
  
If you have identified as your driver version 337.25, for example, you need the mask(s) driver(s) latest(s) to which you want to install.
+
Worse than that, after the split projects use colliding SONAMEs for libraries with potentially different ABI. This means that after switching from one implementation to another, the reverse dependencies may become broken instantly (preserved-libs doesn't help) and need to be rebuilt ASAP.
  
<console>
+
Many packages for video decoding, are done via FFmpeg or Libav.  Differences between FFmpeg and Libav can have a major impact on its behavior: the number of files it can decode, whether it decodes correctly, what video and audio filters are provided, network behavior, and more.
###i## echo “>x11-drivers/nvidia-drivers-340” >> /etc/portage/package.mask
+
</console>
+
  
=== The required kernel options ===
+
== Current status ==
 +
=== Gentoo ===
 +
Gentoo supports both ffmpeg and libav, with a weak preference towards libav. The preference is caused by package order in virtual/ffmpeg — when no other circumstance affects the package choice, Portage will prefer libav. However, if ffmpeg is already installed or a package incompatible with libav is requested, Portage will use ffmpeg instead.
  
{{kernelop|desc=
+
There are two major technical issues with this design:
[*] Enable loadable module support
+
# there is no technically correct way of forcing rebuilds on ABI changes — subslot dependencies do not work with virtuals or || () deps,
}}
+
# there is no way of forcing rebuilds when switching from libav to ffmpeg, and the other way around.
{{kernelop|desc=
+
[*] MTRR (Memory Type Range Register) support
+
}}
+
To we made a successful compilation of the legacy NVIDIA driver, we set before the removal of the native framebuffer drivers into the kernel in order to avoid conflicts for x86 and AMD64 processors, in this case.
+
{{kernelop|desc=
+
Device Drivers --->
+
      Graphics support --->
+
            <*> Support for frame buffer devices --->
+
                  <> NVIDIA Framebuffer Support
+
                  <> NVIDIA Riva support
+
}}
+
  
{{tip|An alternative is to [[uvesafb|uvesafb]] framebuffer, or vesa framebuffer which can be installed in parallel with nvidia-drivers }}
+
=== Funtoo ===
 +
Funtoo supports only FFmpeg. It is forced by Funtoo version of virtual/ffmpeg. While this provides the ability to avoid the Gentoo issues, virtual still breaks ABI rebuilds.
  
== Installation ==
+
Decision made by Oleg, forced by #funtoo community and bugtracker reports.
  
Upgrade and/or configure <code>VIDEO_CARDS</code>  variable to <code>nvidia</code> in <code>/etc/[[make.conf]]</code>. This will serve to while you are installing the Server X, the correct version of nvidia-drivers to be provided for you.
+
== Future status ==
<console>
+
=== Gentoo ===
# ##i##nano /etc/make.conf
+
There is a planned Gentoo change which will eventually replace virtual/ffmpeg and explicit || () deps with 'libav' USE flag. The flag will be added to all packages that support both FFmpeg and libav. When the flag is enabled, the package will use libav; otherwise it will use FFmpeg. The choice of flag name is forced by the fact that USE=ffmpeg is already used as generic ffmpeg-or-libav flag.
VIDEO_CARDS="nvidia"
+
</console>
+
  
{{note|Installing to the driver with the option in '''gtk''' use flags will make it installed the <code>media-video/nvidia-settings</code> which is a graphical tool for monitoring and various settings for your video card}}
+
This change fixes both Gentoo issues:
 +
# USE-conditional dependencies allow subslot dependencies to force rebuilds on ABI changes,
 +
# provider change will force rebuild because of USE flag change.
  
=== Emerging the package ===
+
The change may also eventually make it possible to install FFmpeg and libav side-by-side. Until then, the flag state would involve 'strong' preference of one implementation over the other, and user will have to change USE=libav as a global flag. '''Installing a package that supports only one of the two implementations will result in blocker that needs to be handled manually'''.
<console>
+
###i## emerge x11-drivers/nvidia-drives
+
</console>
+
  
When the installation is complete run '''modprobe''' nvidia module to read kernel memory.
+
=== Funtoo ===
 +
If Funtoo decides to keep supporting FFmpeg only, it only needs to mask libav in the profiles. Then dependencies on updated packages will unconditionally use FFmpeg. Eventually Funtoo will want to remove virtual/ffmpeg and depend on media-video/ffmpeg:0= directly in forked packages.
  
<console>
+
If Funtoo decides to start supporting libav as an option, it may need to add USE="-libav" to profiles if Gentoo decides for libav default. Funtoo will want to progressively update forked packages to match Gentoo dependency specifications.
###i## lsmod | grep nvidia
+
</console>
+
If an update before remove the old module
+
<console>
+
###i## rmmod nvidia
+
###i## modprobe nvidia
+
</console>
+
  
=== Testing your Video Card ===
+
== Detailed information on FFmpeg and libav ==
To test your video card run the glxinfo program, which is part of the mesa-progs package. This will check if direct rendering is enabled.
+
=== FFmpeg and Libav history ===
<console>
+
In 2011, parts of the FFmpeg developers were unhappy about the FFmpeg leadership, and decided to take over. This didn't quite work out. Apparently Fabrice Bellard, original FFmpeg developer and owner of the ffmpeg.org domain name, decided not to hand over the domain name to the new maintainers. So they followed Plan B, and forked FFmpeg, resulting in Libav. Since then, Libav did its own development, and completely ignored whatever FFmpeg did. FFmpeg, on the other hand, started to merge literally everything Libav did.
$ ##i##glxinfo | grep direct
+
$ ##i##  direct rendering: yes
+
</console>
+
  
== Configuring ==
+
The reason for the fork is most likely that the developers hate each other. While this formulation seems somewhat sloppy, it is most likely the truth. To this date, the #libav-devel IRC channel still has Michael Niedermayer (the FFmpeg maintainer since 2004 according to Wikipedia) on their ban list (similar misbehavior is exhibited by some FFmpeg developers). There is little to no cooperation between the two projects.
=== Loading at boot ===
+
To automate the loading of the module when you boot your system, add '''nvidia''' in modules variable.
+
<console>
+
# ##i##nano /etc/conf.d/modules
+
modules="nvidia"
+
</console>
+
  
=== Integration with X Server ===
+
More about FFmpeg's history and the fork incident can be found on Wikipedia
When your X server is installed find, and there's <code>/etc/X11/xorg.conf</code> you can run the nvidia-xconfig which will set in xorg.conf to identify the video card among other possible configurations.
+
 
+
<console>###i## nvidia-xconfig</console>
+
 
+
{{file|name=/etc/X11/xorg.conf|body=
+
Section "Device"
+
    Identifier    "nvidia"
+
    Driver        "nvidia"
+
    VendorName    "NVIDIA Corporation"
+
    BoardName      "[Name] [Model]"
+
EndSection
+
}}
+
  
=== Enabling NVIDIA Support ===
+
=== Situation today ===
Include the use flag in '''nvidia''' in <code>/etc/[[make.conf]]</code> so due to applications that make use of this advantage may withdraw.
+
FFmpeg has more features and slightly more active development than Libav, going by mailing list and commit volume. In particular, FFmpeg's features are a superset of Libav's features. This is because FFmpeg merges Libav's git master on a daily basis. Libav on the other hand seems to prefer to ignore FFmpeg development (with occasional cherry-picking of bug fixes and features).
<console>
+
# ##i##nano /etc/make.conf
+
USE="nvidia"
+
</console>
+
  
=== Enabling OpenGL/OpenCL ===
+
Some Linux distributions, especially those that had Libav developers as FFmpeg package maintainers, replaced FFmpeg with Libav, while other distributions stick with FFmpeg. Application developers typically have to make sure their code works with both libraries. This can be trivial to hard, depending on the details. One larger problem is that the difference between the libraries makes it hard to keep up a consistent level of the user experience, since either library might silently or blatantly be not up to the task. It also encourages library users to implement some features themselves, rather than dealing with the library differences, or the question to which project to contribute.
As a requirement, make sure that the Xorg server is not in use during this change. To enable OpenGL and OpenCL.
+
<console>
+
###i## eselect opengl set nvidia
+
###i## eselect opencl set nvidia
+
</console>
+
  
[[Category:Video Cards]]
+
FFmpeg and Libav developers also seem to have the tendency to ignore the damage their rivalry is causing. Apparently fighting out these issues on the users' backs is better than reconciling. This means everyone using these libraries either has to suffer from the differences, or reimplement functionality that is not the same between FFmpeg and Libav.
[[Category:First Steps]]
+
{{FLOPFooter}}
{{EbuildFooter}}
+

Revision as of 23:22, January 31, 2015

Created on
2015/01/31
Original Author(s)
{{#set:Author={{ #show: User:Oleg | ?Full name }}}}{{ #show: User:Oleg | ?Full name }},{{#set:Author={{ #show: User:Mgorny | ?Full name }}}}{{ #show: User:Mgorny | ?Full name }}
Current Maintainer(s)
Oleg Vinichenko,Michał Górny
Status
Reference Bug
FL-844

Funtoo Linux Optimization Proposal: FFmpeg

Funtoo Linux prefers FFmpeg. Some enlightenment about our choice and why we prefer this or could switch to alternative in future.

Introduction

FFmpeg and Libav are library sets for multimedia decoding (and more). Both libraries expose similar API and features.

Both project have common origins and diverged only recently. The developers share the same bad coding practices causing permanent lack of API and ABI stability, therefore requiring frequent rebuilds of reverse dependencies.

Worse than that, after the split projects use colliding SONAMEs for libraries with potentially different ABI. This means that after switching from one implementation to another, the reverse dependencies may become broken instantly (preserved-libs doesn't help) and need to be rebuilt ASAP.

Many packages for video decoding, are done via FFmpeg or Libav. Differences between FFmpeg and Libav can have a major impact on its behavior: the number of files it can decode, whether it decodes correctly, what video and audio filters are provided, network behavior, and more.

Current status

Gentoo

Gentoo supports both ffmpeg and libav, with a weak preference towards libav. The preference is caused by package order in virtual/ffmpeg — when no other circumstance affects the package choice, Portage will prefer libav. However, if ffmpeg is already installed or a package incompatible with libav is requested, Portage will use ffmpeg instead.

There are two major technical issues with this design:

  1. there is no technically correct way of forcing rebuilds on ABI changes — subslot dependencies do not work with virtuals or || () deps,
  2. there is no way of forcing rebuilds when switching from libav to ffmpeg, and the other way around.

Funtoo

Funtoo supports only FFmpeg. It is forced by Funtoo version of virtual/ffmpeg. While this provides the ability to avoid the Gentoo issues, virtual still breaks ABI rebuilds.

Decision made by Oleg, forced by #funtoo community and bugtracker reports.

Future status

Gentoo

There is a planned Gentoo change which will eventually replace virtual/ffmpeg and explicit || () deps with 'libav' USE flag. The flag will be added to all packages that support both FFmpeg and libav. When the flag is enabled, the package will use libav; otherwise it will use FFmpeg. The choice of flag name is forced by the fact that USE=ffmpeg is already used as generic ffmpeg-or-libav flag.

This change fixes both Gentoo issues:

  1. USE-conditional dependencies allow subslot dependencies to force rebuilds on ABI changes,
  2. provider change will force rebuild because of USE flag change.

The change may also eventually make it possible to install FFmpeg and libav side-by-side. Until then, the flag state would involve 'strong' preference of one implementation over the other, and user will have to change USE=libav as a global flag. Installing a package that supports only one of the two implementations will result in blocker that needs to be handled manually.

Funtoo

If Funtoo decides to keep supporting FFmpeg only, it only needs to mask libav in the profiles. Then dependencies on updated packages will unconditionally use FFmpeg. Eventually Funtoo will want to remove virtual/ffmpeg and depend on media-video/ffmpeg:0= directly in forked packages.

If Funtoo decides to start supporting libav as an option, it may need to add USE="-libav" to profiles if Gentoo decides for libav default. Funtoo will want to progressively update forked packages to match Gentoo dependency specifications.

Detailed information on FFmpeg and libav

FFmpeg and Libav history

In 2011, parts of the FFmpeg developers were unhappy about the FFmpeg leadership, and decided to take over. This didn't quite work out. Apparently Fabrice Bellard, original FFmpeg developer and owner of the ffmpeg.org domain name, decided not to hand over the domain name to the new maintainers. So they followed Plan B, and forked FFmpeg, resulting in Libav. Since then, Libav did its own development, and completely ignored whatever FFmpeg did. FFmpeg, on the other hand, started to merge literally everything Libav did.

The reason for the fork is most likely that the developers hate each other. While this formulation seems somewhat sloppy, it is most likely the truth. To this date, the #libav-devel IRC channel still has Michael Niedermayer (the FFmpeg maintainer since 2004 according to Wikipedia) on their ban list (similar misbehavior is exhibited by some FFmpeg developers). There is little to no cooperation between the two projects.

More about FFmpeg's history and the fork incident can be found on Wikipedia

Situation today

FFmpeg has more features and slightly more active development than Libav, going by mailing list and commit volume. In particular, FFmpeg's features are a superset of Libav's features. This is because FFmpeg merges Libav's git master on a daily basis. Libav on the other hand seems to prefer to ignore FFmpeg development (with occasional cherry-picking of bug fixes and features).

Some Linux distributions, especially those that had Libav developers as FFmpeg package maintainers, replaced FFmpeg with Libav, while other distributions stick with FFmpeg. Application developers typically have to make sure their code works with both libraries. This can be trivial to hard, depending on the details. One larger problem is that the difference between the libraries makes it hard to keep up a consistent level of the user experience, since either library might silently or blatantly be not up to the task. It also encourages library users to implement some features themselves, rather than dealing with the library differences, or the question to which project to contribute.

FFmpeg and Libav developers also seem to have the tendency to ignore the damage their rivalry is causing. Apparently fighting out these issues on the users' backs is better than reconciling. This means everyone using these libraries either has to suffer from the differences, or reimplement functionality that is not the same between FFmpeg and Libav.

blog comments powered by Disqus