From owner-freebsd-questions  Mon Nov 11 15:24:34 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA19477
          for questions-outgoing; Mon, 11 Nov 1996 15:24:34 -0800 (PST)
Received: from mail.gte.net (sm1.gte.net [207.175.111.18])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA19461
          for <questions@FreeBSD.ORG>; Mon, 11 Nov 1996 15:24:25 -0800 (PST)
Received: from mail1.gte.net (mail1.gte.net [206.124.65.236]) by mail.gte.net (950413.SGI.8.6.12/950213.SGI.AutoCF) via ESMTP id RAA24880; Mon, 11 Nov 1996 17:24:17 -0600
Received: from gemini.gouverneur.com by mail1.gte.net (SMI-8.6/SMI-SVR4)
	id RAA09799; Mon, 11 Nov 1996 17:24:14 -0600
Message-ID: <3287B50E.41C67EA6@mail.gte.net>
Date: Mon, 11 Nov 1996 15:21:50 -0800
From: Fred Adorno <fadorno@mail.gte.net>
Organization: Adorno and Associates
X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386)
MIME-Version: 1.0
To: Nick Liu <nickliu@value.net>
CC: Just Baldrick <baldrick@rmsq.com>, fadorno@mail.gte.net,
        questions@FreeBSD.ORG
Subject: Re: ed0 device timeout
References: <Pine.BSI.3.95.961111113410.12021A-100000@value.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Nick Liu wrote:
> 
>  On Mon, 11 Nov 1996, Just Baldrick wrote:
> 
> > Hi,
> >
> > We had the same problem with ed0 'Device timeout'.  In our
> > case it was because the ethernet card was set to a
> > different IRQ than the FreeBSD IRQ.
> > Also, it could be due to an IRQ conflict, eg a SoundBlaster
> > trying to use the same interrupt.
> >
> >
> > Hope this helps.
> >
> >
> 
> Another thing you could try is to take out the on board address specified
> in your kernel config file and then recompile the kernel.
> 
> Good luck.

I am aware of all the above.  I used the softlink setup thru EZsetup.  I 
changed the settings to match the kernel.  It has been working fine
until I went into Windows yesterday after a warm boot.  Went I went back
to FreeBSD after a warm boot the timeout errors appeared again.  It
seems to go away if I do a cold boot and then go into FreeBSD. 
Apparently, what ever the conflict is during Windows stays in memory if
I do a warm boot.  I can't seem to resolve the problem under Windows
now, but I don't care because I plan to drop that hard drive (primary)
into another PC and network it with FreeBSD server.  But on that note
has any one setup to network between a Win95 desktop and a FreeBSD box? 
Was it difficult?  What do I need to do to make them work?