From owner-freebsd-current@FreeBSD.ORG Tue Aug 10 02:56:06 2004 Return-Path: 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 2DB5E16A4CE for ; Tue, 10 Aug 2004 02:56:06 +0000 (GMT) Received: from axe-inc.co.jp (axegw.axe-inc.co.jp [61.199.217.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 685DD43D1D for ; Tue, 10 Aug 2004 02:56:05 +0000 (GMT) (envelope-from takawata@axe-inc.co.jp) Received: from localhost (localhost [127.0.0.1]) by axe-inc.co.jp (8.9.3+3.2W/3.7W) with SMTP id LAA13722; Tue, 10 Aug 2004 11:55:59 +0900 (JST) Message-Id: <200408100255.LAA13722@axe-inc.co.jp> X-Authentication-Warning: axegw.axe-inc.co.jp: localhost [127.0.0.1] didn't use HELO protocol To: martin.mato@wanadoo.fr From: takawata@jp.freebsd.org In-reply-to: Your message of "Tue, 10 Aug 2004 04:43:46 +0200." <41183662.4010802@wanadoo.fr> Date: Tue, 10 Aug 2004 11:55:59 +0900 Sender: takawata@axe-inc.co.jp cc: freebsd-current@freebsd.org Subject: Re: ACPI autoload failed: no such file or directory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 10 Aug 2004 02:56:06 -0000 In message <41183662.4010802@wanadoo.fr>, Martin MATO wrote: >since several days; i ' got this message before the kernel load (not >easy to see that, is not include in the logs) > >ACPI autoload failed: no such file or directory > >after the boot process, i logged in and try this command > >#kldload acpi.ko >kldload: can't load usb.ko: No such file or directory > >#kldload /boot/kernel/acpi.ko >in this case the system try to load the module and, of course, it can't. You cannot load acpi.ko from userland. >- the acpi.ko file is present in /boot/kernel >- i didn't changed anything , except a fresh kernel build >- kldload works with other modules in this directory. > > >anyone could explain this.. strange thing? Hmm, how about trying to escape to boot loader prompt and load acpi module manually ?