From owner-freebsd-questions Mon Dec 21 14:02:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01231 for freebsd-questions-outgoing; Mon, 21 Dec 1998 14:02:52 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01214 for ; Mon, 21 Dec 1998 14:02:44 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id RAA28724; Mon, 21 Dec 1998 17:01:10 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id RAA25959; Mon, 21 Dec 1998 17:47:41 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id RAA16590; Mon, 21 Dec 1998 17:01:38 -0500 (EST) Date: Mon, 21 Dec 1998 17:01:38 -0500 (EST) From: Thomas David Rivers Message-Id: <199812212201.RAA16590@lakes.dignus.com> To: 3dshooter@eudoramail.com, dwhite@resnet.uoregon.edu Subject: Re: question Cc: FAQ@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Sun, 20 Dec 1998, Vladimir wrote: > > > Hi, there guys! First I wonna thank you for what you are doing! That's > > great & really helpfull! > > You're welcome! > > > But I got a problem that's not covered in your FAQs. So I decided to > > write you (hoping smb will read it :-). > > > I'm trying to put FreeBSD on my 386 DX40(4mb) & connect it via > > NE1000compat. to my Pentium133(24mb). I built a new kernel for Pent, > > compiled it & it worked. But when I built a new kernel for 386 & > > installed it my comp (386) hanged up after a string: npx0 at 0xf0-0xff > > irq 13 flags 0x1 on motherboard. > > First of all, what version of FreeBSD are you trying to install? > > Secondly, I generally see this problem if you disable the system console > sc0 in the boot-time configuration. The 'conflicts' note is bogus -- it > should conflict with psm0 since they use the same controller chip. Newer > versions of FreeBSD don't complain about this. > > The test for this is to skip configuring devices -- if it works then don't > touch sc0. :-) Just to add to Doug's response. I also see this with the generic 3.0-RELEASE kernel. I had to disable probes until I got the boot to succeed. This was on all of my machines running 3.0-RELEASE (two older 486's and a P-233) I disabled every ethernet device (during boot) and got everything to go. Then; after I got a system running, I remade kernels with only the devices I care about, and the problem went away. I should do a binary search to determine exactly which probe seems to lock up the machines - but one of them surely does (again, with 3.0-RELEASE) if the hardware you're probing for isn't there. [I waited for 30 minutes just to make sure it wasn't a time-out problem.] - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message