From owner-freebsd-questions Fri Jan 27 13:03:06 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA27431 for questions-outgoing; Fri, 27 Jan 1995 13:03:06 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA27422 for ; Fri, 27 Jan 1995 13:02:51 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id MAA04019; Fri, 27 Jan 1995 12:36:17 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id MAA00898; Fri, 27 Jan 1995 12:36:16 -0800 Message-Id: <199501272036.MAA00898@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: tucker@mdso.vf.ge.com cc: questions@FreeBSD.org Subject: Re: Linksys Ether16 NE2000 card problems In-reply-to: Your message of "Fri, 27 Jan 95 10:37:35 EST." <9501271537.AA09172@sde832.mdso.vf.ge.com> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 27 Jan 1995 12:36:14 -0800 Sender: questions-owner@FreeBSD.org Precedence: bulk >Hello, I'm having trouble getting the above mentioned NE2000 compat. card >to work in a new FreeBSD 2.0 system. The card is configured with base_port >at 0x300, and IRQ 5. It seems to be probed correctly and is detected as >a 16 bit card (correct). The machine is relatively empty, and I'm sure >there is no other card installed on conflicting addresses/IRQ's. >The machine is a 386/25 with 4MB mem. (Small I know, but it won't be >running a Window sys...) > >Symptoms: > "ping's" to other machines on the network seem fine - no dropped packets or > unreasonable delays. > "telnet" out works ok for short (2 minutes) periods, and then freezes. No > characters typed on console appear on screen. ^C or ^D does nothing. > ^\ causes seg fault (only way to exit...) > "ftp" works (and fails) the same as telnet. > >I only have the minimal binaries installed... I'm trying to ftp the bindist >without much luck as you can imagine... This might be caused by a bug in the (2.0) driver that was fixed a few weeks ago. Unfortunately there have been many changes to the driver, some of which will make it not backward source compatible with 2.0. The simple remedy would be to upgrade to the _next_ snapshot (the current snapshot is very broken). I'm expecting this to be available in less than a week. -DG