Date: Thu, 29 May 1997 16:40:28 -0700 (PDT) From: Tom Samplonius <tom@sdf.com> To: pvl@nanoteq.com Cc: FreeBSD-hackers <freebsd-hackers@FreeBSD.ORG> Subject: Re: ed0 : device timeout Message-ID: <Pine.BSF.3.95q.970529163816.11036B-100000@misery.sdf.com> In-Reply-To: <199705291506.RAA01207@oskar.nanoteq.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 May 1997, Pierre Van Leeuwen wrote: > Hi > > I wrote to questions about this earlier, but that didn't solve my > problem. > > I get the following message : > ed0 : device timeout > > It doesn't seem to be fatal all the time though. > > Looking at if_ed.c I see it is because the device doesn't > generate an interrupt after a transmit was started. > I commented the line out that checks for the interrupt, > and had the function return without doing anything. Didn't > do any good as expected. > > It's a D-Link De-220 card which I have exchanged about three > times, as well as putting a new motherboard in. The > only thing I haven't changed is the cpu (Pentium 133). > I've been running FreeBSD on it since 2.1.5 and I have > 2.2-Stable on it at the moment (CVSupped about a week ago -- > I tried to CVSup today, but today the ed0 error is fatal :) ) The D-Link 220 is not really NE-2000 compatible. I have many of these cards around here, and some revs just cause all kinds of problems, when using the ed driver. > What else should I try? Try something other than a DE-220 > pierre > -- > Pierre_Andre van Leeuwen > Electronic Engineer > -------------------------------------------------------------- > | E-mail : pvl@nanoteq.com | Nanoteq (Pty) Ltd. | > | Ph : +27 (0)12 665-1338 | Specialists in data security | > -------------------------------------------------------------- > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970529163816.11036B-100000>