Date: Mon, 7 Aug 2000 18:03:00 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: Kelly Yancey <kbyanc@egroups.net> Cc: freebsd-scsi@freebsd.org Subject: Re: Using the ses driver Message-ID: <Pine.BSF.4.10.10008071801170.85898-100000@beppo.feral.com> In-Reply-To: <Pine.BSF.4.21.0008071750350.24356-100000@kbyanc.corp.ONElist.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > 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: <SYMBIOS 2> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10008071801170.85898-100000>