Jump to content
XPEnology Community

TinyCore RedPill Loader Build Support Tool ( M-Shell )

Peter Suh

By Peter Suh
in Software Modding

 Share

Recommended Posts

Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted (edited)

[NOTICE]

M SHELL for TCRP v0.9.5.0 is released.

 

https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.5.0

 

Added storage panel size selection menu and applied processing Addon (StoragePanel).
Thanks to @wjz304

 

 

If you enter the loader build menu, you will see the new menu below activated by automatic update.
The bay size of the storage panel is basically selected as the size of the genuine model.

2023-08-2512_04_30.png.0fe70bf78e4176079108fb019e619f7b.png

 

You can choose the size you would like to change.
After that, just build the loader as usual.

2023-08-2512_04_50.png.944ff5e1e5222b4570f2062a2734d710.png

 

 

If you want to change the bay panel type again after using it,
Even if DSM is already installed, you can run the Change Storage Panel registered in the manual scheduler.

 

The size selected at the time of the loader build is the last one recorded.

After editing, you can record one of the examples written after the # in the option at the back of storagepanel.sh in the task settings without typos.

The size of the M.2 bay is arbitrarily set to 1X4.

 

If you write only the desired number in ?/# in the form of ?X#, the size of the M.2 bay changes accordingly.

The ? number in front is the singular number, and the # number after it is the quantity for each stage.
Modify the option after .sh, check it, execute it, and reboot once to reflect it.

2023-08-2511_06_53.thumb.png.196f2edcc4330a76b155a286baac2fd3.png

 

Edited by Peter Suh
  • Like 2
  • Thanks 2
Link to comment
Share on other sites
asaf Regular Member

asaf

Posted
Posted
1 hour ago, Peter Suh said:

[NOTICE]

M SHELL for TCRP v0.9.5.0 is released.

 

https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.5.0

 

Added storage panel size selection menu and applied processing Addon (StoragePanel).
Thanks to @wjz304

 

 

If you enter the loader build menu, you will see the new menu below activated by automatic update.
The bay size of the storage panel is basically selected as the size of the genuine model.

2023-08-2512_04_30.png.0fe70bf78e4176079108fb019e619f7b.png

 

You can choose the size you would like to change.
After that, just build the loader as usual.

2023-08-2512_04_50.png.944ff5e1e5222b4570f2062a2734d710.png

 

 

If you want to change the bay panel type again after using it,
Even if DSM is already installed, you can run the Change Storage Panel registered in the manual scheduler.

 

The size selected at the time of the loader build is the last one recorded.

After editing, you can record one of the examples written after the # in the option at the back of storagepanel.sh in the task settings without typos.

The size of the M.2 bay is arbitrarily set to 1X4.

 

If you write only the desired number in ?/# in the form of ?X#, the size of the M.2 bay changes accordingly.

The ? number in front is the singular number, and the # number after it is the quantity for each stage.
Modify the option after .sh, check it, execute it, and reboot once to reflect it.

2023-08-2511_06_53.thumb.png.196f2edcc4330a76b155a286baac2fd3.png

 

 

There's a typo.

l Choose lageuage   must be    l Choose a language.

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted
4 hours ago, asaf said:

 

There's a typo.

l Choose lageuage   must be    l Choose a language.

 

thank you The typo has now been corrected.
The release will be implemented when there is a chance to fix other features next time.
There are probably plans to add a few more add-ons, which will be implemented soon.
https://github.com/PeterSuh-Q3/tinycore-redpill/commit/bdbcc303c106e7ea0d44a5e0383ec90b2d11a6a3

  • Like 1
Link to comment
Share on other sites
asaf Regular Member

asaf

Posted
Posted
42 minutes ago, Peter Suh said:

 

thank you The typo has now been corrected.
The release will be implemented when there is a chance to fix other features next time.
There are probably plans to add a few more add-ons, which will be implemented soon.
https://github.com/PeterSuh-Q3/tinycore-redpill/commit/bdbcc303c106e7ea0d44a5e0383ec90b2d11a6a3

 

Thank you!

 

Has the incompatibility of 918+ to HBA been solved?

Or it still doesn't show HDDs serial numbers when an HBA is used?

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted

[NOTICE]

 

MSHELL for TCRP, NVMe volumeization function has been applied.

NVMe Volumeization is a feature that enables the use of NVMe cache and additional NVMe volumes.

 

As always, you need to rebuild the loader for the feature to work.
If DSM is not activated immediately after installation, you must reboot once.

 

If you want to check that the script is working normally, you can run the command below with sudo privileges.

 

sudo -i

for file in `ls /etc/systemd/system/*.service | awk -F / '{print $NF}'`; do systemctl status ${file}; done

If the check result shows that the file has already been edited as shown below, it is normal. Because the service is running repeatedly

Patches of the libhwcontrol.so.1 file are iterated over and over again.

( DS3622xs+ seems to be patched normally, but it doesn't actually work. )

fca5fff48a6413608a61bfe738a0ff21.thumb.jpg.9d510fcca2e272973d4041328f20ce2c.jpg

 

As a result of testing with

@007revad

the currently operating platform is
Apollo Lake, Gemini Lake, v1000, r1000 and DS1621xs+.
Broadwell, Broadwellnk, Denverton will not work.


https://github.com/007revad/Synology_enable_M2_volume

 

Thanks 007revad

  • Thanks 2
Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted (edited)
On 8/12/2023 at 5:14 AM, asaf said:

Hi does TCRP M-shell support for whatever Synology model all at the same time

- Intel gen10 CPU

- LSI SCSI HBA

- NVMe read cache

- iGPU hardware acceleration 

 

This is the news you've been waiting for.

 

 

However, improvements to MSHELL for TCRP related to 10th generation CPU transcoding are planned.
ARPL-i18n has an addon called i915le10th.

Edited by Peter Suh
  • Like 1
Link to comment
Share on other sites
asaf Regular Member

asaf

Posted
Posted
6 hours ago, Peter Suh said:

 

This is the news you've been waiting for.

 

 

However, improvements to MSHELL for TCRP related to 10th generation CPU transcoding are planned.
ARPL-i18n has an addon called i915le10th.

 

Excellent news!


I'm playing around at the moment with ARC loader.
Seems like it supports both Transcoding and HBA (with proper SN) on 918+ for a while now.

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted (edited)
4 minutes ago, hendry said:

Hi, i tried build 7.1.1 loader, but still not found loader72.img file.. 

and about virtio 9p drivers, i tried to edit & add rpext json file from /home/tc with the content from your tcrp-addons/9p/rpext-index.json. does it means, the build process will include these driver ?

@Peter Suh

 

Finish building only the 7.1.1 loader
Please give me the zlastbuild.log file again.

 

I already mentioned that the virtio module is already installed.
Why do you want to install more?

Edited by Peter Suh
Link to comment
Share on other sites
hendry Advanced Member

hendry

Posted
Posted
Just now, Peter Suh said:

 

7.1.1 Finish building only the loader
Please give me the zlastbuild.log file again.

 

I already mentioned that the virtio module is already installed.
Why do you want to install more?

ok.. then no need to add 9p drivers on /home/tc rpext.json file.. 

will try it after this build success with loader72.img file.. 

zlastbuild.log

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted (edited)
7 minutes ago, hendry said:

ok.. then no need to add 9p drivers on /home/tc rpext.json file.. 

will try it after this build success with loader72.img file.. 

zlastbuild.log 10.79 kB · 0 downloads

 

If something like below appears at the top of the log, it means that the img file will not be created.
makeimg = N
Something is wrong.
I'll make some adjustments to the program. It will always create loader72.img no matter what version of the loader you build.
I'll let you know when the program is redistributed.

Edited by Peter Suh
Link to comment
Share on other sites
hendry Advanced Member

hendry

Posted
Posted
1 minute ago, Peter Suh said:

 

If something like below appears at the top of the log, it means that the img file will not be created.
makeimg = N
Something is wrong.
I'll make some adjustments to the program. We will always create loader72.img no matter what version of the loader we build.
We'll let you know when the program is redistributed.

can i just remark part of rploader.sh which become something like this ? 

    #if [ "$MAKEIMG" = "YES" ]; then
        echo "Stop creating loader and keep loader.img for 7.2"
        sudo cp -vf loader.img /mnt/${loaderdisk}3/loader72.img

        echo "Cleaning up files"
        removemodelexts    
        sudo rm -rf /home/tc/cache/*pat /home/tc/redpill-load/loader.img
        
        exit 0
    #fi

 

 

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted (edited)
9 minutes ago, hendry said:

can i just remark part of rploader.sh which become something like this ? 

    #if [ "$MAKEIMG" = "YES" ]; then
        echo "Stop creating loader and keep loader.img for 7.2"
        sudo cp -vf loader.img /mnt/${loaderdisk}3/loader72.img

        echo "Cleaning up files"
        removemodelexts    
        sudo rm -rf /home/tc/cache/*pat /home/tc/redpill-load/loader.img
        
        exit 0
    #fi

 

 

 

https://github.com/PeterSuh-Q3/tinycore-redpill/commit/8a9d17017b3f773a92c8ca7690abb83e2866eadc

 

It has been modified and distributed as above.
Try it now.

Edited by Peter Suh
Link to comment
Share on other sites
Vodka2014 Super Member

Vodka2014

Posted
Posted
On 8/28/2023 at 5:58 PM, Vodka2014 said:

Hi @Peter Suh

 

DS3622xs+ Would there be a reason why it only shows 16GB vs 32GB in the Info section and is it good to update to Update 3 on DSM 7.2.64570 ?

 

Thanks

 

OH and i have just found i am getting unrecognized firmware on all ym disks. the ones on the SATA Controller and the SAS HBA.

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted (edited)

[notification]

 

Introducing a new add-on "drivedatabase" for unrecognized firmware version issues.

 

It is a shell called Synology_HDD_db created by @007revad,

and with some modifications, it is installed automatically along with the M SHELL for TCRP loader as a service of DSM.
https://github.com/PeterSuh-Q3/tcrp-addons/tree/main/drivedatabase
 
To use this addon you will need to rebuild your loader.

If you are prompted to update the drive database due to a storage manager error as shown below, you can rebuild the loader or run @007revad's Synology_HDD_db directly by connecting to ssh on DSM.

 

2023-08-317_38_07.thumb.png.ca9c2e26c86ea7e0eca1e9abc8d5132a.png.e255762d8e81816e2c122803d4ffb12a.png

 

Execute the command as below.

 

sudo -i
curl -kLO https://raw.githubusercontent.com/007revad/Synology_HDD_db/main/syno_hdd_db.sh
chmod +x syno_hdd_db.sh
./syno_hdd_db.sh

Edited by Peter Suh
  • Like 3
Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted
5 minutes ago, hendry said:

image.png.7609afadd6149483e8bd9912f9a6b080.png

 

After tring to put inside docker vm script, the bootloader which was built by m-shell can start, but wrong choose default boot option. it should be SATA not USB as the default grub boot menu. It was an error unknown file system after that.

How to change this ? 

@Peter Suh

 

 

 

You will see another file /mnt/sda3/grub72.cfg.

 

this file In a virtual machine with loader72.img
Mount the /dev/sda1 device and
In it, replace the /boot/GRUB/grub.cfg file with grub72.cfg.
The name should remain grub.cfg.

 

cp -vf grub72.cfg grub.cfg

 

There are two menus available: the usual FRIEND menu and the TCRP loader build menu.

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted
10 minutes ago, hendry said:

then what should i do next ?

rebuild the loader again ?

does the  /mnt/sda3/grub72.cfg file has default grub boot option to SATA ? 

or do u mean, i need to edit the grub72.cfg file and change the default boot option ?

sorry, i still not understand.. 

 

 

You don't need to change anything or rebuild anything.
Just follow what I told you and everything will be done.

Link to comment
Share on other sites
hendry Advanced Member

hendry

Posted
Posted

why the file system not known at first boot ? it's on v7.2.0-64570 

xpe1  | LoadingLoadin gLinux... Linux..
.pe1  |
xpe1  | LoadingLoadin ginitramfs... initramfs..
.pe1  |
xpe1  | error: unknown filesystem.
error: unknown filesystemStarting.
xpe1  | Startin gkernel kerne lwith wit hUSB US Bboot boo
xpe1  |
Press any key to continue...t
xpe1  |
xpe1  | Press any key to continue...
[    0.000000] Initializing cgroup subsys cpuset
xpe1  | [    0.000000] Initializing cgroup subsys cpu
xpe1  | [    0.000000] Initializing cgroup subsys cpuacct
xpe1  | [    0.000000] Linux version 4.4.302+ (root@build8) (gcc version 12.2.0 (GCC) ) #64570 SMP Sat Jun 3 00:10:35 C3
xpe1  | [    0.000000] Command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS3622xs+ console=ttyS0,115p
xpe1  | [    0.000000] KERNEL supported cpus:
xpe1  | [    0.000000]   Intel GenuineIntel
xpe1  | [    0.000000] x86/fpu: Legacy x87 FPU detected.
xpe1  | [    0.000000] e820: BIOS-provided physical RAM map:
xpe1  | [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
xpe1  | [    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003ffdbfff] usable
xpe1  | [    0.000000] BIOS-e820: [mem 0x000000003ffdc000-0x000000003fffffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
xpe1  | [    0.000000] earlycon: Early serial console at I/O port 0x3f8 (options '115200n8')
xpe1  | [    0.000000] bootconsole [uart0] enabled
xpe1  | [    0.000000] NX (Execute Disable) protection: active
xpe1  | [    0.000000] SMBIOS 2.8 present.
xpe1  | [    0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
xpe1  | [    0.000000] Kernel/User page tables isolation: disabled
xpe1  | [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
xpe1  | [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
xpe1  | [    0.000000] e820: last_pfn = 0x3ffdc max_arch_pfn = 0x400000000
xpe1  | [    0.000000] MTRR default type: write-back
xpe1  | [    0.000000] MTRR fixed ranges enabled:
xpe1  | [    0.000000]   00000-9FFFF write-back

and ends up with kernel panic  

xpe1  | [    0.592682] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
xpe1  | [    0.592682]
xpe1  | [    0.593626] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
xpe1  | [    0.593626]

 

 

while on 7.1.0-42661 the boot process is okay.. 

xpe  |
xpe  | Loadin gLinux... Linux..
.pe  |
xpe  | LoadingLoadin ginitramfs... initramfs..
.pe  |
xpe  | StartingStartin gkernel kerne lwith wit hUSB US Bboot boo
[    0.000000] Initializing cgroup subsys cpuset
xpe  | [    0.000000] Initializing cgroup subsys cpu
xpe  | [    0.000000] Initializing cgroup subsys cpuacct
xpe  | [    0.000000] Linux version 3.10.108 (root@build13) (gcc version 8.5.0 (GCC) ) #42661 SMP Fri Apr 1 15:31:15 CS2
xpe  | [    0.000000] Command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS3615xs console=ttyS0,115201
xpe  | [    0.000000] KERNEL supported cpus:
xpe  | [    0.000000]   Intel GenuineIntel
xpe  | [    0.000000] e820: BIOS-provided physical RAM map:
xpe  | [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
xpe  | [    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003ffdbfff] usable
xpe  | [    0.000000] BIOS-e820: [mem 0x000000003ffdc000-0x000000003fffffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
xpe  | [    0.000000] Early serial console at I/O port 0x3f8 (options '115200n')
xpe  | [    0.000000] bootconsole [uart0] enabled

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...