Updated multimedia and Nvidia driver packages

As many of you have noticed, there are big updates pushed in the repositories. Merging all of them into one big repository is still ongoing; but as part of it all builds now come from these git repositories:

https://github.com/negativo17

Feel free to create merge requests or ask access to them.

VLC

Both Fedora 23 and RHEL / CentOS 7 packages now host VLC with all plugins enabled, so this means you can listen/watch any kind of multimedia file on both distributions. Obligatory screenshot (CentOS 7):

centos-vlc

Of course you can also play Blu-Ray discs with it.

Gstreamer “bad” plugins

Fedora contains also Gstreamer “bad” plugins with all possible options enabled. Some statistics:

$ gst-inspect-1.0 | grep Total
Total count: 227 plugins, 1483 features

Packages for both “ugly” and “bad” plugins are coming for CentOS/RHEL 7 as well.

Updated multimedia packages

Also the update brings in quite a few updates on multimedia libraries (live555, FFMpeg, x265, dcadec, etc.).

Fedora 24 support

Fedora 24 support is coming, most of the packages have been rebuilt and all repositories will be available before the release. Starting from Fedora 24, you can enable all repositories with or without RPMFusion being enabled. This means I will try to maintain compatibility but you will not require to enable it.

Nvidia driver

The Nvidia driver has been updated to 364.19 on all supported Fedora releases. This brings in mode setting for the nvidia-drm module and Vulkan support. In the current state, mode setting works only in conjunction with a custom Wayland and the module does not provide an fb driver for the console. The Wayland patches have not been merged (and is not going very well on this side) and a KMS console is not there; so basically even enabling it just brings absolutely no difference to your experience. As such, modesetting is disabled.

It also brings instability to both my systems, so I guess it needs to mature some more before being usable. To enable mode setting, perform the following changes:

# echo "options nvidia-drm modeset=1" > /etc/depmod.d/nvidia.conf
# depmod -a
# reboot

To be more precise, some kernel command should be removed when the kernel module gets also a fb driver:

# grubby --update-kernel=ALL --remove-args='nomodeset gfxpayload=vga=normal'
# sed -i -e 's/nomodeset gfxpayload=vga=normal //g' /etc/default/grub

At the moment, those parameters are still added by the package as there is absolutely no benefit in enabling mode setting. As I said, you will reboot and get absolutely no difference.

As usual, let me know of any problems. I will be away for holiday for 3 weeks, so do not expect a prompt reply!

27 thoughts on “Updated multimedia and Nvidia driver packages

  1. DKMS updating seems to be currently broken.

    The latest update to fedora 23 (and into fedora 24) has broken the nvidia installation under DKMS. You receive a warning that dkms.conf is not found and the usual GNOME Oops something bad has happened.

    It is necessary to do a manual dkms build and dkms install operation which work fine. Recent change broke something?

    1. They’re coming, I’m just finishing the remaining things. Bad is done (including the NVENC plugin!), ugly is in the works.

  2. Every kernel upgrade, after akmod completes module compilation, GDM fails to load because it tries to use Wayland… any thoughts?

  3. nvidia driver does not work at all on fedora 24. It seems than system runs fb driver or something like that and gdm argues that there is no acceleration. Xorg log says that Failed to initialize GLX extension (Compatible NVIDIA X driver not found).

    http://pastebin.com/8LHgDznz

    Any thoughts?

    1. If you look at the logs, you can see that the nouveau driver is not disabled and is loaded. So the Nvidia drivers bails out saying that no compatible kernel module is found.
      Something is wrong with your installation, as my packages disabled nouveau on boot:

      $ rpm -q --scripts nvidia-driver
      postinstall scriptlet (using /bin/sh):
      if [ "$1" -eq "1" ]; then
        /usr/sbin/grubby --update-kernel=ALL --args='nouveau.modeset=0 rd.driver.blacklist=nouveau nomodeset gfxpayload=vga=normal' &>/dev/null
        sed -i -e 's/GRUB_CMDLINE_LINUX="/GRUB_CMDLINE_LINUX="nouveau.modeset=0 rd.driver.blacklist=nouveau nomodeset gfxpayload=vga=normal /g' /etc/default/grub
      fi || :
      preuninstall scriptlet (using /bin/sh):
      if [ "$1" -eq "0" ]; then
        /usr/sbin/grubby --update-kernel=ALL --remove-args='nouveau.modeset=0 rd.driver.blacklist=nouveau nomodeset gfxpayload=vga=normal' &>/dev/null
        sed -i -e 's/nouveau.modeset=0 rd.driver.blacklist=nouveau nomodeset gfxpayload=vga=normal //g' /etc/default/grub
      fi ||:
      1. dnf install nvidia-driver akmod-nvidia kernel-devel nvidia-driver-libs.i686

        Am i doing it right? Plain new fedora 24, installed from scratch. Should akmod build module before first run? Maybe it is an akmod problem?

      2. Kernel starts with linuxefi /vmlinuz-4.5.5-300.fc24.x86_64 root=UUID=39f88f04-03c3-4fa3-a50f-e9a2dac1ebcc ro rhgb quiet LANG=ru_RU.UTF-8 nouveau.modeset=0 rd.driver.blacklist=nouveau nomodeset gfxpayload=vga=normal

        So it should be fine.

      3. Ok, so i figured it out: the nvidia module failed to load due to secure boot option. Now it works, though not too stable.

  4. Error: nothing provides libvpx.so.2()(64bit) needed by ffmpeg-libs-2.8.7-1.fc23.x86_64

    Probably it needs to be rebuild against the new libvpx.

  5. I decided to do the `rpm -e` on libmpg123 after all. I saw the same issue that Louis had. An `strace` lead me to thinking that the issue was the missing /usr/lib64/mpg123/output_alsa.la file. I downloaded mpg123-1.22.4-1.fc23.x86_64.rpm from Rpm Fusion and unpacked it and put just that one file in place. Seems to work fine now.

    I don’t know much about .so versus .la files but it seems that the Rpm Fusion version has both .so and .la files where this version does not.

      1. I am not sure how to tell what else might need it. Right now it comes from mpg123 but I am currently not using the negativo17 repo, using rpmfusion only.

        I did also just confirm that my current version of mpg123 from rpmfusion does access that file when I play an mp3 file.

        stat /usr/lib64/mpg123/output_alsa.la |grep “Access: 2”
        Access: 2016-05-10 07:54:28.710923134 -0700

        >mpg123 -v laser.mp3

        stat /usr/lib64/mpg123/output_alsa.la |grep “Access: 2”
        Access: 2016-05-25 12:46:27.282605548 -0700

        Details on the file:
        >rpm -qf /usr/lib64/mpg123/output_alsa.la
        mpg123-1.22.4-1.fc23.x86_64

        >sudo dnf info mpg123-1.22.4-1.fc23.x86_64 |egrep “^Installed|^From repo”
        Installed Packages
        From repo : rpmfusion-free-updates

        P.S. I was using the negativo17 repo for Handbrake but I went ahead and built it from source pulled off of github.

  6. Also getting the conflict issue in F23:

    Error: Transaction check error:
    file /usr/lib64/libmpg123.so.0 from install of mpg123-libs-1:1.23.3-1.fc23.x86_64 conflicts with file from package libmpg123-1.22.4-1.fc23.x86_64

    I did not want to mess up my dependencies, so have not forced a remove with `rpm`. I did check what `dnf remove` would do and it wanted to remove too much stuff so am holding off to see what shows up here.

    Note that all non-Hnadbrake updates would install fine when I did:

    dnf update –disablerepo=fedora-HandBrake

  7. Hi
    I had the following when running dnf upgrade on F23:
    Error: Transaction check error:
    file /usr/lib64/libmpg123.so.0 from install of mpg123-libs-1:1.23.3-1.fc23.x86_64 conflicts with file from package libmpg123-1.22.4-1.fc23.x86_64

    libmppg123 was profided by RPMFusion, and provided an earlier version of /usr/lib64/libmpg123.so.0 .

    So of course I force-removed it with:
    rpm -e –nodeps libmpg123-1.22.4-1.fc23.x86_64

    I ran dnf upgrade, and your repo’s mpg123-libs was installed.

    HOWEVER: When I run mpg123 now, I get the error output:

    High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
    version 1.23.3; written and copyright by Michael Hipp and others
    free software (LGPL) without any warranty but with best wishes
    [src/libout123/module.c:141] error: Failed to open module alsa: file not found
    [src/libout123/module.c:141] error: Failed to open module oss: file not found
    [src/libout123/module.c:141] error: Failed to open module jack: file not found
    [src/libout123/module.c:141] error: Failed to open module portaudio: file not found
    [src/libout123/module.c:141] error: Failed to open module pulse: file not found
    [src/libout123/module.c:141] error: Failed to open module sdl: file not found
    [src/libout123/module.c:141] error: Failed to open module nas: file not found
    [src/libout123/module.c:141] error: Failed to open module openal: file not found
    [src/libout123/libout123.c:431] error: Found no driver out of [alsa,oss,jack,portaudio,pulse,sdl,nas,openal] working with device .
    main: [src/mpg123.c:332] error: out123 error 3: failure loading driver module

    Any thoughts on fixing this?

    1. One more thing: when I run with options -vv I get the following:

      [root@fedora ~]# mpg123 -vv /home/louis/Music/01-PhilWickham-Grace.mp3
      High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
      version 1.23.3; written and copyright by Michael Hipp and others
      free software (LGPL) without any warranty but with best wishes
      Decoder: x86-64 (AVX)
      Trying output module: alsa, device:
      Using default module dir: /usr/lib64/mpg123
      Module dir: /usr/lib64/mpg123
      Module path: ./output_alsa.la
      [src/libout123/module.c:141] error: Failed to open module alsa: file not found
      Note: This could be because of braindead path in the .la file…

      … and so on for the various modules.

      The question is why does it thing the DEVICE is , and how do I set that to use my pulseaudio driver (permanently)?

  8. I was able to start the new driver using kernel 4.4.8 from Fedora 23
    All the kernels from Fedora 24 are freezing and not booting. I can’t even get a proper debug output.

    1. It seams to me to be about the same as when fc23 first came out , i can get it going but have to use kdm & cinnamon , or something other than Gnome ..

  9. Can you try to force modeset=0 as per post’s instructions?

    Just the depmod part, not the grubby one.

  10. Hi

    Lats nvidia update make the system not going up anymore.
    I’m on fedora 24 with 4.5.2-302, and no luck to make any config work.
    Module is loaded, including the nvidia_modeset.

    Any suggestion on possible tentatives to fix ?

    []’ s

  11. What does it really mean “now host VLC with all plugins enabled,”?

    I have reinstalled vlc, vlc-core, vlc-extras on Korora 23 xfce, but in vlc>tools>plugins and extensions I have no installed extensions, 1 active extension “VLsub” and a lot of modules for access, demux, filters ….

    Where are these plugins enabled? In extendeted settings? This was possible also before.

    Rgds
    AW

    1. Hello, maybe “modules” would have been more appropriate wording than “plugins”. But basically yes, I have enabled all that I could enable in the build. There are a couple of options still missing, but I will enable then when I come back.

      Also, yes, it was already available, but I had not finalized cleaning all the libraries and had not notified anyone about CentOS/Rhel 7 availability, so I wanted to write something about it. I had some really busy weeks lately and this slipped by almost a month.

      Thanks for feedback!

Leave a Reply