From owner-freebsd-scsi@FreeBSD.ORG Fri May 7 15:22:12 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96AC816A4CE for ; Fri, 7 May 2004 15:22:12 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DFE143D41 for ; Fri, 7 May 2004 15:22:12 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (g4.samsco.home [192.168.0.12]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i47MQau6040957; Fri, 7 May 2004 16:26:37 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <409C0BDB.3050503@freebsd.org> Date: Fri, 07 May 2004 16:21:15 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040214 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Don Bowman References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: "'scsi@freebsd.org'" Subject: Re: AAC 2200s and firmware 7244 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 May 2004 22:22:12 -0000 Don Bowman wrote: > Does anyone know if the aac driver on > RELENG_4 (and/or CURRENT) supports the firmware > which was released yesterday on Adaptec's > web site? This is referenced as version 7244. > > The web page indicates that 'driver version 4.1.0.7244' > is required. I'm not sure what that is (the windows > version?) or how it maps to freebsd. > > (http://www.adaptec.com/worldwide/support/driverdetail.jsp?sess=no&language= > English+US&cat=/Product/ASR-2200S&filekey=asr2200s_fw_v7244.exe) > > --don So far I've no luck from Adaptec in trying to figure out what this means. Given that there is only a new Windows driver but not a new Linux driver, it might not be a big deal. In fact, it might just be something related to Windows Certification. I'll keep pressing to find out. In the mean time, feel free to be the Guinea Pig =-) Scott