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_at_thoth# kldstat > Id Refs Address Size Name > 1 3 0xc0400000 441524 kernel > 2 1 0xc17f3000 3000 daemon_saver.ko > > root_at_thoth# ls -l /boot/kernel/pf.ko > -r-xr-xr-x 1 root wheel 170068 Nov 9 19:12 /boot/kernel/pf.ko > > root_at_thoth# kldload -v pf > kldload: can't load pf: No such file or directory > > root_at_thoth# kldload -v /boot/kernel/pf.ko > kldload: can't load /boot/kernel/pf.ko: No such file or directory > > root_at_thoth# sysctl kern.bootfile kern.module_path > kern.bootfile: /boot/kernel/kernel > > root_at_thoth# uname -a > FreeBSD thoth.seekingfire.prv 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Tue Nov 9 17:44:22 CST 2004 > toor_at_thoth.seekingfire.com:/usr/obj/usr/src/sys/THOTH i386Received on Wed Nov 17 2004 - 17:11:15 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:22 UTC