From owner-freebsd-scsi Mon Aug 7 18: 3: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 978F537B51B for ; Mon, 7 Aug 2000 18:03:00 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA18023; Mon, 7 Aug 2000 18:02:57 -0700 Date: Mon, 7 Aug 2000 18:03:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kelly Yancey Cc: freebsd-scsi@freebsd.org Subject: Re: Using the ses driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > Yuck. Looks like this box doesn't like VPD Inquiries- that'll need a patch in > > cam_xpt.c. It also doesn't like a Mode Sense either. But neitehr should fatal. > > Would you like a PR? :) Sure, but the PR should read: "We're tired of adding goop to cam_xpt.c- need something that the loader can set for cam_xpt to then read" > > > > > Interesting- you've got a JMR JBOD, cool! Mine (fibre channel) nevr seems to > > want to show up- it's really annoying. I think I actually may have the unit > > that *doesn't* have the SES module. > > > > So- did you add > > > > device ses0 > > > > and remove > > > > device pt0 > > > > from your config file? The latter step shouldn't be *required*, but it would > > clarify some confusion. > > > > Because it's showing up as a Processor device, it'll actually be SAF-TE > > instead of SES, so you'll see something like: > > > > ses0 at isp1 bus 0 target 15 lun 0 > > ses0: Fixed Processor SCSI-2 device > > ses0: Serial Number 1 > > ses0: 3.300MB/s transfers > > ses0: SAF-TE Compliant Device > > Yep. Worked like a charm when we took out pt0. Apparently this model > does have it. :) Hmm! That sounds like it warrants a note in ses(4). Send me the dmesg output and a 'getencstat -v' would you for my reference? Thanks! -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message