6 ms·
Well it is a bit of a grey zone but I have gotten Vulkan to work and I think at least NVENC works as well. The solution is rather hacky though. It extracts libr
by erk__ 6y ago
Well it is a bit of a grey zone but I have gotten Vulkan to work and I think at least NVENC works as well. The solution is rather hacky though. It extracts libraries from the Linux driver and loads them when you run programs. A look at the code make it seems like cuda is getting loaded as well so it may work.
https://github.com/shkhln/nvshim https://github.com/shkhln/nvshim
- LargoLasskhyfv 6y agoWhile i respectfully congratulate the authors of that shim for their ingenuity, that is no support.
- chupasaurus 6y agoNothing drastically changed since Torvalds had sended his gratitude[0]. [0] https://youtu.be/MShbP3OpASA?t=2997 https://youtu.be/MShbP3OpASA?t=2997 (time coded)
- LargoLasskhyfv 6y agoI concur.
- chupasaurus 6y agoWayland support fiasco, changes in driver's EULA to deny the usage of consumer-grade GPUs in VMs are 2 things off the top of my head.
- floatboth 6y agoThere was actually some period of time when the Tegra division (I think) contributed to Nouveau a bit (!) but that didn't really grow into anything good.
- magic_quotes 6y ago> changes in driver's EULA to deny the usage of consumer-grade GPUs in VMs Which changes? Where? I'm looking at said EULA right now and I don't see anything related.
- chupasaurus 6y agoMy bad, it was a silently added "feature" in Windows driver[0]. [0] https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#%22Error_43:_Driver_failed_to_load%22_on_Nvidia_GPUs_passed_to_Windows_VMs https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVM...
- loeg 6y agoNvshim is an amazing project, but it is a far cry from official Nvidia support for CUDA/NVENC/NVDEC. (All Nvidia would have to do is build another binary; it's still chatting with the same driver blob internally so it's not really clear to me why they don't bother compiling it for FreeBSD.)
- LargoLasskhyfv 6y agoThey could even do it with less churn, because of https://github.com/freebsd/freebsd/blob/master/sys/conf/options#L90 https://github.com/freebsd/freebsd/blob/master/sys/conf/opti... FreeBSD easily achieves binary compatibility with earlier versions. So no need to mess around with DKMS or their own thing. Or at least less so.
- floatboth 6y ago> FreeBSD easily achieves binary compatibility with earlier versions. So no need to mess around with DKMS Binary compatibility is for userspace programs, not kernel modules.
- loeg 6y agoGP's link is to the COMPAT_FREEBSD binary compatibility for earlier versions of FreeBSD, oddly. I don't think it (or linux emulation) has anything to do with Nvidia's needs re: CUDA/NVENC.
- LargoLasskhyfv 6y agoIt means you have a module from some vendor, or something similar to the NVIDIA installer for linux, which technically is nothing else than a batch compiled makefile, spitting out a kernel-module made for version 1.2.3 while you are running 2.4.5. It worked. I don't know why it shouldn't now. Edit: I'm not having any FreeBSD systems in use right now, so i don't know if they changed the defaults. What i remember is at least the last two versions were compiled into GENERIC, so you didn't even had to compile your own kernel when that range backwards was enough. Similar thing in NetBSD, a loooong time ago, even their own driver for 3Com905 relied on the equivalent of that functionality. That caught me by surprise, because i used NetBSD like Gentoo, found some Compat foobarjurassicBSD, wondered why i should use that at all, and had no working net. Fun! :-)