RedPill - the new loader for 6.2.4 - Discussion

RedwinX · March 7, 2022

4 hours ago, Orphée said:

Okay, let us know then

Right, works fine for installation (thx @dolbycat). I'm installing docker with plex to test HW transcoding lol, let me some time ahahah, just get back from work ahahah

Edited March 7, 2022 by RedwinX

RedwinX · March 7, 2022

Works !!!!! I can confirm you that i915 works like a charm on ds920+ (Asrock J4125). HW transcoding is ok ! And you can say me that I dream, but redpill 920+ is more stable on a J4125 than a redpill 918+. System is more efficient

Edited March 7, 2022 by RedwinX

jumkey · March 7, 2022

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

DS1621+😅

RedwinX · March 8, 2022

7 hours ago, jumkey said:

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

DS1621+😅

Have a TS-873U-RP and TS-463U-RP with AMD to test. It will be funny to test a Qnaplogy

bonus : try the J4125 and J5040, can confirm full works only in 920+ firmware (918+ ko for

lot of features)

ema · March 8, 2022

14 hours ago, RedwinX said:

Works !!!!! I can confirm you that i915 works like a charm on ds920+ (Asrock J4125). HW transcoding is ok ! And you can say me that I dream, but redpill 920+ is more stable on a J4125 than a redpill 918+. System is more efficient

I can confirm it works for me too (HW transcoding is ok w real sn & mac). I used a minipc (minisforum GK41 / J4125 / 8Gb / 1tb SSD / dual realtek nic)

Thanks to all!

shibby · March 8, 2022

is there any way to load new kernel module on boot without recompile redpill-load? I need atlantic.ko. I tried copy module to /usr/lib/modules and create load file in /usr/lib/modules-load.d but after reboot module is not loaded.

Peter Suh · March 8, 2022

5 minutes ago, shibby said:

is there any way to load new kernel module on boot without recompile redpill-load? I need atlantic.ko. I tried copy module to /usr/lib/modules and create load file in /usr/lib/modules-load.d but after reboot module is not loaded.

Is there a reason why it is difficult for the redpill loader to recompile?
If you build with the Tinycore redpill of @pocopico, I think that atlantic.ko will be automatically added and recognized.

https://raw.githubusercontent.com/pocopico/rp-ext/master/atlantic/rpext-index.json

shibby · March 8, 2022

15 minutes ago, Peter Suh said:

Is there a reason

yes, it does

Peter Suh · March 8, 2022

1 hour ago, shibby said:

yes, it does

If H/W transcoding is not required, wouldn't you consider processing the migration change to DS3622xs+?

The atlantic.ko driver of pocopico seems to have been updated to the final version 21 days ago.

shibby · March 8, 2022

i`m using plex so h/w transcoding is required. I`m happy with using DS918+. All i need is switch my old 10gigs card (tn40xx) to new one (atlantic). At the moment i have to use build-in e1000e.

Peter Suh · March 8, 2022

38 minutes ago, shibby said:

i`m using plex so h/w transcoding is required. I`m happy with using DS918+. All i need is switch my old 10gigs card (tn40xx) to new one (atlantic). At the moment i have to use build-in e1000e.

Now, the number of XPEnology's support models is increasing, and there are many drivers to apply for each of these models.

I think it's very overwhelming for Pocopico to break down all these drivers from Synology by himself and make them for XPEnology.

I really want to help if I can. For now, the driver update of DS918+ seems to be the most behind. Shouldn't we wait a long time for the news of the driver update of the pocopico?

shibby · March 8, 2022

atlantic module is working (i tested @pocopico and compiled myself new one). The problem is how to force it to load at boot:

1) copying to /usr/lib/modules + load file in /usr/lib/mobules-load.d doesn`t work

2) compile new redpill loader with build-in atlantic module is not a solution for me because after boot DSM wants to make a fresh instalation and i dont know why.

pocopico · March 8, 2022

1 minute ago, shibby said:

atlantic module is working (i tested @pocopico and compiled myself new one). The problem is how to force it to load at boot:

1) copying to /usr/lib/modules + load file in /usr/lib/mobules-load.d doesn`t work

2) compile new redpill loader with build-in atlantic module is not a solution for me because after boot DSM wants to make a fresh instalation and i dont know why.

Are you looking after 918 platform ?

shibby · March 8, 2022

1 minute ago, pocopico said:

Are you looking after 918 platform ?

what do you mean?

pocopico · March 8, 2022

1 minute ago, shibby said:

what do you mean?

I just recompiled the 918 atlantic extension. Can you please retry ?

shibby · March 8, 2022

but your module is working fine (i can load it manually but i cannot (dont know how) load it at boot)

When i compile new redpill loader (even using yours tinycore), then synology assisntant detect my NAS as "not installed". But is detected so yours atlantic module works. So why DSM doesn`t see previous instalation (even migradable) and want to make a fresh one?

RedwinX · March 8, 2022

On 3/7/2022 at 3:30 PM, 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.

Have a little question :

Here's my 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: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 = "00:12.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:12.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";
};
};

But when I plug 3 disk, only 2 are reconized.

image.png.c7f66dc628a061f8a4caf910d8037631.png

However, when I check in SSH, I can see 3 SATA...

Any idea ?

EDIT : I think I found the solution :

Regarding the spec of motherboard (https://www.asrock.com/MB/Intel/J5040-ITX/index.fr.asp#Specification) there is 2 sata connector. So I need to modify the slot 3 & 4 with the correct ID (with ASMedia so)

@dolbycatdid you think I have to make ASMedia with ata_port at 0 & 1 or 3 & 4 ?

Edited March 8, 2022 by RedwinX

dolbycat · March 8, 2022

internal_slot@3
pcie_root = "00:13.3,00.0"
ata_port = <0x01>

=> DS920+ recognized as the 3rd slot

internal_slot@4
pcie_root = "00:13.3,00.0"
ata_port = <0x01>

=> DS920+ recognized as the 4th slot

internal_slot@5
pcie_root = "00:13.3,00.0"
ata_port = <0x01>

=> DS920+ recognized as slot 5

internal_slot@6
pcie_root = "00:13.3,00.0"
ata_port = <0x01>

=> DS920+ recognized as the 6th slot

jumkey's "The new PortMapping ext(redpill-dtb)" seems great.
There seems to be no need to worry about SataPortMap and DiskIdxMap anymore.

Edited March 8, 2022 by dolbycat

RedwinX · March 8, 2022

3 hours ago, dolbycat said:

internal_slot@3
pcie_root = "00:13.3,00.0"
ata_port = <0x01>

=> DS920+ recognized as the 3rd slot

internal_slot@4
pcie_root = "00:13.3,00.0"
ata_port = <0x01>

=> DS920+ recognized as the 4th slot

internal_slot@5
pcie_root = "00:13.3,00.0"
ata_port = <0x01>

=> DS920+ recognized as slot 5

internal_slot@6
pcie_root = "00:13.3,00.0"
ata_port = <0x01>

=> DS920+ recognized as the 6th slot

jumkey's "The new PortMapping ext(redpill-dtb)" seems great.
There seems to be no need to worry about SataPortMap and DiskIdxMap anymore.

Works fine ! thx !

garciahelp · March 9, 2022

Ich habe mittels Tinycore erfolgreich den Loader für die DS918+ erstellen und auf der Baremetal installieren können.
Nun möchte ich auf dieser Maschine (Asrock N3150-ITX, Intel® 8th generation (Gen 8) graphic [8086:22b1] etc.) das HW transcoding,
Docker, Photo usw testen.

Derzeit bin ich am einlesen und prüfen, welche Auswirkungen die Meldungen haben:

root@DS918_N3150:/# dmesg | grep error
[    5.741305] intel-lpss: probe of 0001:00:16.0 failed with error -22
[    5.748276] intel-lpss: probe of 0001:00:18.0 failed with error -22
[    5.755130] intel-lpss: probe of 0001:00:19.0 failed with error -22
[    5.762000] intel-lpss: probe of 0001:00:19.2 failed with error -22
[    7.400763] ahci: probe of 0001:01:00.0 failed with error -22
[    7.407073] ahci: probe of 0001:00:12.0 failed with error -22
[    8.087065] xhci_hcd: probe of 0001:00:15.0 failed with error -16
[   27.299463] igb: probe of 0001:02:00.0 failed with error -5
[   27.305474] igb: probe of 0001:03:00.0 failed with error -5
[   38.457516] r8169 0000:03:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2

Nachdem ich dann ein paar Themen zum DS920+ gelesen habe (Asrock J4125) wollte ich mir den entsprechenden Loader bauen.
Unter einer VM auf Ubuntu konnte ich einen erstellen, er startet, aber er ich kann die Version nicht installieren,
da er keine Laufwerke findet.

Nun wollte ich mir diesen mittels TC (0.4.6.0) direkt auf der Baremetal-Maschine erstellen.
Leider komme ich da nicht weiter, es fehlen ein paar Informationen.

Wer kann mir einen Tip geben ? Danke schonmal....

RedwinX · March 9, 2022

1 hour ago, garciahelp said:
Ich habe mittels Tinycore erfolgreich den Loader für die DS918+ erstellen und auf der Baremetal installieren können.
Nun möchte ich auf dieser Maschine (Asrock N3150-ITX, Intel® 8th generation (Gen 😎 graphic [8086:22b1] etc.) das HW transcoding,
Docker, Photo usw testen.

Derzeit bin ich am einlesen und prüfen, welche Auswirkungen die Meldungen haben:
root@DS918_N3150:/# dmesg | grep error
[    5.741305] intel-lpss: probe of 0001:00:16.0 failed with error -22
[    5.748276] intel-lpss: probe of 0001:00:18.0 failed with error -22
[    5.755130] intel-lpss: probe of 0001:00:19.0 failed with error -22
[    5.762000] intel-lpss: probe of 0001:00:19.2 failed with error -22
[    7.400763] ahci: probe of 0001:01:00.0 failed with error -22
[    7.407073] ahci: probe of 0001:00:12.0 failed with error -22
[    8.087065] xhci_hcd: probe of 0001:00:15.0 failed with error -16
[   27.299463] igb: probe of 0001:02:00.0 failed with error -5
[   27.305474] igb: probe of 0001:03:00.0 failed with error -5
[   38.457516] r8169 0000:03:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2
Nachdem ich dann ein paar Themen zum DS920+ gelesen habe (Asrock J4125) wollte ich mir den entsprechenden Loader bauen.
Unter einer VM auf Ubuntu konnte ich einen erstellen, er startet, aber er ich kann die Version nicht installieren,
da er keine Laufwerke findet.

Nun wollte ich mir diesen mittels TC (0.4.6.0) direkt auf der Baremetal-Maschine erstellen.
Leider komme ich da nicht weiter, es fehlen ein paar Informationen.

Wer kann mir einen Tip geben ? Danke schonmal....

English ? Cannot understand well German lol

smilenkovski · March 9, 2022

On 3/5/2022 at 1:10 PM, dolbycat said:

'm a beginner, so there may be some mistakes. I would be grateful if the seniors could improve it

@dolbycat

I'm beginner You are advanced user. I followed your instructions edited according j5040 and compile dtb file. Now what? How to make bootable usb ?

Edited March 9, 2022 by smilenkovski

garciahelp · March 9, 2022

2 hours ago, garciahelp said:
I was able to successfully create the loader for the DS918+ using Tinycore and install it on the Baremetal.
Now I want to transcoding the HW on this machine (Asrock N3150-ITX, Intel® 8th generation (Gen 😎 graphic [8086:22b1] etc.),
Test Docker, Photo, etc.

I am currently reading in and checking what effects the messages have:
root@DS918_N3150:/# dmesg | grep error
[    5.741305] intel-lpss: probe of 0001:00:16.0 failed with error -22
[    5.748276] intel-lpss: probe of 0001:00:18.0 failed with error -22
[    5.755130] intel-lpss: probe of 0001:00:19.0 failed with error -22
[    5.762000] intel-lpss: probe of 0001:00:19.2 failed with error -22
[    7.400763] ahci: probe of 0001:01:00.0 failed with error -22
[    7.407073] ahci: probe of 0001:00:12.0 failed with error -22
[    8.087065] xhci_hcd: probe of 0001:00:15.0 failed with error -16
[   27.299463] igb: probe of 0001:02:00.0 failed with error -5
[   27.305474] igb: probe of 0001:03:00.0 failed with error -5
[   38.457516] r8169 0000:03:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2
After reading a few topics about the DS920+ (Asrock J4125) I wanted to build the appropriate loader.
Under a VM on Ubuntu I could create one, it starts, but it I can't install the DSM,
because it can't find any drives.

Now I wanted to create this using TC (0.4.6.0) directly on the baremetal machine.
Unfortunately, I can't get any further, there is a lack of some informations.

Who can give me a tip? Thank you very much....

Sorry my fault regarding the language.

dolbycat · March 9, 2022

6 hours ago, smilenkovski said:

@dolbycat

I'm beginner You are advanced user. I followed your instructions edited according j5040 and compile dtb file. Now what? How to make bootable usb ?

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

dolbycat · March 9, 2022

6 hours ago, smilenkovski said:

@dolbycat

I'm beginner You are advanced user. I followed your instructions edited according j5040 and compile dtb file. Now what? How to make bootable usb ?

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

RedPill - the new loader for 6.2.4 - Discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites