diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-December/020798.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-December/020798.html | 120 |
1 files changed, 120 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-December/020798.html b/zarb-ml/mageia-dev/2012-December/020798.html new file mode 100644 index 000000000..d03915d38 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-December/020798.html @@ -0,0 +1,120 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] NVIDIA CUDA 5 has landed + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20NVIDIA%20CUDA%205%20has%20landed&In-Reply-To=%3C1355519315.1833.19.camel%40localhost%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="020791.html"> + <LINK REL="Next" HREF="020800.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] NVIDIA CUDA 5 has landed</H1> + <B>Dimitri</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20NVIDIA%20CUDA%205%20has%20landed&In-Reply-To=%3C1355519315.1833.19.camel%40localhost%3E" + TITLE="[Mageia-dev] NVIDIA CUDA 5 has landed">mitya at mageia.org + </A><BR> + <I>Fri Dec 14 22:08:35 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="020791.html">[Mageia-dev] [changelog] [RPM] cauldron core/release transmission-2.74-1.mga3 +</A></li> + <LI>Next message: <A HREF="020800.html">[Mageia-dev] NVIDIA CUDA 5 has landed +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20798">[ date ]</a> + <a href="thread.html#20798">[ thread ]</a> + <a href="subject.html#20798">[ subject ]</a> + <a href="author.html#20798">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, + +Finally, NVIDIA CUDA Toolkit 5.0.35 has landed in Cauldron. I apologize +for the delay, and ask everyone interested to test the packages +(especially on x86_64). + +New in packaging: +================= + +* From now on, we are using SLES official packages, because others +(Ubuntu, Fedora) contain cuda-gdb binary that is linked against +libtinfo.so.5 that we do not ship; +* those lame /usr/{nvvm,open64,libnvvp,libnsight} are moved to the +appropriate place, namely %_libdir; +* samples (ex-CUDA SDK) have been included. + +New in CUDA 5.0: +================ + +* NVIDIA Nsight, a full-featured CUDA IDE, based on Eclipse CDT; +* dynamic parallelism - simply speaking, ability to spawn new kernels +from kernels; +* more here: +<A HREF="http://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html">http://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html</A> + +Known issues: +============= + +* GCC 4.7 is not supported. However, you can fool nvcc and compile a +program with -D__GNUC_MINOR__=6; +* In Eclipse based products, you may notice that toolbar buttons don't +respond to mouse hover (look flat all the time). This is a well-known +issue and will be fixed in the upcoming release of +gnome-themes-standard; +* Eclipse-based products are unable to open web browser due to crash in +libxul.so (should we update xulrunner?) + +The work on the package is still not finished. The package contains an +init script (nvidia) that creates device nodes and loads kernel module. +This "service" is intended to be started on GUI-less compute nodes. I +want to ask for assistance in migrating this script to systemd unit. As +far as I know, with latest kernels and NVIDIA drivers the device nodes +always get created automatically (never noticed them not being +created). So probably the only thing left is to load kernel module. +Seems like putting it into modules-load.d/* is a bad idea, because if +the module is absent, systemd-modules-load.service will fail. Should we +simply make a unit with ExecStart=/usr/sbin/modprobe nvidia-current instead? + +Also I'd like to thank Pascal Terjan who helped me to upload a part of +source. Uploading another 700 MBytes took me 2 hours - that was painful. +I remember there was a proposal to provide packagers with their +dedicated VMs with shell accounts on a build cluster - what's the status +of that? + +Regards, +Dimitri + +</PRE> + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="020791.html">[Mageia-dev] [changelog] [RPM] cauldron core/release transmission-2.74-1.mga3 +</A></li> + <LI>Next message: <A HREF="020800.html">[Mageia-dev] NVIDIA CUDA 5 has landed +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20798">[ date ]</a> + <a href="thread.html#20798">[ thread ]</a> + <a href="subject.html#20798">[ subject ]</a> + <a href="author.html#20798">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |