RedPill - the new loader for 6.2.4 - Discussion

[smilenkovski]

@dolbycat

I've done that. I don't get it. I was using tinycore redpil, and the end it generated syno image in partition one. What should I do here?

Edited March 9, 2022 by smilenkovski

[dolbycat]

12 minutes ago, smilenkovski said:

@dolbycat

I've done that. I don't get it. I was using tinycore redpil, and the end it generated syno image in partition one. What should I do here?

Tc does not support ds920p yet.

I used the redpill-tool-chain below.

 

https://github.com/tossp/redpill-tool-chain

[smilenkovski]

5 minutes ago, dolbycat said:

Tc does not support ds920p yet.

I used the redpill-tool-chain below.

@dolbycat

I understand that, I've visited github and, of course , understand nothing. Can You, please , explain me what to do after modifying .dtb file and using ./redpill_tool_chain.sh auto geminilake-7.0.1-42218 to continue. I don't get it that. Where is the image file and how to make usb bootloader.

Edited March 9, 2022 by smilenkovski

[synoxpe]

6 hours ago, smilenkovski said:

@dolbycat

I understand that, I've visited github and, of course , understand nothing. Can You, please , explain me what to do after modifying .dtb file and using ./redpill_tool_chain.sh auto geminilake-7.0.1-42218 to continue. I don't get it that. Where is the image file and how to make usb bootloader.

 

The image is in the ./image folder, as per the docs. You need to flash it to a usb drive using e.g. balena etcher or rufus.

The github repo is in chinese and I used Google translate to get an english version. The actual English README gives a 404 error. Guess it's private so someone with an active Github account might want to raise an issue.

[smilenkovski]

Well, THANK YOU @synoxpe, @dolbycat for guidance. I'll report back if I succeed.

[WiteWulf]

On 3/9/2022 at 2:43 PM, RedwinX said:

English ? Cannot understand well German lol

The whole world doesn't speak English. If you don't understand the poster's native language leave it for someone else who does to respond 🙏

[synoxpe]

@RedwinX do you have a write up of how you installed the ds920+ and i915 drivers to get hw transcoding to work?

[RedwinX]

13 hours ago, synoxpe said:

@RedwinX do you have a write up of how you installed the ds920+ and i915 drivers to get hw transcoding to work?

The installation is the same way than 918+. The only extra step is the DTB file. With a J4125, no need to install a driver, it was working natively. 

For the instruction of dtb file, please follow the topic from @dolbycat, it was very helpful for me.

 

Edited March 11, 2022 by RedwinX

[shibby]

which redpill-loader will be the best choice for i5-6500t (skylake)? At the moment i am on DS918+ but i see there are new models supported by redpill. Should i migrate to other one?

 

[pLastUn]

There is an ASRock J4125-ITX board, on it 4 SATA, 2 standard Intel and 2 on the Asmedia ASM1061 chip. On DS918P-7.0.1-42218, all 4 disks are visible and operate. On DS920P-7.0.1-42218 you can see the only 2 disk. What driver is missing?

[RedwinX]

3 hours ago, pLastUn said:

There is an ASRock J4125-ITX board, on it 4 SATA, 2 standard Intel and 2 on the Asmedia ASM1061 chip. On DS918P-7.0.1-42218, all 4 disks are visible and operate. On DS920P-7.0.1-42218 you can see the only 2 disk. What driver is missing?

Not a driver. Just a misconfiguration on your dbt file. There is 2 sata controller on this board. 

Use this conf : 

root@RedwinX:~# cat /sys/block/sata1/device/syno_block_info
pciepath=00:12.0
ata_port_no=0
driver=ahci
root@RedwinX:~# cat /sys/block/sata2/device/syno_block_info
pciepath=00:12.0
ata_port_no=1
driver=ahci

root@RedwinX:~# cat /sys/block/sata3/device/syno_block_info
pciepath=00:13.3,00.0
ata_port_no=0
driver=ahci
root@RedwinX:~# cat /sys/block/sata4/device/syno_block_info
pciepath=00:13.3,00.0
ata_port_no=1
driver=ahci

 

Use 00:13.3,00.0 and 00:12.0 (port 0 & 1 for each) on the output.dbt and generate the dbt file.

Edited March 11, 2022 by RedwinX

[garciahelp]

My motherboard is a ASRock N3150-ITX with the similar configuration. I tried some configurations, but confused about the second SATA controller.

with lscpi -tnnvq i get another value for the controller

I have installed 3 hdd but only 2 are visible.

 

i tried

pciepath=00:13.0 with <0x00><0x01> and

pciepath=00:1c.3 with <0x00><0x01>

 

Confused about to use 04:00.0 or 00:1c.3.

[dolbycat]

24 minutes ago, garciahelp said:

내 마더보드는 비슷한 구성의 ASRock N3150-ITX입니다. 몇 가지 구성을 시도했지만 두 번째 SATA 컨트롤러에 대해 혼란스러웠습니다.

lscpi -tnnvq를 사용하여 컨트롤러에 대한 다른 값을 얻습니다.

3개의 HDD를 설치했지만 2개만 보입니다.

 

나는 시도했다

pciepath=00:13.0, <0x00><0x01> 및

pciepath=00:1c.3(<0x00><0x01> 포함)

 

04:00.0 또는 00:1c.3을 사용하려고 혼동합니다.

 

 

pciepath=00:1c.3                ( X )

 

pciepath=00:1c.3,00.0       ( O )

[Peter Suh]

On 3/8/2022 at 8:58 AM, jumkey said:

Try on AMD platform, use the same way as DS920+ to create dtb file

DS1621+😅

 

I share some results of the test with @pocopico's tc,ds1621+.
The driver of r8169 does not seem to operate as the bootloader of ds1621+, which was well recognized as the HASWELL mainboard and ds3622xs+ bootloader.
@jumkey told us to try the AMD platform, so I tried it with R8169 of Ryzen 3300x, 3500x, and 3700x, but it didn't work either.
Rather, it operated normally when the 8th generation coffee lake cpu such as i5-8500t and g5500 and r8169 (RTL8111H CHIPSET) were combined.
This part had the help of @dolbycat.
For now, ds1621+ seems to be a little tricky in using cpu. Just like Jun loader ds918+ supported from HASWELL in the past.
More test data is needed for Sky lake, Kaby Lake, and other generations of CPUs.

Edited March 12, 2022 by Peter Suh

[dolbycat]

20 minutes ago, Peter Suh said:

 

I share some results of the test with @pocopico's tc,ds1621+.
The driver of r8169 does not seem to operate as the bootloader of ds1621+, which was well recognized as the HASWELL mainboard and ds3622xs+ bootloader.
@jumkey told us to try the AMD platform, so I tried it with R8169 of Ryzen 3300x, 3500x, and 3700x, but it didn't work either.
Rather, it operated normally when the 8th generation coffee lake cpu such as i5-8500t and g5500 and r8169 (RTL8111H CHIPSET) were combined.
This part had the help of @dolbycat.
For now, ds1621+ seems to be a little tricky in using cpu. Just like Jun loader ds918+ supported from HASWELL in the past.
More test data is needed for Sky lake, Kaby Lake, and other generations of CPUs.

 

Extension drivers should not apply.
If applied, the hard disk cannot be found.

You still need to use pure realtek LAN.

[Peter Suh]

4 minutes ago, dolbycat said:

 

Extension drivers should not apply.
If applied, the hard disk cannot be found.

You still need to use pure realtek LAN.

 

The extension driver was not applied manually.
This is the result of using only r8169, which TC automatically finds.

 

The focus is on NIC behavior rather than trying to find the hard drive with dtc.

Edited March 12, 2022 by Peter Suh

[dolbycat]

DS920+ ,DS1621+ Bootloader Workflow

 

* Asrock J5040, Debian 11.

 

1 ) Boot Asrock J5040 with tinycore and check the pcie_root value of "output.dts" file.

 

tc@box:~$ lspci -tnnvq
-[0000:00]-+-00.0 Intel Corporation Gemini Lake Host Bridge [8086:31f0]
           +-00.1 Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant [8086:318c]
           +-02.0 Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184]
           +-0e.0 Intel Corporation Celeron/Pentium Silver Processor High Definition Audio [8086:3198]
           +-0f.0 Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface [8086:319a]
           +-12.0 Intel Corporation Celeron/Pentium Silver Processor SATA Controller [8086:31e3]
           +-13.0-[01]--+-00.0 Intel Corporation 82575EB Gigabit Network Connection [8086:10a7]
           | \-00.1 Intel Corporation 82575EB Gigabit Network Connection [8086:10a7]
           +-13.1-[02]----00.0 JMicron Technology Corp. JMB58x AHCI SATA controller [197b:0585]
           +-13.2-[03]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168]
           +-13.3-[04]----00.0 ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612]
           +-15.0 Intel Corporation Celeron/Pentium Silver Processor USB 3.0 xHCI Controller [8086:31a8]
           +-1f.0 Intel Corporation Celeron/Pentium Silver Processor LPC Controller [8086:31e8]
           \-1f.1 Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model [8086:31d4]

tc@box:~$

 

2 ) Look at the above sentence and set the following values to be included in the attached "output.dts" file.

 

pcie_root = "00:12.0"
pcie_root = "00:13.1,00.0"
pcie_root = "00:13.3,00.0"

 

 

 

Unpack the attached "outout.zip" file and edit the "output.dts" file in the ds1621 ( DS920 ) folder with an editor as shown below.

 

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.1,00.0";
            ata_port = <0x01>;

pcie_root = "00:13.3,00.0";
            ata_port = <0x00>;

pcie_root = "00:13.3,00.0";
            ata_port = <0x01>;

 

3) Put the modified "output.dts" file in the "redpill-tool-chain-master" folder.

 

https://github.com/tossp/redpill-tool-chain

 

After modifying the "sample_user_config.json" file in the "redpill-tool-chain-master folder" to suit your system, rename it to "ds1621p_user_config.json" and save it.

 

 

4) Copy the "redpill-tool-chain-master" folder to debian 11.

 

5) Follow the procedure below.

 

sudo apt-get update

sudo apt install docker.io

sudo apt install jq

sudo apt install curl

sudo apt install device-tree-compiler

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 ds1621p-7.0.1-42218

./redpill_tool_chain.sh auto ds1621p-7.0.1-42218

 

dtc -I dts -O dtb output.dts > model_ds1621p.dtb

cp model_ds1621p.dtb ./custom/extensions/jumkey.dtb/ds1621p_42218

 

./redpill_tool_chain.sh auto ds1621p-7.0.1-42218

6) Finally, Delete the first "redpill-DS1621+_7.0.1-xxxxxxxx.img" file in the image folder and use the second created redpill-DS1621+_7.0.1-xxxxxxxx.img file.

 

 

< Note >

 

1 )  More accurate pcie_root and ata_port values can be obtained in the following way.

 

cat /sys/block/sataX/device/syno_block_info

X=1~6

 

2) If the extension driver is used, the hard disk is not recognized. You must have a Realtek LAN.

output.zip

Edited March 12, 2022 by dolbycat

[Peter Suh]

I have a very happy news today.
It seems that there is no longer a need to think about adjusting the SataPortMap figures.
In the past, as if the number of HDD physically connected to the Sataport in the Jun loader had to be recorded without caring about the number of ports.
This is the method proposed by "TheSTREET," which is not active in the forum here but is active in NAS-related forums in Korea.
The HotPlug (or HotSWAP) function of the built-in SATA port on the BIOS is changed to enabled.
In this way, it does not matter if the SataPortMap=6, which was automatically found by the internal TC, is left from the DSM installation stage as shown in the attached image.
Attached is the result of the test below.
The error of turning off the Hot Plug,
This is the result after HotPlug is turned on.
If "TheSTREET" allows, we plan to create and post details related to this as topics in the future.

 

 

Edited March 12, 2022 by Peter Suh

[Peter Suh]

12 hours ago, dolbycat said:

DS920+ ,DS1621+ Bootloader Workflow

 

* Asrock J5040, Debian 11.

 

1 ) Boot Asrock J5040 with tinycore and check the pcie_root value of "output.dts" file.

 

tc@box:~$ lspci -tnnvq
-[0000:00]-+-00.0 Intel Corporation Gemini Lake Host Bridge [8086:31f0]
           +-00.1 Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant [8086:318c]
           +-02.0 Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184]
           +-0e.0 Intel Corporation Celeron/Pentium Silver Processor High Definition Audio [8086:3198]
           +-0f.0 Intel Corporation Celeron/Pentium Silver Processor Trusted Execution Engine Interface [8086:319a]
           +-12.0 Intel Corporation Celeron/Pentium Silver Processor SATA Controller [8086:31e3]
           +-13.0-[01]--+-00.0 Intel Corporation 82575EB Gigabit Network Connection [8086:10a7]
           | \-00.1 Intel Corporation 82575EB Gigabit Network Connection [8086:10a7]
           +-13.1-[02]----00.0 JMicron Technology Corp. JMB58x AHCI SATA controller [197b:0585]
           +-13.2-[03]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168]
           +-13.3-[04]----00.0 ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612]
           +-15.0 Intel Corporation Celeron/Pentium Silver Processor USB 3.0 xHCI Controller [8086:31a8]
           +-1f.0 Intel Corporation Celeron/Pentium Silver Processor LPC Controller [8086:31e8]
           \-1f.1 Intel Corporation Celeron/Pentium Silver Processor Gaussian Mixture Model [8086:31d4]

tc@box:~$

 

2 ) Look at the above sentence and set the following values to be included in the attached "output.dts" file.

 

pcie_root = "00:12.0"
pcie_root = "00:13.1,00.0"
pcie_root = "00:13.3,00.0"

 

 

 

Unpack the attached "outout.zip" file and edit the "output.dts" file in the ds1621 ( DS920 ) folder with an editor as shown below.

 

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.1,00.0";
            ata_port = <0x01>;

pcie_root = "00:13.3,00.0";
            ata_port = <0x00>;

pcie_root = "00:13.3,00.0";
            ata_port = <0x01>;

 

3) Put the modified "output.dts" file in the "redpill-tool-chain-master" folder.

 

https://github.com/tossp/redpill-tool-chain

 

After modifying the "sample_user_config.json" file in the "redpill-tool-chain-master folder" to suit your system, rename it to "ds1621p_user_config.json" and save it.

 

 

4) Copy the "redpill-tool-chain-master" folder to debian 11.

 

5) Follow the procedure below.

 

sudo apt-get update

sudo apt install docker.io

sudo apt install jq

sudo apt install curl

sudo apt install device-tree-compiler

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 ds1621p-7.0.1-42218

./redpill_tool_chain.sh auto ds1621p-7.0.1-42218

 

dtc -I dts -O dtb output.dts > model_ds1621p.dtb

cp model_ds1621p.dtb ./custom/extensions/jumkey.dtb/ds1621p_42218

 

./redpill_tool_chain.sh auto ds1621p-7.0.1-42218

6) Finally, Delete the first "redpill-DS1621+_7.0.1-xxxxxxxx.img" file in the image folder and use the second created redpill-DS1621+_7.0.1-xxxxxxxx.img file.

 

 

< Note >

 

1 )  More accurate pcie_root and ata_port values can be obtained in the following way.

 

cat /sys/block/sataX/device/syno_block_info

X=1~6

 

2) If the extension driver is used, the hard disk is not recognized. You must have a Realtek LAN.

output.zip 1.69 kB · 6 downloads

 

Thanks to @dolbycat, both ds920+ and ds1621+ were easily successful.

The CPU specification used is 920 is Haswell Refresh G3240, and 1621 is Coffee Lake G5500.

As I told you in advance below, DS1621+ is not recognized by Haswell. I tested it one more time.

What's a little different from @dolbycat is that it was built using Synology Linux without using Ubuntu or Devian Linux.

Synology Linux doesn't have an apt command, so it's not easy to download this and that.

So, I only need to meet the dtc (device-tree-compiler), so I replaced this with the dtc BIN file that is newly listed on @pocopico's Tinycore Red PILL GitHub.

If there is no SATA pcie_root information mapping due to dtc operation, the HDD of the SATA port is not recognized normally, so it cannot proceed during the DSM installation process.

The lspci-tnnvq command to find out pcie_root information is a Linux default command, so I think you can check it anywhere if you can just float Linux. (Synology Linux, TC Linux, Ubuntu, Debian, etc.)

It would be very convenient if you could automate the dtc and dtb-related parts in the toolchain or TC later.

@tossp, @pocopico If you don't do it, I can make it. Haha

 

[pocopico]

6 minutes ago, Peter Suh said:

 

Thanks to @dolbycat, both ds920+ and ds1621+ were easily successful.

The CPU specification used is 920 is Haswell Refresh G3240, and 1621 is Coffee Lake G5500.

As I told you in advance below, DS1621+ is not recognized by Haswell. I tested it one more time.

What's a little different from @dolbycat is that it was built using Synology Linux without using Ubuntu or Devian Linux.

Synology Linux doesn't have an apt command, so it's not easy to download this and that.

So, I only need to meet the dtc (device-tree-compiler), so I replaced this with the dtc BIN file that is newly listed on @pocopico's Tinycore Red PILL GitHub.

If there is no SATA pcie_root information mapping due to dtc operation, the HDD of the SATA port is not recognized normally, so it cannot proceed during the DSM installation process.

The lspci-tnnvq command to find out pcie_root information is a Linux default command, so I think you can check it anywhere if you can just float Linux. (Synology Linux, TC Linux, Ubuntu, Debian, etc.)

It would be very convenient if you could automate the dtc and dtb-related parts in the toolchain or TC later.

@tossp, @pocopico If you don't do it, I can make it. Haha

 

Sure, feel free to PR your contributed code in rploader. 

[painkiller895]

1 hour ago, Peter Suh said:

 

Thanks to @dolbycat, both ds920+ and ds1621+ were easily successful.

The CPU specification used is 920 is Haswell Refresh G3240, and 1621 is Coffee Lake G5500.

As I told you in advance below, DS1621+ is not recognized by Haswell. I tested it one more time.

What's a little different from @dolbycat is that it was built using Synology Linux without using Ubuntu or Devian Linux.

Synology Linux doesn't have an apt command, so it's not easy to download this and that.

So, I only need to meet the dtc (device-tree-compiler), so I replaced this with the dtc BIN file that is newly listed on @pocopico's Tinycore Red PILL GitHub.

If there is no SATA pcie_root information mapping due to dtc operation, the HDD of the SATA port is not recognized normally, so it cannot proceed during the DSM installation process.

The lspci-tnnvq command to find out pcie_root information is a Linux default command, so I think you can check it anywhere if you can just float Linux. (Synology Linux, TC Linux, Ubuntu, Debian, etc.)

It would be very convenient if you could automate the dtc and dtb-related parts in the toolchain or TC later.

@tossp, @pocopico If you don't do it, I can make it. Haha

 

That's awesome !

[Peter Suh]

9 hours ago, Peter Suh said:

I have a very happy news today.
It seems that there is no longer a need to think about adjusting the SataPortMap figures.
In the past, as if the number of HDD physically connected to the Sataport in the Jun loader had to be recorded without caring about the number of ports.
This is the method proposed by "TheSTREET," which is not active in the forum here but is active in NAS-related forums in Korea.
The HotPlug (or HotSWAP) function of the built-in SATA port on the BIOS is changed to enabled.
In this way, it does not matter if the SataPortMap=6, which was automatically found by the internal TC, is left from the DSM installation stage as shown in the attached image.
Attached is the result of the test below.
The error of turning off the Hot Plug,
This is the result after HotPlug is turned on.
If "TheSTREET" allows, we plan to create and post details related to this as topics in the future.

 

 

 

 

This is a detailed description of "TheSTREET" mentioned above about the relationship between hot plus and SataPortMap.

 

 

[Peter Suh]

17 hours ago, Peter Suh said:

 

I share some results of the test with @pocopico's tc,ds1621+.
The driver of r8169 does not seem to operate as the bootloader of ds1621+, which was well recognized as the HASWELL mainboard and ds3622xs+ bootloader.
@jumkey told us to try the AMD platform, so I tried it with R8169 of Ryzen 3300x, 3500x, and 3700x, but it didn't work either.
Rather, it operated normally when the 8th generation coffee lake cpu such as i5-8500t and g5500 and r8169 (RTL8111H CHIPSET) were combined.
This part had the help of @dolbycat.
For now, ds1621+ seems to be a little tricky in using cpu. Just like Jun loader ds918+ supported from HASWELL in the past.
More test data is needed for Sky lake, Kaby Lake, and other generations of CPUs.

 

Ryzen's 3rd generation Matis has also confirmed that it is normally recognized as DS1621+, Realtec NIC with the tool-chain loader that @dolbycat introduced.
I haven't done DTC work yet, so I checked if only LAN was activated.
I think it will be available with DTC.
I think you can put on Ryzen.

[Aigor]

22 minutes ago, Peter Suh said:

 

 

This is a detailed description of "TheSTREET" mentioned above about the relationship between hot plus and SataPortMap.

 

 

We can't see 

[Peter Suh]

10 hours ago, Aigor said:

We can't see 

 

I'm sorry. I accidentally put it on the testing tree, so no one can see it.
The topic has been put back on the tutorial and guide and is currently pending approval.