From owner-freebsd-questions  Thu Jul  3 19:18:40 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA04114
          for questions-outgoing; Thu, 3 Jul 1997 19:18:40 -0700 (PDT)
Received: from pscwa.psca.com (romulus.pscwa.psca.com [199.99.162.3])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA04105
          for <freebsd-install@freebsd.org>; Thu, 3 Jul 1997 19:18:36 -0700 (PDT)
Received: from vulcan by pscwa.psca.com (NX5.67f2/NX3.0M, PSCWA update 950701)
	id AA24914; Thu, 3 Jul 97 19:18:29 -0700
Message-Id: <9707040218.AA24914@pscwa.psca.com>
Received: by vulcan.pscwa.psca.com (NX5.67g/NX3.0X)
	id AA01367; Thu, 3 Jul 97 19:18:27 -0700
Content-Type: text/plain
Mime-Version: 1.0 (NeXT Mail 4.1mach v148)
In-Reply-To: <199707030636.XAA07817@implode.root.com>
X-Nextstep-Mailer: Mail 4.1mach (Enhance 2.0b5)
Received: by NeXT.Mailer (1.148)
From: Manu Iyengar <iyengar@pscwa.psca.com>
Date: Thu,  3 Jul 97 19:18:24 -0700
To: dg@root.com
Subject: Re: Trouble with NICs while installing 3.0-970618-SNAP via FTP 
Cc: freebsd-install@freebsd.org
Reply-To: m@pscwa.psca.com
References: <199707030636.XAA07817@implode.root.com>
X-Wired: FreeBSD
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hmm, that is what it turned out to be. I had to give up my second serial  
port to make all the IRQs work properly. The sound card was innocent. Thanks!

Two things about the install:
1) The bootstrap loader says the wrong thing for -cv? It says 'v' is for  
config and 'c' is for verbose output.
2) Why does the install program clear the second vty when it comes up? Being  
able to scroll up to catch the kernel boot messages is handy when  
troubleshooting.

Thanks for your help! It's *way* cool to be able to install over the net.  
FreeBSD rocks.

-mi



>From the keyboard of David Greenman on Wed, 02 Jul 1997:
> >de0: transmission timeout
> >
> >Ditto with fxp0 (device timeout), but ex0 is silent. All three cards
> >appear to see traffic (from the activity LEDs) at all times.
>
> The above indicates an interrupt conflict of some kind - for whatever
> reason, the system isn't seeing the interrupts from the card(s). This could
> be caused by BIOS misconfiguration for the interrupt sources (specifically,
> which interrupts are assigned to ISA devices). You might wish to check this
> and perhaps also pull out your sound card.
>
> -DG
>
> David Greenman
> Core-team/Principal Architect, The FreeBSD Project