This is the first (experiential?) test version of the driver extension for loader 1.04b and 918+ DSM 6.2.2
packages for 1.03b and 3615/3617 are coming (need to get an "older" hardware tor testing, my new B360M/G5400 test system did seem to freeze when loading the kernel with 1.03b, even no serial console output after starting loading the kernel)
Tested as fresh install with 1.04b loader with DSM 6.2.2, there are extra.lzma and extra2.lzma in the zip file - you need both - the "extra2" file is used when booting the 1st time and under normal working conditions the extra.lzma is used (i guess also normal updates - jun left no notes about that so i had to find out and guess).
Hardware in my test system used additional driver: r8168, igb, e1000e, bnx2x, tn40xx, mpt2sas
The rest of the drivers just load without any comment on my system, i've seen drivers crashing only when real hardware is present so be warned
extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.2 v0.6_test
!!! still network limit in 1.04b loader for 918+ !!!
atm 918+ has a limit of 2 nic's (as the original hardware)
If there are more than 2 nic's present and you can't find your system in network then you will have to try after boot witch nic is "active" (not necessarily the onboard) or remove additional nic's and look for this after installation
You can change the synoinfo.conf after install to support more then 2 nic's (with 3615/17 it was 8 and keep in mind when doing a major update it will be reset to 2 and you will have manually change this again, same as when you change for more disk as there are in jun's default setting) - more info's are already in the old thread about 918+ DSM 6.2.(0)
I might change that later so it will be set the same way as more disks are set by jun's patch - syno's max disk default for this hardware was 4 disks but jun's pach changes it on boot to 16!!! (so if you have 6+8 sata ports then you should not have problems when updating like you used to have with 3615/17)
I will extend here to what is in the old thread for 6.2 had but atm i'm more willing to add 3615/17 support
Basically what is on the old page is valid, so no sata_*, pata_* drivers
Here are the drivers in the test version listed as kernel modules:
!!! especially read "Other things good to know about DS918+ image and loader 1.03a2:" its still valid for 1.04b loader !!!
This section is about drivers for ds3615xs and ds3617xs image/dsm version 6.2.2 (v24922)
Both use the same kernel (3.10.105) but have different kernel options so don't swap or mix, some drivers might work on the other system some don't at all (kernel oops)
Its a test version and it has limits in case of storage support, read careful and only use it when you know how to recover/downgrade your system !!! do not use this to update when you have a different storage controller then AHCI, LSI MPT SAS 6Gb/s Host Adapters SAS2004/SAS2008/SAS2108/SAS2116/SAS2208/SAS2308/SSS6200 (mpt2sas) or LSI MPT SAS 12Gb/s Host Adapters SAS3004/SAS3008/SAS3108 (mpt3sas - only in 3617), instead you can try a fresh "test" install with a different usb flash drive and a empty single disk on the controller in question to confirm if its working (most likely it will not, reason below) !!!
The reason why 1.03b loader from usb does not work when updating from 6.2.0 to 6.2.2 is that the kernel from 6.2.2 has different options set witch make the drivers from before that change useless (its not a protection or anything), the dsm updating process extracts the new files for the update to HDD, writes the new kernel to the usb flash drive and then reboots - resulting (on USB) in a new kernel and a extra.lzma (jun's original from loader 1.03b for dsm 6.2.0) that contains now incompatible drivers, the only drivers working reliable in that state are the drivers that come with dsm from synology
Beside the different kernel option there is another thing, nearly none of the new compiled scsi und sas drivers worked
They only load as long as no drive is connected to the controller. ATM I assume there was some changes in the kernel source about counting/indexing the drives for scsi/sas, as we only have the 2.5 years old dsm 6 beta kernel source there is hardly a way to compensate
People with 12GBit SAS controllers from LSI/Avago are in luck, the 6.2.2 of 3617 comes with a much newer driver mpt3sas then 6.2.0 and 6.2.1 (13.00 -> 21.00), confirmed install with a SAS3008 based controller (ds3617 loader)
Driver not in this release: ata_piix, mptspi (aka lsi scsi), mptsas (aka lsi sas) - these are drivers for extremely old hardware and mainly important for vmware users, also the vmw_pvscsi is confirmed not to work, bad for vmware/esxi too
Only alternative as scsi diver is the buslogic, the "normal" choice for vmware/ESXi would be SATA/AHCI
I removed all drivers confirmed to not work from rc.modules so they will not be loaded but the *.ko files are still in the extra.lzma and will be copied to /usr/modules/update/ so if some people want to test they can load the driver manually after booting
These drivers will be loaded and are not tested yet (likely to fail when a disk is connected)
megaraid, megaraid_sas, sx8, aacraid, aic94xx, 3w-9xxx, 3w-sas, 3w-xxxx, mvumi, mvsas, arcmsr, isci, hpsa, hptio
(for some explanation of what hardware this means look into to old thread for loader 1.02b)
virtio driver: i added virtio drivers, they will not load automatically (for now), the drivers can be tested and when confirmed working we will try if there are any problems when they are loaded by default along with the other drivers
they should be in /usr/modules/update/ after install
To get a working loader for 6.2.2 it needs the new kernel (zImage and rd.gz) and a (new) extra.lzma containing new drivers (*.ko files)
zImage and rd.gz will be copied to usb when updating DSM or can be manually extracted from the 6.2.2 DSM *.pat file and copied to usb manually
and that's the point where to split up between cases/way's
case 1: update from 6.2.0 to 6.2.2
case 2: fresh install with 6.2.2 or "migration" (aka upgrade) from 6.0/6.1
Case 1: update from 6.2.0 to 6.2.2
Basically you semi brick your system on purpose by installing 6.2.2 and when booting fails you just copy the new extra.lzma to your usb flash drive by plugging it to a windows system (witch can only mount the 2nd partition that contains the extra.lzma) or you mount the 2nd partition of the usb on a linux system
Restart and then it will finish the update process and when internet is available it will (without asking) install the latest update (at the moment update4) and reboot, so check your webinterface of DSM to see whats going or if in doubt wait 15-20 minutes check if the hdd led's are active and check the webinterface or with synology assistant, if there is no activity for that long then power off and start the system, it should work now
Case 2: fresh install with 6.2.2 or "migration" (aka upgrade) from 6.0/6.1
Pretty much the normal way as described in the tutorial for installing 6.x (juns loader, osfmount, Win32DiskImager) but in addition to copy the extra.lzma to the 2nd partition of the usb flash drive you need to copy the new kernel of dsm 6.2.2 too so that kernel (booted from usb) and extra.lzma "match"
You can extract the 2 files (zImage and rd.gz) from the DSM *.pat file you download from synology https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3615xs_24922.pat
or https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3617xs_24922.pat
These are basically zip files so you can extract the two files in question with 7zip (or other programs)
You replace the files on the 2nd partition with the new ones and that's it, install as in the tutorial
In case of a "migration" the dsm installer will detect your former dsm installation and offer you to upgrade (migrate) the installation, usually you will loose plugins, but keep user/shares and network settings
Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+
in Additional Compiled Modules
Posted
FUNCIONA . . . . acabo de actualizar un HP Proliant gen8 a DSM6.2.2.29422 update4 copiando en la microSD los zImage y rd.gz del DSM_DS3617xs_24922.pat y el extra.Izma v0.5 . . . .