>>>>> "jcm" == James C McPherson <james.mcpher...@sun.com> writes:
jcm> As for "will it work on sparc" - yes, I would expect so. BUT jcm> without fcode it won't be bootable. That's what you are really jcm> asking, isn't it? just if it will work. I want to add a slog. jcm> It turns out you can change between IT and IR firmware using jcm> LSI's sasflash utility, is there a reason to use one mode or the other? itmpt sounds like it only works with IT but that's a WAG and probably wrong. Is there a way to tell which mode mpt is using right now? Does mpt behave differently depending on mode? Thanks for the pointer to raidctl---I got this out of it: -----8<----- ja...@dharavi:~$ pfexec raidctl -l -g 0.2.0 2 Disk Vendor Product Firmware Capacity Status HSP ---------------------------------------------------------------------------- 0.2.0 ATA WDC WD10EADS-00 1A01 931.5G GOOD N/A GUID:50014ee202720bc0 ja...@dharavi:~$ pfexec raidctl -l 2 Controller Type Version ---------------------------------------------------------------- c2 LSI_1068E 1.22.01.00 ja...@dharavi:~$ -----8<----- I was hoping to see an -IT or -IR suffix on the version number but there isn't one. In the README for sasflash, it looks like SASFLASH will not tell you what kind of firmware you currently have, either, just let you choose what kind to load. In the ^C peecee boot widget, it shows my card's firmware version ending in -IT, so I think I have IT firmware. If I do, then Will's speculation that IT means the card acts as a SATA target is an incorrect guess because it's acting like a normal card right now. but on SPARC I'd have no way of seeing this -IT suffix, and I don't know if I trust it anyway without understanding what the different versions are supposed to do differently. so, is there any way to tell from mpt in what mode the card's running, or what the consequence of that is? It sounds like it's possible one could buy a 1068E card from another vendor and end up with -IR firmware instead, without changing chip number or necessarily even PCI ID, so if we are trying to predict which cards behave how, it's worth trying to figure out. I did try to RTFM. On OpenSolaris I get this loveliness: ja...@dharavi:~$ man mpt No manual entry for mpt. on SXCE I do at least have a man page, but there's no mention of IT, IR, SR inside it. jcm> Have a look at the other downloads on the LSI url you jcm> mentioned. oops. yeah, a proprietary sparc driver is there! That's not exactly, pow, we're definitely done, because their driver is for Sol10 not nevada. But hopefully that means the card will not need some firmware-provided ``initialization'' and might work with the sparc mpt included in Nevada! As for the closed-source LSI tool 'lsiutil' mentioned in this thread: http://www.opensolaris.org/jive/message.jspa?messageID=184811#184811 A hidden undocumented option 15 -> option 12 in lsiutil, to make drive mapping based on port number rather than some LSI-GUID/drive-serial as it supposedly is by default. My AOC-USAS-L8i card is already behaving port-based, though: Solaris device names corresponding to physical ports even when I move disks around. I guess it's other LSI cards that have the problem mentioned in the thread. there is a lsiutil binary inside the SPARC itmpt_sparc_5.07.04.zip file, so hopefully it's the same one the thread says is hard to find. I guess I'm a little closer to understanding the LSI cards, though I still don't know for sure what chips are on what card models (one can sort of guess), nor what IT, IR, SR mean. I'm still kind of pissed to be passing around warez too. Option 15, 12 wouldn't be secret if we had source to lsiutil. We would have less problems with whether the driver is for Sol10 or Nevada. The firmware on this card is way too big, and there does not seem to be any SAS card for less than $100/port with an open-source driver that works well.
pgpcpqGMhNZwQ.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
