Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Dec 1998 17:01:38 -0500 (EST)
From:      Thomas David Rivers <rivers@dignus.com>
To:        3dshooter@eudoramail.com, dwhite@resnet.uoregon.edu
Cc:        FAQ@FreeBSD.ORG
Subject:   Re: question
Message-ID:  <199812212201.RAA16590@lakes.dignus.com>
In-Reply-To: <Pine.BSF.4.03.9812211322290.5809-100000@resnet.uoregon.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812212201.RAA16590>