From owner-freebsd-questions@FreeBSD.ORG Tue Aug 5 10:39:27 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D84A637B401 for ; Tue, 5 Aug 2003 10:39:27 -0700 (PDT) Received: from sedcsb9.nrl.navy.mil (sedcsb9.nrl.navy.mil [132.250.138.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A43443F3F for ; Tue, 5 Aug 2003 10:39:27 -0700 (PDT) (envelope-from machine@sedcsb9.nrl.navy.mil) Received: from sedcsb9.nrl.navy.mil (localhost.nrl.navy.mil [127.0.0.1]) h75Hdq1R000406; Tue, 5 Aug 2003 13:39:52 -0400 (EDT) (envelope-from machine@sedcsb9.nrl.navy.mil) Received: from localhost (localhost [[UNIX: localhost]]) by sedcsb9.nrl.navy.mil (8.12.8p1/8.12.8/Submit) id h75HdqVP000405; Tue, 5 Aug 2003 13:39:52 -0400 (EDT) From: Carl Glen Henshaw Organization: U.S. Naval Research Laboratory To: lreid@okstate.edu Date: Tue, 5 Aug 2003 13:39:51 -0400 User-Agent: KMail/1.5.2 References: <522433577.1060038127017.JavaMail.root@dexter.okstate.edu> In-Reply-To: <522433577.1060038127017.JavaMail.root@dexter.okstate.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200308051339.51970.ghenshaw@space.nrl.navy.mil> cc: freebsd-questions@freebsd.org Subject: Re: dri falling back to software in 4.8-stable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2003 17:39:28 -0000 On Monday 04 August 2003 07:02 pm, lreid@okstate.edu wrote: > [CC'd for anyone who may need this resolution] > > Hi Carl, > Yes, I actually did determine the resolution to the problem. Since I had > been running the system since 4.7-release, I used the drm-kmod package in > the ports tree to get the DRI support. An undocumented (as far as I can > tell) change from 4.7-stable to 4.8-stable includes the drm kernel module > in the kernel module sources, and the drm-kmod port is depricated. If you > remove the drm-kmod startup script from /usr/local/etc/rc.d, optionaly > pkg_delete the drm-kmod package, and rebuild your kernel with options drm > and agp added, you should have hardware support upon loading the new > kernel. I've browsed through the UPDATING file from my last source update > and I've found no mention of this change between 4.7-release and > 4.8-release. Does anyone know why? (my being dense is a perfectly valid > reason) I also discovered that you must install the -stable sources *from cvs*, and then make the /usr/src/sys/modules/drm directory in order for drm to show up as a kernel module. It's not there in the default binary install, and installing the sources via /stand/sysinstall doesn't do it either. Odd. In any case, it works now. Thanks for the help. Glen ____________________________________________________________ Dr. Glen Henshaw (202) 767-1196 Naval Center for Space Technology ghenshaw@space.nrl.navy.mil U.S. Naval Research Laboratory