From owner-freebsd-current@FreeBSD.ORG Thu Jan 28 12:44:10 2010 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 BCD041065672 for ; Thu, 28 Jan 2010 12:44:10 +0000 (UTC) (envelope-from giovanni.trematerra@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 4FF8D8FC1B for ; Thu, 28 Jan 2010 12:44:09 +0000 (UTC) Received: by fxm27 with SMTP id 27so132312fxm.3 for ; Thu, 28 Jan 2010 04:44:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=sWj2brLXatRuCw7fQQY1B5Hw8/NT16UDtv2LMFfs4LI=; b=jdHYFL1VLfq0ImJ2xoqlvlmRlZS0LZZZlqjeIlmnhk0JD8+kWl/Rhlyo4BshAK515s U5ogxTipwhS03mCxUtOpKywHgzoSA7VrQfZWbglrVWc8+9bsm0t7qN2AxKo3PORsuYCR 3bxNS8JtpARr5Dcx/DKcYl424qoTmUhMZJfek= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=tQsk9xXZbzaQ8+TnfnwEd8SXSM4mM1hp/h7qyMQENwOwAy8Iqf49Bett8AAz+l43bE C/aDuwBmftjutLjOYwh8mjoTXXKuz1Z6rkZNV5ZVOSwCKBChMVUcBE20zkDmPru8LTF8 rXgZet+t3YscHZvJ0jfBoEAyJgVGbJf5ntzRM= MIME-Version: 1.0 Received: by 10.223.58.198 with SMTP id i6mr2767674fah.28.1264682648822; Thu, 28 Jan 2010 04:44:08 -0800 (PST) In-Reply-To: <20100126232707.GG26462@mech-cluster241.men.bris.ac.uk> References: <20100126232707.GG26462@mech-cluster241.men.bris.ac.uk> Date: Thu, 28 Jan 2010 13:44:08 +0100 Message-ID: <4e6cba831001280444g12ba21b3hcc51c8180f08b3c3@mail.gmail.com> From: Giovanni Trematerra To: Anton Shterenlikht Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: can't load smbfs kernel module 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: Thu, 28 Jan 2010 12:44:10 -0000 On Wed, Jan 27, 2010 at 12:27 AM, Anton Shterenlikht wrote: > I didn't get any luck asking in questions@, > so maybe this is a current@ 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 =A01 root =A0wheel =A0265579 25 Jan 13:36 /boot/kernel/sm= bfs.ko >> > > -r-xr-xr-x =A01 root =A0wheel =A0680186 25 Jan 13:36 /boot/kernel/sm= bfs.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: >> >> =A0kernel: 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