From owner-freebsd-stable Mon Oct 2 12:54:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id AD4DD37B66D for ; Mon, 2 Oct 2000 12:54:35 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.10.1/8.10.1) with ESMTP id e92JsG413818; Mon, 2 Oct 2000 15:54:32 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id PAA38186; Mon, 2 Oct 2000 15:54:14 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id PAA45176; Mon, 2 Oct 2000 15:54:13 -0400 (EDT) Date: Mon, 2 Oct 2000 15:54:13 -0400 (EDT) From: Thomas David Rivers Message-Id: <200010021954.PAA45176@lakes.dignus.com> To: imp@village.org, rivers@dignus.com Subject: Re: 4.1-RELEASE pccard? Cc: freebsd-stable@FreeBSD.ORG, jim@siteplus.net In-Reply-To: <200010021651.KAA12261@harmony.village.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, some news. I tried booting the kernel found on the 4.1.1-RELEASE kern.flp... and, guess what... I don't get the ed1 timeouts anymore; and a `ping' to an IP address on that line almost works... Note the *almost*... It seems packets go out the interface (as is evidenced by the flashing lights on the dongle - but pings, etc... don't work. Could this be due to kernel <-> user-land mismatch? (Also - interestingly enough - routes begin showing up in the laptop's routing table to other machines on the network, and they include the correct ARP address, etc... so, the low-level hardware seems to be "working".) If I could determine just which source diff to apply to the 4.1-RELEASE tree that made this work, I should be able to build a fixed up 4.1-RELEASE kernel (which would then match my user-land code) and be all done... Any pointers would be appreciated! - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message