Live data from Hacker News

CUDA 11.0

docs.nvidia.com

11–20 of 67 posts

Re: CUDA 11.0

#11
post #7

Interesting that Fedora support seems to have been dropped. Anyone know why that might be? Edit: oh wait I think I see. Latest supported gcc for CUDA 11 is gcc 9.x, but I think latest Fedora is on gcc 10.

They've come to the conclusion that you should also come to, that Fedora is basically a waste of time to support because whatever you've gotten working will be terribly broken in the next release for no good reason anyone can point to?

Re: CUDA 11.0

#12
post #3

I noticed CUDA 11.0 was almost ready for release last week when I went to install CUDA and the default download page linked to the 11.0 Release Candidate. The 10.1 and 10.2 links were buried behind a link off to the side labeled "legacy". The thing is, no library you use is going to be supporting the CUDA 11.0 RC, that's ridiculous. For example, Pytorch stable is on 10.2 and Tensorflow only goes up to 10.1. This is g…

Yeah, and the CUDA 10.0 official Visual Studio demo project build was broken for... looks like a year, at least, because they didn't want to populate the toolkit path. NVidia, you're better than this.

https://forums.developer.nvidia.com/t/the-cuda-toolkit-v10-0...

> The Conda dependency manager has made this a lot easier

Yeah but conda is "Let's do dependency management with a SAT solver, it'll be great!" On a good day, it's just slow. On a bad day, the SAT solver spins for hours before failing to converge. On a really bad day, the SAT solver does something "clever."

I've had a couple of really bad days this year. I'm really starting to not like conda very much.

Re: CUDA 11.0

#13
post #3

I noticed CUDA 11.0 was almost ready for release last week when I went to install CUDA and the default download page linked to the 11.0 Release Candidate. The 10.1 and 10.2 links were buried behind a link off to the side labeled "legacy". The thing is, no library you use is going to be supporting the CUDA 11.0 RC, that's ridiculous. For example, Pytorch stable is on 10.2 and Tensorflow only goes up to 10.1. This is g…

I have to use containers with nvidia-docker because NVIDIA so consistently and relentlessly breaks things without so much as a glance at backward compatibility.

Re: CUDA 11.0

#14
Everytime I have to deal with multiple versions of CUDA on Linux I feel like poking my eyes out. I get that supporting developer libraries that have to interact with hardware is hard but come on...

Re: CUDA 11.0

#15
post #3

I noticed CUDA 11.0 was almost ready for release last week when I went to install CUDA and the default download page linked to the 11.0 Release Candidate. The 10.1 and 10.2 links were buried behind a link off to the side labeled "legacy". The thing is, no library you use is going to be supporting the CUDA 11.0 RC, that's ridiculous. For example, Pytorch stable is on 10.2 and Tensorflow only goes up to 10.1. This is g…

Yeah, and the CUDA 10.0 official Visual Studio demo project build was broken for... looks like a year, at least, because they didn't want to populate the toolkit path. NVidia, you're better than this. https://forums.developer.nvidia.com/t/the-cuda-toolkit-v10-0... > The Conda dependency manager has made this a lot easier Yeah but conda is "Let's do dependency management with a SAT solver, it'll be great!" On a good d…

You might find https://github.com/TheSnakePit/mamba useful, especially if you are slowed down by package resolution.

Re: CUDA 11.0

#16

Earlier quoted context omitted.

Yeah, and the CUDA 10.0 official Visual Studio demo project build was broken for... looks like a year, at least, because they didn't want to populate the toolkit path. NVidia, you're better than this. https://forums.developer.nvidia.com/t/the-cuda-toolkit-v10-0... > The Conda dependency manager has made this a lot easier Yeah but conda is "Let's do dependency management with a SAT solver, it'll be great!" On a good d…

You might find https://github.com/TheSnakePit/mamba useful, especially if you are slowed down by package resolution.

That looks worth a look for sure!

Re: CUDA 11.0

#18
post #9
post #8

>cuFFT now accepts __nv_bfloat16 input and output data type for power-of-two sizes with single precision computations within the kernels. This exact sentence is listed both under "New Feature" and "Known Issues". I'm not super familiar with CUDA stuff, but, it can't be both right?

Looks like a mistake, should only be in New Features.

So a known issue in the known issues?

Re: CUDA 11.0

#19
post #3

I noticed CUDA 11.0 was almost ready for release last week when I went to install CUDA and the default download page linked to the 11.0 Release Candidate. The 10.1 and 10.2 links were buried behind a link off to the side labeled "legacy". The thing is, no library you use is going to be supporting the CUDA 11.0 RC, that's ridiculous. For example, Pytorch stable is on 10.2 and Tensorflow only goes up to 10.1. This is g…

Yeah, and the CUDA 10.0 official Visual Studio demo project build was broken for... looks like a year, at least, because they didn't want to populate the toolkit path. NVidia, you're better than this. https://forums.developer.nvidia.com/t/the-cuda-toolkit-v10-0... > The Conda dependency manager has made this a lot easier Yeah but conda is "Let's do dependency management with a SAT solver, it'll be great!" On a good d…

Conda's SAT solver for dependency management is the bane of my existence. For pip-installable packages, I'll almost always turn to pip rather than conda even when in a conda environment.

Re: CUDA 11.0

#20
post #2

> Added support for Ubuntu 20.04 LTS on x86_64 platforms. Huh? I've been using CUDA for a while now on my Ubuntu 20.04 machine

This has been problematic for me after upgrading from 18.04 to 20.04. Every time I apt update cuda or some nvidia package my x server fails to start for several different reasons.

Just today I've already spent 30 minutes trying to start x with this latest cuda update. Too bad I can't switch back to the open source nouveau driver.

Post reply on HN