[Request] nouveau-fw about packages HOT 16 CLOSED

Then you can close this error or put a tag on it while I go write to the person who wrote extract-firmware.py since I as the maintainer did not make any errors in pkgbuild it is just that the script itself does not work

from packages.

That package hasn't been updated in 8 years, and has been flagged out of date for 3 years. The package needs major updates before it can be added.

from packages.

That package hasn't been updated in 8 years and has been flagged out of date for 3 years. Based on comments, it's delivering 32-bit binaries. Arch supports only 64-bits.

Here is the pkgbuild I changed, which is already the newest, unfortunately I haven't figured out how to become a new maintainer for the package yet so I sent pkgbuild here

from packages.

I took care of the maintenance and updated the package to the newest version available at the moment

from packages.

... if there is the same log, then in principle it should be so ...

Here is the log from Gentoo after build. That's the way it should be

Having the same error occur on multiple platforms does not mean "That's the way it should be". It means the error is not platform specific. This is easily seen by swapping out the error with any other, like a segfault.

If this were a warning or an info message, then it might be safely be skipped. But there is no indication of severity, cause, or consequence. If the package comes with file lists and checksums, then the results could be checked.

Poking at the python code, skipping the blobs should result in missing files, but not corrupt files. So whatever is created is presumably safe to use. However, different versions have different numbers of files with some checksums not matching.

You could try extracting a newer version, then filling in the gaps with an older version. Also, create baseline checksum files to help detect issues in the future.

nouveau-fw.zip

from packages.

The article on this site was updated in March 2023 which means that it is still relevant and the fact that the script can only get 340 drivers probably because he does not need newer in the wiki gentoo also does not say that the package is obsolete so I think that adding it still makes sense

from packages.

@Boria138 do an orphan request, it's been MUCH longer than 2 weeks! https://wiki.archlinux.org/title/AUR_submission_guidelines#Orphan

from packages.

What's up with this @Boria138?
nouveau-fw.log

==> Starting build()...
Creating directory NVIDIA-Linux-x86_64-340.108
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64 340.108........
Unknown PGRAPH archive order in this version.
Skipping gzip blob at 0x6460c0 (524288 bytes), wrong magic: 0xfc000000
Skipping gzip blob at 0x6464e0 (524288 bytes), wrong magic: 0xfc000000
Skipping gzip blob at 0x956ec4 (39744 bytes), wrong magic: 0x2
Skipping gzip blob at 0x958364 (10624 bytes), wrong magic: 0x100c

from packages.

I do not have the nvidia card to test but if you just look in /usr/lib/firmware/nouveau/ you can see that all the firmware is there I tried the script with different versions of drivers and even with x86 bit which arch does not support these errors were everywhere but the files were so I guess this error can be ignored

from packages.

The only thing I found was this post, but the person there uses an old version of the python 2 script and lacks nva8_fuc084 which the new version already unpacks

from packages.

I reduced the version of the driver to 325.15 because in the script to unpack the firmware says that the set of firmware in all versions listed in the script the same, so you can do downgrade and in general the number of errors decreased to two

Creating directory NVIDIA-Linux-x86_64-325.15
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64 325.15....
Skipping gzip blob at 0x6954e4 (33440 bytes), wrong magic: 0x2
Skipping gzip blob at 0x6966e4 (7648 bytes), wrong magic: 0x100c

from packages.

Proof of my words that the firmware itself is up to date regardless of the driver version

# The firmware changes fairly rarely. From a limited sample, when the
# firmware does change, the starts of the firmware remain the
# same. When changing the version though, one should double-check the
# sizes, which can be different.
#
# This is the list of tested versions that produce the same binaries
VERSIONS = (
    "319.17",
    "319.23",
    "319.32",
    "325.08",
    "325.15",
    "340.32",
    "340.108",
    )

ARCHES = ("x86_64", "x86")

from packages.

@Boria138 Don't ignore the errors. Files may be corrupt, even if present.

from packages.

Well, we are now checking whether this is a problem. There is a similar package from Gentoo.
I asked my friends to check the assembly of the package, if there is the same log, then in principle it should be so

from packages.

* nvidia_extract_firmware-a0b9f9be0efad90cc84b8b2eaf587c3d7d350ea9.py BLAKE2B SHA512 size ;-) ...     [ ok ]
 * Checking whether python3_11 is suitable ...
 *   >=dev-lang/python-3.11.1-r1:3.11 ...                                                    [ ok ]
 * Using python3.11 to build (via PYTHON_COMPAT iteration)
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86-340.32.run to /var/tmp/portage/sys-firmware/nvidia-firmware-340.32-r1/work/NVIDIA-Linux-x86-340.32
>>> Source unpacked in /var/tmp/portage/sys-firmware/nvidia-firmware-340.32-r1/work
>>> Preparing source in /var/tmp/portage/sys-firmware/nvidia-firmware-340.32-r1/work ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-firmware/nvidia-firmware-340.32-r1/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-firmware/nvidia-firmware-340.32-r1/work ...
Unknown PGRAPH archive order in this version.
Skipping gzip blob at 0x587040 (524288 bytes), wrong magic: 0xfc000000
Skipping gzip blob at 0x587440 (524288 bytes), wrong magic: 0xfc000000
Skipping gzip blob at 0x87dd44 (39552 bytes), wrong magic: 0x2
Skipping gzip blob at 0x87f104 (9568 bytes), wrong magic: 0x100c
>>> Source compiled.
>>> Test phase [not enabled]: sys-firmware/nvidia-firmware-340.32-r1

>>> Install sys-firmware/nvidia-firmware-340.32-r1 into /var/tmp/portage/sys-firmware/nvidia-firmware-340.32-r1/image
>>> Completed installing sys-firmware/nvidia-firmware-340.32-r1 into /var/tmp/portage/sys-firmware/nvidia-firmware-340.32-r1/image

 * Final size of build directory: 168164 KiB (164.2 MiB)
 * Final size of installed tree:    1600 KiB (  1.5 MiB)

Here is the log from Gentoo after build. That's the way it should be

from packages.

@xiota Thanks for the help in fixing your changes I already added to aur I guess now the package can be added to chaotic-aur

from packages.