Hackaro

My main machine is a Mac one. I've installed HomeBrew and followed these instructions . At this point I'm completely stuck because if I put my NAS IP's address in Safari browser's window on port 7681 I get repeatedly two messages: "connection closed" "315x67" which tells me the problem occurs on my NAS. I can confirm you that ttyd has been installed on NAS side during TC installation: ------- [#] Downloading remote file https://github.com/tsl0922/ttyd/releases/download/1.6.3/ttyd.x86_64 to /home/tc/redpill-load/custom/extensions/redpill-misc/ds920p_42218/ttyd ######################################################################################################################### 100.0% ------- But, as you can see, with the command: "systemctl status ttyd" I get this result: ● ttyd.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) ----- So it seems to me that the service is not loaded. Any hint? What am I doing wrong?

@giacomoleopardo @Peter Suh AFAIK the NVMe cache support is very well implemented in DS918+ with all the DSM up to the current 7.1 version; It's based upon the patching process of the libsynonvme.so.1 file in /usr/lib64 dir with the correct PCI addresses (related to your motherboard). As for DS920+ (or other models too), the same libsynonvme.so.1 file doesn't contain ANY DSxxx model's reference inside its binary contents, so that the patching process is not available anymore. This leave the chances to have a correct NVMe cache support to only one method (at least that I Know!): to modify or to create, if it doesn't exist, the following file: /etc.defaults/ConfigurationPorts to add the correct PCI addresses of NVMe's drives, i.e. : [PCI] pci1="0000:00:001b" pci2="0000:00:001c" does anyone have experience with this latest process? how does the ARPL's fabio's dtbpatch ext. can get the job done automatically? And what can we do if the patch doesn't work? Thanks in advance to all who will answer.

I guess the best thread to continue this discussion about NVMe already exists and it's this one: NVME-CACHE-SUPPORT, I'll write my observations there and I invite you and @Peter Suh to do the same.

YES!!!! this is quite interesting!!! I know that my 918+ has NVMe hardcoded in libnvme.sys but which other models have the same charateristics so that they are patchable with an hex editor?

So according to you @Peter Suh and @IG-88 which is the low cost PCI SATA cards which are really compatible at the moment? An additional 6/8 ports would be very welcome. Consider that I'd like to stay on DS918+ model because I have real S/N for it but I might evaluate a change if it's really needed.

yeah... I'm interested as well as I've just bout a Marvell controller with 6 ports and I'm planning to add it to my Xpenology DS918+ (see my signature). If there is a way to mod jumkey.qjs.dtb file for DS918 in order to correctly see all the ports of Marvell controllers would be very nice!

@pocopico @giacomoleopardo yes, AHCI is compiled in Synology kernel and Marvell controllers are natively supported. But are we sure that all the ports are hardcoded in Synology DSM's files? Or maybe some (all?) ports needs to be correctly addressed modifying some binaries so that DSM can "see" all the mapped ports?

@IG-88 thanks for the reply! ... not sure if I understood correctly but yesterday I noticed this error and maybe it's related to the discussion we're having here: dmesg | grep error [ 1.610201] intel-lpss: probe of 0001:00:16.0 failed with error -22 [ 1.610298] intel-lpss: probe of 0001:00:18.0 failed with error -22 [ 1.610411] intel-lpss: probe of 0001:00:19.0 failed with error -22 [ 1.610708] intel-lpss: probe of 0001:00:19.2 failed with error -22 [ 4.155854] ahci: probe of 0001:01:00.0 failed with error -22 [ 4.155945] ahci: probe of 0001:00:12.0 failed with error -22 [ 4.407352] xhci_hcd: probe of 0001:00:15.0 failed with error -16 [ 4.462722] igb: probe of 0001:02:00.0 failed with error -5 [ 4.462811] igb: probe of 0001:03:00.0 failed with error -5 [ 17.328835] i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2 look at the last line's error. And in fact: :/lib/firmware/i915# dir total 32 drwxr-xr-x 2 root root 4096 Mar 14 18:29 . drwxr-xr-x 3 root root 4096 Mar 14 18:29 .. -rwxr-xr-x 1 root root 8380 Jan 18 2021 bxt_dmc_ver1_07.bin -rwxr-xr-x 1 root root 8800 Jan 18 2021 glk_dmc_ver1_04.bin so the file kbl_dmc_ver1_04.bin is missing, as you said. So I just add that file and I'm done, correct? Even if i3-8100 is not a kbl (kaByLake) but Coffee Lake?

Thanks! @RedwinX Recently I've installed RedPill-TC (0.46-uefi version) with DSM 7.0.1-42818 on my hardware (in signature) and everything is working pretty well after one month of testing. But one small problem is with HW acceleration of my iGPU... my CPU is an i3-8100 and its Device ID is 3e91 which is supported OOB from Synology DSM (at least the 6.x version). lspci -nnQ 0000:00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core 4-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] [8086:3e1f] (rev 08) 0000:00:02.0 VGA compatible controller [0300]: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] [8086:3e91] but if I check: more /usr/syno/etc/codec/activation.conf {"success":false,"msg":"SN format is wrong."} it seems there is no HW acceleration... even if this check of the presence of dev/dri: ls -al /dev/dri total 0 drwxr-xr-x 2 root root 80 Mar 25 10:47 . drwxr-xr-x 12 root root 14440 Mar 25 10:48 .. crw------- 1 root root 226, 0 Mar 25 10:47 card0 crw-rw---- 1 root videodriver 226, 128 Mar 25 10:47 renderD128 which might indicate me that the HW GPU acceleration is in place. Using VideoStation I can see it can transcode FHD H.264 movies with roughly 25/26% of CPU utilisation, which is significant higher than expected for a 4 cores CPU. Can someone help me in going in the right direction?

how have you modded i915.ko? @RedwinX

I'm working on a XPE 918+ and I do have Marvell9215 but I guess it's because it's builtin hardware directly in the .pat file of this specific DS918 version of DSM 7.0.1 . In other words DSM loads Marvell SATA controller because it knows a real DS918 has a Marvell controller among its peripherals. it loads without checking a real presence of that peripheral, just because it's built-in. I was wondering whether I really insert a PCI Marvell 9215 controller card, Synology DSM correctly recognises it in the appropriate PCI address...

@pocopico @IG-88 Recently I've installed RedPill-TC (0.46-uefi version) with DSM 7.0.1-42818 on my hardware (in signature) and everything is working pretty well after one month of testing. But one small problem is with HW acceleration of my iGPU... my CPU is an i3-8100 and its Device ID is 3e91 which, from this old (DSM 6.2.x) link , is supported OOB from Synology DSM (at least the 6.x version). but if I check: more /usr/syno/etc/codec/activation.conf {"success":false,"msg":"SN format is wrong."} but if I check the presence of dev/dri: /dev/dri# dir total 0 drwxr-xr-x 2 root root 80 Mar 25 10:47 . drwxr-xr-x 12 root root 14440 Mar 25 10:48 .. crw------- 1 root root 226, 0 Mar 25 10:47 card0 crw-rw---- 1 root videodriver 226, 128 Mar 25 10:47 renderD128 which might indicate me that the HW GPU acceleration is in place. Using VideoStation I can see it can transcode FHD H.264 movies with roughly 25/26% of CPU utilisation, which is significant higher than expected for a 4 cores CPU. Can someone help me in going in the right direction?

Hi all !!!! just a couple of simple questions: I would like to make a second USB stick as backup, is there any method to duplicate the 1st one? Or Do I have to make all the TC method again? Which one of the HBA LSI or ANY other SATA card can I add at the moment which gives me a fair level of stability with Red-Pill DSM 7.0.1 for 918+ ? thanks in advance!

@jumkey @pocopico I've recompiled and I have: systemctl status acpid.service: • acpid.service - ACPI Daemon Loaded: loaded (/usr/lib/systemd/system/acpid.service; enabled; vendor preset disabled) Active: active (running) since Wed 2022-03-23 17:06:52 CET; 54s ago Process: 7142 ExecStart=/us/sbin/acpid (code=exited, status=0/SUCCESS) Main PID: 7148 (acpid) Group: /system.slice/acpid.service L7148 /usr/sbin/acpid thanks!!!!

Anybody on my ACPI Topic?

systemctl status acpid.service ● acpid.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) and also: Admin@DS918:~$ dmesg | grep -i "acpi" [ 0.000000] BIOS-e820: [mem 0x000000002faed000-0x000000002faedfff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x0000000039205000-0x00000000395adfff] ACPI NVS [ 0.000000] efi: ACPI 2.0=0x39522000 ACPI=0x39522000 SMBIOS=0x39c4e000 SMBIOS 3.0=0x39c4d000 MPS=0xfcb50 ESRT=0x340a2398 [ 0.000000] ACPI: Early table checksum verification disabled [ 0.000000] ACPI: RSDP 0x0000000039522000 000024 (v02 ALASKA) [ 0.000000] ACPI: XSDT 0x00000000395220A8 0000D4 (v01 ALASKA A M I 01072009 AMI 00010013) [ 0.000000] ACPI: FACP 0x0000000039562E68 000114 (v06 ALASKA A M I 01072009 AMI 00010013) [ 0.000000] ACPI: DSDT 0x0000000039522218 040C49 (v02 ALASKA A M I 01072009 INTL 20160527) [ 0.000000] ACPI: FACS 0x00000000395AD080 000040 [ 0.000000] ACPI: APIC 0x0000000039562F80 000084 (v04 ALASKA A M I 01072009 AMI 00010013) [ 0.000000] ACPI: FPDT 0x0000000039563008 000044 (v01 ALASKA A M I 01072009 AMI 00010013) [ 0.000000] ACPI: FIDT 0x0000000039563050 00009C (v01 ALASKA A M I 01072009 AMI 00010013) [ 0.000000] ACPI: MCFG 0x00000000395630F0 00003C (v01 ALASKA A M I 01072009 MSFT 00000097) [ 0.000000] ACPI: SSDT 0x0000000039563130 000204 (v01 ALASKA A M I 00001000 INTL 20160527) [ 0.000000] ACPI: SSDT 0x0000000039563338 0017D5 (v02 ALASKA A M I 00003000 INTL 20160527) [ 0.000000] ACPI: SSDT 0x0000000039564B10 007C36 (v01 ALASKA A M I 00000001 INTL 20160527) [ 0.000000] ACPI: SSDT 0x000000003956C748 0031C7 (v02 ALASKA A M I 00003000 INTL 20160527) [ 0.000000] ACPI: HPET 0x000000003956F910 000038 (v01 ALASKA A M I 00000002 01000013) [ 0.000000] ACPI: SSDT 0x000000003956F948 000F9E (v02 ALASKA A M I 00001000 INTL 20160527) [ 0.000000] ACPI: SSDT 0x00000000395708E8 002D1B (v02 ALASKA A M I 00000000 INTL 20160527) [ 0.000000] ACPI: UEFI 0x0000000039573608 000042 (v01 ALASKA A M I 00000002 01000013) [ 0.000000] ACPI: LPIT 0x0000000039573650 00005C (v01 ALASKA A M I 00000002 01000013) [ 0.000000] ACPI: SSDT 0x00000000395736B0 0027DE (v02 ALASKA A M I 00001000 INTL 20160527) [ 0.000000] ACPI: SSDT 0x0000000039575E90 000FFE (v02 ALASKA A M I 00000000 INTL 20160527) [ 0.000000] ACPI: DBGP 0x0000000039576E90 000034 (v01 ALASKA A M I 00000002 01000013) [ 0.000000] ACPI: DBG2 0x0000000039576EC8 000054 (v00 ALASKA A M I 00000002 01000013) [ 0.000000] ACPI: DMAR 0x0000000039576F20 0000A8 (v01 ALASKA A M I 00000002 01000013) [ 0.000000] ACPI: BGRT 0x0000000039576FC8 000038 (v01 ALASKA A M I 01072009 AMI 00010013) [ 0.000000] ACPI: ASF! 0x0000000039577000 0000A0 (v32 ALASKA A M I 00000002 01000013) [ 0.000000] ACPI: WSMT 0x00000000395770A0 000028 (v01 ALASKA A M I 01072009 AMI 00010013) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: PM-Timer IO Port: 0x1808 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ACPI: IRQ0 used by override. [ 0.000000] ACPI: IRQ9 used by override. [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.001561] ACPI: Core revision 20150930 [ 0.031784] ACPI: 9 ACPI AML tables successfully acquired and loaded [ 0.127450] PM: Registering ACPI NVS region [mem 0x2faed000-0x2faedfff] (4096 bytes) [ 0.128181] PM: Registering ACPI NVS region [mem 0x39205000-0x395adfff] (3837952 bytes) [ 0.142176] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [ 0.142891] ACPI: bus type PCI registered [ 0.150571] ACPI: Added _OSI(Module Device) [ 0.150976] ACPI: Added _OSI(Processor Device) [ 0.151416] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.151866] ACPI: Added _OSI(Processor Aggregator Device) [ 0.172901] ACPI: Executed 42 blocks of module-level executable AML code [ 0.706685] ACPI: Dynamic OEM Table Load: [ 0.707112] ACPI: SSDT 0xFFFF8804A7B7A800 00076B (v02 PmRef Cpu0Ist 00003000 INTL 20160527) [ 0.708542] ACPI: Executed 1 blocks of module-level executable AML code [ 0.709259] ACPI: \_SB_.PR00: _OSC native thermal LVT Acked [ 0.710628] ACPI: Dynamic OEM Table Load: [ 0.711050] ACPI: SSDT 0xFFFF8804A82A1C00 000400 (v02 PmRef Cpu0Cst 00003001 INTL 20160527) [ 0.712466] ACPI: Executed 1 blocks of module-level executable AML code [ 0.713403] ACPI: Dynamic OEM Table Load: [ 0.713825] ACPI: SSDT 0xFFFF8804A8092000 000EF1 (v02 PmRef ApIst 00003000 INTL 20160527) [ 0.715559] ACPI: Executed 1 blocks of module-level executable AML code [ 0.716320] ACPI: Dynamic OEM Table Load: [ 0.716741] ACPI: SSDT 0xFFFF8804A82A2400 00030A (v02 PmRef ApCst 00003000 INTL 20160527) [ 0.718182] ACPI: Executed 1 blocks of module-level executable AML code [ 0.719791] ACPI: Interpreter enabled [ 0.720160] ACPI: (supports S0 S4 S5) [ 0.720518] ACPI: Using IOAPIC for interrupt routing [ 0.721014] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.730335] ACPI: Power Resource [USBC] (on) [ 0.732714] ACPI: Power Resource [V0PR] (on) [ 0.733248] ACPI: Power Resource [V1PR] (on) [ 0.733774] ACPI: Power Resource [V2PR] (on) [ 0.736088] ACPI: Power Resource [WRST] (on) [ 0.738284] ACPI: Power Resource [FN00] (off) [ 0.738756] ACPI: Power Resource [FN01] (off) [ 0.739223] ACPI: Power Resource [FN02] (off) [ 0.739690] ACPI: Power Resource [FN03] (off) [ 0.740158] ACPI: Power Resource [FN04] (off) [ 0.741020] ACPI: Power Resource [PIN] (off) [ 0.741829] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) [ 0.742420] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.743285] acpi PNP0A08:00: _OSC: platform does not support [PME] [ 0.743958] acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability] [ 0.744586] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [ 0.756887] pci 0000:00:14.0: System wakeup disabled by ACPI [ 0.769622] pci 0000:00:1b.0: System wakeup disabled by ACPI [ 0.771647] pci 0000:00:1b.4: System wakeup disabled by ACPI [ 0.773627] pci 0000:00:1c.0: System wakeup disabled by ACPI [ 0.775644] pci 0000:00:1c.5: System wakeup disabled by ACPI [ 0.777630] pci 0000:00:1c.7: System wakeup disabled by ACPI [ 0.779620] pci 0000:00:1d.0: System wakeup disabled by ACPI [ 0.784029] pci 0000:00:1f.3: System wakeup disabled by ACPI [ 0.790969] pci 0000:02:00.0: System wakeup disabled by ACPI [ 0.797495] pci 0000:04:00.0: System wakeup disabled by ACPI [ 0.809887] pci 0000:05:00.0: System wakeup disabled by ACPI [ 0.816581] pci 0000:06:00.0: System wakeup disabled by ACPI [ 0.820264] ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20150930/pci_link-174) [ 0.821007] ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20150930/pci_link-174) [ 0.821747] ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20150930/pci_link-174) [ 0.822487] ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20150930/pci_link-174) [ 0.823228] ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20150930/pci_link-174) [ 0.823967] ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20150930/pci_link-174) [ 0.824706] ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20150930/pci_link-174) [ 0.825445] ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20150930/pci_link-174) [ 0.826503] ACPI: Enabled 5 GPEs in block 00 to 7F [ 0.860829] PCI: Using ACPI for IRQ routing [ 0.956717] pnp: PnP ACPI init [ 0.959400] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.962363] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.963018] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active) [ 0.964699] system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active) [ 0.971849] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.978315] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.979842] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.981375] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.982617] pnp: PnP ACPI: found 8 devices [ 0.992638] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns [ 4.439885] ACPI: bus type USB registered [ 16.106811] ACPI: acpi_idle registered with cpuidle [ 16.416293] ACPI: Sleep Button [SLPB] [ 16.416750] ACPI: Power Button [PWRB] [ 16.417186] ACPI: Power Button [PWRF] [ 16.678312] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 16.678954] acpi device:0f: registered as cooling_device4 @jumkey where is the mistake?

@jumkey I've just compiled the v. 0.46 UEFI of TC and installed onto my HW (see signature)with test HDDs. Everything is going fine so far but ACPI ext is not working as expected. And I'm trying to understand why as I've tested the same extension on other motherboard with positive result. In particular this time the power button is not working and it doesn't initialise the shutdown process. This is the command I've used to add the extension: sudo ./rploader.sh ext apollolake-7.0.1-42218 add https://github.com/jumkey/redpill-load/raw/develop/redpill-acpid/rpext-index.json which I assume it's correct. are there any BIOS option that I can try? these are a list of my HW components seen by DSM: Admin@DS918:~$ lspci -tnnvq -+-[0001:03]---00.0 Intel Corporation I211 Gigabit Network Connection [8086:1539] +-[0001:02]---00.0 Intel Corporation I211 Gigabit Network Connection [8086:1539] +-[0001:01]---00.0 Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] +-[0001:00]-+-12.0 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller [8086:5ae3] | +-13.0 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 [8086:5ad8] | +-14.0 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 [8086:5ad6] | +-15.0 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI [8086:5aa8] | +-16.0 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #1 [8086:5aac] | +-18.0 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 [8086:5abc] | +-19.0 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 [8086:5ac6] | +-19.2 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 [8086:5ac6] | +-1f.0 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller [8086:5ad4] | \-1f.1 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller [8086:5ad4] \-[0000:00]-+-00.0 Intel Corporation 8th Gen Core 4-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] [8086:3e1f] +-02.0 Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] [8086:3e91] +-12.0 Intel Corporation Cannon Lake PCH Thermal Controller [8086:a379] +-14.0 Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller [8086:a36d] +-14.2 Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f] +-16.0 Intel Corporation Cannon Lake PCH HECI Controller [8086:a360] +-16.3 Intel Corporation Cannon Lake PCH Active Management Technology - SOL [8086:a363] +-17.0 Intel Corporation Cannon Lake PCH SATA AHCI Controller [8086:a352] +-1b.0-[01]-- +-1b.4-[02]----00.0 Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] +-1c.0-[03]-- +-1c.5-[04]----00.0 Intel Corporation I210 Gigabit Network Connection [8086:1533] +-1c.7-[05]----00.0 Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] +-1d.0-[06]----00.0 Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] +-1f.0 Intel Corporation Cannon Point-LP LPC Controller [8086:a309] +-1f.3 Intel Corporation Cannon Lake PCH cAVS [8086:a348] +-1f.4 Intel Corporation Cannon Lake PCH SMBus Controller [8086:a323] \-1f.5 Intel Corporation Cannon Lake PCH SPI Controller [8086:a324] As you can notice I've just added a Realtek 2,5GB NIC as other ext. Nothing else. Those are the error shown: Admin@DS918:~$ dmesg | grep error [ 1.835222] intel-lpss: probe of 0001:00:16.0 failed with error -22 [ 1.835639] intel-lpss: probe of 0001:00:18.0 failed with error -22 [ 1.835917] intel-lpss: probe of 0001:00:19.0 failed with error -22 [ 1.836194] intel-lpss: probe of 0001:00:19.2 failed with error -22 [ 4.402516] ahci: probe of 0001:01:00.0 failed with error -22 [ 4.402726] ahci: probe of 0001:00:12.0 failed with error -22 [ 4.658599] xhci_hcd: probe of 0001:00:15.0 failed with error -16 [ 4.715892] igb: probe of 0001:02:00.0 failed with error -5 [ 4.716099] igb: probe of 0001:03:00.0 failed with error -5 [ 16.586618] i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2 Admin@DS918:~$ not so many as you can see. But if @pocopico would be so kind to suggest any other ext to add to repair those errors I'd recompile and add them. Thanks in advance! 🙏

@Amoureux as we share the same Baremetal Hardware, could you be so kind to give details of your red-pill 7.0.1u2 make process? Thanks!

Ciao PincOPallA, it seems to me that something has been written about the NVMe support between page 80 and page 90 on this thread... you should dig further in those pages. If you found something please re-post it here to us, because I'm very interested. Furthermore Could you be so kind to tell us: what is not working correctly? far more important which is your detailed list of BareMetal hardware? Thank you!

Thanks for your long answer. I've analysed the HW in official Synology... and it's quite embarrassing to me, especially compared to price, I will give a look to TinyCore as starting point. Or even to Unraid at this point. I do agree with you about the spinning up/down, in fact I'm working with NAS shutdown most of the times to preserve the HDD's life. I truly hope this open project goes on and become much more stable in the near future.

I will for sure help the community with my experience with my test rig. Therefore I will not post useless comment as yours which has answered none of my questions.

HI all ! @WiteWulf @pocopico After many months of following this thread I was able to play with some VM's (actually Fusion) and successfully install DSM 7.0.1 (918+) on them. Now I would jump on my BareMetal rig, firstly with some test HDDs then with the working ones. My HW is pretty simple (the one in signature): Gigabyte C246-m with Intel i7-9700T CPU, two onboard NICs (i-219 and a 1000e) plus an added NIC (Realtek 8125 2,5Gbe working thanks to extra_lma in Jun's loader 🙏 DSM 6.2.3u3), and two NVMe disks working as RAID1 cache. Now, considering that my mobo belongs to Intel 300's series and so it's SATA controller is 8th/9th gen and therefore I will go for DS918+ setup, some questions for you: To your experience do you expect any problems with the correct recognition of its 8 SATA ports? I need them all! IS there any chance of having both the 2 NVMe working as caching drives as expected? Please if someone could provide a procedure to successfully patch the necessary library, post it in replying to this msg. Thanks! I truly need my Realtek 8125 to work correctly because I've implemented a 2,5Gbe ring that's working very well. But I might consider upgrading to a 10Gb NIC if needed (which one is most compatible at the moment?) If I buy a Synology 10Gb NIC, I would have the chance to use QC? (which now is not enabled because I was not able the change the MAC address in a hardware manner). from a software's point of view I don't need that much: I do not use Docker at the moment. TM MUST work because I absolutely need a backup. It's very important to me. I do use extensively PLEX and I need it, with HW acceleration. The lack of it would be a no-go for me. I do use NextCloud, installed with this procedure . It needs Apache web server, mariaDB and Php. The lack of it would be a no-go for me. It would be nice if Synology Photos works correctly, including the facial recognition. WakeOnLan must work, on all the NICs. The lack of it would be a no-go for me. Sleep should work and HDD hibernation too, as I don't want useless spins of my HDDs. CPU should work at the correct frequencies, I really hate waste of energy and noise. QuickConnect would be nice if it's possible... Last but not least please suggest me the best branch of git which is now more robust and stable, including the necessary compiled drivers. Sorry for the length of my post and thanks and gratitude 🙏 to all who will have the patience of reading it all and answer all the questions.☺️

Thanks for the reply, @pocopico. My primary intention is to go with bare metal machine, with the hardware you can see in my signature. Indeed I will make some tests before upgrading my RAID disks! Now, after creating the .img file, I've installed it onto an USB stick with this command: sudo dd if=redpill-DS918+_7.0.1-42218_b1637771683.img of=/dev/sdb where /sdb is my USB stick's dos partition. In this way I should create a bootable USB stick, shouldn't I? Second question: at the moment I've used the simplest apollo lake_user_config.json possible for testing under VMware: { "extra_cmdline": { "vid": "0x46f4", "pid": "0x0001", "sn": "xxxxxxxxx", "mac1": "xxxxxxxxxx" }, "synoinfo": {}, "ramdisk_copy": {} } for having the full functionalities of a 918+ from an hardware point of view, should I add something? You already taught me to add compiled drivers for my network card, do I need something else? At moment my xpeno_918 gives me 16 SATA ports (even if I really have only 8 on the mobo) and 2 cache NVMe drives. Do I need to modify the config.json to add something else which is present in my real machine? Thanks!

Thanks for the reply. Yes, the rphelper, v 0.12 downloaded here somewhere in the forum. Basically I followed this video and I was able to have a working test machine under VW Fusion on MacOS BigSur. I built the .img file under another vm with Ubuntu installed on it.

@pocopico I need a driver for a Realtek 8125 2,5gb ETH and I've noticed you have added... but ... sorry for the noob question... I don't know how to add the compiled module to the Apollolake build, could you be so kind to show how to do it? Thanks!