From owner-freebsd-stable Sun Aug 9 22:30:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12027 for freebsd-stable-outgoing; Sun, 9 Aug 1998 22:30:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles217.castles.com [208.214.165.217]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12022 for ; Sun, 9 Aug 1998 22:30:27 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA09831; Sun, 9 Aug 1998 22:28:56 -0700 (PDT) Message-Id: <199808100528.WAA09831@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: software@kew.com cc: stable@FreeBSD.ORG Subject: Re: zp0 not receiving under 2.2.7? In-reply-to: Your message of "Sun, 09 Aug 1998 23:32:52 EDT." <35CE69E3.DF0367FB@kew.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Aug 1998 22:28:56 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anyone seen a condition where zp0 (3COM PC-Card, rev C) can send but not > receive under 2.2.7? Card/machine/etc work fine under Windows 95. Card is > > seen at boot and dumps packets into network, does not see responses. Incorrect interrupt setting is the most likely cause. If this isn't for an install, you should be using the pccard support and the 'ep' driver. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message