From owner-freebsd-questions@FreeBSD.ORG Mon Dec 20 05:41:01 2004 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 7365F16A4CE for ; Mon, 20 Dec 2004 05:41:01 +0000 (GMT) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id B788143D49 for ; Mon, 20 Dec 2004 05:41:00 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from [69.27.131.0] ([69.27.131.0]) by ns1.tiadon.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 19 Dec 2004 23:42:25 -0600 Message-ID: <41C665EB.9000901@daleco.biz> Date: Sun, 19 Dec 2004 23:40:59 -0600 From: Kevin Kinsey User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel O'Connor References: <200412201033.48519.doconnor@gsoft.com.au> <200412201254.11797.doconnor@gsoft.com.au> In-Reply-To: <200412201254.11797.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Dec 2004 05:42:29.0109 (UTC) FILETIME=[B166B250:01C4E656] cc: admin2@forkthepenguin.com cc: ctodd@chrismiller.com cc: freebsd-questions@freebsd.org Subject: Re: 5.3 Release and Realtek 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: Mon, 20 Dec 2004 05:41:01 -0000 This is questions@ fodder, isn't it? Daniel O'Connor wrote: >On Mon, 20 Dec 2004 12:44, ctodd@chrismiller.com wrote: > > >>The problem was that none of the snd_* modules were built, and I did >>rebuild the kernel. Once I built the modules, I was able to load the >>drivers. I think you need to add "device sound" to get these modules to >>build automgically. >> >> > >No, the modules are built regardless of the kernel options you use. > > > Hmm; how did ctodd know they weren't? I had one box that seemed weird in that it couldn't kldload anything; I somehow discovered that it had left /boot/kernel/ empty, but put all the *ko's in /boot/modules/ (or was it the other way 'round??) ... Anyway, once I copied everything over to the other dir, no problems with "kldload" (or sound, or ....) Could this be what happened in this case? Kevin Kinsey