From owner-freebsd-questions@FreeBSD.ORG Wed May 21 06:29:02 2003 Return-Path: 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 380DA37B401 for ; Wed, 21 May 2003 06:29:02 -0700 (PDT) Received: from everest.cs.du.edu (everest.cs.du.edu [130.253.191.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 474D143F75 for ; Wed, 21 May 2003 06:29:01 -0700 (PDT) (envelope-from ifetch@cs.du.edu) Received: from mail.cs.du.edu (mail.cs.du.edu [130.253.191.12]) by everest.cs.du.edu (8.12.8+Sun/8.12.2) with ESMTP id h4LDSgQ2023817; Wed, 21 May 2003 07:28:51 -0600 (MDT) Date: Wed, 21 May 2003 07:28:41 -0600 (MDT) From: Ivan Fetch To: Dirk-Willem van Gulik In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner: clean cc: freebsd-questions@freebsd.org Subject: Re: Dlink DWL520 Rev 2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 13:29:02 -0000 Hello Running pciconf -l, I get: agp0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x162110b9 rev=0x05 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x524710b9 rev=0x01 hdr=0x01 isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x153310b9 rev=0xc3 hdr=0x00 atapci0@pci0:15:0: class=0x0101fa card=0x00000000 chip=0x522910b9 rev=0xc1 hdr=0x00 xl0@pci0:18:0: class=0x020000 card=0x00000000 chip=0x905010b7 rev=0x00 hdr=0x00 none0@pci1:0:0: class=0x030000 card=0x8a135333 chip=0x8a135333 rev=0x02 hdr=0x00 Maybe the "none" line? The card says rev A2 on it (in answer to your other inquiry about whether it is a "plus" model). Thanks, Ivan Fetch. Today, at 9:35am, Dirk-Willem van Gulik wrote: > > > I'm attempting to get a Dlink DWL520 (revision 2) wireless card to work > > under FreeBSD 5.0-RELEASE. My eventual goal is to have this machine > > Is that a rev 2 or a '+' ? Perhaps a dmesg from a verbose boot or a > pciconf -l would help. The wi driver should be fine. > > Dw. >