From owner-freebsd-current@FreeBSD.ORG Mon Aug 4 21:12:07 2003 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 00B9F37B401 for ; Mon, 4 Aug 2003 21:12:07 -0700 (PDT) Received: from remt19.cluster1.charter.net (remt19.cluster1.charter.net [209.225.8.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0718E43FAF for ; Mon, 4 Aug 2003 21:12:06 -0700 (PDT) (envelope-from glennpj@charter.net) Received: from [24.158.214.251] (HELO gforce.johnson.home) by remt19.cluster1.charter.net (CommuniGate Pro SMTP 4.0.6) with ESMTP id 112824031; Tue, 05 Aug 2003 00:12:01 -0400 Received: from gforce.johnson.home (localhost [127.0.0.1]) by gforce.johnson.home (8.12.9/8.12.9) with ESMTP id h754BxRv000940; Mon, 4 Aug 2003 23:11:59 -0500 (CDT) (envelope-from glenn@gforce.johnson.home) Received: (from glenn@localhost) by gforce.johnson.home (8.12.9/8.12.9/Submit) id h754Bxia000939; Mon, 4 Aug 2003 23:11:59 -0500 (CDT) (envelope-from glenn) Date: Mon, 4 Aug 2003 23:11:59 -0500 From: Glenn Johnson To: "Alastair G. Hogge" Message-ID: <20030805041159.GA898@gforce.johnson.home> Mail-Followup-To: "Alastair G. Hogge" , FreeBSD current users References: <20030804044856.GA1904@gforce.johnson.home> <20030805030717.GA6732@gforce.johnson.home> <200308051328.58317.agh@tpg.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200308051328.58317.agh@tpg.com.au> User-Agent: Mutt/1.5.4i X-Spam-Status: No, hits=-5.0 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: FreeBSD current users Subject: Re: problem with nvidia graphics card and -current 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: Tue, 05 Aug 2003 04:12:07 -0000 On Tue, Aug 05, 2003 at 01:28:58PM +1000, Alastair G. Hogge wrote: > On Tuesday, 05 August 2003 13:07, Glenn Johnson wrote: > > > On Sun, Aug 03, 2003 at 11:48:56PM -0500, wrote: > > > > > I was setting up a system today with an nvidia Geforce4-MX 440 > > > graphics card. I am not at the system at the moment but the > > > -current sources were from about 2:00 PM CDT. I installed the > > > nvidia-driver port (1.0.4365) trying various combinations of > > > WITH_FREEBSD_AGP, FORCE_AGP_RATE, and WITH_NVIDIA_HACKS. I > > > get the same result. The first time an X server is started, > > > everything works fine, including glx loading. After exiting the X > > > session and shutting down the server and then at some point later > > > starting the X server again, the system will freeze. No messages, > > > no panic, nothing. The only thing to do is hit the reset button. > > > > I played with this a bit more tonight. I rebuilt the kernel (fresh > > cvsup) and the nvidia-driver bits. I even tried loading without > > glx. I still have the same problem. At this point I do not know > > if this is a problem with the nvidia-driver port, a problem with > > -current, or something I am doing wrong. Does anybody have a > > functioning nvidia card with FreeBSD -current at this time? > > Yes I do. > > I posted to the list a few days with a glx problem. However the > problem was solved when I did an update one day ago. I didn't have to > changed anything either. I didn't know what was wrong for some reason > X would about with sig 10 or 11 when the glx module was loaded. Well, after much hair pulling and trying various troubleshooting steps I had one last idea. I had the vesa kernel module loaded and thought "maybe that is causing the hangup." I disabled the loading of the vesa kernel module in /boot/loader.conf and rebooted. Sure enough, everything worked. I now have the nvidia card working and can proceed with the rest of the setup for this machine. Thanks for your reply stating that it works for you. It gave me the incentive to try "one more time". Question for the developers: Is there someway to avoid having the combination of vesa and nvidia cause a total lockup of the machine? I have a feeling I may not be the last person to try the nvidia driver with vesa enabled, either as a module, or compiled in the kernel. Thanks. -- Glenn Johnson glennpj@charter.net