From owner-freebsd-bugs Sun Feb 13 18:39:53 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by builder.freebsd.org (Postfix) with ESMTP id CA0F54935 for ; Sun, 13 Feb 2000 18:39:51 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id SAA30546; Sun, 13 Feb 2000 18:40:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sun, 13 Feb 2000 18:40:03 -0800 (PST) Message-Id: <200002140240.SAA30546@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Matthew N. Dodd" Subject: Re: i386/16620: 4.0-20000208-CURRENT fails to boot on ASUS P5A-B Reply-To: "Matthew N. Dodd" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR i386/16620; it has been noted by GNATS. From: "Matthew N. Dodd" To: Jin Guojun Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: i386/16620: 4.0-20000208-CURRENT fails to boot on ASUS P5A-B Date: Sun, 13 Feb 2000 21:36:33 -0500 (EST) On Sun, 13 Feb 2000, Jin Guojun wrote: > Nop. It could be any one of the following ISA driver with port 0x300 > since device "ep" no longer has no dependent description -- > at isa? port 0x300 irq 10 > in its line, so the other devices may be confused. Is there any way > to resolve this problem without disable all such ISA driver? Disabling the other drivers is the correct solution. I believe the INSTALL procedure makes specific mention of this. The final solution will be to convert everything to newbus and to make resource reservation, assignment and activation more friendly. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message