TinyCore RedPill Loader Build Support Tool ( M-Shell )

[Peter Suh]

36 minutes ago, apriliars3 said:

 

It is less intuitive if you need commands and new graphical menu.

 

 

Criticism is appreciated, but there are no plans to make this menu.sh more convenient and beautiful.

 

pocopico is developing the Next Generation TCRP loader.

 

If you look closely at the repo of TCRP, there is a web page under development under html, which is the next-generation design that will replace the menu.sh

that I temporarily created in ARPL style.

https://github.com/pocopico/tinycore-redpill/tree/main/html

 

 

 

pocopico said they needed some time to develop this new loader with a new design.

I am very much looking forward to it.

Edited November 16, 2022 by Peter Suh

[apriliars3]

1 hour ago, Peter Suh said:

 

Criticism is appreciated, but there are no plans to make this menu.sh more convenient and beautiful.

 

pocopico is developing the Next Generation TCRP loader.

 

If you look closely at the repo of TCRP, there is a web page under development under html, which is the next-generation design that will replace the menu.sh

that I temporarily created in ARPL style.

https://github.com/pocopico/tinycore-redpill/tree/main/html

 

 

 

pocopico said they needed some time to develop this new loader with a new design.

I am very much looking forward to it.

 

It´s better than menu ARPL, but I think there are only one form to make a build and intuitive without issue.

 

I know at least three forms to make a build.

[Peter Suh]

5 minutes ago, apriliars3 said:

 

It´s better than menu ARPL, but I think there are only one form to make a build and intuitive without issue.

 

I know at least three forms to make a build.

 

Your advice should reach pocopico.

pocopico probably spends a lot of time designing the new structure of the loader now rather than the interface of the TCRP loader management web page.

[Peter Suh]

15 hours ago, apriliars3 said:

 

 

 

 

If it is a test in proxmox vm, the above capture is a bit strange.

 

The Loader Bus should be ata, not usb.

 

ata must point to synnoboot_satadom = 1, but this value does not exist in usb.

 

This is definitely going to be a problem here.

Due to the problem of not being able to find the synoboot partition, even if DSM is installed,

you may encounter a file corruption message in the middle.

[apriliars3]

 
 
If it is a test in proxmox vm, the above capture is a bit strange.
 
The Loader Bus should be ata, not usb.
 
ata must point to synnoboot_satadom = 1, but this value does not exist in usb.
 
This is definitely going to be a problem here.

Due to the problem of not being able to find the synoboot partition, even if DSM is installed,
you may encounter a file corruption message in the middle.

With the same bootloader 0.9.3 m-shell

- DSM 7.1.1-42962 install and works
- Now update to U2 and not ip
- Delete .img and use fresh img, create an other build. Can detect ip and need to migrate, and other time lost ip

With bootloader 0.9.3 pocopico

- Create a build and migrate, works then restart and login to DSM

I use this configuration on Proxmox because I don’t want to loss a sata. Img over usb works well with all bootloaders.

Thanks

[Peter Suh]

10 minutes ago, apriliars3 said:

 

With the same bootloader 0.9.3 m-shell

- DSM 7.1.1-42962 install and works
- Now update to U2 and not ip
- Delete .img and use fresh img, create an other build. Can detect ip and need to migrate, and other time lost ip

With bootloader 0.9.3 pocopico

- Create a build and migrate, works then restart and login to DSM

I use this configuration on Proxmox because I don’t want to loss a sata. Img over usb works well with all bootloaders.

Thanks

 

 

 

TCRP of pocopico and The TCRP of the m shell differs in handling extension drivers.

 

pocopico's TCRP adds only the necessary NIC drivers during the loader build process.

 

m shell uses the integrated driver pack just like ARPL.

 

Perhaps your system partition has already installed DSM, which is stabilized through pocopico's TCRP.

 

In that state, you will not get a chance to install My Full Featured Driver Pack on your system partition.

 

This problem was confirmed today during the testing of the vmxnet3 driver of Proxmox.

 

Perhaps there is a dependency between drivers.

 

If all the M shell's integrated driver packs are installed through Junior mode, the problem may be resolved.

[Peter Suh]

[Notice]

 

Today I added a Keymap function to menu.sh for multilingual keyboard support.

 

TCRP's keymap is based on tinycore and is slightly different from APRL's keymap.

 

@apriliars3
As in the last request, please select a keymap for your language and check whether it is working properly.

 

If you have problems, don't go through menu.sh

 

Try changing the keymap by using the command below at the prompt.

 

 

tc@box:~$ ll /usr/share/kmap
total 4
drwxr-xr-x 2 root root 200 Dec 22 2010 azerty/
drwxr-xr-x 2 root root 60 Dec 22 2010 coleak/
drwxr-xr-x 2 root root 160 Dec 22 2010 dvorak/
drwxr-xr-x 2 root root 80 Dec 22 2010 fgGIod/
drwxr-xr-x 2 root root 80 Dec 22 2010 olpc/
drwxr-xr-x 2 root root 2360 Dec 22 2010 qwerty/
drwxr-xr-x 2 root root 380 Dec 22 2010 qwertz/
lrwxrwxrwx 1 root root 47 Nov 17 10:14 th-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/th-latin1.kmap
lrwxrwxrwx 1 root root 51 Nov 17 10:14 th-win-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/th-win-latin1.kmap
-rw-rw-r-- 1 root root 2055 Feb 13 2021 us.kmap
tc@box:~$ ll /usr/share/kmap/azerty
total 0
lrwxrwxrwx 1 root root 51 Nov 17 10:14 azerty.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/azerty.kmap
lrwxrwxrwx 1 root root 54 Nov 17 10:14 be-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/be-latin1.kmap
lrwxrwxrwx 1 root root 54 Nov 17 10:14 fr-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/fr-latin1.kmap
lrwxrwxrwx 1 root root 54 Nov 17 10:14 fr-latin9.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/fr-latin9.kmap
lrwxrwxrwx 1 root root 50 Nov 17 10:14 fr-pc.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/fr-pc.kmap
lrwxrwxrwx 1 root root 47 Nov 17 10:14 fr.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/fr.kmap
lrwxrwxrwx 1 root root 51 Nov 17 10:14 wangbe.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/wangbe.kmap
lrwxrwxrwx 1 root root 52 Nov 17 10:14 wangbe2.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/wangbe2.kmap
tc@box:~$ loadkmap < /usr/share/kmap/azerty/fr-pc.kmap

 

[apriliars3]

@Peter Suh I add your lastest .img but I can´t boot on Proxmox

 

I try like sata with this command and change order boot to sata 

 

qm importdisk 102 /var/lib/vz/dump/tinycore-redpill.v0.9.3.0.m-shell.img local-lvm

 

Also I test it like usb but no boot, I think is issue of .img because I try with tinycore-redpill.v0.9.3.0.img and boot without errors.

 

Thanks 

 

 

[Peter Suh]

@Peter Suh I add your lastest .img but I can´t boot on Proxmox
 
I try like sata with this command and change order boot to sata 
 
qm importdisk 102 /var/lib/vz/dump/tinycore-redpill.v0.9.3.0.m-shell.img local-lvm
 
Also I test it like usb but no boot, I think is issue of .img because I try with tinycore-redpill.v0.9.3.0.img and boot without errors.
 
Thanks 
 
 

What about keymaps?
does it work well?

As for the issues of img files and proxmox, other users in Korea also reported the same phenomenon to me. I will build the same environment and focus the exam on this part today. Please wait a moment.


Sent from my iPhone using Tapatalk

[Peter Suh]

On 11/16/2022 at 3:29 AM, apriliars3 said:

I tested with Proxmox new tinycore-redpill.v0.9.3.0.m-shell.img. 

 

I have installed DSM 7.1.1-42962 over DS3622xs+ and works, but then I try to update to DSM 7.1.1-429662 Updte 2 and not works.

 

Only works with Update 0 and then need rebuild for Update 2?

 

 

 

 

I think I got the point wrong with your point.
Isn't your first screen capture a bare metal test capture via USB Stick?
In Proxmox, Loader Bus is not represented as USB.
It is always ata .

And, your problem is that DS3622xs+ installs well up to DSM 7.1.1-42962 Update 0 in Proxmox Loader bus ata.

Is it correct that if you update to Update 2 you will lose your IP?

 

I have configured the same environment as yours as in the capture below.
But the Loader Bus is ata, not USB.
And, even after processing up to Update 2, the IP also receives a response as shown below.
Normal login is possible.

 

Is there anything I set differently from you?

 

And the MAC address of the network on your Proxmox is different from the above capture,

did you use Realmac in the menu.sh configuration process?
Different mac addresses can be set when used as a virtual mac address.

 

 

 

 

 

 

Edited November 18, 2022 by Peter Suh

[pkdick1]

Hello Peter,

I have setup a DS920+ Nas with J4105-ITX board. I recently installed a PCI-e board whose description is enclosed. I tried to build a new loader using ./my.sh DS920+F
When I rebooted my NAS, I could see that the network lights of my PCI-e went off and after that the NAS was no more recognized by my system. Do you have a piece of advice?

Thank you in advance

Envoyé de mon LE2113 en utilisant Tapatalk

[Peter Suh]

10 minutes ago, pkdick1 said:

Hello Peter,

I have setup a DS920+ Nas with J4105-ITX board. I recently installed a PCI-e board whose description is enclosed. I tried to build a new loader using ./my.sh DS920+F
When I rebooted my NAS, I could see that the network lights of my PCI-e went off and after that the NAS was no more recognized by my system. Do you have a piece of advice?

Thank you in advance

Envoyé de mon LE2113 en utilisant Tapatalk
 

 

If so, are you running one of the onboard nics? If this nic is working,

 

you can check junior logs to see why the other 2.5G dual nic is not working.

Is this the right situation?

[pkdick1]

Hello peter,

I am a newbie so I do not know how to get to the information you want...[emoji26]

What I noticed is: the starting boot is Ok and I can see the Redpill Friend Menu. When I start Redpill, there is even an IP that is defined, but then nothing happens. When I put my dual Gbit PCI-e card, I can build a functional loader: so I guess that there is some driver issue...

Envoyé de mon LE2113 en utilisant Tapatalk

[Peter Suh]

30 minutes ago, pkdick1 said:

Hello peter,

I am a newbie so I do not know how to get to the information you want...

What I noticed is: the starting boot is Ok and I can see the Redpill Friend Menu. When I start Redpill, there is even an IP that is defined, but then nothing happens. When I put my dual Gbit PCI-e card, I can build a functional loader: so I guess that there is some driver issue...

Envoyé de mon LE2113 en utilisant Tapatalk
 

 

You did not give me an accurate answer to my question.  Does the built-in nic work?  And if dual nic is included, did you record netif_num=“3” up to mac3 in user_config.json?

Edited November 20, 2022 by Peter Suh

[pkdick1]

 
You did not give me an accurate answer to my question.  Does the built-in nic work?  And if dual nic is included, did you record netif_num=“3” up to mac3 in user_config.json?

Sorry I deactivated the onboard NIC and the netif_num parameter value is 2.

Envoyé de mon LE2113 en utilisant Tapatalk

[Peter Suh]

4 minutes ago, pkdick1 said:

Sorry I deactivated the onboard NIC and the netif_num parameter value is 2.

Envoyé de mon LE2113 en utilisant Tapatalk
 

 

No plans to enable built-in nic rules?  Then there is no solution either.

[pkdick1]

 
No plans to enable built-in nic rules?  Then there is no solution either.

Sorry again but when I put my "old" dual Intel Gbit card I succeed to make the loader working. So it seems that there is something wrong my new realtek 8125B PCI card...

Envoyé de mon LE2113 en utilisant Tapatalk

[Peter Suh]

45 minutes ago, pkdick1 said:

Sorry again but when I put my "old" dual Intel Gbit card I succeed to make the loader working. So it seems that there is something wrong my new realtek 8125B PCI card...

Envoyé de mon LE2113 en utilisant Tapatalk
 

 

If you can access the DSM installation request screen with ttyd as below,

Then send me the log with the command you see.

You must use a web browser.

 

http://<youripaddr>:7681/

id : root / pw : ( no password )

 

cat /var/log/linuxrc.syno.log

 

 

This method assumes that at least 1 of your 3 nics is working.

[pkdick1]

 
If you can access the DSM installation request screen with ttyd as below,
Then send me the log with the command you see.
You must use a web browser.
 
http://:7681/
id : root / pw : ( no password )
 
cat /var/log/linuxrc.syno.log
 
 
This method assumes that at least 1 of your 3 nics is working.

Thank you for your support. I will try to get the log you asked to me. I will get back to you as soon as I can.

Best regards

Envoyé de mon LE2113 en utilisant Tapatalk

[pkdick1]

 
If you can access the DSM installation request screen with ttyd as below,
Then send me the log with the command you see.
You must use a web browser.
 
http://:7681/
id : root / pw : ( no password )
 
cat /var/log/linuxrc.syno.log
 
 
This method assumes that at least 1 of your 3 nics is working.

Hello Peter,

Just to tell you that I failed to get the log you were expecting to help me. I installed again my RTL8125 dual nic card and activated the onboard nic: after having built the RedPill loader using ./my.sh DS920+F command, I had to modify the network parameter (sorry I don't remember it but I am sure you know it [emoji28]), in order to be able to boot. In any case, the boot seems OK, but then I could see that none of the nic cards were operational (no lights).
I reflashed again my USB stick with the last RedPill software and I used the XPENOLOGY tutorial to install RTL8125 drivers (I am not sure that it was necessary) and build the loader: this time it worked! And I have now a functional DS920+ NAS with a dual 2.5GBit nic.

It seems to me that there is maybe something wrong with the ./my.sh script (it didn't recognize my card). Sorry not being able to give more information.

Thank you for your help anyway!

Envoyé de mon LE2113 en utilisant Tapatalk

[Peter Suh]

27 minutes ago, pkdick1 said:

Hello Peter,

Just to tell you that I failed to get the log you were expecting to help me. I installed again my RTL8125 dual nic card and activated the onboard nic: after having built the RedPill loader using ./my.sh DS920+F command, I had to modify the network parameter (sorry I don't remember it but I am sure you know it ), in order to be able to boot. In any case, the boot seems OK, but then I could see that none of the nic cards were operational (no lights).
I reflashed again my USB stick with the last RedPill software and I used the XPENOLOGY tutorial to install RTL8125 drivers (I am not sure that it was necessary) and build the loader: this time it worked! And I have now a functional DS920+ NAS with a dual 2.5GBit nic.

It seems to me that there is maybe something wrong with the ./my.sh script (it didn't recognize my card). Sorry not being able to give more information.

Thank you for your help anyway!

Envoyé de mon LE2113 en utilisant Tapatalk
 

 

 

Although no separate guide was provided,
Now my.sh (m shell) has been modified and developed in many ways.

 

./menu.sh makes it easier to build loaders like ARPL and
There is no need to find and install extension drivers in advance like the conventional method.
It uses the unified driver pack, just like ARPL uses.

 

It may not be helpful for the part that makes the NIC driver work, but
First of all, I want to tell you that the loader build method through M SHELL has changed a lot.
Users no longer type shell commands directly.

[Peter Suh]

The ARPL-style menu.sh that works like M Shell has been developed for a little more stabilization and the final version has been released a little while ago.

 

The moment menu.sh of m shell is executed in tinycore, everything is automatically updated.

 

[ Fixes ]

 

1. DS3615xs showing unstable state of loader in TCRP has been temporarily removed.

 

2. By using a USB stick, all the elements that were unstable in bare metal have been improved.
(It is recommended that the USB stick use version 3.0 and 3.0 or higher ports if possible.
Fast processing of USB stick reduces the chance of encountering file corruption messages in 55% of the DSM installation stage.)

 

3. The necessary dialog.tcz and kmaps.tcz are included as built-in packages so that they are not downloaded every time they are executed, and the execution speed on a relatively slow USB stick is increased.

 

4. When the rploader monitor on the left is executed for the first time, the time is automatically synchronized when menu.sh is executed so that there is no discrepancy in UTC time.

 

5.In the rploader monitor, the current time and the extension required for the Ethernet interface have been added.

 

6. In the process of updating from 6.TCRP FRIEND to DSM 7.1.1-42962 Update 2, the size of the first partition has been increased to 72M to prevent insufficient space in the first partition. (Worked with tinycore gparted.)
https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.3.0-1

 

7.Mac address input is supported up to 2 nics.
The image in the capture is when there is 1 nic.

 

8. The multilingual keymap has not yet been verified in operation.

 

[chdeast]

Hello, the guided production has not been completed after the production according to the method you provided. How to deal with the following situations? (Poor English, translated by translation software)

Reboot can only start from the first step again. This is a cycle.

[Peter Suh]

5 hours ago, chdeast said:

Hello, the guided production has not been completed after the production according to the method you provided. How to deal with the following situations? (Poor English, translated by translation software)

Reboot can only start from the first step again. This is a cycle.

 

During the loader build process
./my.sh DS918+F noconfig
It is executed with the command
my.sh tries to update the latest version by default.
The update seems to be processing abnormally.

 

exit menu.sh and

./my.sh DS918+F noconfig
Try building it yourself with just the above command.

[Peter Suh]

Xpenology NVMe Cache auto-activator for TCRP release.

 

 

https://github.com/PeterSuh-Q3/rp-ext/tree/main/nvme-cache

 

If you have newly built the M SHELL for TCRP Friend loader
TCRP automatically activates NVMe cache.

Currently, DS3622xs+ and DS918+ are shipped, and support models will be shared as they continue to expand.

After DSM installation is complete, reboot to enable NVMe cache.

 

Developed as a service like powersched
When the nvme-cache service is running, the first time when booting DSM, it searches whether or not NVMe cache is installed and activates it.

 

like below
You can also download and run nvme-cache.sh separately without building a loader.
However, nvme-cache.sh, which is not included in the service type or scheduler, is executed once, and NVMe cache may be disabled again due to migration between Synology models or DSM Update.

sudo -i
curl -L "https://github.com/PeterSuh-Q3/rp-ext/raw/main/nvme-cache/src/nvme-cache.sh" -O
chmod +x nvme-cache.sh
./nvme-cache.sh

 

It is recommended to rebuild the loader and use it if possible.

 

In conclusion, if you rebuild M SHELL for TCRP, install DSM, and reboot, the cache will be recognized by itself.