From owner-freebsd-bugs Sun Feb 13 15:29:57 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 959593D8E for ; Sun, 13 Feb 2000 15:29:52 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id PAA20000; Sun, 13 Feb 2000 15:30:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sun, 13 Feb 2000 15:30:03 -0800 (PST) Message-Id: <200002132330.PAA20000@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 18:27:56 -0500 (EST) On Sun, 13 Feb 2000, Jin Guojun wrote: > It obviously is the wrong configuration on the installation floppies, > because after I installed 4.0-20000208-CURRENT by moving 3c509 to port 0x310, > and rebuild the kernel as > > device ep > > and moved the 3C509 back to port 0x300, the new kernel is happy with it > and boots up without any problem. Ok, thats weird. Did you disable all devices in the visual config screen that are set to probe 0x300? Realistically you should be disabling all devices that you know you don't have. -- | 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