From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 23 08:10:38 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 AC9EA16A400 for ; Thu, 23 Mar 2006 08:10:38 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 367A243D49 for ; Thu, 23 Mar 2006 08:10:37 +0000 (GMT) (envelope-from lydianconcepts@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so580260wri for ; Thu, 23 Mar 2006 00:10:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QHvi9NyhZFi1HKCyEvN1J0ee5n4eCVLmW1IiscPaBoBW74RZHH6EItOhdVA425Rw93yq9ul9KuzfJSrOk1Gkxr4vGqF45ZW+xghO7/QWaoSQJv2biyrNbsJrS4zxBkmYQXeXiRZmS53ijB5RFRWk/on6hCIvQz529Z39kcKLApw= Received: by 10.65.151.17 with SMTP id d17mr1385867qbo; Thu, 23 Mar 2006 00:04:04 -0800 (PST) Received: by 10.65.154.14 with HTTP; Thu, 23 Mar 2006 00:04:04 -0800 (PST) Message-ID: <7579f7fb0603230004tfeef32cx61185793bc2d3dbd@mail.gmail.com> Date: Thu, 23 Mar 2006 00:04:04 -0800 From: "Matthew Jacob" To: "jason kawaja" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <44200030.9090400@centtech.com> Cc: freebsd-scsi@freebsd.org Subject: Re: qlogic isp 6312 device not showing up X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Mar 2006 08:10:38 -0000 > >> I'm guessing the "bad hard address 125" is the problem. Sounds like y= ou > >> manually set a hard address in the BIOS - is that necessary for your > >> configuration? > > No- that's not the problem. There's a bug in the driver about thinking that 125 is a bad loop id.