TinyCore RedPill Loader Build Support Tool ( M-Shell )

[gericb]

Quickie question: If I am running DS3622xs+ DSM 7.1.1-42962 Update 5 using an older build TCRP M-Shell Friend, should I be able to create a USB with newest version of TCRP M-Shell Friend, and simultaneously upgrade to Version: 7.2-64561, which is supported in the newest "Friend" AND MIGRATE to a 920+ build/image?

 

Thanks

[Peter Suh]

14 hours ago, Peter Suh said:

[notification]

 

A new TCRP ADDON has been added.

 

https://github.com/PeterSuh-Q3/tcrp-addons/tree/main/reboottotcrp

 

When DSM is booted, it automatically registers a manual scheduler that modifies the default value of grub.cfg to enter "Tiny Core Image Build" on the next boot.

 

If this Addon is installed successfully,
As shown in the screenshot below, one scheduler will be automatically registered. (The loader must be newly built.)

 

Scripts in this scheduler only work if run manually.

 

The boot order of grub.cfg is fixed to "Tiny Core Image Build" at the end. (Jot with 4 menus is also supported.)

 

 

 

 

If you are using M SHELL and do not want to rebuild the loader, you can manually install it with the command below.

 

sudo -i
curl -kLO https://github.com/PeterSuh-Q3/tcrp-addons/raw/main/reboottotcrp/installondsm.sh
./installondsm.sh

[Peter Suh]

13 hours ago, gericb said:

Quickie question: If I am running DS3622xs+ DSM 7.1.1-42962 Update 5 using an older build TCRP M-Shell Friend, should I be able to create a USB with newest version of TCRP M-Shell Friend, and simultaneously upgrade to Version: 7.2-64561, which is supported in the newest "Friend" AND MIGRATE to a 920+ build/image?

 

Thanks

 

You don't have to start with USB recording.
When entering TCRP Linux, it is automatically updated to the latest version of M SHELL.
You only need to rebuild the loader in response to 7.2-64561.
After rebooting, the 7.2 DSM installation process proceeds, and migration proceeds by itself.

[Huey_Pilot]

6 hours ago, Peter Suh said:

 

If you are using M SHELL and do not want to rebuild the loader, you can manually install it with the command below.

 

sudo -i
curl -kLO https://github.com/PeterSuh-Q3/tcrp-addons/raw/main/reboottotcrp/installondsm.sh
./installondsm.sh

I get a permission denied when I run ./installondsm.sh

What can I do?

[Peter Suh]

1 minute ago, Huey_Pilot said:

I get a permission denied when I run ./installondsm.sh

What can I do?

 

Are you sure you changed to the root user?

[Huey_Pilot]

4 minutes ago, Peter Suh said:

 

Are you sure you changed to the root user?

Yes did a chmod 755 installondsm.sh and now it is working

And now I have a task named RebootToTcrp

Edited May 25 by Huey_Pilot

[digitalscreen]

sudo su -u for root.

[Rebutia]

23 hours ago, Peter Suh said:

 

If you are using M SHELL and do not want to rebuild the loader, you can manually install it with the command below.

 

sudo -i
curl -kLO https://github.com/PeterSuh-Q3/tcrp-addons/raw/main/reboottotcrp/installondsm.sh
./installondsm.sh

It generated with the following error:

 

 

But the scheduled job seems to be added successfully:

 

 

 

Edited May 26 by Rebutia

[Rebutia]

Hi Peter, another question, is there anyway to load igc.ko into your version of TCRP?

I attempt to install 7.2 using your latest TCRP m-shell on an i225/226 based N5105 ITX board. Booting up with TCRP is fine, but without network.

Thanks for your answer in advance.

[Rebutia]

On 5/23/2023 at 10:40 PM, Peter Suh said:

 

There is nothing wrong with the mpt3sas module itself, and I was using Synol incorrectly.

https://kb.synology.com/en-us/DSM/tutorial/DSM_update_insufficient_system_capacity_for_update
-------------------------------------------------- ---------------------------------------------
Insufficient system capacity for update. What can I do?

 

Resolution

You are seeing this error because your system does not have sufficient capacity to unzip and install update files in the system partition. Please check the following list before attempting to update DSM or the firmware of your Synology drives again.

 

Store your data in the shared folders only

The output from terminal commands (e.g., creating files or folders within the system partition such as in /root or /opt, or executing your own binary files/scripts) may fill up the system partition and result in update failure. Please move such data to the shared folders and only store your data and command output inside them.

-------------------------------------------------- ---------------------------------------------

During DSM installation, I received a message that the system partition is running out of space.

The /root directory should always be left empty.

The GeekBench installation pack and folder remain the same as the last CPU performance test,
I don't know why the Synology backups are piling up here, but the backups were also taking up quite a bit of space.

I checked with du -h /root , cleaned up space and installed DSM 7.2-64561 successfully.

Rather than doing this and that by myself, it ended with a happening.

Hi Peter, based on your reply, can I safely assume that mpt3sas module has no issue with dsm7.2 when using your latest m-shell?

[Peter Suh]

54 minutes ago, Rebutia said:

It generated with the following error:

 

 

But the scheduled job seems to be added successfully:

 

 

 

 

If you rebuild the loader, the addon is already automatically added.
Running the above shell again is unnecessary.
Duplicate registration of the scheduler with the same name occurred while it was already created.

[Peter Suh]

55 minutes ago, Rebutia said:

Hi Peter, another question, is there anyway to load igc.ko into your version of TCRP?

I attempt to install 7.2 using your latest TCRP m-shell on an i225/226 based N5105 ITX board. Booting up with TCRP is fine, but without network.

Thanks for your answer in advance.

 

The igc.ko module for each platform is already included.
The cause of igc not working must be somewhere else.
You need to check it through log analysis.
Currently, we are testing so that getty console can work in 7.2.
As mentioned above, the release
The getty console is a useful feature that helps you visually check the cause of an error. Please wait a moment.

[Rebutia]

4 minutes ago, Peter Suh said:

 

If you rebuild the loader, the addon is already automatically added.
Running the above shell again is unnecessary.
Duplicate registration of the scheduler with the same name occurred while it was already created.

ok... it seems strange that the 7.2 loader was only built last night, and there was no entry in the scheduler.

Anyway, thanks for your kind help of making the ever-improving m-shell, much appreciated.

[Peter Suh]

47 minutes ago, Rebutia said:

Hi Peter, based on your reply, can I safely assume that mpt3sas module has no issue with dsm7.2 when using your latest m-shell?

 

I cannot guarantee 100% about the stability of the mpt3sas module.
Please contact pocopico.

[Rebutia]

1 minute ago, Peter Suh said:

 

I cannot guarantee 100% about the stability of the mpt3sas module.
Please contact pocopico.

sure of course, I am not asking for 100% guarantee. Dont get me wrong.

What I meant is, can I assume your previously stated "mpt3sas/dsm7.2 warning" as "fixed"?

[Peter Suh]

28 minutes ago, Rebutia said:

sure of course, I am not asking for 100% guarantee. Dont get me wrong.

What I meant is, can I assume your previously stated "mpt3sas/dsm7.2 warning" as "fixed"?

 

That too is the role of pocopico.

Currently, most modules of M SHELL are borrowed from pocopico.

[pocopico]

58 minutes ago, Rebutia said:

sure of course, I am not asking for 100% guarantee. Dont get me wrong.

What I meant is, can I assume your previously stated "mpt3sas/dsm7.2 warning" as "fixed"?

 

I see no reason for mpt3sas not to work, its a minor kernel upgrade and the modules have been recompiled for 4.4.302.

 

We have though shifted from a per module extension to all-modules distribution. Which you should be aware of.

Edited May 26 by pocopico

[Peter Suh]

2 hours ago, Rebutia said:

Hi Peter, another question, is there anyway to load igc.ko into your version of TCRP?

I attempt to install 7.2 using your latest TCRP m-shell on an i225/226 based N5105 ITX board. Booting up with TCRP is fine, but without network.

Thanks for your answer in advance.

 

Getty Console has also been applied to DSM 7.2.
The Broadwell nk (DS3622xs+, RS4021xs+) you are interested in are well supported.
DS918+ (Apollo Lake) and DS920+ (Gemini Lake) are not yet supported.
Please enter the g key within 7 seconds in FRIEND booting.
You can also see the screen from the announcement on page 16.
You can check the problem with the igc module.

Things to note about rebuilding the loader are:
with

./rploader.sh clean
You should start by clearing the redpill-load directory first.

Edited May 26 by Peter Suh

[pedroj666]

On 4/29/2023 at 8:40 AM, Peter Suh said:

 

Applied the acpid power button addon.

https://github.com/PeterSuh-Q3/tcrp-addons

https://github.com/PeterSuh-Q3/redpill-load/commit/2b2fd946e22bccdc5a7bd2514405021220cba7b9

 

Please rebuild the loader.

 

On bare metal, I confirmed that synopoweroff was handled well without any errors by briefly pressing the power button.

(The power was turned off twice.)

 

 

How should I test in Proxmox?

Please test.

 

 

How do I apply the acpid power button addon?

What command should I use to get this applied?

[Peter Suh]

5 hours ago, pedroj666 said:

 

How do I apply the acpid power button addon?

What command should I use to get this applied?

 

Over the past few days I've been getting the same question over and over again.
I think the time has come to explain and highlight the difference in style.

ADDON of ARPL and ADDON of M SHELL for TCRP are applied differently.
pocopico's TCRP ADDON follows the ARPL method.

ARPL/TCRP's ADDON gives users the opportunity to select and add.
But my opinion is a little different.
Most of the ADDON must be added, and the optional ones are not very visible.
So, in M SHELL for TCRP, there is no option to select ADDON.
Most of them add them all up.

ADDON, which you are curious about, is of course included like this.

[Peter Suh]

 

The ADDON bundled modules that are enforced equally on all platforms are listed below.

 

https://github.com/PeterSuh-Q3/redpill-load/blob/master/bundled-exts.json

 

And, the case where you need to adjust and use it for each other platform is defined here.

 

https://github.com/PeterSuh-Q3/tinycore-redpill/blob/main/custom_config.json

Edited May 26 by Peter Suh

[pedroj666]

14 minutes ago, Peter Suh said:

 

Over the past few days I've been getting the same question over and over again.
I think the time has come to explain and highlight the difference in style.

ADDON of ARPL and ADDON of M SHELL for TCRP are applied differently.
pocopico's TCRP ADDON follows the ARPL method.

ARPL/TCRP's ADDON gives users the opportunity to select and add.
But my opinion is a little different.
Most of the ADDON must be added, and the optional ones are not very visible.
So, in M SHELL for TCRP, there is no option to select ADDON.
Most of them add them all up.

ADDON, which you are curious about, is of course included like this.

 

Thanks for answering my question but just to see if I got it right, are you saying that most ADDON's like the acpid power button are automatically added during boot creation using your M-Shell?

Edited May 26 by pedroj666

[Peter Suh]

7 hours ago, pedroj666 said:

 

Thanks for answering my question but just to see if I got it right, are you saying that most ADDON's like the acpid power button are automatically added during boot creation using your M-Shell?

 

Yes, it is. If the power does not turn off with a quick button press, the condition of the motherboard is the problem. Some of my bare metals worked and some didn't.

[gericb]

6 hours ago, Peter Suh said:

 

Yes, it is. If the power does not turn off with a quick button press, the condition of the motherboard is the problem. Some of my bare metals worked and some didn't.

Kind of assumed you were baking it all into the build of the loader, but without that add-on menu system, didn't really know where or how to confirm.  Indeed this functional worked flawlessly on my Dell Precision 3630, just tested it.  Took all of 60sec or less to fully power off.  Most appreciated! 🤠👍🏻

[JackieWu]

On 4/12/2023 at 10:31 PM, Peter Suh said:

 

If you mean the loader.img file that is created during TCRP loader building, you can do that with a little modification to the script.
In TCRP rploader.sh, pocopico organizes this file to reduce the size of the backup.
You can also adjust it in my m shell for TCRP.
do you need this file?

 

Block line 283 of my.sh with #.
https://github.com/PeterSuh-Q3/tinycore-redpill/blob/main/my.sh#L283

 

and

 

Block Line 2954 of rploader.sh with # or
Delete only the /home/tc/redpill-load/loader.img part.

https://github.com/PeterSuh-Q3/tinycore-redpill/blob/main/rploader.sh#L2954

 

Even after building the loader
/home/tc/redpill-load/loader.img
The file will remain undeleted.

Hi @Peter Suh, it seems like the block line 283 of my.sh https://github.com/PeterSuh-Q3/tinycore-redpill/blob/main/my.sh#L283 have changed, what can i do to preserve the loader.img nowdays? Thanks!

Edited May 28 by JackieWu