Popular Post IG-88 Posted October 6, 2019 Popular Post Share #1 Posted October 6, 2019 (edited) This post was recognized by Polanskiman! IG-88 was awarded the badge 'Super Developer' and 5 points. DSM 6.2.3 will not work with these drivers, if you install or update you will fall back to "native" drivers that come with DSM, like no realtek nic on 3615/17 but on 918+ or no mpt2/mpt3sas on 918+ or no broadcom onboard nic on HP microserver or Dell server read this if you want to know about "native" drivers https://xpenology.com/forum/topic/13922-guide-to-native-drivers-dsm-617-and-621-on-ds3615/ synology reverted the changes made in 6.2.2 so the old drivers made for 6.2.(0) are working again and there are new drivers made for 6.2.3 too (we got recent kernel source from synology lately) https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/ This is the new 2nd test version of the driver extension for loader 1.04b and 918+ DSM 6.2.2, network drivers for intel and realtek are now all latest and the same as in 3615/17 from mid. december (also broadcoam tg3 driver is working), tries to address the problems with the different GPU's by haveing 3 versions of the pack additional information and packages for 1.03b and 3615/3617 are in the lower half under a separate topic (i will unify the 918+ and 3615/17 parts later as they are now on the same level again) mainly 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, i assume any storage driver beside ahci and mps2sas/mpt3sas as not working, so if you use any other storage as listed before you would need to do a test install with a new usb and a single empty disk to find out before doing anything with your "production" system i suggest testing with a new usb and a empty disk and it that's ok then you have a good chance for updating for updating its the same as below in the 3615/17 section with case 1 and 2 but you have extra.lzma and extra2.lzma and you will need to use https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS918+_24922.pat most important is to have zImage and rd.gz from the "DSM_DS918+_24922.pat" file (can be opened with 7zip) together with the new extra/extra2, same procedure as for the new extra for 3615/17 (see below) all 4 files extra.lzma, extra2.lzma (both extracted from the zip downloaded), zImage and rd.gz go to the 2nd partition of the usb (or image when using osfmount), replacing the 4 files there if you want the "old" files of the original loader back you can always use 7zip to open the img file from jun and extract the original files for copying them to usb if really wanting to test with a running 6.2.x system then you should empty /usr/lib/modules/update/ and /usr/lib/firmware/i915/ before rebooting with the new extra/extra2 rm -rf /usr/lib/modules/update/* rm -rf /usr/lib/firmware/i915/* the loader will put its files on that locations when booting again, this step will prevent having old incompatible drivers in that locations as the loader replaces only files that are listed in rc.modules and in case of "syno" and "recovery" there are fewer entries, leaving out i915 related files, as long as the system boots up this cleaning can be done with the new 0.8 test version there a 3 types of driver package, all come with the same drivers (latest nic drivers for realtek and intel) and conditions/limitations as the 3615/17 driver set from mid. december (mainly storage untested, ahci and mpt3sas is tested). 1. "syno" - all extended i915 stuff removed and some firmware added to max compatibility, mainly for "iGPU gen9" (Skylake, Apollo Lake and some Kaby Lake) and older and cases where std did not work, i915 driver source date: 20160919, positive feedback for J3455, J1800 and N3150 2. "std" - with jun's i915 driver from 1.04b (tested for coffee lake cpu from q2/2018), needed for anything newer then kaby lake like gemini lake, coffee lake, cannon lake, ice lake, i915 driver source date: 20180514 - as i had no source i915 driver is the same binary as in jun's original extra/extra2, on my system its working with a G5400, not just /dev/dri present, tested completely with really transcoding a video, so its working in general but might fail in some(?) cases, also 8th/9th gen cpu like i3/i5 8100/9400 produce a /dev/dri, tested with a 9400 and it does work 3. "recovery" - mainly for cases where the system stops booting because of i915 driver (seen on one N3150 braswell), it overwrites all gpu drivers and firmware with files of 0 size on booting so they can't be loaded anymore, should also work for any system above but guarantees not having /dev/dri as even the firmware used from the dsm's own i915 driver is invalid (on purpose) - if that does not work its most likely a network driver problem, safe choice but no transcoding support start with syno, then std and last resort would be recovery anything with a kernel driver oops in the log is a "invalid" as it will result in shutdown problems - so check /var/log/dmesg the often seen Gemini Lake GPU's might work with "std", pretty sure not with "syno", most (all?) testers with gemini lake where unsuccessful with "std" so if you don't like experimenting and need hardware transcoding you should wait with the version you have the "_mod" on the end of the loader name below is a reminder that you need to to "modding" as in make sure you have zImage and rd.gz from DSM 6.2.2 on you usb for booting, the new extra.lzma will not work with older files 0.8_syno ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_syno https://gofile.io/d/mVBHGi SHA256: 21B0CCC8BE24A71311D3CC6D7241D8D8887BE367C800AC97CE2CCB84B48D869A Mirrors by @rcached https://clicknupload.cc/zh8zm4nc762m https://dailyuploads.net/qc8wy6b5h5u7 https://usersdrive.com/t0fgl0mkcrr0.html https://www104.zippyshare.com/v/hPycz12O/file.html 0.8_std ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_std https://gofile.io/d/y8neID SHA256: F611BCA5457A74AE65ABC4596F1D0E6B36A2749B16A827087D97C1CAF3FEA89A Mirrors by @rcached https://clicknupload.cc/h9zrwienhr7h https://dailyuploads.net/elgd5rqu06vm https://usersdrive.com/peltplqkfxvj.html https://www104.zippyshare.com/v/r9I7Tm0K/file.html 0.8_recovery ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_recovery https://gofile.io/d/4K3WPE SHA256: 5236CC6235FB7B5BB303460FC0281730EEA64852D210DA636E472299C07DE5E5 Mirrors by @rcached https://clicknupload.cc/uha07uso7vng https://dailyuploads.net/uwh710etr3hm https://usersdrive.com/ykrt1z0ho7cm.html https://www104.zippyshare.com/v/7gufl3yh/file.html Spoiler J1xxx - Bay Trail (Silvermont), Intel HD Graphics for Intel Atom Processor Z3700 Series with Quick Sync Video, same as Ivy Bridge J33xx/J34xx - Apollo Lake (Goldmont), Intel HD Graphics 500 J4205 - Apollo Lake (Goldmont), Intel HD Graphics 505 J40xx/J41xx - Gemini Lake (Goldmont Plus), Intel UHD Graphics 600 J50xx - Gemini Lake (Goldmont Plus), Intel UHD Graphics 605 Intel GPU Gen's Gen 1 810, 815 Gen 2 i830M, 845G, 855GM, 865G Gen 3 915G/GM, 945G/GM, G/Q33, Q35, Atom D4xx/D5xx/N4xx/N5xx Gen 4 965G/GM/Q, G35, G41, G/Q43, G/GM/Q45 Gen 5 Nehalem (Ironlake) Gen 6 Sandy Bridge Gen 7 Ivy Bridge, Valley View, Bay Trail Gen 7.5 Haswell Gen 8 Broadwell, Cherryview Gen 9 Skylake, Broxton, Apollo Lake Gen 9.5 Kaby Lake, Coffee Lake, Gemini Lake Gen 10 Cannon Lake !!! 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) and here https://xpenology.com/forum/topic/12679-progress-of-62-loader/?do=findComment&comment=92682 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) 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: Spoiler network: alx aqc111 - new, Aquantia 111U 1/2.5/5G USB nic asix atl1 atl1c atl1e atl2 atlantic ax88179_178a be2net bna bnx2 bnx2x cx82310_eth cxgb cxgb3 cxgb4 dl2k e100 e1000 e1000e - latest enic forcedeth igb - latest ixgbe - latest jme mcs7830 mii mlx_compat mlx4_core mlx4_en mlx5_core mvmdio netxen_nic pcnet32 pegasus plusb qla3xxx qlcnic qlge r8101 r8125 r8152 r8168 - latest r8169 rtl8150 sc92031 sfc skge sky2 tg3 tn40xx - latest !!! (also support for MV phys) vmxnet3 vxlan storage: 3w-9xxx 3w-sas aacraid aic94xx arcmsr BusLogic gdth hpsa hptiop ips isci megaraid megaraid_mbox megaraid_mm megaraid_sas mpt2sas/mpt3sas - tested, working mptsas mvsas mvumi sx8 vmw_pvscsi The old thread as reference !!! 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 DS3615: extra.lzma for loader 1.03b_mod ds3615 DSM 6.2.2 v0.5_test https://gofile.io/d/iQuInV SHA256: BAA019C55B0D4366864DE67E29D45A2F624877726552DA2AD64E4057143DBAF0 Mirrors by @rcached https://clicknupload.cc/h622ubb799on https://dailyuploads.net/wxj8tmyat4te https://usersdrive.com/sdqib92nspf3.html https://www104.zippyshare.com/v/Cdbnh7jR/file.html DS3617: extra.lzma for loader 1.03b_mod ds3617 DSM 6.2.2 v0.5_test https://gofile.io/d/blXT9f SHA256: 4A2922F5181B3DB604262236CE70BA7B1927A829B9C67F53B613F40C85DA9209 Mirrors by @rcached https://clicknupload.cc/0z7bf9stycr7 https://dailyuploads.net/68fdx8vuwx7y https://usersdrive.com/jh1pkd33tmx0.html https://www104.zippyshare.com/v/twDIrPXu/file.html Edited January 24, 2022 by IG-88 new links 25 16 1 Quote Link to comment Share on other sites More sharing options...
Mell1ej Posted October 7, 2019 Share #2 Posted October 7, 2019 Nice! Any idea about when you'll be able to release the 3617 version? Also, could you please enable the virtio_* drivers? This would be helpful for promox/kvm etc. users 1 Quote Link to comment Share on other sites More sharing options...
IG-88 Posted October 7, 2019 Author Share #3 Posted October 7, 2019 1 hour ago, Mell1ej said: ice! Any idea about when you'll be able to release the 3617 version? i hope next weekend 1 hour ago, Mell1ej said: Also, could you please enable the virtio_* drivers? This would be helpful for promox/kvm etc. users last thing i remember from last year is that i compiled some of this but people got nowhere with it because the kernel options in the synology kernel where not set (we cant change the kernel), but we might try later again atm i want to do the drivers for 3615/17, then some newer versions of drivers people need 1 Quote Link to comment Share on other sites More sharing options...
Mell1ej Posted October 7, 2019 Share #4 Posted October 7, 2019 (edited) 25 minutes ago, IG-88 said: last thing i remember from last year is that i compiled some of this but people got nowhere with it because the kernel options in the synology kernel where not set (we cant change the kernel), but we might try later again I've been messing around with the sources, and have been able to compile the virtio drivers, and succesfully load them into the kernel. Everything loaded fine, and no errors where thrown, however, no virtio devices (ethernet, disk) actually work. Is this the same problem you've had before? Why can't we compile a new zImage? I can't seem to find a tutorial anywhere? I'm guesing a simple "CROSS_COMPILE=... make zImage" won't work? 25 minutes ago, IG-88 said: i hope next weekend Good news! Edited October 7, 2019 by Mell1ej Quote Link to comment Share on other sites More sharing options...
IG-88 Posted October 7, 2019 Author Share #5 Posted October 7, 2019 1 hour ago, Mell1ej said: Why can't we compile a new zImage? I can't seem to find a tutorial anywhere synology protects its dsm system, we are using the original dsm files from them so it needs a hack to circumvent this protections its supposed to still look like its running on a original hardware, so the kernel is still the original and all checks (at least on loading) will signal that the integrity is intact i guess its much easier to just squeeze around the protection then completely analyze everything and build a whole new system, especially as synology is not releasing the whole source, there is no new kernel source for dsm for about 2 years now its a hacked appliance, not a linux distribution, if you are looking for something open then open media vault or maybe freenas might be more interesting Quote Link to comment Share on other sites More sharing options...
Mell1ej Posted October 8, 2019 Share #6 Posted October 8, 2019 (edited) Ahh oke, i did'nt know that synology did those checks, thanks for clarifying. The checks are done in DSM? Then kexec also will also not do much good..? 14 hours ago, IG-88 said: if you are looking for something open then open media vault or maybe freenas might be more interesting I've been happely running a 3617 vm in proxmox for quite some time now Edited October 8, 2019 by Mell1ej Quote Link to comment Share on other sites More sharing options...
swanbird Posted October 8, 2019 Share #7 Posted October 8, 2019 Did ata_piix work in 1.04b? I try it in 1.03b 3517, it work well in 6.2, not in 6.2.1+ because my nic not intel Quote Link to comment Share on other sites More sharing options...
IG-88 Posted October 8, 2019 Author Share #8 Posted October 8, 2019 (edited) ata_piix is still in the same state as documented in the old 918+ thread i guess it will present in 3615/17 extra.lzma (work in progress) […] Either confirmed by users that it is not working OR not supported for DSM 6.2 (kernel 4.4.59) OR does not load at all. Driver was compiled/tested but removed - if someone finds a way to get it working in some way, tell us here and it will be added 30 minutes ago, swanbird said: because my nic not intel whats your nic, i guess it should work with the new 6.2.2 capable extra.lzma if it did in the old one Edited October 8, 2019 by IG-88 Quote Link to comment Share on other sites More sharing options...
swanbird Posted October 8, 2019 Share #9 Posted October 8, 2019 6 minutes ago, IG-88 said: whats your nic, i guess it should work with the new 6.2.2 capable extra.lzma if it did in the old one rtl8111D Quote Link to comment Share on other sites More sharing options...
IG-88 Posted October 8, 2019 Author Share #10 Posted October 8, 2019 juns 1.03b had 8.045.08, i do have that as source too but plan to use 8.047.01 i also have a realtek for testing here so i will check on this one (its also very common) Quote Link to comment Share on other sites More sharing options...
swanbird Posted October 9, 2019 Share #11 Posted October 9, 2019 7 hours ago, IG-88 said: juns 1.03b had 8.045.08, i do have that as source too but plan to use 8.047.01 i also have a realtek for testing here so i will check on this one (its also very common) Thanks for your good job!waiting good news.. Quote Link to comment Share on other sites More sharing options...
Hostilian Posted October 15, 2019 Share #12 Posted October 15, 2019 (edited) Good job! Looking for Intel 82579LM drivers for 1.03b loader - DS3617.. (Might be e1000e)Any plans to add these in - or might anyone have a set of drivers please? Edited October 15, 2019 by Hostilian Quote Link to comment Share on other sites More sharing options...
Snowail Posted October 15, 2019 Share #13 Posted October 15, 2019 Great Work!! Waiting for fix igb driver, a lot of people here are using INTEL I211 nic ~ Quote Link to comment Share on other sites More sharing options...
altas Posted October 25, 2019 Share #14 Posted October 25, 2019 New News about the Driver release for 3615/17 ? Quote Link to comment Share on other sites More sharing options...
typer77 Posted October 27, 2019 Share #15 Posted October 27, 2019 Eagerly awaiting here too. :) Quote Link to comment Share on other sites More sharing options...
heroares Posted October 28, 2019 Share #16 Posted October 28, 2019 Thank you very much And Can my XG-C100C network card be supported? Quote Link to comment Share on other sites More sharing options...
kazuni Posted November 1, 2019 Share #17 Posted November 1, 2019 (edited) are there compiled vmxnet3 modules for DS3615xs / 1.03b? as I'm still on older hardware (xeon v2) and would like to use vmxnet3, thanks! Edited November 1, 2019 by kazuni Quote Link to comment Share on other sites More sharing options...
IG-88 Posted November 1, 2019 Author Share #18 Posted November 1, 2019 1 hour ago, kazuni said: are there compiled vmxnet3 modules for DS3615xs / 1.03b? yes Quote Link to comment Share on other sites More sharing options...
kazuni Posted November 1, 2019 Share #19 Posted November 1, 2019 (edited) 6 minutes ago, IG-88 said: yes Thanks, but I think I shall rephrase, I checked that there are, but I don't think it will work on anything beyond 6.2? (Tried 6.2.1 and 6.2.2, both got reported OOOFs during dmesg, even tho they are using the same kernel), and to be exact, dmesg is as attached. Edited November 1, 2019 by kazuni Quote Link to comment Share on other sites More sharing options...
IG-88 Posted November 1, 2019 Author Share #20 Posted November 1, 2019 i already have driver packages 3615/17 for 6.2.2 the new extra/extra2 for 918+ contains new modules for vmware and the 3615/17 will also have the normal set of drivers after finding the problem with the 3617 drivers and having a fresh install working i'm now testing the migration's from 6.1.x and 6.2.0 i dont want people to end up with semi-bricks and the need to downgrade 3 1 Quote Link to comment Share on other sites More sharing options...
kazuni Posted November 1, 2019 Share #21 Posted November 1, 2019 Much appreciated, I shall wait for the release for 3615 then, Quote Link to comment Share on other sites More sharing options...
xexen Posted November 2, 2019 Share #22 Posted November 2, 2019 On 11/1/2019 at 2:14 AM, IG-88 said: i already have driver packages 3615/17 for 6.2.2 the new extra/extra2 for 918+ contains new modules for vmware and the 3615/17 will also have the normal set of drivers after finding the problem with the 3617 drivers and having a fresh install working i'm now testing the migration's from 6.1.x and 6.2.0 i dont want people to end up with semi-bricks and the need to downgrade Would you mind sending me the driver package you have for 3615/17 for 6.2.2. I built a test system on an old Acer Veriton m4620G which I think is using a BCM5761 ethernet chip. It is a fresh install, but I can install 6.1.x and do a migration test. Quote Link to comment Share on other sites More sharing options...
Guest Posted November 4, 2019 Share #23 Posted November 4, 2019 On 10/6/2019 at 9:07 PM, IG-88 said: ..... extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.2 v0.6_test http://s000.tinyupload.com/?file_id=29784352988385987676 ............... Sorry for my stupid question. How use/handle I this driver extension file after download and unzip? How to put it it on booting usb stick ? I use Synologolgy/Xpenology a longer time but I have no Idea how and where to add driver extension file. Quote Link to comment Share on other sites More sharing options...
IG-88 Posted November 4, 2019 Author Share #24 Posted November 4, 2019 2 hours ago, sunshine said: How to put it it on booting usb stick ? I use Synologolgy/Xpenology a longer time but I have no Idea how and where to add driver extension file. if you don't know then its not for you (at least for now), its just for testing and its a little vague on purpose you need to read the tutorial for installing dsm 6.1 and the description of the former (safer) extra.lzma's atm im working on the 3615/17 versions but i already know what i want to do for the next 918+ version please just wait a while until we got more feedback and better versions, its not ready for normal use yet Quote Link to comment Share on other sites More sharing options...
Guest Posted November 5, 2019 Share #25 Posted November 5, 2019 Thanks for your quick answer. It seems its too difficult for me and I wait. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.