giorgosperi Posted March 4, 2022 Share #3776 Posted March 4, 2022 47 minutes ago, Orphée said: Yes how i do that? i just load the new pat file? Link to comment Share on other sites More sharing options...
giorgosperi Posted March 5, 2022 Share #3777 Posted March 5, 2022 13 hours ago, giorgosperi said: how i do that? i just load the new pat file? just an update. i added the vmxnet3 driver in the image and it recognized full speed the sfp+ card but i did this like a new installation. how i can update the existing installation with the new image? sorry for the questions i m missing only this part. Link to comment Share on other sites More sharing options...
Orphée Posted March 5, 2022 Share #3778 Posted March 5, 2022 just an update. i added the vmxnet3 driver in the image and it recognized full speed the sfp+ card but i did this like a new installation. how i can update the existing installation with the new image? sorry for the questions i m missing only this part.As long as you only added the missing driver and left user_config.json exactly the same, just replace loader disk (SATA 0:0)And it should be strait forward. Nothing else to do if you already are at same DSM version.If you upgrading, read other thread/posts. Others did it already. But DSM should ask you to upgrade, as usual Link to comment Share on other sites More sharing options...
dolbycat Posted March 5, 2022 Share #3779 Posted March 5, 2022 On 3/1/2022 at 4:29 PM, jumkey said: https://github.com/jumkey/redpill-load/blob/develop/redpill-dtb/README.md Hi~ jumkey Success thanks to jumkey's advice. Also, tossp's redpill-tool-chain was very helpful. I had a hard time understanding the ds920p.dtb file. I haven't fully understood it yet, and I'm not sure if the way I did it is correct, but I succeeded with DS920+ on i5-8500t and asrock h370 motherboards. Thank you very much. 1 Link to comment Share on other sites More sharing options...
stefauresi Posted March 5, 2022 Share #3780 Posted March 5, 2022 il y a 8 minutes, dolbycat a dit : Hi~ jumkey Success thanks to jumkey's advice. Also, tossp's redpill-tool-chain was very helpful. I had a hard time understanding the ds920p.dtb file. I haven't fully understood it yet, and I'm not sure if the way I did it is correct, but I succeeded with DS920+ on i5-8500t and asrock h370 motherboards. Thank you very much. Hi , I have the same hardware (baremetal) , how you have compile Redpill for DS920+ ? Best regards Link to comment Share on other sites More sharing options...
dolbycat Posted March 5, 2022 Share #3781 Posted March 5, 2022 46 minutes ago, stefauresi said: Hi , I have the same hardware (baremetal) , how you have compile Redpill for DS920+ ? Best regards First of all, only Realtek LAN is recognized. Intel doesn't work. Additional driver support is not yet available. Link to comment Share on other sites More sharing options...
dolbycat Posted March 5, 2022 Share #3782 Posted March 5, 2022 (edited) 3 hours ago, stefauresi said: Hi , I have the same hardware (baremetal) , how you have compile Redpill for DS920+ ? Best regards Jumkey's DS920+ First of all, only Realtek LAN is recognized. Intel doesn't work. Additional driver support is not yet available. I've been working on debian11. I downloaded redpill-tool-chain from https://github.com/tossp/redpill-tool-chain and installed it on debian11. sudo apt-get update sudo apt install docker.io sudo apt install jq sudo apt install curl cd /home/dolbycat/redpill-tool-chain-master chmod +x redpill_tool_chain.sh ./redpill_tool_chain.sh add https://github.com/jumkey/redpill-load/raw/develop/redpill-dtb/rpext-index.json ./redpill_tool_chain.sh build geminilake-7.0.1-42218 ./redpill_tool_chain.sh auto geminilake-7.0.1-42218 After working as above, if you go inside the custom folder, there is a "model_ds920p.dtb" file. You need to modify "model_ds920p.dtb". sudo apt install device-tree-compiler dtc -I dtb -O dts -o output.dts model_ds920p.dtb Edit the newly created "output.dts" file with an editor to suit your system. I booted asrock h370 with "tinycore-redpill.v0.4.5" and typed lspci -tnnvq. tc@box:~$ lspci -tnnvq -[0000:00]-+-00.0 Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers [8086:3ec2] +-01.0-[01]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] +-02.0 Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] [8086:3e92] +-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] +-17.0 Intel Corporation Cannon Lake PCH SATA AHCI Controller [8086:a352] +-1c.0-[02]----00.0 Intel Corporation I211 Gigabit Network Connection [8086:1539] +-1c.6-[03]----00.0 Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] [8086:24fb] +-1d.0-[04]----00.0 SK hynix Device [1c5c:1627] +-1f.0 Intel Corporation H370 Chipset LPC/eSPI Controller [8086:a304] +-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] \-1f.6 Intel Corporation Ethernet Connection (7) I219-V [8086:15bc] tc@box:~$ From the above, you can see that pcie_root = "00:17.0" So, I modified the "output.dts" file as follows. /dts-v1/; / { compatible = "Synology"; model = "synology_geminilake_920+"; version = <0x01>; syno_spinup_group = <0x02 0x01 0x01>; syno_spinup_group_delay = <0x0b>; syno_hdd_powerup_seq = "true"; syno_cmos_reg_secure_flash = <0x66>; syno_cmos_reg_secure_boot = <0x68>; DX517 { compatible = "Synology"; model = "synology_dx517"; pmp_slot@1 { libata { EMID = <0x00>; pmp_link = <0x00>; }; }; pmp_slot@2 { libata { EMID = <0x00>; pmp_link = <0x01>; }; }; pmp_slot@3 { libata { EMID = <0x00>; pmp_link = <0x02>; }; }; pmp_slot@4 { libata { EMID = <0x00>; pmp_link = <0x03>; }; }; pmp_slot@5 { libata { EMID = <0x00>; pmp_link = <0x04>; }; }; }; internal_slot@1 { protocol_type = "sata"; power_pin_gpio = <0x14 0x00>; detect_pin_gpio = <0x23 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x00>; }; led_green { led_name = "syno_led0"; }; led_orange { led_name = "syno_led1"; }; }; internal_slot@2 { protocol_type = "sata"; power_pin_gpio = <0x15 0x00>; detect_pin_gpio = <0x24 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x01>; }; led_green { led_name = "syno_led2"; }; led_orange { led_name = "syno_led3"; }; }; internal_slot@3 { protocol_type = "sata"; power_pin_gpio = <0x16 0x00>; detect_pin_gpio = <0x25 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x02>; }; led_green { led_name = "syno_led4"; }; led_orange { led_name = "syno_led5"; }; }; internal_slot@4 { protocol_type = "sata"; power_pin_gpio = <0x17 0x00>; detect_pin_gpio = <0x26 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x03>; }; led_green { led_name = "syno_led6"; }; led_orange { led_name = "syno_led7"; }; }; internal_slot@5 { protocol_type = "sata"; power_pin_gpio = <0x18 0x00>; detect_pin_gpio = <0x27 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x04>; }; led_green { led_name = "syno_led8"; }; led_orange { led_name = "syno_led9"; }; }; internal_slot@6 { protocol_type = "sata"; power_pin_gpio = <0x19 0x00>; detect_pin_gpio = <0x28 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:17.0"; ata_port = <0x05>; }; led_green { led_name = "syno_led10"; }; led_orange { led_name = "syno_led11"; }; }; esata_port@1 { ahci { pcie_root = "00:13.0,00.0"; ata_port = <0x03>; }; }; usb_slot@1 { vbus { syno_gpio = <0x1d 0x01>; }; usb2 { usb_port = "1-1"; }; usb3 { usb_port = "2-1"; }; }; usb_slot@2 { vbus { syno_gpio = <0x1e 0x01>; }; usb2 { usb_port = "1-2"; }; usb3 { usb_port = "2-2"; }; }; nvme_slot@1 { pcie_root = "00:1d.0"; port_type = "ssdcache"; }; nvme_slot@2 { pcie_root = "00:14.0"; port_type = "ssdcache"; }; }; My asrock h370 motherboard has 6 sata ports. So I made the "internal_slot" to six. Create "model_ds920p.dtb" using the "output.dts" file. dtc -I dts -O dtb -o model_ds920p.dtb output.dts You need to overwrite the created "model_ds920p.dtb" file to the original location. Finally, run the below: ./redpill_tool_chain.sh auto geminilake-7.0.1-42218 I'm a beginner, so there may be some mistakes. I would be grateful if the seniors could improve it. Edited March 5, 2022 by dolbycat 1 Link to comment Share on other sites More sharing options...
RedwinX Posted March 5, 2022 Share #3783 Posted March 5, 2022 @jumkey Hey ! Is there any chance to have a bsp compatible with 918+ v7.1 ? Only available for 920+. Can I use the same BSP from 920+ to 918+ ? 920+ didn't work on my hardware... Need 7.1 to have new features on Active Backup Thx for your work Link to comment Share on other sites More sharing options...
giorgosperi Posted March 5, 2022 Share #3784 Posted March 5, 2022 10 hours ago, Orphée said: As long as you only added the missing driver and left user_config.json exactly the same, just replace loader disk (SATA 0:0) And it should be strait forward. Nothing else to do if you already are at same DSM version. If you upgrading, read other thread/posts. Others did it already. But DSM should ask you to upgrade, as usual thanks i think i got it. i ll check also the other posts to upgrade the old one Link to comment Share on other sites More sharing options...
pigr8 Posted March 5, 2022 Share #3785 Posted March 5, 2022 On 3/3/2022 at 5:41 PM, Orphée said: Welcome back A really quick summary, as you said, TTG still MIA, some motivated guys worked hard in the meantime and we currently have a working DS3622xs+ loader able to replace 3617 and 3615 loaders (they are still working too) There is still a little issue remaining with mpt3sas drivers on DS362xs+, it seems some SMART info are still missing, so SMART may not be revelant on this loader. But some of us migrated to 7.0.1, as I did, from 3615 to 3622. I don't remember since when you left, but @pocopico created a tinycore OS loader. It can build the loader and flash the running OS to have a ready to run loader. It is able to generate fake serials, list needed modules, find satamap needed values, a real great tool ! sorry to bother, are the issues with the LSI passthrou card still present with the 3622 build? Link to comment Share on other sites More sharing options...
cferra Posted March 5, 2022 Share #3786 Posted March 5, 2022 sorry to bother, are the issues with the LSI passthrou card still present with the 3622 build?So I am running 3622xs with an lsi 9305-24i - SAS drives do not show smart data however SATA drivesWork with smart data as expected. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
dolbycat Posted March 6, 2022 Share #3787 Posted March 6, 2022 (edited) On 3/3/2022 at 9:00 PM, jumkey said: replace model_ds920p.dtb and add redpill-dtb ext Hello. I'm having trouble installing DS920+. Asrock J5040 motherboard has a total of 6 SATA ports with a SATA 2-port expansion card installed. But only 2 ports are recognized. dolbycat@debian:~$ lspci 00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 06) 00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant (rev 06) 00:02.0 VGA compatible controller: Intel Corporation GeminiLake [UHD Graphics 605] (rev 06) 00:00e.0 Audio device: Intel Corporation Celeron/Pentium Silver Processor High Definition Audio (rev 06) 00:00f.0 Communication controller: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface (rev 06) 00:12.0 SATA controller: Intel Corporation Celeron/Pentium Silver Processor SATA Controller (rev 06) 00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f6) 00:13.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f6) 00:13.2 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f6) 00:13.3 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev f6) 00:15.0 USB controller: Intel Corporation Celeron/Pentium Silver Processor USB 3.0 xHCI Controller (rev 06) 00:1f.0 ISA bridge: Intel Corporation Celeron/Pentium Silver Processor LPC Controller (rev 06) 00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 06) 01:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02) 01:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02) 02:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) Based on the above lspci information, I got the below values. pcie_root = "00:12.0" <- Processor SATA Controller pcie_root = "02:00.0" <- JMB58x AHCI SATA controller pcie_root = "04:00.0" <- ASM1062 Serial ATA Controller But only pcie_root = "00:12.0" seems to be recognized. How can I recognize JMB58x AHCI SATA controller and ASM1062 Serial ATA Controller? * model_ds920p.dtb is as below. /dts-v1/; / { compatible = "Synology"; model = "synology_geminilake_920+"; version = <0x01>; syno_spinup_group = <0x02 0x01 0x01>; syno_spinup_group_delay = <0x0b>; syno_hdd_powerup_seq = "true"; syno_cmos_reg_secure_flash = <0x66>; syno_cmos_reg_secure_boot = <0x68>; DX517 { compatible = "Synology"; model = "synology_dx517"; pmp_slot@1 { libata { EMID = <0x00>; pmp_link = <0x00>; }; }; pmp_slot@2 { libata { EMID = <0x00>; pmp_link = <0x01>; }; }; pmp_slot@3 { libata { EMID = <0x00>; pmp_link = <0x02>; }; }; pmp_slot@4 { libata { EMID = <0x00>; pmp_link = <0x03>; }; }; pmp_slot@5 { libata { EMID = <0x00>; pmp_link = <0x04>; }; }; }; internal_slot@1 { protocol_type = "sata"; power_pin_gpio = <0x14 0x00>; detect_pin_gpio = <0x23 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:12.0"; ata_port = <0x00>; }; led_green { led_name = "syno_led0"; }; led_orange { led_name = "syno_led1"; }; }; internal_slot@2 { protocol_type = "sata"; power_pin_gpio = <0x15 0x00>; detect_pin_gpio = <0x24 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:12.0"; ata_port = <0x01>; }; led_green { led_name = "syno_led2"; }; led_orange { led_name = "syno_led3"; }; }; internal_slot@3 { protocol_type = "sata"; power_pin_gpio = <0x16 0x00>; detect_pin_gpio = <0x25 0x01>; led_type = "lp3943"; ahci { pcie_root = "02:00.0"; ata_port = <0x02>; }; led_green { led_name = "syno_led4"; }; led_orange { led_name = "syno_led5"; }; }; internal_slot@4 { protocol_type = "sata"; power_pin_gpio = <0x17 0x00>; detect_pin_gpio = <0x26 0x01>; led_type = "lp3943"; ahci { pcie_root = "02:00.0"; ata_port = <0x03>; }; led_green { led_name = "syno_led6"; }; led_orange { led_name = "syno_led7"; }; }; internal_slot@5 { protocol_type = "sata"; power_pin_gpio = <0x18 0x00>; detect_pin_gpio = <0x27 0x01>; led_type = "lp3943"; ahci { pcie_root = "04:00.0"; ata_port = <0x04>; }; led_green { led_name = "syno_led8"; }; led_orange { led_name = "syno_led9"; }; }; internal_slot@6 { protocol_type = "sata"; power_pin_gpio = <0x19 0x00>; detect_pin_gpio = <0x28 0x01>; led_type = "lp3943"; ahci { pcie_root = "04:00.0"; ata_port = <0x05>; }; led_green { led_name = "syno_led10"; }; led_orange { led_name = "syno_led11"; }; }; esata_port@1 { ahci { pcie_root = "02:00.0"; ata_port = <0x03>; }; }; usb_slot@1 { vbus { syno_gpio = <0x1d 0x01>; }; usb2 { usb_port = "1-1"; }; usb3 { usb_port = "2-1"; }; }; usb_slot@2 { vbus { syno_gpio = <0x1e 0x01>; }; usb2 { usb_port = "1-2"; }; usb3 { usb_port = "2-2"; }; }; nvme_slot@1 { pcie_root = "00:1d.0"; port_type = "ssdcache"; }; nvme_slot@2 { pcie_root = "00:14.0"; port_type = "ssdcache"; }; }; Edited March 6, 2022 by dolbycat Link to comment Share on other sites More sharing options...
jumkey Posted March 6, 2022 Share #3788 Posted March 6, 2022 8 hours ago, RedwinX said: @jumkey Hey ! Is there any chance to have a bsp compatible with 918+ v7.1 ? Only available for 920+. Can I use the same BSP from 920+ to 918+ ? 920+ didn't work on my hardware... Need 7.1 to have new features on Active Backup Thx for your work 7.1 is currently a beta version, the bsp file is just for testing Link to comment Share on other sites More sharing options...
dolbycat Posted March 6, 2022 Share #3789 Posted March 6, 2022 Thank you for your interest. Below are the values given. root@xpenology:~# root@xpenology:~# ls /dev/sata* /dev/sata1 /dev/sata2p1 /dev/sata3p2 /dev/sata4p2 /dev/sata5p3 /dev/sata1p1 /dev/sata2p2 /dev/sata3p3 /dev/sata4p3 /dev/sata1p2 /dev/sata2p3 /dev/sata3p4 /dev/sata5 /dev/sata1p3 /dev/sata3 /dev/sata4 /dev/sata5p1 /dev/sata2 /dev/sata3p1 /dev/sata4p1 /dev/sata5p2 root@xpenology:~# root@xpenology:~# root@xpenology:~# cat /sys/block/sata1/device/syno_block_info pciepath=00:12.0 ata_port_no=0 driver=ahci root@xpenology:~# cat /sys/block/sata2/device/syno_block_info pciepath=00:12.0 ata_port_no=1 driver=ahci root@xpenology:~# cat /sys/block/sata3/device/syno_block_info pciepath=00:13.1,00.0 ata_port_no=0 driver=ahci root@xpenology:~# cat /sys/block/sata4/device/syno_block_info pciepath=00:13.3,00.0 ata_port_no=0 driver=ahci root@xpenology:~# cat /sys/block/sata5/device/syno_block_info pciepath=00:13.3,00.0 ata_port_no=1 driver=ahci root@xpenology:~# cat /sys/block/sata6/device/syno_block_info cat: /sys/block/sata6/device/syno_block_info: No such file or directory root@xpenology:~# Link to comment Share on other sites More sharing options...
jumkey Posted March 6, 2022 Share #3790 Posted March 6, 2022 9 minutes ago, dolbycat said: Thank you for your interest. Below are the values given. root@xpenology:~# root@xpenology:~# ls /dev/sata* /dev/sata1 /dev/sata2p1 /dev/sata3p2 /dev/sata4p2 /dev/sata5p3 /dev/sata1p1 /dev/sata2p2 /dev/sata3p3 /dev/sata4p3 /dev/sata1p2 /dev/sata2p3 /dev/sata3p4 /dev/sata5 /dev/sata1p3 /dev/sata3 /dev/sata4 /dev/sata5p1 /dev/sata2 /dev/sata3p1 /dev/sata4p1 /dev/sata5p2 root@xpenology:~# root@xpenology:~# root@xpenology:~# cat /sys/block/sata1/device/syno_block_info pciepath=00:12.0 ata_port_no=0 driver=ahci root@xpenology:~# cat /sys/block/sata2/device/syno_block_info pciepath=00:12.0 ata_port_no=1 driver=ahci root@xpenology:~# cat /sys/block/sata3/device/syno_block_info pciepath=00:13.1,00.0 ata_port_no=0 driver=ahci root@xpenology:~# cat /sys/block/sata4/device/syno_block_info pciepath=00:13.3,00.0 ata_port_no=0 driver=ahci root@xpenology:~# cat /sys/block/sata5/device/syno_block_info pciepath=00:13.3,00.0 ata_port_no=1 driver=ahci root@xpenology:~# cat /sys/block/sata6/device/syno_block_info cat: /sys/block/sata6/device/syno_block_info: No such file or directory root@xpenology:~# Quote pcie_root = "00:12.0" ata_port = <0x00> pcie_root = "00:12.0" ata_port = <0x01> pcie_root = "00:13.1,00.0" ata_port = <0x00> pcie_root = "00:13.3,00.0" ata_port = <0x00> pcie_root = "00:13.3,00.0" ata_port = <0x01> you know what that means Link to comment Share on other sites More sharing options...
dolbycat Posted March 6, 2022 Share #3791 Posted March 6, 2022 24 minutes ago, jumkey said: you know what that means I think it is an address that designates the sata port. Looking at it now, it seems that the ata_port value is different among the model_ds920p.dtb values I have created. jumkey's instruction is required...😅 Link to comment Share on other sites More sharing options...
root616 Posted March 7, 2022 Share #3792 Posted March 7, 2022 23 hours ago, jumkey said: you know what that means Hi, Jum is ds918p's VMnet3 driver compatible ds920p? Link to comment Share on other sites More sharing options...
jumkey Posted March 7, 2022 Share #3793 Posted March 7, 2022 1 hour ago, root616 said: Hi, Jum is ds918p's VMnet3 driver compatible ds920p? I used my own compiled virtio, I haven't tested this case Link to comment Share on other sites More sharing options...
dolbycat Posted March 7, 2022 Share #3794 Posted March 7, 2022 (edited) On 3/6/2022 at 1:41 PM, jumkey said: you know what that means Hi , jumkey DS920+ Finally, Asrock J5040 succeeded in recognizing all hard disks. I was stupid. I should have looked carefully at jumkey's words. cat /sys/block/sataX/device/syno_block_info X=1-4 When I put the value obtained by executing the above command in model_ds920p.dtb, it was recognized properly. The new PortMapping ext(redpill-dtb) seems great. There seems to be no need to worry about SataPortMap and DiskIdxMap anymore. Edited March 7, 2022 by dolbycat Link to comment Share on other sites More sharing options...
RedwinX Posted March 7, 2022 Share #3795 Posted March 7, 2022 On 3/5/2022 at 12:32 AM, dolbycat said: Hi~ jumkey Success thanks to jumkey's advice. Also, tossp's redpill-tool-chain was very helpful. I had a hard time understanding the ds920p.dtb file. I haven't fully understood it yet, and I'm not sure if the way I did it is correct, but I succeeded with DS920+ on i5-8500t and asrock h370 motherboards. Thank you very much. Maybe you can help me so, because I think I'm not fully understand too Have a test motherboard should be perfect for 920+ : Asrock J4125 lspci : Quote 0000:00:00.0 Class 0600: Intel Corporation Gemini Lake Host Bridge (rev 06) 0000:00:00.1 Class 1180: Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant (rev 06) 0000:00:02.0 Class 0300: Intel Corporation GeminiLake [UHD Graphics 600] (rev 06) 0000:00:0e.0 Class 0403: Intel Corporation Celeron/Pentium Silver Processor High Definition Audio (rev 06) 0000:00:0f.0 Class 0780: Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface (rev 06) 0000:00:12.0 Class 0106: Intel Corporation Celeron/Pentium Silver Processor SATA Controller (rev 06) 0000:00:13.0 Class 0604: Intel Corporation Device 31d8 (rev f6) 0000:00:13.1 Class 0604: Intel Corporation Device 31d9 (rev f6) 0000:00:13.2 Class 0604: Intel Corporation Device 31da (rev f6) 0000:00:13.3 Class 0604: Intel Corporation Device 31db (rev f6) 0000:00:15.0 Class 0c03: Intel Corporation Celeron/Pentium Silver Processor USB 3.0 xHCI Controller (rev 06) 0000:00:1f.0 Class 0601: Intel Corporation Celeron/Pentium Silver Processor LPC Controller (rev 06) 0000:00:1f.1 Class 0c05: Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model (rev 06) 0000:03:00.0 Class 0200: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 0000:04:00.0 Class 0106: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0001:00:12.0 Class 0106: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller 0001:00:13.0 Class 0000: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 0001:00:14.0 Class 0000: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 0001:00:15.0 Class 0c03: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI 0001:00:16.0 Class 1180: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #1 0001:00:18.0 Class 1180: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 0001:00:19.0 Class 1180: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 0001:00:19.2 Class 1180: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 0001:00:1f.0 Class 0c05: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller 0001:00:1f.1 Class 0c05: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller 0001:01:00.0 Class 0106: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller (rev 11) 0001:02:00.0 Class 0200: Intel Corporation I211 Gigabit Network Connection (rev 03) 0001:03:00.0 Class 0200: Intel Corporation I211 Gigabit Network Connection (rev 03) output.dts : Quote /dts-v1/; / { compatible = "Synology"; model = "synology_geminilake_920+"; version = <0x01>; syno_spinup_group = <0x02 0x01 0x01>; syno_spinup_group_delay = <0x0b>; syno_hdd_powerup_seq = "true"; syno_cmos_reg_secure_flash = <0x66>; syno_cmos_reg_secure_boot = <0x68>; DX517 { compatible = "Synology"; model = "synology_dx517"; pmp_slot@1 { libata { EMID = <0x00>; pmp_link = <0x00>; }; }; pmp_slot@2 { libata { EMID = <0x00>; pmp_link = <0x01>; }; }; pmp_slot@3 { libata { EMID = <0x00>; pmp_link = <0x02>; }; }; pmp_slot@4 { libata { EMID = <0x00>; pmp_link = <0x03>; }; }; pmp_slot@5 { libata { EMID = <0x00>; pmp_link = <0x04>; }; }; }; internal_slot@1 { protocol_type = "sata"; power_pin_gpio = <0x14 0x00>; detect_pin_gpio = <0x23 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:1e.0,01.0,07.0"; ata_port = <0x00>; }; led_green { led_name = "syno_led0"; }; led_orange { led_name = "syno_led1"; }; }; internal_slot@2 { protocol_type = "sata"; power_pin_gpio = <0x15 0x00>; detect_pin_gpio = <0x24 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:1e.0,01.0,07.0"; ata_port = <0x01>; }; led_green { led_name = "syno_led2"; }; led_orange { led_name = "syno_led3"; }; }; internal_slot@3 { protocol_type = "sata"; power_pin_gpio = <0x16 0x00>; detect_pin_gpio = <0x25 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:1e.0,01.0,07.0"; ata_port = <0x02>; }; led_green { led_name = "syno_led4"; }; led_orange { led_name = "syno_led5"; }; }; internal_slot@4 { protocol_type = "sata"; power_pin_gpio = <0x17 0x00>; detect_pin_gpio = <0x26 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:1e.0,01.0,07.0"; ata_port = <0x03>; }; led_green { led_name = "syno_led6"; }; led_orange { led_name = "syno_led7"; }; }; esata_port@1 { ahci { pcie_root = "00:13.0,00.0"; ata_port = <0x03>; }; }; usb_slot@1 { vbus { syno_gpio = <0x1d 0x01>; }; usb2 { usb_port = "1-1"; }; usb3 { usb_port = "2-1"; }; }; usb_slot@2 { vbus { syno_gpio = <0x1e 0x01>; }; usb2 { usb_port = "1-2"; }; usb3 { usb_port = "2-2"; }; }; nvme_slot@1 { pcie_root = "00:14.1"; port_type = "ssdcache"; }; nvme_slot@2 { pcie_root = "00:14.0"; port_type = "ssdcache"; }; }; I need to replace "pcie_root = "00:1e.0,01.0,07.0"; " by "00:12.0" or "04:0.00" or "01:00.0" ? Nothing seams to be working lol Link to comment Share on other sites More sharing options...
dolbycat Posted March 7, 2022 Share #3796 Posted March 7, 2022 53 minutes ago, RedwinX said: Maybe you can help me so, because I think I'm not fully understand too Have a test motherboard should be perfect for 920+ : Asrock J4125 lspci : output.dts : I need to replace "pcie_root = "00:1e.0,01.0,07.0"; " by "00:12.0" or "04:0.00" or "01:00.0" ? Nothing seams to be working lol 0000:00:12.0 Class 0106: Intel Corporation Celeron/Pentium Silver Processor SATA Controller (rev 06) Referring to the above sentence, pcie_root = "00:12.0" internal_slot@1 { protocol_type = "sata"; power_pin_gpio = <0x14 0x00>; detect_pin_gpio = <0x23 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:12.0"; ata_port = <0x00>; }; led_green { led_name = "syno_led0"; }; led_orange { led_name = "syno_led1"; }; }; internal_slot@2 { protocol_type = "sata"; power_pin_gpio = <0x15 0x00>; detect_pin_gpio = <0x24 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:12.0"; ata_port = <0x01>; }; led_green { led_name = "syno_led2"; }; led_orange { led_name = "syno_led3"; }; }; After compiling with the above values, run DS920+. Then, as in the picture below, get the remaining pcie_root values and compile again. 1 Link to comment Share on other sites More sharing options...
RedwinX Posted March 7, 2022 Share #3797 Posted March 7, 2022 1 hour ago, dolbycat said: 0000:00:12.0 Class 0106: Intel Corporation Celeron/Pentium Silver Processor SATA Controller (rev 06) Referring to the above sentence, pcie_root = "00:12.0" internal_slot@1 { protocol_type = "sata"; power_pin_gpio = <0x14 0x00>; detect_pin_gpio = <0x23 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:12.0"; ata_port = <0x00>; }; led_green { led_name = "syno_led0"; }; led_orange { led_name = "syno_led1"; }; }; internal_slot@2 { protocol_type = "sata"; power_pin_gpio = <0x15 0x00>; detect_pin_gpio = <0x24 0x01>; led_type = "lp3943"; ahci { pcie_root = "00:12.0"; ata_port = <0x01>; }; led_green { led_name = "syno_led2"; }; led_orange { led_name = "syno_led3"; }; }; After compiling with the above values, run DS920+. Then, as in the picture below, get the remaining pcie_root values and compile again. Thx, will try this afternoon Link to comment Share on other sites More sharing options...
Orphée Posted March 7, 2022 Share #3798 Posted March 7, 2022 (edited) I don't get the point to build DS920+ over DS918+. Is there a real benefit ? Edited March 7, 2022 by Orphée Link to comment Share on other sites More sharing options...
RedwinX Posted March 7, 2022 Share #3799 Posted March 7, 2022 Just now, Orphée said: I don't get the point to build DS920+ over DS918+. Is there a real benefit ? The 920+ with J4125 has a Intel HD600 vs HD500 for the 918+. When you installed DS918+ with J4125, the hw transcoding didn't work, even with the modified driver from IG-88. So 920+ has the exact same driver as the Asrock J4125... So it may have benefits in some use case... 1 Link to comment Share on other sites More sharing options...
Orphée Posted March 7, 2022 Share #3800 Posted March 7, 2022 Okay, let us know then Link to comment Share on other sites More sharing options...
Recommended Posts