Re: can't load smbfs kernel module

On Wed, Jan 27, 2010 at 12:27 AM, Anton Shterenlikht
<mexas_at_bristol.ac.uk> wrote:
> I didn't get any luck asking in questions_at_,
> so maybe this is a current_at_ issue:
>
>
> On Mon, Jan 25, 2010 at 09:56:54PM +0000, Anton Shterenlikht wrote:
>> 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
>>

If you have all modules compiled do:
#kldload libiconv
#kldload libmchain
#kldload smbfs

otherwise you have to include/compile such modules

Have fun!

--
Gianni