Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nvidia releases open-source GPU kernel modules

developer.nvidia.com

Post reply on HN
Print view View original

221–230 of 415 posts

Re: Nvidia releases open-source GPU kernel modules

#221

Post by sabujp »

kaladin-jasnah wrote: post #116
pixelmonkey wrote: post #75

> In this open-source release, support for GeForce and Workstation GPUs is alpha quality. GeForce and Workstation users can use this driver on Turing and NVIDIA Ampere architecture GPUs to run Linux desktops and use features such as multiple displays, G-SYNC, and NVIDIA RTX ray tracing in Vulkan and NVIDIA OptiX. Users can opt in using the kernel module parameter NVreg_EnableUnsupportedGpus as highlighted in the docu…

The reason for this is because NVIDIA's Turing and above GPUs use a new microcontroller called the GSP, which is RISC-V based. From my understanding, NVIDIA has offloaded their proprietary IP from the closed-source driver to the GSP firmware (and not the older microcontroller present on Pascal and lower). This is why `gsp.bin` exists in `linux-firmware` now, and the FOSS driver targets the GSP (because now the propri…

ctrl+f binary, tx this is the answer I was looking for. The binary is still in linux-firmware similar to intel drivers

Re: Nvidia releases open-source GPU kernel modules

#222

Post by adastra22 »

pornel wrote: post #196
adastra22 wrote: post #151

Earlier quoted context omitted.

RMS may have believed or wanted that, but it is my understanding (IANAL!) that the case law has been settled differently. If you are found in violation of the GPL due to a dependency you weren't aware was released under the GPL, you can fix that violation by rewriting your application to avoid the GPL dependency. CLISP et al cannot be forced to distribute their code under the GPL. It's their code and their choice; co…

It's more nuanced. If you've included GPL code and modified or redistributed it , then you either have to comply with the GPL to have permission for that use, or you've potentially committed a copyright violation. To comply with the GPL you only need to publish the one specific snapshot of source code you've combined and redistributed with GPL code, but you don't need to permanently relicense your project if it doesn…

That isn’t any different from what I said though? If someone points out you violated their copyright then you need to (1) fix the issue, and (2) pay appropriate damages. But for open source software the damages are nil, so fixing the violation is the only thing you need to do. And you can do that by either releasing the code as GPL, or removing the dependency. Either would be an acceptable remedy, in the eyes of the law.

Re: Nvidia releases open-source GPU kernel modules

#223

Post by samtheDamned »

And just like that my next gpu will probably be NVIDIA. AMD's recent prices have made nvidia look like a better option and the only thing holding me back was amd's amazing open source drivers and the options that came with. If nvidia's drivers become comparable or are well on their way then they would be the obvious choice in today's market.

Re: Nvidia releases open-source GPU kernel modules

#224

Post by kllrnohj »

paulmd wrote: post #200
SV_BubbleTime wrote: post #124

Earlier quoted context omitted.

It’s pretty damn stunning how quite an AIO 2x 140mm cooler can be. And graphics cards with those big triple fans are silent until needed. I’ve been through a couple 12th gens. I like them, but unless you need the machine updated right now, 13th gen is 6 months out.

AIO performance on CPUs is largely limited by thermal transfer through the coldplate/IHS (Integrated Heat Spreader), not by radiator size. Basically the radiator is keeping the fluid very cool already, but heat can't move through the IHS quickly enough. So it takes a large improvement in fluid temperature to make a small improvement in die temperature - you are "pushing on a string" as the expression goes. Almost no…

It's more of an adventure with a GPU than a CPU but you can add an aio after market with eg https://nzxt.com/product/kraken-g12

Then you're not paying the Kingpin markup if you're not planning to x-oc it. I did that on a Titan X (Pascal) which was still using a blower design and it worked fantastically.

Re: Nvidia releases open-source GPU kernel modules

#225

Post by mepian »

boardwaalk wrote: post #220
eru wrote: post #209

Earlier quoted context omitted.

Are APUs different from what we used to call integrated graphics cards?

APUs are AMD-speak for CPU and GPU on the same die (Intel has similar but doesn't call them that). Integrated graphics cards (a misnomer since there is no card -- IGP or iGPU is probably more accurate) may or may not be on the same die (instead could be on the motherboard, particularly in the chipset). That design is pretty rare/antiquated at this point though. Being on the same die means higher bandwidth, lower late…

I think Intel calls them XPUs.

Re: Nvidia releases open-source GPU kernel modules

#227

Post by SemanticStrengh »

kllrnohj wrote: post #219
SemanticStrengh wrote: post #215

Earlier quoted context omitted.

The difference is getting blurry. Apus have generally better communication/latency/shared resources with the CPU. The ultimate ideal of an APU is to have a unified memory with the CPU, which is the case in e.g the PS3/PS4 Despite progress in heterogenous computing (the neglected HSA), in SOCs, 3D ingerposers, high bandwidth buses interconnects and 3D memory such as HBM, the PC platform has yet to see a proper APU. In…

> the PC platform has yet to see a proper APU Wat. AMD literally invented the term 'APU' and has been shipping them since 2011. Fully unified CPU+GPU memory since 2014's Kavari. That's full cache coherent CPU & GPU along with the GPU using the same shared virtual pageable memory as the CPU. The M1 didn't add anything new to the mix.

It's a spectrum. I don't think that cache coherency was useable by developers/compilers. The two only ways I know (HMM and HSA) are niche, used by nobody. GPGPU compute would GREATLY benefit from programs that can share memory between cpu and gou without having to do needless high latency round-trips and copies. So they failed in practice. They never did a CPU addressable HBM interposer (despite having invented HBM) unlike what I believe is the M1.

Re: Nvidia releases open-source GPU kernel modules

#228

Post by paulmd »

kllrnohj wrote: post #224
paulmd wrote: post #200

Earlier quoted context omitted.

AIO performance on CPUs is largely limited by thermal transfer through the coldplate/IHS (Integrated Heat Spreader), not by radiator size. Basically the radiator is keeping the fluid very cool already, but heat can't move through the IHS quickly enough. So it takes a large improvement in fluid temperature to make a small improvement in die temperature - you are "pushing on a string" as the expression goes. Almost no…

It's more of an adventure with a GPU than a CPU but you can add an aio after market with eg https://nzxt.com/product/kraken-g12 Then you're not paying the Kingpin markup if you're not planning to x-oc it. I did that on a Titan X (Pascal) which was still using a blower design and it worked fantastically.

This is true, but: you have to watch compatibility (note that there are no 3000 series chips on that list - because NVIDIA changed their hole placement again, and AMD has a couple different sizes for their different chips, 6500XT/6400 is definitely smaller for example), and also it doesn't do as good a job cooling VRAM. You can put add-on heatsinks on the VRAM chips, but they can fall off and short something. And adding them on the back can run into compatibility problems with bumping into the CPU heatsink.

And VRAM temperatures are a big problem on the Ampere cards - I don't really think running >100C all the time is really gonna be great for them long-term. Even gaming (vs mining) it's not abnormal to see VRAM over 100C (especially 3090, with the chips on the back, but also on the other GDDR6X cards, GDDR6X just runs extraordinarily hot). I know what NVIDIA and Micron say, I'm not sure I believe it. Above-100C is really really dubious imo.

for the 3090, with the VRAM on the back, I think it makes sense to go with a factory-configured AIO. Other cards, and especially GDDR6 cards, sure, it does work and it does help. Don't go too nuts tightening the AIO down though (ask me why! >.Gelid used to make nice little cooling shields for the VRM and memory modules. I'm disappointed they stopped, although I'm sure it was a tiny market. For single-sided cards that is a much much nicer solution than stick-on heatsinks imo.

https://www.quietpc.com/gelid-icy-vision-gtx1080kit

Re: Nvidia releases open-source GPU kernel modules

#230

Post by brezelgoring »

lawl wrote: post #153
jjoonathan wrote: post #55

Earlier quoted context omitted.

That might not even be overstatement. The last few big desktop linux crash-and-burns I've run into all had display drivers as a common component. I like back-foot, underdog NVIDIA. Ascendent AMD hasn't drawn my ire yet, let's hope power corrupts slowly.

Amd changed their windows drivers to not output video if it detects its running in a VM. Nvidia went the other way and stopped doing so. Both can/could be bypassed with some libvirtd xml magic, but still. Nvidia seem to slowly stop being assholes, AMD started already.

>Amd changed their windows drivers to not output video if it detects its running in a VM.

What? Why?

Post reply on HN