From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 21:04:48 2008 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 58F7A1065679 for ; Sat, 5 Jul 2008 21:04:48 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 310AE8FC0C for ; Sat, 5 Jul 2008 21:04:48 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id A61B346C48; Sat, 5 Jul 2008 17:04:47 -0400 (EDT) Date: Sat, 5 Jul 2008 22:04:47 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Chuck Robey In-Reply-To: <486FD2BA.8050505@telenix.org> Message-ID: <20080705220254.I51796@fledge.watson.org> References: <486FD2BA.8050505@telenix.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: kernel modules wont load 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: Sat, 05 Jul 2008 21:04:48 -0000 On Sat, 5 Jul 2008, Chuck Robey wrote: > I can't get my oss sound to load, and the first error I get is this: > > osscore.ko: depends on kernel - not available > > That came from both the oss logging file and dmesg. I don't understand what > "depends on kernel" means, could I get a hint on that? I think it's the > reason that later oss modules don't load correctly. > > Thanks for any help on this, I'd like to get my sound working again. In HEAD, we're currently building all modules with an automatic version dependency on the version of the kernel they are intended to run in. The error message should be telling you need version X but it found version Y, but doesn't, unfortunately. Rebuilding the module should get it working. I seem to recall printing the error better is awkward because the dependency failure is generated somewhere deep in the linker, and the error is printed on the surface, but should be fixable. Robert N M Watson Computer Laboratory University of Cambridge