From owner-freebsd-current Tue Apr 24 18:32:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id F012037B423 for ; Tue, 24 Apr 2001 18:32:12 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA01900; Tue, 24 Apr 2001 21:31:59 -0400 (EDT) (envelope-from wollman) Date: Tue, 24 Apr 2001 21:31:59 -0400 (EDT) From: Garrett Wollman Message-Id: <200104250131.VAA01900@khavrinen.lcs.mit.edu> To: Dima Dorfman Cc: freebsd-current@FreeBSD.ORG Subject: Re: Boot messages In-Reply-To: <20010424231959.933A63E2B@bazooka.unixfreak.org> References: <20010424231959.933A63E2B@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > This is not a bug. This is an FAQ. So much that it's actually > documented in (*gasp!*) the FAQ: Unfortunately, the A in the FAQ is wrong. The ``can't assign resources'' messages indicate that the devices are legacy ISA devices for which a non-PnP-aware driver is compiled into the kernel. These include devices such as keyboard controllers, the programmable interrupt controller chip, and several other bits of standard infrastructure. The resources can't be assigned because there is already a driver using those addresses. If it didn't say ``can't assign resources'', then *and only then* is the device in question not configured in the kernel. AIUI such messages are currently disabled unless one boots in verbose mode. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message