From owner-freebsd-current@FreeBSD.ORG  Wed Nov 17 18:11:15 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 2FE9116A4CE
	for <current@freebsd.org>; Wed, 17 Nov 2004 18:11:15 +0000 (GMT)
Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 17EAB43D41
	for <current@freebsd.org>; Wed, 17 Nov 2004 18:11:15 +0000 (GMT)
	(envelope-from mhunter@ack.Berkeley.EDU)
Received: (from mhunter@localhost)
	by ack.Berkeley.EDU (8.11.3/8.11.3) id iAHIB8K24666;
	Wed, 17 Nov 2004 10:11:08 -0800 (PST)
Date: Wed, 17 Nov 2004 10:11:08 -0800
From: Mike Hunter <mhunter@ack.Berkeley.EDU>
To: Tillman Hodgson <tillman@seekingfire.com>
Message-ID: <20041117181108.GA24426@ack.Berkeley.EDU>
References: <20041117180157.GO76234@seekingfire.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041117180157.GO76234@seekingfire.com>
User-Agent: Mutt/1.5.6i
cc: FreeBSD -CURRENT <current@freebsd.org>
Subject: 
	Re: `kldload` doesn't find pf.ko, though `ls` finds it easily enough
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Nov 2004 18:11:15 -0000

On Nov 17, "Tillman Hodgson" wrote:

Check dmesg.  There's a bug somewhere that causes kldload to report "file 
not found" to the user even though it was some other error that caused the
problem.  That real error can sometimes be spit out to the console /
syslog / whatever.

> SYNOPSIS:
> 
> kldload doesn't seem to be able to find the pf module in spite of it
> being it the normal place.
> 
> DETAILS:
> 
> root@thoth# kldstat
> Id Refs Address    Size     Name
>  1    3 0xc0400000 441524   kernel
>  2    1 0xc17f3000 3000     daemon_saver.ko
> 
> root@thoth# ls -l /boot/kernel/pf.ko
> -r-xr-xr-x  1 root  wheel  170068 Nov  9 19:12 /boot/kernel/pf.ko
> 
> root@thoth# kldload -v pf
> kldload: can't load pf: No such file or directory
> 
> root@thoth# kldload -v /boot/kernel/pf.ko
> kldload: can't load /boot/kernel/pf.ko: No such file or directory
> 
> root@thoth# sysctl kern.bootfile kern.module_path
> kern.bootfile: /boot/kernel/kernel
> 
> root@thoth# uname -a
> FreeBSD thoth.seekingfire.prv 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Tue Nov  9 17:44:22 CST 2004
> toor@thoth.seekingfire.com:/usr/obj/usr/src/sys/THOTH  i386