From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Vincent Fazio <vfazio@xes-inc.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [External] - Re: [PATCH 2/2] package/nvidia-driver: bump version to 390.151
Date: Mon, 25 Jul 2022 14:46:19 +0200 [thread overview]
Message-ID: <20220725124619.GD3168@scaer> (raw)
In-Reply-To: <PH1P110MB16031BEB9E963C09FFE461E19F959@PH1P110MB1603.NAMP110.PROD.OUTLOOK.COM>
Vincent, All,
On 2022-07-25 12:31 +0000, Vincent Fazio spake thusly:
> > From: Arnout Vandecappelle <arnout@mind.be>
> > I wanted to apply this, but the hash doesn't match... Could you investigate?
> This is a bit concerning because it's the second time this has happened. Thomas had a similar problem when I tried to bump to 390.144
> http://patchwork.ozlabs.org/project/buildroot/patch/20211104141910.1840914-1-vfazio@xes-inc.com/#2813798
>
> Linux:
> vfazio@vfazio2 ~ $ sha256sum NVIDIA-Linux-x86_64-390.151.run
> 5226e4842044cffd9096deadaf68934c133da74e05b80ccd21236584b3afb1fc NVIDIA-Linux-x86_64-390.151.run
>
> vfazio@vfazio2 ~ $ sha256sum ~/Downloads/NVIDIA-Linux-x86_64-390.151-no-compat32.run
> 6e4fd2258465f5d5527fe80abd46de925a30348b4a84658498a6d75caf42c47c /home/vfazio/Downloads/NVIDIA-Linux-x86_64-390.151-no-compat32.run
>
> Can you double check the hashes when directly fetching the files?
> https://download.nvidia.com/XFree86/Linux-x86_64/390.151/
I just did, and got:
5226e4842044cffd9096deadaf68934c133da74e05b80ccd21236584b3afb1fc NVIDIA-Linux-x86_64-390.151.run
6e4fd2258465f5d5527fe80abd46de925a30348b4a84658498a6d75caf42c47c NVIDIA-Linux-x86_64-390.151-no-compat32.run
... which is what Vincent provided.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-25 12:46 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
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 [this message]
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=20220725124619.GD3168@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vfazio@xes-inc.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.