Driver extension jun 1.03b/1.04b for DSM6.2.3 for 918+ / 3615xs / 3617xs (2024)

edit 14.05.2020: 6.2.3 is back online as v25426, for newer coffeelake cpu's with problems using hardware transcoding (dev/dri present after boot) there is a new videostation that fixes the problem

edit2 02.06.2020: as @richv31 pointed out here

there seems to be a serious problem with 918+ and scsi/sas drivers, at least with mpt2sas/mpt3sas, not just with 6.2.2/6.2.3 it also happens with jun's original loader 1.04b and dsm 6.2.0 (23824), breaking raid sets after not properly waking up from hdd hibernation means potential data loss

i had a two disk raid1 set on a lsi 9211-8i and after disks spinning down only one came up and i saw some really worrying messages on the serial console, i was not able to log in to the system, not on the web gui, even not on the serial console, the whole system was in lock down and only switching off seemed to work

Spoiler

[ 1790.685552] blk_update_request: I/O error, dev sdg, sector in range 4980736 + 0-2(12)
[ 1790.694162] blk_update_request: I/O error, dev sdh, sector 4982400
[ 1790.700960] blk_update_request: I/O error, dev sdg, sector in range 9437184 + 0-2(12)
[ 1790.709540] blk_update_request: I/O error, dev sdh, sector 9437192
[ 1790.716337] blk_update_request: I/O error, dev sdg, sector in range 4980736 + 0-2(12)
[ 1790.724884] raid1: Disk failure on sdg1, disabling device.
[ 1790.724884] Operation continuing on 1 devices
[ 1790.735845] blk_update_request: I/O error, dev sdh, sector 4982400
[ 1790.742638] blk_update_request: I/O error, dev sdh, sector 4982400
[ 1790.749436] blk_update_request: I/O error, dev sdh, sector in range 1798144 + 0-2(12)
[ 1790.758050] blk_update_request: I/O error, dev sdh, sector in range 1810432 + 0-2(12)
[ 1790.770432] blk_update_request: I/O error, dev sdh, sector in range 4980736 + 0-2(12)
[ 1790.779049] Buffer I/O error on device md0, logical block in range 225280 + 0-2(12)
[ 1790.780438] blk_update_request: I/O error, dev sdh, sector in range 839680 + 0-2(12)
[ 1790.780448] blk_update_request: I/O error, dev sdh, sector in range 843776 + 0-2(12)
[ 1790.780479] blk_update_request: I/O error, dev sdh, sector 846608
[ 1790.781784] blk_update_request: I/O error, dev sdh, sector in range 1806336 + 0-2(12)
[ 1790.781793] blk_update_request: I/O error, dev sdh, sector in range 1810432 + 0-2(12)
[ 1790.828187] Buffer I/O error on device md0, logical block in range 225280 + 0-2(12)
[ 1790.836561] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.844964] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.853341] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.861702] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.870084] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.878455] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.886819] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.895172] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.903662] Aborting journal on device md0-8.
[ 1790.908677] Buffer I/O error on dev md0, logical block in range 262144 + 0-2(12) , lost sync page write
[ 1790.918993] Buffer I/O error on dev md0, logical block in range 0 + 0-2(12) , lost sync page write
[ 1790.918996] JBD2: Error -5 detected when updating journal superblock for md0-8.
[ 1790.936811] EXT4-fs error (device md0): ext4_journal_check_start:56: write error, md0, sdh1 index [7], sector 2056 [raid1_end_write_request]
[ 1790.943717] Buffer I/O error on dev md0, logical block 0, lost sync page write
[ 1790.943722] EXT4-fs error (device md0): ext4_journal_check_start:56: Detected aborted journal
[ 1790.943723] EXT4-fs (md0): Remounting filesystem read-only
[ 1790.943727] EXT4-fs (md0): previous I/O error to superblock detected
[ 1790.950627] blk_update_request: I/O error, dev sdh, sector 2048
[ 1790.950780] Buffer I/O error on dev md0, logical block 0, lost sync page write
[ 1794.075615] blk_update_request: I/O error, dev sdh, sector 837504
[ 1794.082367] blk_update_request: I/O error, dev sdh, sector 837504
[ 1800.780803] blk_update_request: I/O error, dev sdh, sector in range 843776 + 0-2(12)
[ 1810.789579] blk_update_request: I/O error, dev sdh, sector 846608
[ 1820.796568] blk_update_request: I/O error, dev sdh, sector 846608
[ 1822.044135] blk_update_request: I/O error, dev sdh, sector in range 774144 + 0-2(12)
[ 1822.052679] blk_update_request: I/O error, dev sdh, sector 776184
[ 1822.066628] blk_update_request: I/O error, dev sdh, sector in range 729088 + 0-2(12)
[ 1822.075149] blk_update_request: I/O error, dev sdh, sector 730800
[ 1830.934083] blk_update_request: I/O error, dev sdh, sector in range 843776 + 0-2(12)
[ 1840.942853] blk_update_request: I/O error, dev sdh, sector 846608
[ 1850.949900] blk_update_request: I/O error, dev sdh, sector 846608
[ 1860.956826] blk_update_request: I/O error, dev sdh, sector 846608
[ 1870.963792] blk_update_request: I/O error, dev sdh, sector 846608
[ 1880.970764] blk_update_request: I/O error, dev sdh, sector 846608
[ 1890.977740] blk_update_request: I/O error, dev sdh, sector 846608
[ 1900.984686] blk_update_request: I/O error, dev sdh, sector 846608
[ 1910.991662] blk_update_request: I/O error, dev sdh, sector 846608
[ 1920.998651] blk_update_request: I/O error, dev sdh, sector 846608
[ 1926.606790] blk_update_request: I/O error, dev sdh, sector in range 774144 + 0-2(12)
[ 1926.623021] blk_update_request: I/O error, dev sdh, sector in range 729088 + 0-2(12)
[ 1931.005641] blk_update_request: I/O error, dev sdh, sector in range 843776 + 0-2(12)
[ 1936.902021] blk_update_request: I/O error, dev sdh, sector in range 737280 + 0-2(12)
[ 1936.910568] blk_update_request: I/O error, dev sdh, sector 737800
[ 1941.014441] blk_update_request: I/O error, dev sdh, sector in range 843776 + 0-2(12)
[ 1943.976967] blk_update_request: I/O error, dev sdh, sector in range 450560 + 0-2(12)
[ 1943.985462] blk_update_request: I/O error, dev sdh, sector in range 1069056 + 0-2(12)
[ 1943.994054] blk_update_request: I/O error, dev sdh, sector in range 446464 + 0-2(12)
[ 1944.002551] blk_update_request: I/O error, dev sdh, sector in range 450560 + 0-2(12)
[ 1944.011056] blk_update_request: I/O error, dev sdh, sector in range 1069056 + 0-2(12)
[ 1944.019658] blk_update_request: I/O error, dev sdh, sector in range 1069056 + 0-2(12)
[ 1944.028247] blk_update_request: I/O error, dev sdh, sector in range 1069056 + 0-2(12)
[ 1944.036823] blk_update_request: I/O error, dev sdh, sector in range 1069056 + 0-2(12)
[ 1944.047345] blk_update_request: I/O error, dev sdh, sector 452360
[ 1944.056151] blk_update_request: I/O error, dev sdh, sector 347928
[ 1944.062956] blk_update_request: I/O error, dev sdh, sector 452064
[ 1944.069715] blk_update_request: I/O error, dev sdh, sector 349352
[ 1944.076507] blk_update_request: I/O error, dev sdh, sector 458760
[ 1944.083383] blk_update_request: I/O error, dev sdh, sector 456704
[ 1944.090223] blk_update_request: I/O error, dev sdh, sector 1576904
[ 1944.097147] blk_update_request: I/O error, dev sdh, sector 445736
[ 1944.103846] md/raid1:md2: sdg3: rescheduling sector 4525376
[ 1944.110073] raid1: Disk failure on sdg3, disabling device.
[ 1944.110073] Operation continuing on 1 devices
[ 1944.121641] md/raid1:md2: redirecting sector 4525376 to other mirror: sdh3
[ 1944.137078] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0
[ 1944.146632] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.159127] blk_update_request: I/O error, dev sdh, sector 1742824
[ 1944.159458] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.159467] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.188028] blk_update_request: I/O error, dev sdh, sector 1742824
[ 1944.208072] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0
[ 1944.217600] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 3, flush 0, corrupt 0, gen 0
[ 1944.217615] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.237971] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 4, flush 0, corrupt 0, gen 0
[ 1944.237980] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258357] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258418] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 5, flush 0, corrupt 0, gen 0
[ 1944.258424] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 6, flush 0, corrupt 0, gen 0
[ 1944.258471] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258483] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258511] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 7, flush 0, corrupt 0, gen 0
[ 1944.258516] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258527] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 8, flush 0, corrupt 0, gen 0
[ 1944.258534] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258551] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 9, flush 0, corrupt 0, gen 0
[ 1944.258564] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 10, flush 0, corrupt 0, gen 0
[ 1944.258821] BTRFS error (device md2): failed to repair data csum of ino 15266 off 0 (ran out of all copies)
[ 1944.258821]
[ 1944.258827] BTRFS error (device md2): failed to repair data csum of ino 15266 off 4096 (ran out of all copies)
[ 1944.258827]
[ 1944.395099] BTRFS error (device md2): failed to repair data csum of ino 15266 off 8192 (ran out of all copies)
[ 1944.395099]
[ 1944.557549] EXT4-fs error (device md0): ext4_find_entry:1624: inode #33349: comm synopkg: reading directory lblock 0
[ 1944.569078] EXT4-fs (md0): previous I/O error to superblock detected
[ 1944.576170] Buffer I/O error on dev md0, logical block 0, lost sync page write
[ 1944.793737] BTRFS: error (device md2) in btrfs_commit_transaction:2434: errno=-5 IO failure (Error while writing out transaction)
[ 1944.806642] BTRFS: error (device md2) in cleanup_transaction:2032: errno=-5 IO failure
[ 1951.515009] blk_update_request: I/O error, dev sdh, sector in range 69632 + 0-2(12)
[ 1951.539799] blk_update_request: I/O error, dev sdh, sector 73472
[ 1951.563740] blk_update_request: I/O error, dev sdh, sector 73472
[ 1951.586584] blk_update_request: I/O error, dev sdh, sector 73472
[ 1951.594097] blk_update_request: I/O error, dev sdh, sector 73472
[ 1951.601295] blk_update_request: I/O error, dev sdh, sector 73472

as of the problems with not getting s.m.a.r.t. values i used juns old original raid_class.ko, scsi_transport_sas.ko, scsi_transport_spi.ko to get the old state back (replacing my newly made ones from more recent synology kernel source 24922 ) in 0.11/0.12 - these version inherit the problem that seems to be present since the beginning with loader 1.04b

anyone using mpt2sas/mpt3sas and disk hibernation on 918+ should disable it for now to not risk any data loss

the new 0.13 for 918+ will have the raid_class.ko, scsi_transport_sas.ko, scsi_transport_spi.ko from kernel source 24922, that version did work on testing on my system without breaking anything and without such alarming errors on wakeup of disks, there will be no smart data but at least it seems safer then disks not waking up properly

for "proper" lsi sas controller support i'd suggest using 3615 or 3617 as it is "native" in these units and should work better, maybe there are kernel options missing in the 918+ kernel and that cant be fixed, if anyone finds out more just add a comment (i might not have the time to dig into this)

the other alternative is to use sata/ahci instead of scsi/sas with 918+, that works without problems on my system using 918+ (12 disks), JMB585 based controller seem to be the best choice atm as they support pcie 3.0 and can have up to 2000 MByte/s for its 5 sata ports (the older marvell and asm chips use only pcie 2.0 limiting the data rate to 500 MB/s or 1000 MB/s, even 8 port controller with two of the older chips use a pcie bridge chip with just two lanes making them terrible choice for a high port count - might be ok with just one or two 1GBit nic's but will at least limit the rebuild speed and ssd's should be kept away from these controllers and place in internal sata ports)

for Instructions about installing or updating please read "Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+"
if i have time i will write more in this place
the new package is not well tested i just did some tests with hardware i have at hand (ahci, e1000e, r8168, igb, bnx2x, mpt2sas/mpt3sas) and tested update from 6.2.2 to 6.2.3


basically synology reverted the kernel config change made in 6.2.2 back to what was before so old drivers from original 1.04b loader (and older driver i made before 6.2.2) should work again - but as synology also introduced there own new i915 driver with 6.2.3 there will be a conflict when jun's i915 driver is loaded with 6.2.3


there are two positive new things, synology released a nearly recent kernel source code (24922) and 6.2.3 has a new i915 driver supporting as much gpu hardware as jun's backported i915 driver in loader 1.04b - so there is no need for jun's i915 driver anymore and in theory we should have good support for apollo lake, gemini lake and other newer hardware but it seems not all new UHD630 is supported as there is dev id "3E98" unsupported (i5-9400, i5-9600k, i7-9700t, i7-9700), ark.intel.com and wikichip.og are usually good sources to check the id

https://ark.intel.com/content/www/us/en/ark/products/134898/intel-core-i5-9400-processor-9m-cache-up-to-4-10-ghz.html

edit: there seems to be versions of the i5-9400 with a "3E92" GPU this versions don t need the patched driver, they will run with the default driver, /dev/dri should be present ootb, it also can be checked in /var/log/dmesg when searching for "[8086:3e92]"

https://en.wikichip.org/wiki/intel/core_i5/i5-9400

there is also a good document from intel listing all coffeelake's

https://01.org/sites/default/files/documentation/intel-gfx-prm-osrc-cfl-vol01-configurations.pdf

coffeelake cup's without driver support (no hardware transcoding), SKU numbers should be listed when buying and can be checked on the box

i9 SKU S82
i7 SKU S82
i5 SKU S6f2

a new 10th gen i5-10500 / i3-10300 have device id's "9BC8" and there are no "9xxx" numbers in the driver we use so don't expect any newer gen10 cpu to work with hardware transcoding even when it "only" has UHD630 igpu

edit: there are also even lower end 10th gen cpus (2 core) with a different GPU device id "9BA8" like G5920, G5925, G6400 with a iGPU UHD 610, the equivalent in the 9th gen would be a G5400 and that comes with pci device id's 3E90/3E93, so we need to edit a different entry when patching for this

edit: i made a modded i915 driver were the pci device id of the 9th gen UHD 630 iGPU (3E92/3E93) is replaces with the device id's of the newer/different UHD 610/630 iGPU's that are unsupported

8086:3E92 => iGPU UHD 630, Low End Desktop 9 Series (original driver)

->

8086:3E98 => iGPU UHD 630, High End Desktop 9 Series (i5-9400, i5-9600k, i7-9700t, i7-9700)
8086:9BC8 => iGPU UHD 630, Low End Desktop i5-10500, i5-10600T and lower
8086:9BC5 => iGPU UHD 630, High End Desktop i510600K and higher

8086:3E93 => iGPU UHD 610, Low End Desktop 9 Series
->
8086:9BA8 => iGPU UHD 610, low End Desktop Series like G6400

the zip file contains 3 versions in every one is 3E92 replaced with the one we want to get working, as its just a crude binary patch i choose 3E92 as it seemed the most similar device, was tested for 3E98 iGPU and seemed to work, for the 10th there is at least one positive feedback with plex

its intended to be used with the extra/extra2 from this thread as this removes jun's old i915 driver (not just one file) that will prevent synologys new driver to work properly

the patched i915.ko file is supposed to be copied to /usr/lib/modules/ and replaces the original file from synology

for 6.2.3 Update3 (added 9BA8 support)

https://gofile.io/d/4fFJA5

https://dailyuploads.net/x3e0nkxk6p0e
https://usersdrive.com/zfl9csl91xwr.html
https://www34.zippyshare.com/v/304gfbnO/file.html

SHA256: EC2447F47FEE6457FE3F409E26B83E5BF73023310E10A624575A822FDBC10642

a little warning, in worst case the system might crash or freeze when transcoding and and such undefined states and hard resets can result i data loss (cache) or damaged raids (depending on the load of the system at this time) so until its more tested it should not be used on system with "important" data and a recent backup - ok i know its a little over cautious but i dont like the thought someone looses data because of this nice to have feature (software mdadm raids can be repaired in most cases if the worst happens)

-> positive feedback for a i5-9400, i5-9600K, i9-9900T (8086:3E98) to fully working

-> positive feedback for a G6400 (8086:9BA8) to have /dev/dri

-> one user positive feedback for a i5-10600T (8086:9BC8) to fully working with plex

-> one user negative feedback for a i5-10500 (8086:9BC8) to get /dev/dri devices but no transcoding with emby

-> one user negative feedback for a i9-10900 (8086:9BC5) system does not boot anymore - seems to be a solid hands off?

edit: there is a driver source patch for 10th gen that came up along 7.x and 9BC5 was confirmed to work with this new driver, so anyone with a 10th gen gpu and trouble can change to 7.x (tc rp loader) ot can try these 6.2.3 modules from this link (i915_918_623.7z)

Spoiler

0042
0046
0102
0106
010A
0112
0116
0122
0126
0152
0155
0156
0157
015A
0162
0166
016A
016A
0402
0406
040A
040B
040E
0412
0416
041A
041B
041E
0422
0426
042A
042B
042E
0A02
0A06
0A0A
0A0B
0A0E
0A12
0A16
0A1A
0A1B
0A1E
0A22
0A26
0A2A
0A2B
0A2E
0A84
0C02
0C06
0C0A
0C0B
0C0E
0C12
0C16
0C1A
0C1B
0C1E
0C22
0C26
0C2A
0C2B
0C2E
0D02
0D06
0D0A
0D0B
0D0E
0D12
0D16
0D1A
0D1B
0D1E
0D22
0D26
0D2A
0D2B
0D2E
0F30
0F31
0F32
0F33
1602
1606
160A
160B
160D
160E
1612
1616
161A
161B
161D
161E
1622
1626
162A
162B
162D
162E
1632
1636
163A
163B
163D
163E
1902
1906
190A
190B
190E
1912
1916
191A
191B
191D
191E
1921
1923
1926
1927
192A
192B
192D
1932
193A
193B
193D
1A84
1A85
22B0
22B1
22B2
22B3
2562
2572
2582
258A
2592
2772
27A2
27AE
2972
2982
2992
29A2
29B2
29C2
29D2
2A02
2A12
2A42
2E02
2E12
2E22
2E32
2E42
2E92
3184
3185
3577
3582
358E
3E90
3E91
3E92
3E93
3E94
3E96
3E99
3E9A
3E9B
3EA0
3EA1
3EA2
3EA3
3EA4
3EA5
3EA6
3EA7
3EA8
3EA9
5902
5906
5908
590A
590B
590E
5912
5913
5915
5916
5917
591A
591B
591D
591E
5921
5923
5926
5927
593B
5A41
5A42
5A49
5A4A
5A51
5A52
5A59
5A5A
5A71
5A79
5A84
5A85
8990
A001
A011

Spoiler

Gemini Lake
N4000/J4005/N4100/J4105 UHD600, EU=12, 0x3185
N5000/J5005 UHD605, EU=18, 0x3184

Gemini Lake Refresh
N4020/J4025/N4120/J4125 UHD600, EU=12 0x3185
N5030/J5040 UHD605, EU=18, 0x3184

Jasper Lake
N4500/N4505 UHDxxx, EU=16, 0x4E55
N5100/N5105 UHDxxx, EU=24, 0x4E61
N6000/N6005 UHDxxx, EU=32, 0x4E71
UHD = Tiger Lake G4, 11th gen intel gpu

looks like jasper lake is the last one using the "old" UHD, anything beefier in the 11th gen cpu line uses the new Xe architecture

the new pci id's are not covered by the i915 we have, so expect it not to work until you read otherwise

it might be possible to use some older pci id's for patching the i915 driver and test if the newer gpu's work with the old code, but as the higher tier 10th gen cpu's already had problems with this i dont expct any 11th gen stuff to work, we will only know for sure when its tested

i completely removed jun's i915 drivers from the extra/extra2 and changed/added the i915 firmware needed, also i took care of the "old" i915 drivers on the installed system in /usr/lib/modules/update/, they are now deleted on boot so if you come from 6.2.2 and used extra/extra2 std or recovery or you did already used juns original 1.04b extra/extra2, it should work as soon as you boot up (when drivers in "update" are not present then the default drivers from synology will be used and with the added i915 in place it will work on most intel gpu's up to coffee lake)
the driver versions are the same as in the 6.2.2 extra/extra2 but are newly compiled, as every driver from 6.2.2 is renewed all the old drivers are overwritten and there should be no crashing drivers on boot (which can prevent proper shutdown or reboot)
we now have one universal i915 driver (and not jun's and synologys) its back to one package for all cpu/gpu, if needed there will be a recovery version too

i only did test a new created loader from 1.04b image file with zImage and rd.gz from "DSM_DS918+_25426.pat" and the new extra.extra2, it will also work with the 6.2.0 kernel that is by default in the 1.04b image

if there are problems getting hardware transcoding to work it might help to disable vt-x/vt-d in bios (reported on a J5005 Gemini Lake), but there are other possible reasons because of the licensing thats needed for this to work, but at least it will not hurt as as lon as you dint intent to use the vmm package


if you accidentally updated 6.2.2 to 6.2.3 and now have problems like no network after boot, no proper shutdown/reboot or missing /dev/dri (hardware transcoding) then you just copy the new extra/extra2 to your already updated usb drive (the update to 6.2.3 already installed the new kernel on it)

with latest updates of win10 there is no drive letter anymore, its possible to still do it with the tools already used for creating the usb drive, read the usb to a imgae file with "Win32DiskImager 1.0" (activate "read only allocated partitions"), mount that image with osfmount (like in the tutorial section), overwrite old /extra/extra2.lzma and write the image back to usb with Win32DiskImager

extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.9

some intel and realtek driver updated so hopefully more onboard nic's will work (like realtek 8125), also realtek 8152 is newer so all 2.5G usb solutions from realtek schould work, there is still no way for the intel 2.5G nic as there is no standalone driver for older kernel versions, removed fireware, added bnxt_en and sr_mod/cdrom, nic Killer E2500, added *vf.ko in rc.modules

https://pixeldrain.com/u/jHa2eYrc

1CED32FCF63EB54DAA44335FA1EFBCE408D41A3E16D55771D35B0FD423F0B9CF

extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.3

scsi/sas disks will have no s.m.a.r.t. infos with lsi sas controllers (see edit2 above), newer atlantic.ko driver 2.3.4, r8125 added to rc.modules, used latest source for realtek drivers r8101/r8125/r8152/r8168/r8169, bna.ko firmware corrected

https://pixeldrain.com/u/pkBY9XjC

SHA256: EF6F26999C006A29B3B37A7D40C694943100F0A9F53EC22D50E749F729347EC6

for special purpose and tests, extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.12.1 - this version shows s.m.a.r.t. info and serial of disks for lsi scsi/sas but might corrupt the raid when disk hibernation is active (see warning above)

https://pixeldrain.com/u/kZJdPj1H
SHA256: 9089D38A4975AB212553DA7E35CE54027DE4F84D526A74A46A089FC7E88C1693

extra.lzma for loader 1.03b ds3615 DSM 6.2.3 v0.12.1_test, added virtio/9p, CDROM drivers, nic Killer E2500

https://pixeldrain.com/u/Rx4tV6ay

SHA256: E72820BF648CFD7F6075DEEB1208A3E0D8A61F38289AE17AC7E355910B9B0E0E

extra.lzma for loader 1.03b ds3615 DSM 6.2.3 v0.11_test, same added drivers as for 6.2.2 like newer intel drivers, 10G nics, ...

https://pixeldrain.com/u/5aN77nWf
SHA256: 5DE93F95841CC01F9E87EE4EE2A330084B447E44EBAA6013A575A935D227D4AF

extra.lzma for loader 1.03b ds3617 DSM 6.2.3 v0.12_test (2/2022), added virtio/9p, CDROM drivers, nic Killer E2500

https://pixeldrain.com/u/xmhCVxck
SHA256: B9AC8705D5D9DCEED1C0315346E4F2C7C4CD07C4ED519FC9901E8E368A3AE448

extra.lzma for loader 1.03b ds3617 DSM 6.2.3 v0.11.2_test, same added drivers as for 6.2.2 like newer intel drivers, 10G nics, ... (0.11.2 because i forgot bnx2/bnx2x firmware and mpt2/mp3 driver problem when updating from 6.2.2 in 0.11)

https://pixeldrain.com/u/zwAJzKa9
SHA256: D467914E55582D238AC5EC4D31750F47AEB5347240F2EAE54F1866E58A8BD1C9

Edited by IG-88
checked links and removed non working

Driver extension jun 1.03b/1.04b for DSM6.2.3 for 918+ / 3615xs / 3617xs (2024)

References

Top Articles
Latest Posts
Article information

Author: Prof. Nancy Dach

Last Updated:

Views: 6295

Rating: 4.7 / 5 (77 voted)

Reviews: 84% of readers found this page helpful

Author information

Name: Prof. Nancy Dach

Birthday: 1993-08-23

Address: 569 Waelchi Ports, South Blainebury, LA 11589

Phone: +9958996486049

Job: Sales Manager

Hobby: Web surfing, Scuba diving, Mountaineering, Writing, Sailing, Dance, Blacksmithing

Introduction: My name is Prof. Nancy Dach, I am a lively, joyous, courageous, lovely, tender, charming, open person who loves writing and wants to share my knowledge and understanding with you.