IG-88

from my point of view the drivers (kernel) are not related to the DSM package center, thats just a application inside DSM there should be no difference using jun's extra.lzma or mine, i've not changed anything beside driver (*.ko) files and the "rc.modules" (containing the names of drivers and firmware loaded)

if you look here in the network driver list here https://xpenology.com/forum/topic/12859-driver-extension-jun-103a2dsm62x-for-ds918/ you will find that it is sky2.ko and skge.ko what you ask for when in doubt you can open the extra.lzma with 7zip and check if the files are in and they are present so you might try the new extra.lzma for 6.2.2 with a fresh test install to a empty disk or even just boot up a fresh prepared usb to check if you can find the system in network. no need to install anything if you want to know that the network driver is working, most important part is to copy the 6.2.2 zImage and rd.gz to the usb together with the new extra.lzma

there is no guarantee for that, there is just one person doing it and maybe he has no time or is not interested in that stuff anymore (job, marriage, children - you know life is changing) and it also depends on the amount of protection, lets say they use more advanced tech like TPM's, its still possible but might get harder to break in that its not worth the effort, DSM is not iOS, the amount of people interested in that stuff is limited and there are plenty alternatives around (like OMV, FeeNAS, NAS4Free, ...)

don't count on that, even if someone (jun?) does a hack it will not be released before the official dsm 7.0 release also there is no kernel source available, even the kernel code we use now is from beta 6.0, looks like synology does not mind the GPL

no need to change anything if you dont need the pcie slot and the additional power consumtion (3-5W?) is no concern for you dont try to fix anything that is not broken

i did drivers for Aquantia AQC111U (5Gbp) on request and they are in the latest driver extension (you can search here for aqc111) but an the other side of the (copper) cable you need a nic or switch that is aware of IEEE 802.3bz,NBASE-T thats the adapters i know about: QNAP QNA-UC5G1T TRENDnet TUC-ET5G not 10G but close enough - if your notebook supports usb3

usually you dont need new drivers or a new loader when keeping inside a major version like 6.2 we did not have this kind of problem/change inside 6.0 or 6.1 line i don't expect that synology will do much, they are busy bringing up 7.0 and that will usually need a new loader/hack/driver pack i have read about 2 people having problems with plugins after migrating from 6.1 in the last week, not seen someone commenting on that, i don't see a connection to drivers here so its not really my department, my update tests where usually just without additional packages and i'm not sure i even opened the package center see above, all microserver have broadcom nic's onboard using tg3.ko as driver

after this you could only see more an a serial connected console (null modem cable) so it normal that it "stops" you should see the system in network after ~2-3 minutes, check your dhcp server or/and use synology assistant (program can be downloaded from synology) the network chip is realtek, should work in bios you the sata settings nee to be AHCI in theory you could also use 1.04b loader and 918+ image (you have a 4th gen intel cpu) just for testing about network and storage you dent need to bother vid/pid or serial or mac wrong vid/pid will result in error after ~50% installing at this point you already know whats needed, network works, disk can be detected serial is only needed for same codecs and specials, basic nas will work without a valid one, mac is only needed if you use WOL but its better to fill in the real mac anyway so for quick testing dont mess around with the grub.cfg, only takes time 1st step is to find it in network and you dont need to customize grubfgt for this when dsm 6.2 is tested then use v23739 with the loader to use 24922 it needs more steps as it needs different drivers https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

what hardware do you use? did you try the already released 0.5 version?

as i have no reliable information what exactly is checked, i can't make a guess why not use jun's 1.03b for ds3615 loader?

kind of reference to freenas from your footnote, there are other "free" nas systems, some are not such a closed source appliance as DSM is https://www.openmediavault.org its a real open source one (so not that much driver problems) and the gui is good too still my fall back plan when DSM fails or i cant use DSM anymore

yes, also to consider is the power consumption and heat is produces (often equals noise level) having a system wasting 60 watt, 24h, 7days a week for years ... also xeon mainboards are often more expansive and ecc ram also adds to that beside virtualization as with VMM there is also docker, that seems to used a lot lately instead of synology specific packages, but in most cases more ram is far better then more cpu cores (there might be some cases where 4 cores is not enough when having multi user streaming with transcoding and lots o home automation vm's in background) just as file server and some streaming (without transcoding or using hardware support for transcoding) even a 2 core system can do it i've seen it be used as webserver for a online shop or lately one user had a 16 SSD's with a 40BGit nic hardware (i didn't wanted to be nosy so i did not ask what he wanted to do with it) i guess in most cases 4 cores of a 8 core system (in home use) are there just to make sure the owner has a better sleep, as long he is not concerned about global warming :-))) to small, to slow (i'm using a 12 disk system with 10G network) why? what about open media vault?

NO NECESSARY INFORMATION GIVEN ;-)

looks like a hardware or driver related problem the section about the driver loading is missing (for e1000e) whats the version number you see in the log? also there should be no odd comments when the driver loads if you are not using additional drivers (as it looks to me) you can copy the extra/extra2.lzma files from here https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ to your usb (2nd partition, it should be accessible on a windows computer), overwrite the existing files (extra/extra2) and reboot as the driver 3.6.0 in that package is recent it might work then (you should see a change in version number in log when the driver loads) whats the exact hardware you are using (board, nic, storage)?

it does work on 3615/17 and also does on my current test version for 918+ (6.2.2) atm i'm using juns mpt3sas driver and i have no clue whey my compiled drivers do not work (kernel oops when drive is attached to controller) if we get no (recent) kernel source from synology and they alter things further then there might be no way for dsm versions that do not come with lsi support (like 918+) i got a 8 port ahci controller for my new build (additional network drivers seem to be no problem) https://xpenology.com/forum/topic/19854-sata-controllers-not-recognized/?do=findComment&comment=122709

there are newer bnx2 drivers then the one from kernel like netxtreme2-7.14.53 (bnx2-2.713.21) willing to test if i make a new version?

das ist normal, die sind ja nicht zwangsläufig mit 6.2 compatibel und mache (wie power button) instalieren unterschiedliches je nach dsm version es kann sogar passiren das es manche pakete gar nicht für 6.2 gibt nicht funktionierende pakete deinstalliert man und reinstalliert sie, in den mesiten fällen geht das das ist eine dsm eigene funktion und sollte eher nicht passieren, gibts fehlermeldungen? irgendlwelche logs geprüft? nein, migrieren isr schon der normalfall, neuinstallation verwirft alle einstellungen/pakete, angelegte user, shares usw., das macht man nur wenn man auf nummer sicher gehen will oder probleme hat, bedeutet halt das man alle seine anpassungen noch mal von hand machen muss bei einem reinstall werden die raid arrays mit den daten nicht angefasst, sa wird nur system neu aufgespielt dann ist zurücksetzen die beste wahl, es kann haarig werden manche probleme nach einem update zu finden, wenn nicht viel konfiguriert ist dann mit default starten am besten

if you block the 16x pcie slot with the controller you cant have aother 4x card for 10G network or another 4x storage controller i used this one https://www.gigabyte.com/Motherboard/B360M-HD3-rev-10 more or less the same https://www.gigabyte.com/Motherboard/B365M-HD3-rev-10 thats the same as the one you already have, you will depend on a working mpt2sas/mpt3sas driver and atm its a little unclear how scsi/sas added drivers will develop, there are present/working for 6.2.2 now (mpt2sas/mpt3sys) but on long term a ahci solution is a safe choice as it will work with dsm ootb as synology uses ahci for there own boxes, mpt drivers are only ootb supported on some units, mainly business units you might read about "native" drivers here https://xpenology.com/forum/topic/14127-guide-to-native-drivers-dsm-621-on-ds918/

afair from jun's inforamtion about hacking dsm, the protection checks about the presence of pci devices to check, so even if you get it starting somehow you might fail to get it running as of differences in hardware between 1511+/1512+

if possible dont use mini-itx board, use something with more pcie slots so you can extend for controller or 10G nic (pcie 4x/8x) think about using a 8 port ahci controller, ahci does not need any additional drivers to run dsm, less dependencies i found 2 good looking candidates https://xpenology.com/forum/topic/19854-sata-controllers-not-recognized/?do=findComment&comment=122709 if there are enough pcie slots then also 2x4port controller might be a option

that sound pretty "adventurous", what hp controller is this? so you use the backplane's sas connector of the 2nd unit to connect to the sas controller of the 1st unit (that is running dsm)? 250GB ssd is used on internat sata of 2nd unit and uses the mainboard (without the backplane) there are SAS housings for cases like this https://www.silverstonetek.com/product.php?pid=423&bno=74&tb=32&area=en (imho there are not much affordable choices when it hast to be a sas enclosure) also depending on what kind of build you plan something like this can be useful (there are different brands for a thing like this) https://www.silverstonetek.com/product.php?pid=885&area=en

just remove the button.ko and evdev.ko from /usr/lib/modules there are new one in /usr/lib/modules/update already the plugin is not aware of the changes of 6.2.2 and blindly overwrites with old 6.2.0 files the rest is fine, after removing the old/wrong files and rebooting your system should be able to use acpi power off i'm using this with my dsm test vm's in virtualbox the plugin needs to be extended for 6.2.2 and needs new button.ko/evdev.ko files (can be extraxted from my extra.lzma's)

not anymore there are drivers for 6.2.2 now, with that internal broadcom nic should work with the latest 6.2.2 https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

i found out some more (most firmware file id's where ending on "L" like Lake) bxt -> Broxton (Goldmont line, same as Apollolake but Broxton was cancelled) cml -> Cometlake (2020+) cnl -> Cannonlake ehl -> Elkhartlake (Goldmont line, Denverton successor, 2020+) glk -> Geminilake (Goldmont Plus line) icl -> Icelake kbl -> Kabylake (also for Coffeelake because of same GPU?) skl -> Skylake tgl -> Tigerlake (2020+) dmc -> Display Microcontroller guc -> Graphics micro (µ) Controlle huc -> HEVC/H.265 micro (µ) Controller https://en.wikichip.org/wiki/intel/microarchitectures https://en.wikipedia.org/wiki/Ice_Lake_(microarchitecture) https://github.com/wkennington/linux-firmware/tree/master/i915 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 https://01.org/linuxgraphics/downloads/firmware 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 looks like the original driver is usable up to kabylake with the right firmware and jun's driver is good up to icelake but it might depend on the pci id's used, so newer icelake versions having a new identifier might not work even if being icelake firmware referenced in driver i915.ko synology DSM: bxt_dmc_ver1_07.bin bxt_guc_ver8_7.bin kbl_dmc_ver1_01.bin kbl_guc_ver9_14.bin skl_dmc_ver1_26.bin skl_guc_ver6_1.bin Synology delivered firmware files with DSM: bxt_dmc_ver1_07.bin glk_dmc_ver1_04.bin -> not used by driver referenced firmware files in jun's i915.ko: bxt_dmc_ver1_07.bin bxt_guc_ver9_29.bin bxt_huc_ver01_07_1398.bin cnl_dmc_ver1_07.bin glk_dmc_ver1_04.bin kbl_dmc_ver1_04.bin kbl_guc_ver9_39.bin kbl_huc_ver02_00_1810.bin skl_dmc_ver1_27.bin skl_guc_ver9_33.bin skl_huc_ver01_07_1398.bin jun's firmware files in rc.modules with extra.lzma: bxt_dmc_ver1_07.bin bxt_guc_ver9_29.bin bxt_huc_ver01_07_1398.bin cnl_dmc_ver1_07.bin glk_dmc_ver1_04.bin kbl_dmc_ver1_04.bin kbl_guc_ver9_39.bin kbl_huc_ver02_00_1810.bin skl_dmc_ver1_27.bin skl_guc_ver9_33.bin skl_huc_ver01_07_1398.bin

was für datei typen sind betroffen? was verwendest du zum steamen? schon mal plex versucht?