2009/4/1 Dale Ghent <[email protected]>: > > On Mar 29, 2009, at 12:53 PM, Marty Faltesek wrote: > >> On Sun, 2009-03-29 at 12:18 +0100, Nicholas Brealey wrote: >>> >>> The nv_sata driver supports the CK804 and MCP55 SATA HBA adapters >>> (pci10de,37f , pci10de,55 and pci10de,54) but I have a MCP51 SATA HBA >>> adapter (see below). >>> >>> 1) Is there some way I can tell the OpenSolaris 2008.11 Live CD to use >>> the nv_sata for this device? >>> (Something like the following the instructions at >>> >>> http://www.sun.com/bigadmin/features/techtips/assign_device_to_driver.jsp). >>> >>> 2) Would it be wise to try the nv_sata dirver with the MCP51 or are >>> there some problems with this device which would need workarounds in the >>> driver? >> >> It works: the MCP51 pci id is being added to the next onnv build > > ...and here's the relevant putback info: > > http://mail.opensolaris.org/pipermail/onnv-notify/2009-March/008994.html > > Judging from the putback diff, the only changes were to make a few data > types and function names more generic (eg; mcp5x... instead of mcp55...) so > I bet if Nicholas just adds the PCI ID of the MCP51 SATA HBA (pci10de,266) > to his driver_alias, it will even work with a current onnv build: > > update_drv -a -i '"pci10de,266"' nv_sata
Yep, I've used such an update_drv on an ASUS M2N-PV VM mainboard (MCP51), and it worked just fine. Note that the MCP51 has two sata controllers, with different pci ids (pci10de,266 + pci10de,267) and both ids need to be added. But I think such an updata_drv command for nv_sata won't work in the opensolaris livecd environment, because without these specific bindings the ata driver is already bound to the pci device nodes. To fix this you have to modify the opensolaris livecd and add the two new driver binding entries to the etc/driver_aliases file on the livecd's ramdisk root filesystem image. Btw. if you try to use S3 suspend/resume, you may run into bug 6760699 when using nv_sata. > /dale > >> >>> 3) Is there any compelling reason to use the SATA driver instead of the >>> PATA driver? >> >> hotplug and maybe performance On systems with physical memory at addresses >= 4GB PATA may become quite slow because the PATA hardware can't to DMA to addresses >= 4GB.. The nv_sata controller interface might be able to use DMA addresses >= 4GB in the future, when 6807762 "nv_sata: DMA to addresses > 4GB should be enabled" is fixed. >>> 4) I only have Solaris 10 10/08 on my hard disk because it won't coexist >>> with OpenSolaris. Would it be safe to create a new ZFS boot environment >>> using live upgrade and use a modified version of the postinstall script >>> from SUNWnv-sata to fix the system? (Using the standard live upgrade >>> procedure to fallback to a previous boot environment if things go wrong). >> >> try it and see. Seems like it would work. _______________________________________________ driver-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/driver-discuss
