From owner-freebsd-current@FreeBSD.ORG Thu Nov 22 09:25:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B440216A41A for ; Thu, 22 Nov 2007 09:25:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 5614413C469 for ; Thu, 22 Nov 2007 09:25:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 28924 invoked by uid 399); 22 Nov 2007 09:25:04 -0000 Received: from localhost (HELO ?192.168.0.4?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 22 Nov 2007 09:25:04 -0000 X-Originating-IP: 127.0.0.1 Date: Thu, 22 Nov 2007 01:25:00 -0800 (PST) From: Doug Barton To: Alexey Dokuchaev In-Reply-To: <20071122091826.GA38417@FreeBSD.org> Message-ID: References: <20071122091826.GA38417@FreeBSD.org> User-Agent: Alpine 0.99999 (BSF 796 2007-11-08) X-message-flag: Outlook -- Not just for spreading viruses anymore! X-OpenPGP-Key-ID: 0xD5B2F0FB Organization: http://www.FreeBSD.org/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Lack of agpvar.h causing nvidia-driver build to fail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 22 Nov 2007 09:25:16 -0000 On Thu, 22 Nov 2007, Alexey Dokuchaev wrote: > Exactly right, I have a fix I will commit after I make my -current up to > date to test it and get portmgr@ approval. Great news, today really is my day for quick responses on broken stuff. :) If you want to send me the patch I'll be glad to test it as well. My system is right up to the minute, and I always clean out old cruft. FYI, I took a look at what's different between versions .14 and .19, and it looks to me like it's an issue of "hot" docking vs. "warm" docking. I've made the change to "warm" docking in my BIOS, so the next step is to try things with the latest driver version to confirm that theory. Doug -- This .signature sanitized for your protection