From owner-freebsd-current Fri Sep 14 12:44:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 9C67E37B410 for ; Fri, 14 Sep 2001 12:44:24 -0700 (PDT) Received: from notebook.vega.com (dialup12-40.iptelecom.net.ua [212.9.228.232]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id WAA66218; Fri, 14 Sep 2001 22:43:59 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Date: Fri, 14 Sep 2001 22:43:59 +0300 (EEST) Message-Id: <200109141943.WAA66218@ipcard.iptcom.net> To: dwmalone@maths.tcd.ie, current@FreeBSD.org From: Maxim Sobolev Subject: Re: ACPI module loading. X-Mailer: Pygmy (v0.5.11) In-Reply-To: <200109142010.aa54118@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 14 Sep 2001 20:10:13 +0100, David Malone wrote: > If you boot from an old kernel then the loader seems to load the acpi > module from the wrong place. I tried booting with both: > > unload > boot /boot/kernel.old/kernel > and: > unload > load /boot/kernel.old/kernel > boot > > and both loaded the acpi moduse from /boot/kernel/acpi.ko. I thought > that the loader was supposed to be clever enough to find these > things. I suppose it could be the acpi loader, the loader or me > which is broked. The following is a correct way of doing this: unload boot kernel.old This will load both kernel and modules from the correct place, i.e. /boot/kernel.old. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message