From owner-freebsd-bugs Mon Mar 18 15:40: 8 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6D89437B400 for ; Mon, 18 Mar 2002 15:40:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2INe3777575; Mon, 18 Mar 2002 15:40:03 -0800 (PST) (envelope-from gnats) Date: Mon, 18 Mar 2002 15:40:03 -0800 (PST) Message-Id: <200203182340.g2INe3777575@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: George Mitchell Subject: Re: misc/35350: Can't boot on ASUS TXP Reply-To: George Mitchell Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR misc/35350; it has been noted by GNATS. From: George Mitchell To: freebsd-gnats-submit@freebsd.org Cc: Subject: Re: misc/35350: Can't boot on ASUS TXP Date: Mon, 18 Mar 2002 15:30:33 -0800 (PST) I tried a different motherboard (FIC VA-503+) (which works fine in other machines on my network) and the problem did not go away. I finally isolated it to my generic NE2000 network card. Apparently the "ex" driver hangs up the machine when the NE2000 is there. Everything is fine without the NE2000. But now I'm finding that the "sym" driver believes my NCR SCSI card is defective, although it too has been running just fine under 3.4 for more than two years. I built a kernel with the "ncr" driver and without the "sym" driver and got an endless loop of error messages. Any suggestions? -- George Mitchell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message