From owner-freebsd-current@FreeBSD.ORG Sun Aug 15 02:03:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 555AB16A4CE for ; Sun, 15 Aug 2004 02:03:44 +0000 (GMT) Received: from mail.tpgi.com.au (mail.tpgi.com.au [203.12.160.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id A50C643D3F for ; Sun, 15 Aug 2004 02:03:43 +0000 (GMT) (envelope-from agh@tpg.com.au) Received: from [192.168.0.4] (220-244-72-6.tpgi.com.au [220.244.72.6]) by mail.tpgi.com.au (8.12.10/8.12.10) with ESMTP id i7F23fZa008731 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 15 Aug 2004 12:03:42 +1000 From: "Alastair G. Hogge" To: freebsd-current@FreeBSD.ORG Date: Sun, 15 Aug 2004 12:04:25 +1000 User-Agent: KMail/1.6.2 References: <200408141934.24107.dfr@nlsystems.com> In-Reply-To: <200408141934.24107.dfr@nlsystems.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408151204.25592.agh@tpg.com.au> X-TPG-Antivirus: Passed Subject: Re: New nvidia drivers available X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Aug 2004 02:03:44 -0000 On Sun, 15 Aug 2004 04:34, Doug Rabson wrote: > The latest 6113 build of the nvidia graphics drivers has just appeared > on nvidia's web site. Check out > http://www.nvidia.com/object/freebsd_1.0-6113.html if you are currently > using the nvidia proprietary drivers. This driver works nicely on > FreeBSD-current and while this version is not thread-safe, it does not > conflict with libpthread or libthr's use of %gs so you don't have to > map everything down to libc_r any more :-). > > There will be a thread-safe driver available for FreeBSD-current > sometime after I commit the pthread parts of the TLS support code. This is most awesome. I could only get the the module to load if I had device mem and device io in my kernel spec. Using the mem and io kernel modules would cause undefined symbols to mem_range_attr_set when trying to load nvidia.ko in /boot/loader.conf Nice work :-) -Alastair