From owner-freebsd-mobile@FreeBSD.ORG Mon May 10 07:49:06 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D6D116A4CE for ; Mon, 10 May 2004 07:49:06 -0700 (PDT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08C2943D54 for ; Mon, 10 May 2004 07:49:06 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i4AEmvOd065072; Mon, 10 May 2004 08:48:57 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 10 May 2004 08:49:46 -0600 (MDT) Message-Id: <20040510.084946.98609542.imp@bsdimp.com> To: drew@corrupt.co.nz From: "M. Warner Losh" In-Reply-To: <409CDC4C.4030808@corrupt.co.nz> References: <409CDC4C.4030808@corrupt.co.nz> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: BelkinF5D6020 + 5.2.1 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 14:49:06 -0000 In message: <409CDC4C.4030808@corrupt.co.nz> Drew Broadley writes: : Hi all, : : I am having issues getting my Belkin F5D6020 (ver 2.0) with FreeBSD 5.2.1 : : This is the output with "hw.pci.allow_unsupported_io_range=1" enabled in : dmesg : : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> : start (20000000) < sc->membase (80000000) : end (ffffffff) > sc->memlimit (803fffff) : start (20000000) < sc->membase (80000000) : end (ffffffff) > sc->memlimit (803fffff) : pccard0: (manufacturer=0x01bf, product=0x3302) at function 0 : pccard0: CIS info: Belkin, 11Mbps-Wireless-Notebook-Network-Adapter, : (null) : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< : : I try to ifconfig pccard0 (as there is no wi0 device showing up) and : still no luck. : : Any ideas ? Word on the street is that is has prism2 compatibility. Are you absolutely sure it has prism2 compat? Do you have wi0 in your kernel? Have you tried adding the mfg/product to the driver? Warner