From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Vincent Fazio <vfazio@xes-inc.com>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/nvidia-driver: bump version to 390.144
Date: Thu, 30 Dec 2021 17:35:13 +0100 [thread overview]
Message-ID: <20211230173513.21e06b0e@windsurf> (raw)
In-Reply-To: <20211104141910.1840914-1-vfazio@xes-inc.com>
Hello Vincent,
On Thu, 4 Nov 2021 09:19:10 -0500
Vincent Fazio <vfazio@xes-inc.com> wrote:
> Adds support for Linux kernel 5.11.
>
> Define IGNORE_CC_MISMATCH for kernel module builds to avoid an issue
> where NVIDIA's `cc_version_check` in kernel/conftest.sh may falsely
> detect a mismatch and fail due to matching on the pkgversion substring
> of the GCC version string in the kernel's include/generated/compile.h.
>
> Signed-off-by: Vincent Fazio <vfazio@xes-inc.com>
> ---
> package/nvidia-driver/nvidia-driver.hash | 4 ++--
> package/nvidia-driver/nvidia-driver.mk | 3 ++-
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/package/nvidia-driver/nvidia-driver.hash b/package/nvidia-driver/nvidia-driver.hash
> index 7f2248d0f9..9e6deb0061 100644
> --- a/package/nvidia-driver/nvidia-driver.hash
> +++ b/package/nvidia-driver/nvidia-driver.hash
> @@ -1,4 +1,4 @@
> # Locally computed
> -sha256 51adb28f0ed4548f35a88a93ad6767ebd807fa14f418bf5e51a6d63a3ff7f275 NVIDIA-Linux-x86-390.132.run
> -sha256 b6b4b8af37e78e026c9ebdf4a5c64ea412dfcb710931dd028c22dac228de659d NVIDIA-Linux-x86_64-390.132-no-compat32.run
> +sha256 8bb6e8de89e8f8325466af29cf0fa235c988d19137f7fe3eb6bfae1d5e305e74 NVIDIA-Linux-x86-390.144.run
> +sha256 d9b36e51253592d7aeecb9758ebccf30348ab364c88f95aa5ba33c767470949c NVIDIA-Linux-x86_64-390.144-no-compat32.run
> sha256 bd28b0c5aeeb00eb11d3ec6f6f3449d4b3a40100914258332734a53527997526 LICENSE
Sorry for the slow feedback, but could you check those hashes? Indeed,
I don't get the same here:
ERROR: NVIDIA-Linux-x86-390.144.run has wrong sha256 hash:
ERROR: expected: 8bb6e8de89e8f8325466af29cf0fa235c988d19137f7fe3eb6bfae1d5e305e74
ERROR: got : fa586d11fcf103f81eda7d859a2a8ccdeb7371f4742fe942cb4a9b0aeb6bbb30
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
However, *before* doing a test, please keep aside your existing
NVIDIA-Linux-x86-390.144.run and
NVIDIA-Linux-x86_64-390.144-no-compat32.run from your download folder,
and verify their hashes. We indeed want to see if you got the hashes
wrong in the .hash file, or if really NVidia changed the files they are
serving.
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-30 16:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 14:19 [Buildroot] [PATCH 1/1] package/nvidia-driver: bump version to 390.144 Vincent Fazio
2021-12-30 16:35 ` Thomas Petazzoni [this message]
2021-12-30 17:20 ` [Buildroot] [External] - " Vincent Fazio
2022-06-20 17:09 ` [Buildroot] [PATCH 1/1] package/nvidia-driver: bump version to 390.151 Vincent Fazio
2022-06-20 18:20 ` Arnout Vandecappelle
2022-06-20 18:42 ` [Buildroot] [External] - " Vincent Fazio
2022-06-20 19:01 ` [Buildroot] [PATCH 1/2] package/nvidia-driver: define IGNORE_CC_MISMATCH Vincent Fazio
2022-06-20 19:01 ` [Buildroot] [PATCH 2/2] package/nvidia-driver: bump version to 390.151 Vincent Fazio
2022-07-23 19:20 ` Arnout Vandecappelle
2022-07-25 12:31 ` [Buildroot] [External] - " Vincent Fazio
2022-07-25 12:46 ` Yann E. MORIN
2022-07-25 13:25 ` [Buildroot] [PATCH v2 " Vincent Fazio
2022-07-25 22:23 ` Arnout Vandecappelle
2022-07-23 19:38 ` [Buildroot] [PATCH 1/2] package/nvidia-driver: define IGNORE_CC_MISMATCH Arnout Vandecappelle
2022-08-17 6:55 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211230173513.21e06b0e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=vfazio@xes-inc.com \
--cc=yann.morin.1998@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox