TinyCore RedPill loader (TCRP) - Development release 0.9

[djvas335]

27 minutes ago, Peter Suh said:

 

 

Since igb already has vanilla modules, it seems to work without installing all-modules like my T1700.

 

As in the caption below
Comment out LINE 293 of my.sh with #.
Delete LINE 2490 in custom_config.json.
Can this be done with the vi editor?

 

Modification to persist modified custom_config.json .

 

 

 

Once you have finished editing, build DS3622xs+ 7.2 again from the menu.

 

Determination of whether the all-modules integration pack has been correctly removed is successful if only misc and nvme-cache are mentioned in the Removing model exts directories at the end of the loader's build log as shown below and all-modules are not present.
There is nothing to delete because it has never been added.

 

 

I have changed the files according to instructions and rebuilt the loader, however after the restart the system is now listed as not installed in Synology Assistant

Edited June 1, 2023 by djvas335

[Peter Suh]

43 minutes ago, djvas335 said:

 

I have changed the files according to instructions and rebuilt the loader, however after the restart the system is now listed as not installed in Synology Assistant

 

It looks like the vanilla igb module is not compatible with your nic's pid/vid.
I will prepare to add the igb module instead and let you know again.

[Peter Suh]

2 hours ago, djvas335 said:

 

I have changed the files according to instructions and rebuilt the loader, however after the restart the system is now listed as not installed in Synology Assistant

 

 

We prepared igb.ko for use with DS3622xs+.
to LINE 4290 in custom_config.json like below
Please add this again.

"PeterSuh-Q3.igb": "https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/igb/rpext-index.json",

Rebuilding the loader is OK if you see the message below in the log.

 

 

[HonB]

I have used the final build with UEFI boot. I use USB dongle 3.0.

Install for DSN 7.2 is good. Reboot is good too. But after shutdown and wake up by schedule in BIOS setting. Boot screen mention that it can not mount tcrp-1

Then I do manual reboo.t it is ok.

How to solve this issue ? Thank you so much.

[Peter Suh]

11 minutes ago, HonB said:

I have used the final build with UEFI boot. I use USB dongle 3.0.

Install for DSN 7.2 is good. Reboot is good too. But after shutdown and wake up by schedule in BIOS setting. Boot screen mention that it can not mount tcrp-1

Then I do manual reboo.t it is ok.

How to solve this issue ? Thank you so much.

 

There is a problem that the three partitions assigned to the USB cannot be found. Is it possible to switch from BIOS to legacy instead of UEFI?

[djvas335]

50 minutes ago, Peter Suh said:

 

 

We prepared igb.ko for use with DS3622xs+.
to LINE 4290 in custom_config.json like below
Please add this again.

"PeterSuh-Q3.igb": "https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/igb/rpext-index.json",

Rebuilding the loader is OK if you see the message below in the log.

 

 

 

I followed your instructions and got a corresponding entry in the log however my device still shows as not installed, I added the entry on line 2490 by the way

 

 

[Peter Suh]

18 minutes ago, djvas335 said:

 

I followed your instructions and got a corresponding entry in the log however my device still shows as not installed, I added the entry on line 2490 by the way

 

 

 

The explanation isn't clear.
The igb I added worked, but can this mean that mlx4 is showing the same message as the capture from dmesg?

[djvas335]

4 minutes ago, Peter Suh said:

 

The explanation isn't clear.
The igb I added worked, but can this mean that mlx4 is showing the same message as the capture from dmesg?

Let me explain better, I added your igb entry on line 2490 and rebuilt the loader, after restart the system shows as not installed, I even tried to upload the dsm installation file and after reboot it still shows as not installed in Synology Assistant

[Peter Suh]

24 minutes ago, djvas335 said:

Let me explain better, I added your igb entry on line 2490 and rebuilt the loader, after restart the system shows as not installed, I even tried to upload the dsm installation file and after reboot it still shows as not installed in Synology Assistant

 

Removed mlx4_core.ko and mlx4_en.ko, the way you initially wanted, from the all-modules integration pack as shown below.

 

 

Please remove the # comment in my.sh LINE 293 as it was.

 

custom_config.json will be automatically restored in the same way that it refers to all-modules as before.

If the log shows that you deleted all-modules , that's OK.
It will probably be the last try.
Please test.

[djvas335]

21 minutes ago, Peter Suh said:

 

Removed mlx4_core.ko and mlx4_en.ko, the way you initially wanted, from the all-modules integration pack as shown below.

 

 

Please remove the # comment in my.sh LINE 293 as it was.

 

custom_config.json will be automatically restored in the same way that it refers to all-modules as before.

If the log shows that you deleted all-modules , that's OK.
It will probably be the last try.
Please test.

Success, the system started up and working properly, below screen with dmesg with correct driver, do you maybe need some additional information ?

 

 

Edited June 1, 2023 by djvas335

[Peter Suh]

40 minutes ago, djvas335 said:

Success, the system started up and working properly, below screen with dmesg with correct driver, do you maybe need some additional information ?

 

 

 

 

This content alone is sufficient.
Your prediction was correct. Congratulations.

A second case was identified where a vanilla module was sufficient for a 10G NIC.
Intel ixgbe was the same case.

ARPL fabio's method used the method of copying the vanilla driver as it is and including it as a module of XPE.
In the case of mlx4, it seems that the same method should be used.

That way, you can install DSM with just mlx4 without the help of additional modules like igb.
I will spread it to redfill developers and fix the module.
thank you

[djvas335]

5 minutes ago, Peter Suh said:

 

 

This content alone is sufficient.
Your prediction was correct. Congratulations.

A second case was identified where a vanilla module was sufficient for a 10G NIC.
Intel ixgbe was the same case.

ARPL fabio's method used the method of copying the vanilla driver as it is and including it as a module of XPE.
In the case of mlx4, it seems that the same method should be used.

That way, you can install DSM with just mlx4 without the help of additional modules like igb.
I will spread it to redfill developers and fix the module.
thank you

Thank you very much for your time and support, I really appreciate this

[Blubster]

@pocopico

Regarding my issue with the integrated Aquantia AQC107 in Terramaster F5-422, it appears atlantic driver needs something it does not have :

When i compared the content of the old way to add drivers (if i understand correctly), the atlantic-4.4.180plus.tgz contained two files :

But when i check the all-module release apollolake-4.4.302.tgz available here, while it does have atlantic.ko, it does not have any crc-itu-t.ko in it.

My issue, if i understand correctly, would be that the atlantic.ko driver is indeed there but that it would need another kernel module for it to work, am i right?

 

EDIT : i should add, the crc-itu-t.ko was indeed there in the apollolake-4.4.180.tgz file.

 

EDIT 2 : the header file crc-itu-t.h is indeed included in the source code of the atlantic driver here, which would confirm it is required.

 

Edited June 1, 2023 by Blubster

[Peter Suh]

4 hours ago, djvas335 said:

Thank you very much for your time and support, I really appreciate this

 

If you can, may I ask you to take one last test?

As mentioned, I ported mlx4's vanilla driver to the all-modules integration pack, replacing the compiled module.

What is shown in the capture is not the DS3622xs+ with DSM installed
This is /lib/modules of Junior level before DSM installation.
The files you checked with me in DSM will be confirmed.

 

 

You only need to build 7.2-64561 one more time from the M SHELL menu without any manipulation.

It would be best to turn off the igb nic,
Can you test the DSM installation process with the IP address given to mlx4?

 

[djvas335]

1 hour ago, Peter Suh said:

 

If you can, may I ask you to take one last test?

As mentioned, I ported mlx4's vanilla driver to the all-modules integration pack, replacing the compiled module.

What is shown in the capture is not the DS3622xs+ with DSM installed
This is /lib/modules of Junior level before DSM installation.
The files you checked with me in DSM will be confirmed.

 

 

You only need to build 7.2-64561 one more time from the M SHELL menu without any manipulation.

It would be best to turn off the igb nic,
Can you test the DSM installation process with the IP address given to mlx4?

 

 

Sure, I can test, however I can't disable the IGB because of the particularities of my setup, ie I can't access mellanox nic directly because it's on another network switch which I do not have direct access to and is only used for the storage network, please tell me if you still want me to do the test without disabling the igb nic

[Peter Suh]

13 minutes ago, djvas335 said:

 

Sure, I can test, however I can't disable the IGB because of the particularities of my setup, ie I can't access mellanox nic directly because it's on another network switch which I do not have direct access to and is only used for the storage network, please tell me if you still want me to do the test without disabling the igb nic

 

keep igb active(It would be good to unplug the igb nic cable.),
Instead, please confirm that mlx4 is given an IP on Synology Assist and operates. After that, please check dmesg one more time in the same way.

Edited June 1, 2023 by Peter Suh

[djvas335]

2 hours ago, Peter Suh said:

 

keep igb active(It would be good to unplug the igb nic cable.),
Instead, please confirm that mlx4 is given an IP on Synology Assist and operates. After that, please check dmesg one more time in the same way.

 

I did the test, I erased the hdd's to also be able to make an install test and recompiled the loader, unplugged igb and rebooted the server, after reboot during the install phase, the mellanox card did not initialize, ie no lights on the cards, no system in synology assistant, replugged igb and installed DSM via igb, system started without issue and Mellanox card is available however there is someting about unknown symbol backport in dmesg, attached below.

 

 

[Peter Suh]

7 hours ago, djvas335 said:

 

I did the test, I erased the hdd's to also be able to make an install test and recompiled the loader, unplugged igb and rebooted the server, after reboot during the install phase, the mellanox card did not initialize, ie no lights on the cards, no system in synology assistant, replugged igb and installed DSM via igb, system started without issue and Mellanox card is available however there is someting about unknown symbol backport in dmesg, attached below.

 

 

 

 

thanks for the test

Integration module pack of mellanox mlx4 (probably connectX-3) will keep the status quo including vanilla modules (mlx4_core.ko, mlx4_en.ko).
I expected it to initialize and load itself in Junior mode, but it's a pity.

 

I think I will buy mellanox connectX-3 in the near future.

After that point, I'll try to see if more fine-tuning or testing is possible.

 

Yesterday, I confirmed several platforms that I already have, the Intel X540-T2 (ixgbe) should work as a vanilla module.
(broadwell, broadwellnk, v1000, epyc7002, etc.)

 

Thanks to you, it gave me an opportunity to further research the need for vanilla modules in XPE.

Have a nice day.

[djvas335]

1 hour ago, Peter Suh said:

 

 

thanks for the test

Integration module pack of mellanox mlx4 (probably connectX-3) will keep the status quo including vanilla modules (mlx4_core.ko, mlx4_en.ko).
I expected it to initialize and load itself in Junior mode, but it's a pity.

 

I think I will buy mellanox connectX-3 in the near future.

After that point, I'll try to see if more fine-tuning or testing is possible.

 

Yesterday, I confirmed several platforms that I already have, the Intel X540-T2 (ixgbe) should work as a vanilla module.
(broadwell, broadwellnk, v1000, epyc7002, etc.)

 

Thanks to you, it gave me an opportunity to further research the need for vanilla modules in XPE.

Have a nice day.

 

As it's not working in junior mode can I ask that you please keep the mlx4 module out of the all-modules integration pack for now ? You can add it later when it will be working better. The reason I am asking for this are those errors in dmesg about unknown symbol backport dependency.

[Peter Suh]

9 minutes ago, djvas335 said:

 

As it's not working in junior mode can I ask that you please keep the mlx4 module out of the all-modules integration pack for now ? You can add it later when it will be working better. The reason I am asking for this are those errors in dmesg about unknown symbol backport dependency.

 

By any chance, what physical error does that log message cause?
After that message, it seems that mlx4_core has entered the normal loading phase?

[HonB]

20 hours ago, Peter Suh said:

 

There is a problem that the three partitions assigned to the USB cannot be found. Is it possible to switch from BIOS to legacy instead of UEFI?

I have change to legacy. It's good now. Thank you so much.

[djvas335]

10 minutes ago, Peter Suh said:

 

By any chance, what physical error does that log message cause?
After that message, it seems that mlx4_core has entered the normal loading phase?

 

I did not see any issues with this for now, just trying to avoid possible issues that can creep up in the future

[zjcai]

 hey, guys. need some help here.

build with this command: 

./rploader.sh build ds918p-7.2.0-64561 manual

It appears that the pocopico.e1000e extension is not yet compatible with ds918p_64561. What steps should be taken to resolve this issue?

[-] Failed to update recipe for pocopico.e1000e extension for platform ds918p_64561. The script will terminate as you do not
[-] have previously downloaded recipe which can be used if download fails. Try again later. If problem
[-] persists contact the extension packer for support (displayed below)
[#] ========================================== pocopico.e1000e ==========================================
[#] Extension name: e1000e
[#] Description: Adds Intel(R) PRO/1000 Network Driver Support
[#] To get help visit: <todo>
[#] Extension preparer/packer: https://github.com/pocopico/rp-ext/tree/main/e1000e
[#] Software author: https://github.com/pocopico
[#] Update URL: https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000e/rpext-index.json
[#] Platforms supported: ds1621p_42218 ds1621p_42951 ds918p_41890 dva3221_42661 ds3617xs_42621 ds3617xs_42218 ds920p_42661 dva3221_42962 ds918p_42661 ds3622xsp_42962 ds3617xs_42951 dva1622_42218 dva1622_42621 ds920p_42962 ds1621p_42661 dva1622_42951 ds918p_25556 dva3221_42218 ds3615xs_42661 dva3221_42951 ds3622xsp_42661 ds2422p_42661 ds3622xsp_42218 ds2422p_42962 rs4021xsp_42621 dva1622_42962 ds2422p_42218 rs4021xsp_42962 dva3221_42621 ds3615xs_42962 ds3617xs_42962 ds3615xs_41222 ds920p_42951 rs4021xsp_42218 ds2422p_42951 ds918p_42621 ds3617xs_42661 ds3615xs_25556 ds920p_42218 rs4021xsp_42951 ds920p_42621 ds918p_42962 ds3615xs_42951 ds3622xsp_42951 dva1622_42661 ds918p_42218 ds2422p_42621 ds1621p_42621 ds3615xs_42621 ds3615xs_42218 ds1621p_42962 ds3622xsp_42621 rs4021xsp_42661
[#] =======================================================================================

[!] Cannot continue due to previous errors (see above)

*** Process will exit ***
[!] Failed to update all extensions for ds918p_64561 platform - see errors above

*** Process will exit ***

 

 

[zjcai]

1 hour ago, zjcai said:

 hey, guys. need some help here.

build with this command: 

./rploader.sh build ds918p-7.2.0-64561 manual

It appears that the pocopico.e1000e extension is not yet compatible with ds918p_64561. What steps should be taken to resolve this issue?

[-] Failed to update recipe for pocopico.e1000e extension for platform ds918p_64561. The script will terminate as you do not
[-] have previously downloaded recipe which can be used if download fails. Try again later. If problem
[-] persists contact the extension packer for support (displayed below)
[#] ========================================== pocopico.e1000e ==========================================
[#] Extension name: e1000e
[#] Description: Adds Intel(R) PRO/1000 Network Driver Support
[#] To get help visit: <todo>
[#] Extension preparer/packer: https://github.com/pocopico/rp-ext/tree/main/e1000e
[#] Software author: https://github.com/pocopico
[#] Update URL: https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000e/rpext-index.json
[#] Platforms supported: ds1621p_42218 ds1621p_42951 ds918p_41890 dva3221_42661 ds3617xs_42621 ds3617xs_42218 ds920p_42661 dva3221_42962 ds918p_42661 ds3622xsp_42962 ds3617xs_42951 dva1622_42218 dva1622_42621 ds920p_42962 ds1621p_42661 dva1622_42951 ds918p_25556 dva3221_42218 ds3615xs_42661 dva3221_42951 ds3622xsp_42661 ds2422p_42661 ds3622xsp_42218 ds2422p_42962 rs4021xsp_42621 dva1622_42962 ds2422p_42218 rs4021xsp_42962 dva3221_42621 ds3615xs_42962 ds3617xs_42962 ds3615xs_41222 ds920p_42951 rs4021xsp_42218 ds2422p_42951 ds918p_42621 ds3617xs_42661 ds3615xs_25556 ds920p_42218 rs4021xsp_42951 ds920p_42621 ds918p_42962 ds3615xs_42951 ds3622xsp_42951 dva1622_42661 ds918p_42218 ds2422p_42621 ds1621p_42621 ds3615xs_42621 ds3615xs_42218 ds1621p_42962 ds3622xsp_42621 rs4021xsp_42661
[#] =======================================================================================

[!] Cannot continue due to previous errors (see above)

*** Process will exit ***
[!] Failed to update all extensions for ds918p_64561 platform - see errors above

*** Process will exit ***

 

 

[-] The extension pocopico.e1000e was found. However, the extension index has no recipe for ds918p_64561 platform. It may not be
[-] supported on that platform, or author didn't updated it for that platform yet. You can try running
[-] "ext-manager.sh update" to refresh indexes for all extensions manually. Below are the currently known information about
[-] the extension stored locally:

[Blubster]

Hey @zjcai

From my understanding, starting with DSM7.2, it is no longer required to "add" specific drivers, they should be taken care from the "all-modules" approach. I tried your way for adding support for AQC107 when i found that it was no longer working in DSM7.2, but faced the same issue you have.

I found later that the module was indeed included but for me another issue prevent the module atlantic.ko from working.

You should try to build the loader without anything special, it would pull whatever it needs and hopefully you have everything working.

Btw, try the HTML builder, it is awesome!

pocopico explained in this thread a bit earlier how to run it, very simple. You may have to recover your satamap, i don't think it worked for me at first though.

You can look at this post for instance.