TinyCore RedPill Loader Build Support Tool ( M-Shell )

[shibby]

On 3/17/2024 at 7:03 AM, Peter Suh said:

Perhaps you want to take the loader.img file that was created in the middle.

Yep, this is exacly what i need

At the moment i`m running DSM 6.2.3 for DS3615xs using Jun`s loader 1.3b.


I am able to boot loader from USB drive by pressing "backup" button for 30 seconds on boot. This is a temporary solution. After all i want to flash loader permamently to ReadyNAS flash by "dd" command.

 

I tried to boot your TCRP from USB drive and it works. I`ll try to compile redpill using M-Shell tools BUT after all i will not able to flash loader to internal flash memory 😕 Each time when i will restart ReadyNAS i will have to push "backup" button to start NAS from USB drive.

[shibby]

Nevermind All works fine

 

 

Works even with Exos 14TB

 

[Peter Suh]

[NOTICE]

TCRP-mshell NMVe / MMC type media bootloader available function distribution

 

This function has already been implemented in rr a long time ago.

It was reflected a little late in mshell.

 

It was difficult to obtain mmc and I didn't know how to create emmc by emulating it,

so I put it on hold and then added the NMVe / MMC bootloader function.

 

NVMe has been sufficiently tested and verified.

MMC has asked Korean users to test it.

 

Like the picture below
This is an example of NVMe, but the information for the nvme0n1 device will be displayed instead, as shown below.
Below that, in Friend, Loader BUS: nvme
If you see , it is normal.

 

 

 

[djvas335]

Hi, Peter, how can we pass parameters for kernel modules, I tried using modprobe.d however this did not work, I need to set some parameters for mlx4_core driver to be applied at boottime

[Peter Suh]

15 hours ago, djvas335 said:

Hi, Peter, how can we pass parameters for kernel modules, I tried using modprobe.d however this did not work, I need to set some parameters for mlx4_core driver to be applied at boottime

 

 

[djvas335]

Thanks for replying, I checked the link however I did not find the relevant information, can you please point the relevant section ?

 

What I need is to add some options to the mlx4_core driver like this, I am not sure how to do this, is this to be done at loader creation ? Or this can be done directly from DSM ?

 

options mlx4_core roce_mode=2

 

5 hours ago, Peter Suh said:

 

 

 

[Captainfingerbang]

On 3/23/2024 at 10:50 AM, Peter Suh said:

[NOTICE]

TCRP-mshell NMVe / MMC type media bootloader available function distribution

 

This function has already been implemented in rr a long time ago.

It was reflected a little late in mshell.

 

It was difficult to obtain mmc and I didn't know how to create emmc by emulating it,

so I put it on hold and then added the NMVe / MMC bootloader function.

 

NVMe has been sufficiently tested and verified.

MMC has asked Korean users to test it.

 

Like the picture below
This is an example of NVMe, but the information for the nvme0n1 device will be displayed instead, as shown below.
Below that, in Friend, Loader BUS: nvme
If you see , it is normal.

 

 

 

 

 

 

Hi peter, sorry off topic but i know you dont like pm's

 

I have a friend who needs a solution for a loader that will allow 40 or so drives plus LSI 9x00 HBA card.

Do you have something like HD6500 with ability for HBA? Or at least know of something like this? possibly in RR?

 

OR ANY loader in fact, that will allow 40 drives + HBA card?

Edited April 5 by Captainfingerbang

[ULSY]

Hey @Peter Suh

I have Kernel issues, Network is no longer reachable. How can I solve this issue ?

 

[Peter Suh]

14 hours ago, ULSY said:

Hey @Peter Suh

I have Kernel issues, Network is no longer reachable. How can I solve this issue ?

 

 

Wait a minute, but I don't think you should do this.
There is one more thing that needs to be modified.

Sorry

[Peter Suh]

vi my

 

:295

 

#curl -skL# https://raw.githubusercontent.com/PeterSuh-Q3/redpill-load/master/bundled-exts.json -o /home/tc/redpill-load/bundled-exts.json

 

:wq!

 

Edit the *load/b*.json file once again
You need to take one more action as shown below.

Otherwise, the changes made above will disappear and be restored.

[midiman007]

On 5/2/2023 at 11:16 AM, Peter Suh said:

[NOTICE]

 

Official distribution of DSM 7.2-64551 RC version to M SHELL for TCRP has been completed.

 

During the DSM 7.2 RC installation process, the automatic installation of the latest version of DSM still has problems, so a file corruption message appears.

 

If you download and install DSM manually, there is no problem.

 

Thanks @wjz304

 

I just installed bare metal

THis was a bare metal box with spare parts I had from my old pc

 

Thanks so much for this I just built a DS1823xs+ with 7.2.1 DSM update 5 on a MSI Z97-GD65 Gaming LGA 1150 Intel Z97 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard and Intel Core i7-4790K with 32 gigs of ram with version v0.9.5.0.

 

 

Now for set it was 1,2,3. The only issue I can see is if I try and set the power schedule it is giving me a network error. Say please check you network setting.

 

Now the case has 6 bays for HD, the mother board has 8 HD dId I over do my install by installing a DS1823xs+?

Right now I have 5 HD installed.

 

 

 

[Peter Suh]

On 4/25/2024 at 4:42 AM, midiman007 said:

I just installed bare metal

THis was a bare metal box with spare parts I had from my old pc

 

Thanks so much for this I just built a DS1823xs+ with 7.2.1 DSM update 5 on a MSI Z97-GD65 Gaming LGA 1150 Intel Z97 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard and Intel Core i7-4790K with 32 gigs of ram with version v0.9.5.0.

 

 

Now for set it was 1,2,3. The only issue I can see is if I try and set the power schedule it is giving me a network error. Say please check you network setting.

 

Now the case has 6 bays for HD, the mother board has 8 HD dId I over do my install by installing a DS1823xs+?

Right now I have 5 HD installed.

 

 

 

 

The above error message appears not only here but also in other places. However, it does not affect the actual operation of the scheduler. The last changed settings will remain the same. Please try out StartUp and Shutdown in action.

However, I'm not sure if it's a Synology bug or a REDPILL bug, but there is a problem with the schedule operating because weekdays and weekends are differentiated. Maybe your weekend doesn't work out the way you want it to.

I experienced this phenomenon a long time ago and was not using the weekend setting.
Didn't this problem occur with the genuine product?

 

 

[midiman007]

16 minutes ago, Peter Suh said:

 

The above error message appears not only here but also in other places. However, it does not affect the actual operation of the scheduler. The last changed settings will remain the same. Please try out StartUp and Shutdown in action.

However, I'm not sure if it's a Synology bug or a REDPILL bug, but there is a problem with the schedule operating because weekdays and weekends are differentiated. Maybe your weekend doesn't work out the way you want it to.

I experienced this phenomenon a long time ago and was not using the weekend setting.
Didn't this problem occur with the genuine product?

 

 

Peter thanks for your reply. Again thank you for your hard work on the loader.

 

 

After a complete rebuild the PC will shut down and not power on. Really strange.

Yes I did notice that even though the error appeared the boxes were checked and the PC shutdown at night but will not power on in the morning.

 

I will try removing the weekend task and just use the weekday and see if that is the issue.

 

I don't know about a true Sysology NAS since all of my OEM NAS's are QNaps.

 

 

 

[Peter Suh]

13 hours ago, midiman007 said:

Peter thanks for your reply. Again thank you for your hard work on the loader.

 

 

After a complete rebuild the PC will shut down and not power on. Really strange.

Yes I did notice that even though the error appeared the boxes were checked and the PC shutdown at night but will not power on in the morning.

 

I will try removing the weekend task and just use the weekday and see if that is the issue.

 

I don't know about a true Sysology NAS since all of my OEM NAS's are QNaps.

 

 

 

 

There was one thing I didn't mention.

The point is that not all MOBOs work with this power reservation setting.
(I understand that S5 in the CMOS BIOS is involved.)

In particular, there are reports from users that MSI's products are incompatible with REDPILL. (The NIC does not respond for no particular reason, etc.)