phone guy Posted April 16, 2022 Share #2601 Posted April 16, 2022 53 minutes ago, Peter Suh said: I don't know if it was shared somewhere, but I'm sharing it for people who don't know. This function is called ttyd. If redpill-misc ext is installed correctly, No separate telnet management is required. The port 7681 enables you to take advantage of existing Telnet access capabilities. (without separate Telnet clients) From your browser, go to http://<yourip>:7681 user root / no password. NOT WORKING. It simply loads and closes connection every second. Like flipping a switch on/off really fast Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2602 Posted April 16, 2022 2 hours ago, Peter Suh said: @pocopico Here is the TCRP loader boot log for ds920p-42218. As mentioned above, ds920p-42218 is missing from all ext, so I temporarily modified my repo and used it. There is a problem with the install_rd.sh file script handling the dtb file. It seems that the disc cannot be found because of this. SynologyNAS> cat /var/log/junior_reason Exit on error [99] rp ext init exec failure... SynologyNAS> cat /var/log/*rc* START /linuxrc.syno.impl '/etc.defaults/model.dtb' -> '/var/run/model.dtb' Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for PeterSuh-Q3.e1000e (args: ) Loading kmod #0 "igb.ko" for PeterSuh-Q3.igb (args: ) Loading kmod #0 "raid_class.ko" for PeterSuh-Q3.mpt3sas (args: ) Loading kmod #1 "scsi_transport_sas.ko" for PeterSuh-Q3.mpt3sas (args: ) Loading kmod #2 "mpt3sas.ko" for PeterSuh-Q3.mpt3sas (args: ) Loading kmod #0 "mii.ko" for PeterSuh-Q3.r8169 (args: ) Loading kmod #1 "r8169.ko" for PeterSuh-Q3.r8169 (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot - exit=0 Running "check-igb.sh" for PeterSuh-Q3.igb->on_boot Loading module igb -> Module igb loaded succesfully Ran "check-igb.sh" for PeterSuh-Q3.igb->on_boot - exit=0 Running "check-mpt3sas.sh" for PeterSuh-Q3.mpt3sas->on_boot Loading module mpt3sas -> Module mpt3sas loaded succesfully Ran "check-mpt3sas.sh" for PeterSuh-Q3.mpt3sas->on_boot - exit=0 Running "check-r8169.sh" for PeterSuh-Q3.r8169->on_boot Loading module r8169 -> Module r8169 loaded succesfully Ran "check-r8169.sh" for PeterSuh-Q3.r8169->on_boot - exit=0 Running "boot-wait.sh" for redpill-boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Still waiting for boot device (waited 5 of 30 seconds) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Still waiting for boot device (waited 8 of 30 seconds) Still waiting for boot device (waited 9 of 30 seconds) Still waiting for boot device (waited 10 of 30 seconds) Still waiting for boot device (waited 11 of 30 seconds) Still waiting for boot device (waited 12 of 30 seconds) Still waiting for boot device (waited 13 of 30 seconds) Still waiting for boot device (waited 14 of 30 seconds) Still waiting for boot device (waited 15 of 30 seconds) Still waiting for boot device (waited 16 of 30 seconds) Still waiting for boot device (waited 17 of 30 seconds) Still waiting for boot device (waited 18 of 30 seconds) Still waiting for boot device (waited 19 of 30 seconds) Still waiting for boot device (waited 20 of 30 seconds) Still waiting for boot device (waited 21 of 30 seconds) Still waiting for boot device (waited 22 of 30 seconds) Still waiting for boot device (waited 23 of 30 seconds) Still waiting for boot device (waited 24 of 30 seconds) Still waiting for boot device (waited 25 of 30 seconds) Still waiting for boot device (waited 26 of 30 seconds) Still waiting for boot device (waited 27 of 30 seconds) Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=1 Running "install_rd.sh" for redpill-dtb->on_boot 'model_ds920p.dtb' -> '/etc.defaults/model.dtb' 'model_ds920p.dtb' -> '/var/run/model.dtb' Ran "install_rd.sh" for redpill-dtb->on_boot - exit=0 ERROR: Some of the scripts failed! See above for any with exit != 0 :: Executing "on_boot" custom scripts ... [ OK ] Exit on error [99] rp ext init exec failure... Sat Apr 16 04:14:41 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 I think that the message is clear heard. boot wait didn’t find the Synoboot device. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2603 Posted April 16, 2022 (edited) @pocopico All ds920p-42218 ext were lost. The same applies to the five exts under the repo's pocopico/redpill-load. Is there time to recover this part? Edited April 16, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2604 Posted April 16, 2022 38 minutes ago, phone guy said: NOT WORKING. It simply loads and closes connection every second. Like flipping a switch on/off really fast It will only work on junior. AKA, install, recover etc. 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2605 Posted April 16, 2022 1 hour ago, pocopico said: It will only work on junior. AKA, install, recover etc. Does junior mean that you can see the DSM installation preparation/migration/recovery screen? Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2606 Posted April 16, 2022 13 minutes ago, Peter Suh said: Does junior mean that you can see the DSM installation preparation/migration/recovery screen? Yes Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2607 Posted April 16, 2022 @pocopico It's very strange. This time, I tried to launch ds920+ as a junior through the tool-chain. The logs are pretty much the same The results are good at spotting disks. What is the difference? SynologyNAS> cat /var/log/junior_reason Exit on error [99] rp ext init exec failure... SynologyNAS> cat /var/log/*rc* START /linuxrc.syno.impl '/etc.defaults/model.dtb' -> '/var/run/model.dtb' Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) Loading kmod #0 "igb.ko" for pocopico.igb (args: ) Loading kmod #0 "raid_class.ko" for pocopico.mpt3sas (args: ) Loading kmod #1 "scsi_transport_sas.ko" for pocopico.mpt3sas (args: ) Loading kmod #2 "mpt3sas.ko" for pocopico.mpt3sas (args: ) Loading kmod #0 "mii.ko" for pocopico.r8169 (args: ) Loading kmod #1 "r8169.ko" for pocopico.r8169 (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for pocopico.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0 Running "check-igb.sh" for pocopico.igb->on_boot Loading module igb -> Module igb loaded succesfully Ran "check-igb.sh" for pocopico.igb->on_boot - exit=0 Running "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot Loading module mpt3sas -> Module mpt3sas loaded succesfully Ran "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot - exit=0 Running "check-r8169.sh" for pocopico.r8169->on_boot Loading module r8169 -> Module r8169 loaded succesfully Ran "check-r8169.sh" for pocopico.r8169->on_boot - exit=0 Running "boot-wait.sh" for redpill-boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Still waiting for boot device (waited 5 of 30 seconds) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Still waiting for boot device (waited 8 of 30 seconds) Still waiting for boot device (waited 9 of 30 seconds) Still waiting for boot device (waited 10 of 30 seconds) Still waiting for boot device (waited 11 of 30 seconds) Still waiting for boot device (waited 12 of 30 seconds) Still waiting for boot device (waited 13 of 30 seconds) Still waiting for boot device (waited 14 of 30 seconds) Still waiting for boot device (waited 15 of 30 seconds) Still waiting for boot device (waited 16 of 30 seconds) Still waiting for boot device (waited 17 of 30 seconds) Still waiting for boot device (waited 18 of 30 seconds) Still waiting for boot device (waited 19 of 30 seconds) Still waiting for boot device (waited 20 of 30 seconds) Still waiting for boot device (waited 21 of 30 seconds) Still waiting for boot device (waited 22 of 30 seconds) Still waiting for boot device (waited 23 of 30 seconds) Still waiting for boot device (waited 24 of 30 seconds) Still waiting for boot device (waited 25 of 30 seconds) Still waiting for boot device (waited 26 of 30 seconds) Still waiting for boot device (waited 27 of 30 seconds) Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=1 Running "install_rd.sh" for redpill-dtb->on_boot 'model_ds920p.dtb' -> '/etc.defaults/model.dtb' 'model_ds920p.dtb' -> '/var/run/model.dtb' Ran "install_rd.sh" for redpill-dtb->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 ERROR: Some of the scripts failed! See above for any with exit != 0 :: Executing "on_boot" custom scripts ... [ OK ] Exit on error [99] rp ext init exec failure... Sat Apr 16 08:54:42 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2608 Posted April 16, 2022 9 minutes ago, Peter Suh said: @pocopico It's very strange. This time, I tried to launch ds920+ as a junior through the tool-chain. The logs are pretty much the same The results are good at spotting disks. What is the difference? SynologyNAS> cat /var/log/junior_reason Exit on error [99] rp ext init exec failure... SynologyNAS> cat /var/log/*rc* START /linuxrc.syno.impl '/etc.defaults/model.dtb' -> '/var/run/model.dtb' Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) Loading kmod #0 "igb.ko" for pocopico.igb (args: ) Loading kmod #0 "raid_class.ko" for pocopico.mpt3sas (args: ) Loading kmod #1 "scsi_transport_sas.ko" for pocopico.mpt3sas (args: ) Loading kmod #2 "mpt3sas.ko" for pocopico.mpt3sas (args: ) Loading kmod #0 "mii.ko" for pocopico.r8169 (args: ) Loading kmod #1 "r8169.ko" for pocopico.r8169 (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for pocopico.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0 Running "check-igb.sh" for pocopico.igb->on_boot Loading module igb -> Module igb loaded succesfully Ran "check-igb.sh" for pocopico.igb->on_boot - exit=0 Running "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot Loading module mpt3sas -> Module mpt3sas loaded succesfully Ran "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot - exit=0 Running "check-r8169.sh" for pocopico.r8169->on_boot Loading module r8169 -> Module r8169 loaded succesfully Ran "check-r8169.sh" for pocopico.r8169->on_boot - exit=0 Running "boot-wait.sh" for redpill-boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Still waiting for boot device (waited 5 of 30 seconds) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Still waiting for boot device (waited 8 of 30 seconds) Still waiting for boot device (waited 9 of 30 seconds) Still waiting for boot device (waited 10 of 30 seconds) Still waiting for boot device (waited 11 of 30 seconds) Still waiting for boot device (waited 12 of 30 seconds) Still waiting for boot device (waited 13 of 30 seconds) Still waiting for boot device (waited 14 of 30 seconds) Still waiting for boot device (waited 15 of 30 seconds) Still waiting for boot device (waited 16 of 30 seconds) Still waiting for boot device (waited 17 of 30 seconds) Still waiting for boot device (waited 18 of 30 seconds) Still waiting for boot device (waited 19 of 30 seconds) Still waiting for boot device (waited 20 of 30 seconds) Still waiting for boot device (waited 21 of 30 seconds) Still waiting for boot device (waited 22 of 30 seconds) Still waiting for boot device (waited 23 of 30 seconds) Still waiting for boot device (waited 24 of 30 seconds) Still waiting for boot device (waited 25 of 30 seconds) Still waiting for boot device (waited 26 of 30 seconds) Still waiting for boot device (waited 27 of 30 seconds) Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=1 Running "install_rd.sh" for redpill-dtb->on_boot 'model_ds920p.dtb' -> '/etc.defaults/model.dtb' 'model_ds920p.dtb' -> '/var/run/model.dtb' Ran "install_rd.sh" for redpill-dtb->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 ERROR: Some of the scripts failed! See above for any with exit != 0 :: Executing "on_boot" custom scripts ... [ OK ] Exit on error [99] rp ext init exec failure... Sat Apr 16 08:54:42 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 I need to further look at the dtb issue. I thought though that this is solved by dtb extension Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2609 Posted April 16, 2022 15 minutes ago, Peter Suh said: @pocopico It's very strange. This time, I tried to launch ds920+ as a junior through the tool-chain. The logs are pretty much the same The results are good at spotting disks. What is the difference? SynologyNAS> cat /var/log/junior_reason Exit on error [99] rp ext init exec failure... SynologyNAS> cat /var/log/*rc* START /linuxrc.syno.impl '/etc.defaults/model.dtb' -> '/var/run/model.dtb' Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) Loading kmod #0 "igb.ko" for pocopico.igb (args: ) Loading kmod #0 "raid_class.ko" for pocopico.mpt3sas (args: ) Loading kmod #1 "scsi_transport_sas.ko" for pocopico.mpt3sas (args: ) Loading kmod #2 "mpt3sas.ko" for pocopico.mpt3sas (args: ) Loading kmod #0 "mii.ko" for pocopico.r8169 (args: ) Loading kmod #1 "r8169.ko" for pocopico.r8169 (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for pocopico.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0 Running "check-igb.sh" for pocopico.igb->on_boot Loading module igb -> Module igb loaded succesfully Ran "check-igb.sh" for pocopico.igb->on_boot - exit=0 Running "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot Loading module mpt3sas -> Module mpt3sas loaded succesfully Ran "check-mpt3sas.sh" for pocopico.mpt3sas->on_boot - exit=0 Running "check-r8169.sh" for pocopico.r8169->on_boot Loading module r8169 -> Module r8169 loaded succesfully Ran "check-r8169.sh" for pocopico.r8169->on_boot - exit=0 Running "boot-wait.sh" for redpill-boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Still waiting for boot device (waited 5 of 30 seconds) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Still waiting for boot device (waited 8 of 30 seconds) Still waiting for boot device (waited 9 of 30 seconds) Still waiting for boot device (waited 10 of 30 seconds) Still waiting for boot device (waited 11 of 30 seconds) Still waiting for boot device (waited 12 of 30 seconds) Still waiting for boot device (waited 13 of 30 seconds) Still waiting for boot device (waited 14 of 30 seconds) Still waiting for boot device (waited 15 of 30 seconds) Still waiting for boot device (waited 16 of 30 seconds) Still waiting for boot device (waited 17 of 30 seconds) Still waiting for boot device (waited 18 of 30 seconds) Still waiting for boot device (waited 19 of 30 seconds) Still waiting for boot device (waited 20 of 30 seconds) Still waiting for boot device (waited 21 of 30 seconds) Still waiting for boot device (waited 22 of 30 seconds) Still waiting for boot device (waited 23 of 30 seconds) Still waiting for boot device (waited 24 of 30 seconds) Still waiting for boot device (waited 25 of 30 seconds) Still waiting for boot device (waited 26 of 30 seconds) Still waiting for boot device (waited 27 of 30 seconds) Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=1 Running "install_rd.sh" for redpill-dtb->on_boot 'model_ds920p.dtb' -> '/etc.defaults/model.dtb' 'model_ds920p.dtb' -> '/var/run/model.dtb' Ran "install_rd.sh" for redpill-dtb->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 ERROR: Some of the scripts failed! See above for any with exit != 0 :: Executing "on_boot" custom scripts ... [ OK ] Exit on error [99] rp ext init exec failure... Sat Apr 16 08:54:42 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 well if you check ds920p dts file, there is a dedicated USB part. Did you fix that ? https://github.com/pocopico/tinycore-redpill/blob/main/ds920p.dts Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2610 Posted April 16, 2022 26 minutes ago, pocopico said: well if you check ds920p dts file, there is a dedicated USB part. Did you fix that ? https://github.com/pocopico/tinycore-redpill/blob/main/ds920p.dts The USB part was never modified. I used the output.dts file that jumkey first shared Below is the contents of the dts file used in my tool-chain. Only the internal_slot part was substituted with 1f.2 value for 6 ports. /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:1f.2"; 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:1f.2"; 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:1f.2"; 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:1f.2"; 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:1f.2"; 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:1f.2"; ata_port = <0x05>; }; led_green { led_name = "syno_led10"; }; led_orange { led_name = "syno_led11"; }; }; esata_port@1 { ahci { pcie_root = "00:13.1"; 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"; }; }; Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2611 Posted April 16, 2022 (edited) 7 minutes ago, Peter Suh said: The USB part was never modified. I used the output.dts file that jumkey first shared Below is the contents of the dts file used in my tool-chain. Only the internal_slot part was substituted with 1f.2 value for 6 ports. /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:1f.2"; 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:1f.2"; 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:1f.2"; 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:1f.2"; 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:1f.2"; 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:1f.2"; ata_port = <0x05>; }; led_green { led_name = "syno_led10"; }; led_orange { led_name = "syno_led11"; }; }; esata_port@1 { ahci { pcie_root = "00:13.1"; 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"; }; }; By the way, @pocopico your dts was reduced from 6 ports originally to 4 ports internal_slot. There's no problem with this, right? Edited April 16, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2612 Posted April 16, 2022 16 minutes ago, Peter Suh said: By the way, @pocopico your dts was reduced from 6 ports originally to 4 ports internal_slot. There's no problem with this, right? DS920p has only 4 internal slots and 2 M2. I really dont know why Jumkeys has 6 ports ... Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2613 Posted April 16, 2022 (edited) DS920 dts has been extracted from the system patch location and has only 4 ports. I guess if you need more you can keep Jumkeys. As for USB. i think its easy to figure this out by running lsusb while on TCRP. -------------------------- 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"; }; }; -------------------------------------- ~ tc@box:~$ lsusb Protocol spec without prior Class and Subclass spec at line 23281 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Edited April 16, 2022 by pocopico 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2614 Posted April 16, 2022 9 minutes ago, pocopico said: DS920 dts extracted from the system patch location has only 4 ports. I guess if you need more you can keep Jumkeys. As for USB. i think its easy to figure this out by running lsusb while on TCRP. -------------------------- usb_slot@1 { vbus { syno_gpio = <0x1d 0x01>; }; usb2 { }; usb3 { usb_port = "2-1"; }; }; usb_slot@2 { vbus { syno_gpio = <0x1e 0x01>; }; usb2 { usb_port = "1-2"; }; usb3 { usb_port = "2-2"; }; }; -------------------------------------- ~ tc@box:~$ lsusb Protocol spec without prior Class and Subclass spec at line 23281 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub In your virtual environment, the usb_port = "1-1"; seems to have been erased on purpose My test environment is BAREMETAL and the USB part of jumkey's dts didn't need to be modified. Do you think my ds920p.dts should be modified based on my log below? usb_slot@1 { vbus { syno_gpio = <0x1d 0x1>; }; usb2 { usb_port = "1-1"; }; usb3 { usb_port = "2-1"; }; }; usb_slot@2 { vbus { syno_gpio = <0x1e 0x1>; }; usb2 { usb_port = "1-2"; }; usb3 { usb_port = "2-2"; }; }; ------------------------------------------- tc@box:~/redpill-load$ lsusb Protocol spec without prior Class and Subclass spec at line 23281 Bus 002 Device 003: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 003: ID 05af:1012 Jing-Mold Enterprise Co., Ltd Bus 003 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 003 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2615 Posted April 16, 2022 1 minute ago, Peter Suh said: In your virtual environment, the usb_port = "1-1"; seems to have been erased on purpose My test environment is BAREMETAL and the USB part of jumkey's dts didn't need to be modified. Do you think my ds920p.dts should be modified based on my log below? usb_slot@1 { vbus { syno_gpio = <0x1d 0x1>; }; usb2 { usb_port = "1-1"; }; usb3 { usb_port = "2-1"; }; }; usb_slot@2 { vbus { syno_gpio = <0x1e 0x1>; }; usb2 { usb_port = "1-2"; }; usb3 { usb_port = "2-2"; }; }; ------------------------------------------- tc@box:~/redpill-load$ lsusb Protocol spec without prior Class and Subclass spec at line 23281 Bus 002 Device 003: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 003: ID 05af:1012 Jing-Mold Enterprise Co., Ltd Bus 003 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 003 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub You can just move your USB Stick to another port that is configured on your DTS Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2616 Posted April 16, 2022 (edited) 8 minutes ago, pocopico said: You can just move your USB Stick to another port that is configured on your DTS I've moved the physical port location of the USB stick to the other three The log result as below came out. Then I think I have to modify the ds920p.dts file Should values 3-6 to 3-8 be used? If it is modified, should I modify the home/tc/redfill-load/ds920p.dts file directly? tc@box:~/redpill-load$ lsusb Protocol spec without prior Class and Subclass spec at line 23281 Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 006: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 003 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 003 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub tc@box:~/redpill-load$ lsusb Protocol spec without prior Class and Subclass spec at line 23281 Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 007: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 003 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 003 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub tc@box:~/redpill-load$ lsusb Protocol spec without prior Class and Subclass spec at line 23281 Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 008: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 003 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 003 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Edited April 16, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2617 Posted April 16, 2022 Yes what ever suits your purpose. I think I explained how to edit. Then you will need to rebuild your loader with the modified dtb in redpill-dtb extension Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2618 Posted April 16, 2022 33 minutes ago, pocopico said: Yes what ever suits your purpose. I think I explained how to edit. Then you will need to rebuild your loader with the modified dtb in redpill-dtb extension As you told me, I changed the part of usb_slot@1 to 3-5 The loader boot log has changed as shown below. But I still can't find the disk. usb_slot@1 { vbus { syno_gpio = <0x1d 0x1>; }; usb2 { usb_port = "3-5"; }; usb3 { usb_port = "2-1"; }; }; SynologyNAS> cat /var/log/*rc* START /linuxrc.syno.impl '/etc.defaults/model.dtb' -> '/var/run/model.dtb' Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for PeterSuh-Q3.e1000e (args: ) Loading kmod #0 "igb.ko" for PeterSuh-Q3.igb (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot - exit=0 Running "check-igb.sh" for PeterSuh-Q3.igb->on_boot Loading module igb -> Module igb loaded succesfully Ran "check-igb.sh" for PeterSuh-Q3.igb->on_boot - exit=0 Running "install_rd.sh" for jumkey.misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for jumkey.misc->on_boot - exit=0 Running "boot-wait.sh" for redpill-boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Still waiting for boot device (waited 5 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0 Running "install_rd.sh" for redpill-dtb->on_boot 'model_ds920p.dtb' -> '/etc.defaults/model.dtb' 'model_ds920p.dtb' -> '/var/run/model.dtb' Ran "install_rd.sh" for redpill-dtb->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 Exit on error [1] DISK NOT INSTALLED... Sat Apr 16 11:19:25 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2619 Posted April 16, 2022 2 minutes ago, Peter Suh said: As you told me, I changed the part of usb_slot@1 to 3-5 The loader boot log has changed as shown below. But I still can't find the disk. usb_slot@1 { vbus { syno_gpio = <0x1d 0x1>; }; usb2 { usb_port = "3-5"; }; usb3 { usb_port = "2-1"; }; }; SynologyNAS> cat /var/log/*rc* START /linuxrc.syno.impl '/etc.defaults/model.dtb' -> '/var/run/model.dtb' Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for PeterSuh-Q3.e1000e (args: ) Loading kmod #0 "igb.ko" for PeterSuh-Q3.igb (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot - exit=0 Running "check-igb.sh" for PeterSuh-Q3.igb->on_boot Loading module igb -> Module igb loaded succesfully Ran "check-igb.sh" for PeterSuh-Q3.igb->on_boot - exit=0 Running "install_rd.sh" for jumkey.misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for jumkey.misc->on_boot - exit=0 Running "boot-wait.sh" for redpill-boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Still waiting for boot device (waited 5 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0 Running "install_rd.sh" for redpill-dtb->on_boot 'model_ds920p.dtb' -> '/etc.defaults/model.dtb' 'model_ds920p.dtb' -> '/var/run/model.dtb' Ran "install_rd.sh" for redpill-dtb->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 Exit on error [1] DISK NOT INSTALLED... Sat Apr 16 11:19:25 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 Did you notice that you’ve passed the boot wait this time ? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2620 Posted April 16, 2022 2 minutes ago, pocopico said: Did you notice that you’ve passed the boot wait this time ? Of course I saw it. However, I can see an error message that I didn't see below. Exit on error [1] DISK NOT INSTALLED.. Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2621 Posted April 16, 2022 (edited) What is your request ? We were checking the USB part of the dtb. Then you jump on another issue about the internal disks part of the dtb . You internal disks should have been auto fixed by the rploader script. If not check cat /sys/block/sata[1-10]/device/syno_block_info Edited April 16, 2022 by pocopico Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2622 Posted April 16, 2022 11 minutes ago, pocopico said: What is your request ? We were checking the USB part of the dtb. Then you jump on another issue about the internal disks part of the dtb . You internal disks should have been auto fixed by the rploader script. If not check /proc/block for valid changes My final request is to recognize even one disk. The rploader script automatically changed the dts file to a 1f.2 value. Since the disk only existed on port Sata 1, it is correct that only internal Sata 1 was changed. I only modified the usb part of this file. Then, how should I check the /proc/block specifically? In ttsy, the /proc path does not show a block. Quote Link to comment Share on other sites More sharing options...
romich7 Posted April 16, 2022 Share #2623 Posted April 16, 2022 Hi all. I want to install redpill on an old GA-p35-DS4 rev.2.0 motherboard. It has 8 sata ports. When I boot from the tinycore-redpill.v0.4.6.img.gz image, I get GRUB and nothing else happens. Can I use this motherboard to install redpill? What needs to be changed in order for TinyCore to load? Thank You Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2624 Posted April 16, 2022 7 minutes ago, Peter Suh said: My final request is to recognize even one disk. The rploader script automatically changed the dts file to a 1f.2 value. Since the disk only existed on port Sata 1, it is correct that only internal Sata 1 was changed. I only modified the usb part of this file. Then, how should I check the /proc/block specifically? In ttsy, the /proc path does not show a block. Well usb port aside, i think i've had the patching of the dtb solved in rploader. It looks like you are going to need more manual editing for the local disks. The pciepath of the disks can be retrieved by checking : SynologyNAS> cat /sys/block/sata[1-12]/device/syno_block_info pciepath=00:11.0,06.0 ata_port_no=0 driver=ahci Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2625 Posted April 16, 2022 11 minutes ago, pocopico said: Well usb port aside, i think i've had the patching of the dtb solved in rploader. It looks like you are going to need more manual editing for the local disks. The pciepath of the disks can be retrieved by checking : SynologyNAS> cat /sys/block/sata[1-12]/device/syno_block_info pciepath=00:11.0,06.0 ata_port_no=0 driver=ahci Below is the result of logging as you told me. SynologyNAS> cat /sys/block/sata1/device/syno_block_info pciepath=00:1f.2 ata_port_no=0 driver=ahci And that's what the rploader found automatically ------------------------ internal_slot@1 { protocol_type = "sata"; power_pin_gpio = <0x14 0x0>; detect_pin_gpio = <0x23 0x1>; led_type = "lp3943"; ahci { pcie_root = "00:1f.2,"; ata_port = <0x0>; }; led_green { led_name = "syno_led0"; }; led_orange { led_name = "syno_led1"; }; }; ------------------------- I don't think there's a problem with this part 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.