Arch Linux User Repository

@ako: Thanks for looking into this.

One reason I feel like it would be a bad idea to update these firmware is because the Nouveau side was validated with these firmware files only. Newer versions may fix some issues, but they may also break badly.

I do not have the time to go and re-validate everything, and since noone is working on video decoding on the Nouveau side (AFAIK), then it feels like this package is pretty much all that will be ever needed.

I sincerely hope that the situation will improve now that Nouveau is getting some attention, and I will be more than happy to transfer maintainership of the package to whoever has sufficient knowledge and involvement in the Nouveau project :)

I just installed nouveau-fw and according to vdpauinfo I have no acceleration for the 264 format. I don't know if this is an expected limitation of the nouveau driver or if it is a bug that can be repaired. I attach the vdpauinfo return for both the nouveau driver and the original nvidia driver.

My video card is NVIDIA Corporation GT218 [GeForce 210] (rev a2)

vdpauinfo with nouveau driver https://pastebin.com/3nwzz5jz

vdapauinfo with nvidia-340 driver https://pastebin.com/VfXn6csC

@xiota Updated pkgbuild thanks for the help in fixing but a little adjustment this script does not work with the new versions of the driver nvidia because it does not need to work with him the firmware files have not changed and the only reason why I decided to update the package is to abandon python 2 and x86 architecture in the Arch

Here's a PKGUILD that merges extracted firmware from 340.108 and 325.15. nouveau-fw.zip It also runs sha256sum on the extracted files. The script doesn't currently work with newer driver versions.

Did some digging.

This script is from a deprecated project [0]. The new project's [1] script is python3. Gentoo is using this newer script [2]. This should be a trivial change for us.

It seems that we're using the 32-bit blob bc in the past 32 & 64 bit blobs contained the same fw [3]. However, we're now only seeing new releases in 64-bit. Compare 32-bit [4] to 64-bit [5].

The fw we're getting is damn near a decade old at this point. Presumably updating this will require splitting the package into various legacy & newer versions, since these breaks in backwards compatibility come from Nvidia itself [6]. If I had half the knowledge of Nvidia internals and the state of nouveau that MuPuF has, I'd look into this, but I don't. The changes here will likely be non-trivial and require significant domain expertise.

[0] - https://github.com/imirkin/re-vp2/pull/7#issuecomment-621921580 [1] - https://github.com/envytools/firmware [2] - https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-firmware/nvidia-firmware/nvidia-firmware-340.32-r1.ebuild [3] - https://aur.archlinux.org/packages/nouveau-fw?O=20#comment-458842 [4] - https://download.nvidia.com/XFree86/Linux-x86/ [5] - https://download.nvidia.com/XFree86/Linux-x86_64/ [6] - https://www.nvidia.com/en-us/drivers/unix/legacy-gpu/

Update Released

This package needs a new maintainer, maybe.

@MuPuf it might be worth updating to the version of extract_firmware.py in envytools for python3 compatibility: https://github.com/envytools/firmware/blob/master/extract_firmware.py. It works alright with your PKGBUILD and the following diff:

11,12c11,12
< makedepends=('python2')
< source=("https://raw.github.com/imirkin/re-vp2/master/extract_firmware.py"
---
> makedepends=('python3')
> source=("https://raw.githubusercontent.com/envytools/firmware/master/extract_firmware.py"
21c21
<   python2 extract_firmware.py
---
>   python3 extract_firmware.py

Can you update this? Or are the firmwares up to date regardless of what driver version there is?

$ egrep CARCH /etc/makepkg.conf

CARCH="x86_64"

(pacman 5.2.2-2 - https://archlinux.org/packages/core/x86_64/pacman/)

So either you changed your makepkg.conf some time ago, or you are not using Arch.