From owner-freebsd-stable Mon Aug 10 09:22:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26577 for freebsd-stable-outgoing; Mon, 10 Aug 1998 09:22:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles176.castles.com [208.214.165.176]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26553 for ; Mon, 10 Aug 1998 09:22:23 -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 JAA12498; Mon, 10 Aug 1998 09:20:39 -0700 (PDT) Message-Id: <199808101620.JAA12498@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Drew Derbyshire cc: Mike Smith , stable@FreeBSD.ORG Subject: Re: zp0 not receiving under 2.2.7? In-reply-to: Your message of "Mon, 10 Aug 1998 08:15:23 EDT." <35CEE45B.ECF5E90E@kew.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 09:20:38 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > 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. > > No doubt I should use ep0 and in fact tried to do so. > > However, configuration failed under pccardd. The error message reported by > pccardd was not sufficient to debug the problem, and I don't have full source > loaded on the target system. Hence, I left off this chapter of the saga since > I didn't feel like getting flamed for reporting the error message was > incomplete. As it is, however, the pccardd message doesn't tell me what the > problem is. No, but it can often tell us what's going on (most of the time). There are three messages you're likely to get: - "no driver found for ..." meaning your pccard.conf file entry is wrong. - "resource allocation failed for ..." meaning that the resource information in your pccard.conf file conflicts with the configuration entry you've selected from the card - "driver allocation failed for ..." meaning that the driver probe failed, or the kernel disagrees with you as to the resources that you've assigned to the card (ie. they're in use elsewhere). > I presume zp0 should at least get the system on to my network. I don't swap > cards, really. It *should* work, yes. The lack of incoming packets does suggest an interrupt problem of some sort though. -- \\ 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