From owner-freebsd-bugs Sun Feb 13 16:19: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 60EEB3E1D for ; Sun, 13 Feb 2000 16:19:51 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id QAA22231; Sun, 13 Feb 2000 16:20:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sun, 13 Feb 2000 16:20:02 -0800 (PST) Message-Id: <200002140020.QAA22231@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Jin Guojun (FTG staff) Subject: Re: i386/16620: 4.0-20000208-CURRENT fails to boot on ASUS P5A-B Reply-To: Jin Guojun (FTG staff) 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: Jin Guojun (FTG staff) To: winter@jurai.net 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 16:03:57 -0800 (PST) } > 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. 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? -Jin % more /sys/i386/conf/New ... # ISA Ethernet NICs. device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 device ex device ep # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. device an # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device fe0 at isa? port 0x300 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message