From owner-freebsd-questions Mon Sep 2 14:41: 4 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06A7B37B400 for ; Mon, 2 Sep 2002 14:41:01 -0700 (PDT) Received: from janeway.vonbek.dhs.org (bgm-24-24-79-198.stny.rr.com [24.24.79.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DBF143E91 for ; Mon, 2 Sep 2002 14:40:56 -0700 (PDT) (envelope-from syborg@stny.rr.com) Received: by janeway.vonbek.dhs.org (Postfix, from userid 507) id 6E86C4FC88; Mon, 2 Sep 2002 17:36:25 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by janeway.vonbek.dhs.org (Postfix) with ESMTP id 694424A0E for ; Mon, 2 Sep 2002 17:36:25 -0400 (EDT) Date: Mon, 2 Sep 2002 17:36:25 -0400 (EDT) From: John Bleichert X-X-Sender: syborg@janeway.vonbek.dhs.org Reply-To: John Bleichert To: freebsd-questions@freebsd.org Subject: pcmcia ed0 driver question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello all I'm trying to get a Network Anywhere 10/100 pc-card to work in my Thinkpad. According to the docs, it uses the ed(4) driver. In 4.6.2 should I really need to whip out mknod to make such a common device? ifconfig tells me /dev # ifconfig ed0 create ifconfig: SIOCIFCREATE: Invalid argument pccardc also tells me the "Device not configured" - MAKEDEV returns a "no such device name". ed support (and miibus) are both compiled into the kernel. Do I need to build a device entry with mknod? Or am I missing something easy? If not, should I take this over to freebsd-mobile? The last time I did this (with a different NIC) it worked out of the box... pciconf shows the pc-card bus, but no NIC. Thanks - JB # John Bleichert # http://vonbek.dhs.org/latest.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message