Date: Mon, 11 Nov 1996 15:21:50 -0800 From: Fred Adorno <fadorno@mail.gte.net> To: Nick Liu <nickliu@value.net> Cc: Just Baldrick <baldrick@rmsq.com>, fadorno@mail.gte.net, questions@FreeBSD.ORG Subject: Re: ed0 device timeout Message-ID: <3287B50E.41C67EA6@mail.gte.net> References: <Pine.BSI.3.95.961111113410.12021A-100000@value.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3287B50E.41C67EA6>