From owner-freebsd-current Wed Mar 5 8:59:45 2003 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 3CF8F37B401 for ; Wed, 5 Mar 2003 08:59:44 -0800 (PST) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9938243FE0 for ; Wed, 5 Mar 2003 08:59:43 -0800 (PST) (envelope-from wa1ter@myrealbox.com) Received: from myrealbox.com wa1ter@smtp-send.myrealbox.com [67.114.254.145] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.32 $ on Novell NetWare via secured & encrypted transport (TLS); Wed, 05 Mar 2003 09:59:46 -0700 Message-ID: <3E662D12.4080703@myrealbox.com> Date: Wed, 05 Mar 2003 09:00:02 -0800 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030213 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Another nVidia question, maybe a bit OT. Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Because of the repeated breakage of the proprietary nVidia driver in -CURRENT I've been trying out the native XFree86 'nv' driver with some puzzling results. Maybe one of the nVidia whiz-kids in this group can explain: I reboot the machine, then start the X server. The X server immediately aborts with an unresolved symbol vgaHWUnmapMem in nv_drv.o. Okay, so I forgot to load some module in my XF86Config, right? Wrong. All I need to do to is to start X a *second* time and the unresolved symbol error goes away like magic and X starts up. It took me a good while to discover that :-( How the hell does an unresolved symbol get resolved just by retyping the same command? My thought was to look for some kernel module that got loaded in the background, but no. Same kernel modules before and after. And the problem reappears after the next reboot. Any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message