Date: Tue, 24 Apr 2001 21:31:59 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Dima Dorfman <dima@unixfreak.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Boot messages Message-ID: <200104250131.VAA01900@khavrinen.lcs.mit.edu> In-Reply-To: <20010424231959.933A63E2B@bazooka.unixfreak.org> References: <XFMail.010425002716.riccardo@torrini.org> <20010424231959.933A63E2B@bazooka.unixfreak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Tue, 24 Apr 2001 16:19:59 -0700, Dima Dorfman <dima@unixfreak.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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104250131.VAA01900>