On Mon, Jan 25, 2010 at 10:38:47AM -0600, Kevin Kinsey wrote: > Anton Shterenlikht wrote: > > This is on FreeBSD 9.0-CURRENT #0 r202964M ia64 > > > > I've built a kernel with smbfs module: > > > > # ls -al /boot/kernel/smb* > > -r-xr-xr-x 1 root wheel 265579 25 Jan 13:36 /boot/kernel/smbfs.ko > > -r-xr-xr-x 1 root wheel 680186 25 Jan 13:36 /boot/kernel/smbfs.ko.symbols > > > > but can't load it: > > > > # kldload smbfs > > kldload: can't load smbfs: No such file or directory > > > > > > Other modules load fine with kldload, e.g.: > > Does it make any difference to use the ".ko" extension, to > call it by absolute path, or to use "-v" for more information, > per The Friendly Manual?
no, doesn't make any difference: # kldload -v /boot/kernel/smbfs.ko kldload: can't load /boot/kernel/smbfs.ko: No such file or directory # but I see in /var/log/messages: kernel: KLD smbfs.ko: depends on libiconv - not available or version mismatch I've rebuilt world, rebuilt and reinstalled kernel, installed world, and merged, etc., including rm -rf /usr/obj/* , so there shouldn't be any version mismatch. Is there a way to debug this further? > Also, for curiosity, `file /boot/kernel/smbfs.ko`? seems to be the same as other modules: # file /boot/kernel/smbfs.ko /boot/kernel/smbfs.ko: ELF 64-bit LSB shared object, IA-64, version 1 (FreeBSD), dynamically linked, not stripped # file /boot/kernel/geom_mirror.ko /boot/kernel/geom_mirror.ko: ELF 64-bit LSB shared object, IA-64, version 1 (FreeBSD), dynamically linked, not stripped # many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"