odie82544

This is ICH7 controller for SATA MB, not supported, try another build. http://www.mini-itx.com/reviews/atoms/?page=6

I am not sure if you are discussing with my previous released. If yes, the generic answer are: 1.All MB storage controller newer than Intel ICH7 with AHCI mode. (not including ICH7/ICH7R). AMD platforms must newer than SB700 (including SB700) 2.Intel NIC driver base on e1000e.ko and e1000.ko or Realtek NIC driver base on r8168.ko. 3.AMI BIOS (nice to have) 4.MB support booting from USB Flash. If meet to the rules, suppose all MB can work with my Repack version. Note: ASMedia SATAII/III controllers are not supported by my previous Repack version.

No, in fact, Intel IRST/RST/RSTe just SW/FW RAID, this almost the same as OS RAID. (just cheap for RAID solution with MB). Intel also no official support for IRST/RST/RSTe driver release on Linux OS. You can also check the Intel RAID IDs from Linux kernel source code, all belong to AHCI portion.

I only focus on repack, not recompiler. Not understand your meaning, seems there are no boot.img inside every DSM build.

No and No.

Yes, I saw some error inside this release that relate to USB printer and other USB device (maybe UPS) , but I don't have them to test the function, so decided to skip it.

bummer... althoug "DS3612xs - DSM 4.1 build 2668" runs great in VMware... latest update would have been nice, Thanks anyway! Maybe you are talking the XPEnology version, that wan't my build.

Update the USB Boot Key to DSM 4.2 (.img) then use Assistant to provide the new .pat to box, the update manager will let you select update/migrate or clean install. Thanks! is it possible to use drivers from 4.1 pack, to use with "dsm 4.2 build 3202" and VMware some how? My DSM do not show op in VMware No plan to support VMware in my released, only support Virtual BOX.

Update the USB Boot Key to DSM 4.2 (.img) then use Assistant to provide the new .pat to box, the update manager will let you select update/migrate or clean install.

No plan to do it, I am considering the DS3612xs almost same as RS3413xs+ from repack view. Let DS2413 have SSD caching function maybe more interesting.

Had finished, under testing. Extra support NIC: e1000 and r8168 Support SSD Cache List: viewtopic.php?f=2&t=58

Update your DSM boot device and "Migrate" it. The web update scenario in DSM are not supported for fake BOX.

No, I don't have this NIC for test. Only support e1000, r8168 for extra NIC controller now. Base on previous experience, the first major release from Synology were not reliabled, so I won't spend too many time on this DSM build.

Support e1000 and r8168 NIC controller and USB ports x 12 Download URL #1: EOL Download URL #2: http://yadi.sk/d/4XcO57wR41pnj Download URL #3: http://yadi.sk/d/nrxEPCBX41txa Note: If Assistant message still not show ready (ex: Starting...) when first time installation or 600secs expired, reboot DSM and search it again. Support NIC: Intel Gigabits series for PCI and PCI-E (intel e1000 and e1000e driver base) Realtek gigabits PCI-E series (r1868 driver base) Support embedded controller on MB: AHCI SATA controller after Intel ICH7. No plan to support other controller, especially need to recompiler the kernel. My release just for evaluation purpose, not project. Please turn to XPEnology build if uable to install this release on your box.

Atom 2700 belongs to "cedarview" build, so you should use the build for DS1512+/DS1812+/DS2143+ series. My experience, for running "bromolow" build, at least should use the "Celeron" series CPU. You can paste your dmesg log on post for reference.

Before build 2668, it is very easy. From 2668, Synology including the SAS/SCSI common driver/library into kernel and do some process to SCSI/SAS HDDs, cause unable to use "insmod" scenario to extend more controllers. Maybe need to recompiler the kernel and can meet your requirement. If you had try to compiler the kernel, suppose you know what I am saying. Below are some dmesg info from "Linux DS3612 3.2.11 #2668 SMP Tue Dec 11 12:50:50 CST 2012 x86_64 GNU/Linux synology_bromolow_3612xs" [ 0.508274] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 2 53) [ 0.508685] io scheduler noop registered [ 0.508983] io scheduler cfq registered (default) [ 0.676576] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 0.753215] brd: module loaded [ 0.754581] Loading iSCSI transport class v2.0-870. [ 0.760939] rdac: device handler registered [ 0.761403] mpt2sas version 11.100.00.00 loaded [ 0.764212] ahci 0000:00:1f.2: version 3.0 [ 0.764300] ahci 0000:00:1f.2: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 0.765443] ahci 0000:00:1f.2: irq 40 for MSI/MSI-X Do you know what is the SAS controller on RS10613xs+ ?

For me, use two SSD as cache are wasting money. The limitation fixed inside some source code, maybe need to review the source code and recompiler it then have chance to remove it. But... where is the source code for this limitation?

The same model and capacity are the original design and limitation, you can check the help page for detail information.

Please submit the SSD info in this topic. viewtopic.php?f=2&t=58

Synology started to do some "handle" on SSD and SAS HDD in script and binary files from 2668 build. I didn't do lots of test on the Beta version, but you can try to change the SSD to SATA Port 2 (3rd SATA port), maybe work.

Support list now. [sSDSA2SH032G1GN] brand="Intel" size="30GB" [MKNSSDCR240GB-DX] brand="Mushkin" size="240GB" [OCZ-VERTEX2] brand="OCZ" size="60GB" [OCZ-VERTEX4] brand="OCZ" size="120GB" [sSD] -> Tested brand="SAMSUNG SSD PM800 Series 2.5" 256GB" size="256GB" [sSDSC2BW480A3D] brand="Intel" size="480GB" [M4-CT128M4SSD2] -> Tested brand="Crucial" size="128GB" [M4-CT256M4SSD2] brand="Crucial" size="256GB" [M4-CT512M4SSD2] brand="Crucial" size="512GB" [HUSML4040ASS600] brand="Hitachi" size="400GB" [sKC100S3120G] brand="Kingston" size="120GB" [sSDSC2CW240A3] brand="Intel" size="240GB" [sSDSC2CW24] brand="Intel" size="240GB" [sSDSC2CW480A3] brand="Intel" size="480GB" [sSDSA2BW600G3] brand="Intel" size="600GB" [sSDSC2CT180A3] brand="Intel" size="180GB" [sSDSA2BW60] brand="Intel" size="600GB" [sSDSC2CT18] brand="Intel" size="180GB" [sSDSC2CW48] brand="Intel" size="480GB" [sKC100S] brand="Kingston" size="120GB"

Support Virtual BOX not means also work on VMware, and no plan to do it.

I never use xpenology DSM, the table came from http://download.synology.com/ssddb/support_ssd.db

I had repack the DSM 4.2 Beta (Build version 3161) for RS3413xs+, below are major information for this release. 1.Extra Support NIC: r8168 and e1000 (suppose can run with VBOX) 2.Extra support Crucial M4-CT128M4SSD2/M4-CT256M4SSD2/M4-CT512M4SSD2 as SSD Cache 3.You must install the SSD on SATA port 0 & 1 as SSD Cache, the data HDD will start from SATA Port 2 4.Support AHCI SATA HDDs x10 and 12 USB ports Download URL: EOL

I had let unsupport SSD as cache disk on DSM, below are my Crucial - M4-CT128M4SSD2 128GB SSD working capture. Now, please post your SSD infomration on this topic, I will try to summary and build up in my next release. Please check your SSD model in BIOS menu, ex: Crucial M4 128GB will show as "M4-CT128M4SSD2" in BIOS HDD information page or during POST. Follow up below format and submit on this page: ex: [M4-CT128M4SSD2] -> SSD model show on POST or BIOS menu brand="Crucial" -> SSD brand size="128GB" -> SSD Capacity Below are supported list, so skip your POST if inside. Thanks. [HUSML4040ASS600] brand="Hitachi" size="400GB" [sKC100S3120G] brand="Kingston" size="120GB" [sSDSC2CW240A3] brand="Intel" size="240GB" [sSDSC2CW24] brand="Intel" size="240GB" [sSDSC2CW480A3] brand="Intel" size="480GB" [sSDSA2BW600G3] brand="Intel" size="600GB" [sSDSC2CT180A3] brand="Intel" size="180GB" [sKC100S] brand="Kingston" size="120GB" [sSDSC2CT18] brand="Intel" size="180GB" [sSDSC2CW48] brand="Intel" size="480GB" [sSDSA2BW60] brand="Intel" size="600GB"