IG-88

not too bad, you just "loose" one pcie 1x slot, things like 6xsata, pcie 16x and pcie4x (open at the end so it can take 8x/16x cards) and M.2 is there too so you might keep it, close enough when it comes to add storage and 10G nic no, it was B365M-HD3, skipping the "M" will end you with a completely different product in this case like https://www.gigabyte.com/Motherboard/B365-HD3-rev-10 instead of https://www.gigabyte.com/Motherboard/B365M-HD3-rev-10 you can stay with the B365M DS 3H as you only miss a 1x slot and that would probably stay unused anyway

thats just a small change in synoinfo.conf that a documented, i use 3 nic's in my 918+ system i reference to this in the 1st post in the thread about 6.2.2 https://xpenology.com/forum/topic/12679-progress-of-62-loader/page/9/?tab=comments#comment-92682 yes i guessed that from your cpu, but the limit is not about "threads" ts just cores, the kernel config states 8 cores for 918+ so if you disable HT you can have all 6 cores used in 918+ and would loose only minor performance as HT is far from that much of a gain

da müssen wir mal auseinander dröseln, bootet es immer den loader und man sieht die grub auswahl und die happy hacking nachricht (dann hat es nichts it der boot selection zu tun) oder startet es gelgentlich nicht den loader hast du ein nullmodem kabe und das board einen seriellen anschluss? man kann den boot prozess nur über seriell verfolgen und sich sogar an der console anmelden und netwerk checken, dmesg ansehen usw. wenn es nicht richtig startet gibt es dann plattenaktivität die anzeigt das dsam an sich startert aber evtl. nur kein netzerk hat? man sollte solche vorgänge im log sehen und prüfen können ob z.b. der netzwerktreiber oder was anderes nicht richtig geladen wurden

i've seen one case where a cooler came loose and hat a loose fit, resulting in switch off's because of overheating so check the mounting of the cooler too

you dont give much deail about your hardware (like system board) a guess would be that for 6.2 you need to use CMS/legacy mode, not uefi and you need to boot from the "non uefi" usb device, in some cases you will see that legacy boot device only after rebooting with active csm mode the difference with the loader is documented here https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ also try dsm 6.2.0 or 6.2.3 when not using any different extra.lzma when using 6.2.2 you will need a different extra.lzma as drivers are different for this version, but with dms 6.2.3 it's back to normal an 6.2.2 is obsolete

no drivers crashing, some acpi errors i'd need to compare with a test system (i'm testing 315/17 new extra.lzma, so additional work as i'm looking into demsg anyway) maybe you can try to reduce some acpi / power management features in bios for testing, 3617 has a older kernel then 918+, like using older or dumped down acpi version maybe disabling HT and using 918+ is a option (when shutdown is working with it)

dmesg | more space to scroll page, strg-c to end it its also a file /var/log/dmesg

there might be dependency that is missing or some specific changes in th source by synology that is missing in this module as synology did not used/need it i will look for a dependency, it its a source problem there is nothing i can do about it looks like it would need to replace other cpu-frequ driver files too (coming from synology) cpufreq_stats.ko cpufreq_powersave.ko cpufreq_performance.ko acpi-cpufreq.ko that might interfere with other things, so i#m not going to do this in a new extra/extra2 and without any substantial plan what its good for and how to use it im's not goint to invest any more time into this @deadsquirrel what exactly is you plan for using this? i guess it would need more additional code in the system to make use of it i can send you the files if you want to experiment on your own

the occurrence of ram problems can depend on type of system usage and operating system i'd suggest doing a ram test (often live linux system have a option for memtest when booting), check for funny looking capacitors on the system board and if possible exchange psu with another computer for testing

ja. würde ich den dem fall machen, sorge dafür das der usb immer benutzt wird (alles andere macht auch keinen sinn denn es gibt ja kein andere bootfähiges medium)

that are lib's (.so files are dynamic libraries), independent from the driver and might be newer then the used (backported) driver from synology so they may contain references to newer hardware i don't think a lib will be working without a driver and the i915 is the driver for this hardware, its all UHD 630, maybe intel decided on some minor changes and gave it a new number the name i965 is used since intel graphics gen 4, so its no new standalone kernel driver for any newer hardware imho differentiating start with x11 and there might be different x11 drivers depending on the intel graphiccs gen (intel, intel 915, intel 965), but the kernel driver is all the same and the base

thats usually because of drivers crashing an boot, check dmesg so find it maybe some left overs from 918+ driver set that are still loaded a safe choice is also to empty /usr/lib/modules/update/ and reboot the loader will copy all missing files from the extra.lzma on boot back and you get rid of any left overs

yes, and slight correction, the (new) i915 driver is a "native" driver from synology originally made for geminilake units like the new DS x20+ the 0.11 extra/extra2 makes sure jun's i915 (not compatible with 6.2.3) gets deleted so the native driver from synology is loaded i dont think that will help you, without a kernel driver you won't be able to use it

if you are on 6.2.2 now and want to use 6.2.3 then you will need the old extra.lzma that was originally on the 2nd partition (con be copied from the img file by opening it wth 7zip) the 6.2.2 was special with its drivers, 6.2.3 reverted that change so old drivers are working again

install 6.2.3 25426, the 24922 (aka 6.2.2) needs different driver (extra.lzma), when using 6.2.3 the "old" driver package that is default on the loader will work again and the onboard nic will work

maybe just buy a marvell 88se9215 based controller for you pcie slot https://sybausa.com/index.php?route=product/product&product_id=775 (btw. thats the same chip as in the original 918+)

hallo, das gleich kann man auch mit diesem tool machen (nutze ich seit einer weile da Win10 mittlerweile weder die erste noch die zweite partition mountet) http://www.ext2fsd.com bei mir konnte ich nicht einfach mit dem angemeldeten user auf das neue laufwerk der ersten partition zugreifen aber wenn ich notepad++ mit erhöhten rechten starte kann ich die grub.cfg laden und ändern außerdem kann man nach dem mounten der ersten partition wieder mit "Win32DiskImager" den stick lesen um ein backup zu erzeugen

i did not change anything in that direction and its a generic driver, maybe a difference is between the 1st 6.2.3. v25423 and the 2nd 25426? there might be dependency that is missing or some specific changes in th source by synology that is missing in this module as synology did not used/need it i will look for a dependency, it its a source problem there is nothing i can do about it lsi sas connected or ahci?

i have a i3 9100 https://en.wikichip.org/wiki/intel/core_i3/i3-9100 pcie id for the gpu is "3E91" yours https://en.wikichip.org/wiki/intel/core_i5/i5-9600k pcie id for the gpu is "3E98" i looked up that number in the driver 915.ko with a editor i only find he UHD 630 id for the 9100, the UHD 630 id of the 9600k is not listed that might explain why its not found, is not supported in the driver its the same with jun's i915 driver (slightly newer source), do downgrading would not change anything the 3e98 is also used in other cpu's (that might be avoided i5-9400 i5-9600k i7-9700t i7-9700 lucky me, i was thinking about a 9400 instead of 9100 a bought

i've now set up my own nas for hibernation i did need to extend the synoinfo.conf for my 3rd nic (defaul 918+ is max 2, 3615/17 has max.8) that is handling the normal network trafic, to activate WOL and after that i could enable hibernation set it so minimum (10 min) and after rebooting and a normal shutdwon i tested WOL, it dis wake up and after this a let the box without activity and it was going to hibernation after a while, did wake it up with WOL again and checked the log - no problem, seems to work (with the 0.11 extra/extra2) and so my conclusion is that its not a general problem (never used this for years, i use the acpi power button for start and shutdown) some messages from log center in gui 2020-05-20 00:19:27 Internal disks woke up from hibernation. 2020-05-19 23:39:26 System started to boot up. 2020-05-19 23:34:35 System started to shutdown due to auto poweroff time up 2020-05-19 23:34:35 Server started counting down to shutdown. 2020-05-19 22:55:09 Internal disks woke up from hibernation.

ja, seit anfang 2020 ist win10 zickig und ordnet keinen laufwekrsbuchstaben mehr zu "Ext2 Volume Manager" (http://www.ext2fsd.com) installieren und der ersten partition einen buchstaben zuordnen, dann kann man wieder mit "Win32DiskImager 1.0" den stick einlesen es gingen auch recovery tools die image files erzeugen können (z.b. DMDE, https://dmde.com, free edition), da muss man dann den lesebereich begrenzen so das hinter der dritten partition aufgehört wird zu lesen (kommt ja nix mehr, wäre beim 918+ image sektor 102366) - und natürlich geht auf dd unter linux wenn du vom alten die grub.cfg holst (1. partition) und von der 2. partition die extra/extra2 und zImage+rd.gz solltest du auch das default image nehmen können (und dann mit osfmount die datein draufspielen) man kann den stick übrigens auch in dsm mounten (oder einen anderen linux) mkdir -p /mnt/synoboot1 mkdir -p /mnt/synoboot2 echo 1 > /proc/sys/kernel/syno_install_flag mount /dev/synoboot1 /mnt/synoboot1 mount /dev/synoboot2 /mnt/synoboot2

ahh, good, 1st thing you are using jun's drivers now (i'm not to blame;-)), also you are using synology's new kernel of 6.2.3 of witch we dont have the config (no 6.2.3 toolchains) for 1.04b/918+ i used the same kernel config as for 6.2.2 but removed the change about CONFIG_PCIEASPM the fact that it happen on 918+ and 3615 might point to the kernel (source, that we dont have, the 3/2020 release is for 6.2.2) and we dont have the kernel config synology used to build the kernel for 6.2.3 that's just the boot process, i mend to get the log for a attempt to go into hibernation to took a error message that prevents the process to work the boot log at least say's - or is it about he hibernation option grayed out under hardware and power / hdd hibernation? on my new hardware i can't enable wol waht is needed for hibernation ... [ 0.259175] ACPI: (supports S0 S4 S5) ... S4 is hibernation aka suspend to disk is possible when it comes to acpi

??? im bios? und worauf beziehen sich die zahlen?

i talked about using the same dsm version but 3617 instead of 3615, you would need to change the loader (same version but for 3617) no use of 8 is hardcoded into the kernel of 3615, nothing you can do about it beside cross update to 3617

i'm pretty sure you know clearly what dsm version and extra you had before (when is last worked) and what hardware you use - but you need to tell other people if you talking about a problem, also a log would be good to see whats going on