Jump to content
XPEnology Community

TinyCore RedPill Loader Build Support Tool ( M-Shell )


Peter Suh

Recommended Posts

1.This is a shell script that executes several commands at once as described in the "Redpill Tinycore Loader DSM 7.1 Build" guide.

 

To use, you can download and untar it as follows and use it in the /home/tc directory.

 

Helps build DSM 7.1 by managing the PAT file directory required for decryption.

 

(  It currently supports the latest version of the DSM, 7.1.0-42661 update 1 nanopack version. )

 

Automatically add mac2 to user_config.json file for dual NIC, a feature that TC doesn't have.

 

( Manual Response Version )

wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/m.sh.gz; tar -zxvf m.sh.gz;

 

( Auto Answer Version with y )
wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz; tar -zxvf my.sh.gz;

 

Where y is unnecessarily asked, it automatically responds.

 

Usage: ./my.sh <Synology Model Name> <Option> <Option> <Option>

 

Options: noconfig, noclean, manual

 

- noconfig: SKIP automatic detection change processing such as SN/Mac/Vid/Pid/SataPortMap of user_config.json file.

 

- noclean: SKIP the 💊   RedPill LKM/LOAD directory without clearing it with the Clean now command. 
           However, delete the Cache directory and loader.img.

 

- manual: Options for manual extension processing and manual dtc processing in build action (skipping extension auto detection)

 

Please type Synology Model Name after ./my.sh

 

./my.sh DS918+
./my.sh DS3617xs
./my.sh DS3615xs
./my.sh DS3622xs+
./my.sh DVA3221
./my.sh DS920+
./my.sh DS1621+

 

# Update : add noconfig, noclean, manual combination options

# 2022.05.06

 

You can use it like this.

./my.sh DS918+ noconfig noclean manual

 

 

1059308286_2022-05-1511_22_36.thumb.png.96ecb83da5e6bf505ee63b17b307fa39.png228208861_2022-05-1511_23_21.thumb.png.f4426b2dd841cce85e9109d68052e4ac.png1865285771_2022-05-1511_25_40.thumb.png.e4681123b84aa73e03bf4343c53ac0a1.png1833222636_2022-05-1511_26_01.thumb.png.72eb9cd95e347ac4c9d46f05d4148551.png

 

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

 

2. Deploy scripts that you can leverage if you need to add a separate ext manually for VM users.

It includes the fuction to add exts created by @FOXBI with multiple selections like capture.

 

For the instructions on how to use, you can download and decompress as below and use it in /home/tc directory.

 

( Auto Answer Version with y )

wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/myv.sh.gz; tar -zxvf myv.sh.gz;

 

The way to use it is existing same as my.sh. Where y is unnecessarily asked, it automatically responds.

 

----------------------------------------------------------------------------------------
Usage: ./myv.sh <Synology Model Name> <Options>

Options: noconfig, noclean, manual

- noconfig: SKIP automatic detection change processing such as SN/Mac/Vid/Pid/SataPortMap of user_config.json file.

- noclean: SKIP the 💊   RedPill LKM/LOAD directory without clearing it with the Clean now command. 
           However, delete the Cache directory and loader.img.

- manual: Options for manual extension processing and manual dtc processing in build action (skipping extension auto detection)

Please type Synology Model Name after ./myv.sh

 

./myv.sh DS918+
./myv.sh DS3617xs
./myv.sh DS3615xs
./myv.sh DS3622xs+
./myv.sh DVA3221
./myv.sh DS920+
./myv.sh DS1621+

 

CAUTION) Not all exts correspond to 7.1.0-42661.
Please check @pocopico's ext GITHUB in advance and use it.
We do not respond to errors caused by unsupported revisions.

 

1573609525_2022-04-199_54_07.thumb.png.f44c890de62c6f8b6d71d4abb9279c36.png.fb04d59fd3ad8bd8159478580256056d.png.7e90212201d927d16f3609732bacad04.png

 

 

 

 

Edited by Peter Suh
  • Like 6
  • Thanks 2
Link to comment
Share on other sites

  • 2 weeks later...

[NOTICE]

 

M Shell, Tinycore jun mode build function added distribution

 

I don't have time

So, I only applied my.sh.

The rest of the shells will be updated soon.

 

DSM 7.0.1-42218, which is a required pat file for the current Jun Mode application, is changed to update 4.

The contents of the download pat file have been changed again.

In this changed state, pocopico's tinycore does not respond, so when building in jun mode, build is not possible due to sha256sum mismatch.


In order to bypass this part in the m shell,

DSM 7.0.1-42218 update 4 Download the pat file to avoid build errors.

 

Automatic update is supported, so if you use "./my.sh model name" only once, it will be updated to the latest version.

 

For new users, please download and decompress it using the command below in TC Linux.

wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz; tar -zxvf my.sh.gz;


For jun mode, just add one more "J" after the existing model name.
It's like this.

 

./my.sh DS918+J

./my.sh DS3622xsJ

  • Thanks 1
Link to comment
Share on other sites

In @pocopico's 0.4.6 img for legacy, the first partition is increased from 48mb to 96mb to secure space for the dtc utility to be copied, and it is an image that has been fully upgraded to the latest version 0.7.1.7.
Download it from the Google link below, decompress the gz and record it on a new USB stick.
And rploader.sh on my Github repo blocks the patchdtc function so that there are no errors like the log above, and also blocks the update of rploader.sh itself.

 

It's for the use of the new dtb util of jumkey

 

[tinycore-redpill.v0.7.1.7.img]

https://drive.google.com/file/d/1Jxr0znrDxkqIhcbFPTyll44VwdvuPBu-/view?usp=sharing

 

tc@box:~$ curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/rploader.sh" --output rploader.sh

 

mkdir /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles; sudo ln -s /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles /home/tc/custom-module;

 

./rploader.sh build geminilake-7.1.0-42661

 

./rploader.sh backup now

 

And

 

Share the tincore-redfill.v0.7.1.7.vmdk file.

For the use of the new dtb util of jumkey

This is a file that increased the first partition from 48MB to 96MB, as shown above in img for legacy.

 

[tinycore-redpill.v0.7.1.7.vmdk]

https://drive.google.com/file/d/1UCOzK1LTjLy3-bD2u5feeGblhqYN5UH_/view?usp=sharing

Edited by Peter Suh
  • Thanks 1
Link to comment
Share on other sites

[NOTICE]

 

Because pocopico's redpill-dtb ext is changed to redpill-dtb-static ext
In TCRP, the dynamic and automatic dtc patch of jumkey was disabled, so the function was branched so that it can be used as a separate option.

 

To update a new function, follow the steps below.

 

./my.sh

 

If you want to use jumkey's dynamic and automatic dtc patch, you can build it with the options below and use it.

 

./my.sh DS920+ jumkey

 

----------------------------------------------------------------------------------------
Usage: ./my.sh <Synology Model Name> <Options>

Options: jumkey, noconfig, noclean, manual

- jumkey  : Option to apply jumkey's dynamic automatic dtc patch extension files (contrary to pocopico's static dtc patch).  

- noconfig: SKIP automatic detection change processing such as SN/Mac/Vid/Pid/SataPortMap of user_config.json file.

- noclean: SKIP the 💊   RedPill LKM/LOAD directory without clearing it with the Clean now command. 
           However, delete the Cache directory and loader.img.

- manual: Options for manual extension processing and manual dtc processing in build action (skipping extension auto detection)

Please type Synology Model Name after ./my.sh

./my.sh DS918+
./my.sh DS3617xs
./my.sh DS3615xs
./my.sh DS3622xs+
./my.sh DVA3221
./my.sh DS920+
./my.sh DS1621+

- for jun mode

./my.sh DS918+J                                                                                                      
./my.sh DS3617xsJ                                                                                                    
./my.sh DS3615xsJ                                                                                                    
./my.sh DS3622xs+J                                                                                                   
./my.sh DVA3221J                                                                                                     
./my.sh DS920+J                                                                                                      
./my.sh DS1621+J  

Edited by Peter Suh
  • Thanks 1
Link to comment
Share on other sites

[NOTICE]

 

After applying DSM 7.1.0-42661 Update 2, a postupdate option has been added to solve the restore loop. No additional build is required.

 

To update a new function, follow the steps below.

 

./my.sh

 

you can patch it with the options below and use it.

 

./my.sh DS918+ postupdate

 

----------------------------------------------------------------------------------------
Usage: ./my.sh <Synology Model Name> <Options>

 

Options: jumkey, noconfig, noclean, manual

 

- postupdate : Option to patch the restore loop after applying DSM 7.1.0-42661 Update 2, no additional build required.

 

- jumkey  : Option to apply jumkey's dynamic automatic dtc patch extension files (contrary to pocopico's static dtc patch).  

 

- noconfig: SKIP automatic detection change processing such as SN/Mac/Vid/Pid/SataPortMap of user_config.json file.

 

- noclean: SKIP the 💊   RedPill LKM/LOAD directory without clearing it with the Clean now command. 

           However, delete the Cache directory and loader.img.

 

- manual: Options for manual extension processing and manual dtc processing in build action (skipping extension auto detection)

 

Please type Synology Model Name after ./my.sh

 

./my.sh DS918+
./my.sh DS3617xs
./my.sh DS3615xs
./my.sh DS3622xs+
./my.sh DVA3221
./my.sh DS920+
./my.sh DS1621+

 

- for jun mode

 

./my.sh DS918+J                                                                                                      
./my.sh DS3617xsJ                                                                                                    
./my.sh DS3615xsJ                                                                                                    
./my.sh DS3622xs+J                                                                                                   
./my.sh DVA3221J                                                                                                     
./my.sh DS920+J                                                                                                      
./my.sh DS1621+J  

  • Thanks 1
Link to comment
Share on other sites

  • 2 weeks later...

With the help of @dolbycat
ds920+ / ds1621+ jun mode build for TC
The nic waiting time was reduced from 3 minutes to 2 minutes and 10 seconds.

 

Modification of sha256sum of ds920+ 42218 config.json requested by @pocopico may not be necessary at this time.

As for the jun mode, it was completely switched to refer only to @jumkey's repo, and it was possible to build so that even the use of dynamic dtc patches was possible in TC without any problem.

 

It has been changed to be able to respond to both dtc models in m shell.


(jumkey option is whether or not to use dynamic dtc patch)

./my.sh ds920+J jumkey
./my.sh ds1621+J jumkey

 

If additional ext is needed in the VM environment, use it as follows.
./myv.sh ds920+J jumkey
./myv.sh ds1621+J jumkey

Link to comment
Share on other sites

  • 2 weeks later...

The DS920+ recommended 4 ports
As Dolbycat tested, there is no problem with operation even if you increase it to six.
I increased the maximum to 16 and changed it to be available.

So, on dtc DS920(4 port)+, DS1621+(6 port) Jun mode,

If you use the dynamic dtb mapping feature with the jumkey option, we have implemented it to extend to 16 ports so that automatic mapping is recognized.

"Jumkey.qjs.dtb" ext has been modified a little to force the use of the dtb file for 16 ports.

If you want to use the dts file manually, you can download it by referring to my GitHub.
https://github.com/PeterSuh-Q3/tinycore-redpill

After downloading and installing as shown below,
Build the load again
curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" --output my.sh.gz; tar -zxvf my.sh.gz;

./my.sh DS920+J jumkey noclean
./my.sh DS1621+J jumkey noclean

Use the ll command to check if the model.dtb file is in the list
ll /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds920p_42218
ll /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds1621p_42218

If you check once again whether the script (spoiler) below looks like the one I modified with the cat command, it will definitely be applied.
cat /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds920p_42218/install_rd.sh
cat /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds1621p_42218/install_rd.sh

 

Spoiler

#!/bin/sh

tar -zxvf patch.tar.gz
# install dtc
chmod +x dtc
cp dtc /usr/sbin/dtc

# copy 16 ports dts file to /etc.defaults
#echo $PLATFORM_ID
if [ "${PLATFORM_ID}" = "ds920p_42218" ]; then
  echo "copy DS920+'s 16 ports ds920p_16ports.dts to /etc.defaults"
  ./dtc -I dts -O dtb -o model.dtb ds920p_16ports.dts
  cp -vf model.dtb /etc.defaults/model.dtb
elif [ "${PLATFORM_ID}" = "ds1621p_42218" ]; then
  echo "copy DS1621+'s 16 ports ds1621p_16ports.dts to /etc.defaults"
  ./dtc -I dts -O dtb -o model.dtb ds1621p_16ports.dts
  cp -vf model.dtb /etc.defaults/model.dtb
fi  

# copy file
if [ ! -f model_${PLATFORM_ID%%_*}.dtb ]; then
  # Dynamic generation
  ./dtc -I dtb -O dts -o output.dts /etc.defaults/model.dtb
  qjs --std ./dts.js output.dts output.dts.out
  if [ $? -ne 0 ]; then
    echo "auto generated dts file is broken"
    exit 0
  fi
  ./dtc -I dts -O dtb -o model_r2.dtb output.dts.out
  cp -vf model_r2.dtb /etc.defaults/model.dtb
  cp -vf model_r2.dtb /var/run/model.dtb
else
  cp -vf model_${PLATFORM_ID%%_*}.dtb /etc.defaults/model.dtb
  cp -vf model_${PLATFORM_ID%%_*}.dtb /var/run/model.dtb
fi
 

 

I've installed up to 14 discs.

6 built-in sata

I used the following product, external 8 ports (Marvel 88SE9215 chip 4 ports + ASM1166 chip 2 ports [unrecognized]) X2.
 

https://ko.aliexpress.com/item/33016481933.html

 

1789401761_2022-06-2211_55_21.thumb.png.46e3b85790d6032807356952538995cb.png1376218062_2022-06-2211_55_42.thumb.png.0cc170d90e655654d28b94e5e189b798.png1971668188_2022-06-231_26_53.thumb.png.2086a4a436abd4b582c9f4d44884918b.png

Edited by Peter Suh
  • Like 1
  • Thanks 1
Link to comment
Share on other sites

On 6/11/2022 at 5:37 PM, Peter Suh said:

With the help of @dolbycat
ds920+ / ds1621+ jun mode build for TC
The nic waiting time was reduced from 3 minutes to 2 minutes and 10 seconds.

 

Modification of sha256sum of ds920+ 42218 config.json requested by @pocopico may not be necessary at this time.

As for the jun mode, it was completely switched to refer only to @jumkey's repo, and it was possible to build so that even the use of dynamic dtc patches was possible in TC without any problem.

 

It has been changed to be able to respond to both dtc models in m shell.


(jumkey option is whether or not to use dynamic dtc patch)

./my.sh ds920+J jumkey
./my.sh ds1621+J jumkey

 

If additional ext is needed in the VM environment, use it as follows.
./myv.sh ds920+J jumkey
./myv.sh ds1621+J jumkey

 

I am testing in VMWare DS920+ with ./myv.sh DS920+J jumkey, and works perfecty with DSM 7.1-42661 Update 2 and new dynamic dtc patch ds920p.dts for 16 disks.

 

But I want to have a loader.img with noclean, and not possible, not permitted for you. Can I do something with script for get the loader.img?

 

- noclean: SKIP the 💊   RedPill LKM/LOAD directory without clearing it with the Clean now command. 
           However, delete the Cache directory and loader.img.

photo_2022-06-22_23-12-18.jpg

photo_2022-06-22_23-12-12.jpg

photo_2022-06-22_23-12-05.jpg

Link to comment
Share on other sites

12 hours ago, apriliars3 said:

 

I am testing in VMWare DS920+ with ./myv.sh DS920+J jumkey, and works perfecty with DSM 7.1-42661 Update 2 and new dynamic dtc patch ds920p.dts for 16 disks.

 

But I want to have a loader.img with noclean, and not possible, not permitted for you. Can I do something with script for get the loader.img?

 

- noclean: SKIP the 💊   RedPill LKM/LOAD directory without clearing it with the Clean now command. 
           However, delete the Cache directory and loader.img.

photo_2022-06-22_23-12-18.jpg

photo_2022-06-22_23-12-12.jpg

photo_2022-06-22_23-12-05.jpg

 

 

To preserve the loader.img file, edit my.sh directly as shown below.

vi my.sh
:535
(press i key for edit)
# rm -f /home/tc/redpill-load/loader.img
Comment it out by putting # in front of it so that it doesn't work.

 

 

Edited by Peter Suh
Link to comment
Share on other sites

On 6/22/2022 at 11:37 PM, Peter Suh said:

The DS920+ recommended 4 ports
As Dolbycat tested, there is no problem with operation even if you increase it to six.
I increased the maximum to 16 and changed it to be available.

So, on dtc DS920(4 port)+, DS1621+(6 port) Jun mode,

If you use the dynamic dtb mapping feature with the jumkey option, we have implemented it to extend to 16 ports so that automatic mapping is recognized.

"Jumkey.qjs.dtb" ext has been modified a little to force the use of the dtb file for 16 ports.

If you want to use the dts file manually, you can download it by referring to my GitHub.
https://github.com/PeterSuh-Q3/tinycore-redpill

After downloading and installing as shown below,
Build the load again
curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" --output my.sh.gz; tar -zxvf my.sh.gz;

./my.sh DS920+J jumkey noclean
./my.sh DS1621+J jumkey noclean

Use the ll command to check if the model.dtb file is in the list
ll /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds920p_42218
ll /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds1621p_42218

If you check once again whether the script (spoiler) below looks like the one I modified with the cat command, it will definitely be applied.
cat /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds920p_42218/install_rd.sh
cat /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds1621p_42218/install_rd.sh

 

  install_rd.sh (Reveal hidden contents)

#!/bin/sh

tar -zxvf patch.tar.gz
# install dtc
chmod +x dtc
cp dtc /usr/sbin/dtc

# copy 16 ports dts file to /etc.defaults
#echo $PLATFORM_ID
if [ "${PLATFORM_ID}" = "ds920p_42218" ]; then
  echo "copy DS920+'s 16 ports ds920p_16ports.dts to /etc.defaults"
  ./dtc -I dts -O dtb -o model.dtb ds920p_16ports.dts
  cp -vf model.dtb /etc.defaults/model.dtb
elif [ "${PLATFORM_ID}" = "ds1621p_42218" ]; then
  echo "copy DS1621+'s 16 ports ds1621p_16ports.dts to /etc.defaults"
  ./dtc -I dts -O dtb -o model.dtb ds1621p_16ports.dts
  cp -vf model.dtb /etc.defaults/model.dtb
fi  

# copy file
if [ ! -f model_${PLATFORM_ID%%_*}.dtb ]; then
  # Dynamic generation
  ./dtc -I dtb -O dts -o output.dts /etc.defaults/model.dtb
  qjs --std ./dts.js output.dts output.dts.out
  if [ $? -ne 0 ]; then
    echo "auto generated dts file is broken"
    exit 0
  fi
  ./dtc -I dts -O dtb -o model_r2.dtb output.dts.out
  cp -vf model_r2.dtb /etc.defaults/model.dtb
  cp -vf model_r2.dtb /var/run/model.dtb
else
  cp -vf model_${PLATFORM_ID%%_*}.dtb /etc.defaults/model.dtb
  cp -vf model_${PLATFORM_ID%%_*}.dtb /var/run/model.dtb
fi
 

 

I've installed up to 14 discs.

6 built-in sata

I used the following product, external 8 ports (Marvel 88SE9215 chip 4 ports + ASM1166 chip 2 ports [unrecognized]) X2.
 

https://ko.aliexpress.com/item/33016481933.html

 

1789401761_2022-06-2211_55_21.thumb.png.46e3b85790d6032807356952538995cb.png1376218062_2022-06-2211_55_42.thumb.png.0cc170d90e655654d28b94e5e189b798.png1971668188_2022-06-231_26_53.thumb.png.2086a4a436abd4b582c9f4d44884918b.png

I got "Wrong EFI signature..." when boot, please help :((
This is all command i use:
 ./rploader.sh update
./rploader.sh fullupgrade
wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz; tar -zxvf my.sh.gz;
curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/rploader.sh" --output rploader.sh
./my.sh DS920+J jumkey

Edited by akanepro
Link to comment
Share on other sites

TC now extends the DTC support model to the full model.

 

5 Models Known as Non-DTC Supported Models
Also on DS918+, DS3615xs, DS3617xs, DS3622xs+, DVA3221
When only the model.dtb file is copied to the /etc.defaults/ and /var/run/ directories,
The sataport starts working in the device tree.

 

in the user_config.json file
SataPortMap and DiskIdxMap options work with DTC.
It may cause side effects.
So, M shell replaces the empty values of SataPortMap = "", DiskIdxMap = "".

 

As it is currently implemented as a unique function of the M shell,

It is not possible to build using only the existing rploader.sh.

 

before use,
Please update to the latest version by executing only

./my.sh

 

Build options for the above 5 models are listed below.

 

[JOT Mode]
./my.sh DS918+ poco

 

[JUN Mode]
./my.sh DS918+J poco

 

Since @jumkey did not modify quick js for dynamic dtc patch for the above 5 models, the jumkey option is not available yet.

The poco option must be used for pocopico's static dtc patch function to work.

 

Currently, two models, DS918+ and DS3622xs+, have been tested on baremetal.

All DTC models supported by M shell support up to 16 SATA disks.

 

HBA card is recognized and operated separately regardless of SataPortMap or DTC's dtb file.

DS920+ and DS1621+ appear to have broken mpt3sas ext.
@pocopico I need your help.

 

719513533_2022-06-261_29_08.thumb.png.de357edcc9d3ca24773ef20d620914de.png

 

Edited by Peter Suh
Link to comment
Share on other sites

On 6/22/2022 at 6:37 PM, Peter Suh said:

I increased the maximum to 16 and changed it to be available.

i wanted to say THANKS for your work. I migrated today from DS3622xsp to DS920+. All my 6 drives are detected, nvme cache works, 10GbE ethernet card works, HW acceleration works. I am happy again :)

Best Regards

  • Like 1
Link to comment
Share on other sites

Tinycore M shell DS2422+ model additional version released.

The new model DS2422+ can be built from the m shell.
 

Because it is a version that has not been officially added to pocopico's TC yet.

It can only be built from within the m shell.


Please update the new version with the command below in Tc linux.
./my.sh
./myv.sh

 

M shell DS2422+ does not support Jot Mode yet.

DS2422+ is the same AMD v1000 platform as DS1621+,
So it shares ext with DS1621+.

DS1621+ only has 6 bays, while DS2422+ supports 12 bays like Capture.

 

1987894087_2022-07-0110_13_56.thumb.png.57bb360bf459108f4d7840260fee5a99.png

 

In the m shell, jumkey and poco options are deprecated.

 

You can use it like below to build.
./my.sh DS2422+J


In the VM, use it as below and add the necessary drivers first.

When asked if you want to clean redpill-load in the middle, you should never type y.

Tested on proxmox and VirtualBox.

./myv.sh DS2422+J

 

 

 

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

So I'm running into an issue with this.

 

It doesn't detect my 8125 base 2.5gbe and when I use the manual option, it never actually allows me to suggest other modules

acpid and 8125 that I definately need.

 

the m.sh script is depreciated so I can't force it..

 

How do I get past this?

 

Edit: NM I added them manually via rp-loader then ran my.sh.. all good now.

 

Edited by rok1
Link to comment
Share on other sites

15 hours ago, rok1 said:

So I'm running into an issue with this.

 

It doesn't detect my 8125 base 2.5gbe and when I use the manual option, it never actually allows me to suggest other modules

acpid and 8125 that I definately need.

 

the m.sh script is depreciated so I can't force it..

 

How do I get past this?

 

Edit: NM I added them manually via rp-loader then ran my.sh.. all good now.

 

 

 

If you want to pre-add ext to my.sh dictionary
Just use myv.sh .
After myv.sh is used my.sh is called automatically.
Apply the same options you used for my.sh to myv.sh.

 

A guide to using myv.sh and how it works is described at the end of the guide content at the top of this topic.

  • Thanks 1
Link to comment
Share on other sites

5 hours ago, Peter Suh said:

 

 

The DVA1622 loader build function in M SHELL has been restored.
There seems to have been a problem while developing DS2422+ feature fixes at the same time.
Now it can be used normally.

 

Thanks.

Edited by bluecatus
Link to comment
Share on other sites

  • 3 weeks later...

M SHELL Jun Mode DS1621xs+ is released.

This time, it is the DS1621xs+, a 6-bay model.

Unlike DS1621+, it is a Broadwellnk platform like DS3622xs+.


Only jun mode is supported.

jot mode is not created unless there is a special reason.
 

It is supported by TC original and can only be built with my M Shell.

./my.sh DS1621xs+J

For VMs that require additional drivers, etc.

./myv.sh DS1621xs+J

You can use it as

 

 

921884403_2022-07-1910_58_54.thumb.png.a8e2a6e6952411e4fd469e2a6e558df2.png

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

M SHELL Jot Mode DS1621xs+ is released.

Following the jun mode I uploaded yesterday, I also created a jot mode.

 

When migrating between jun modes, the system partition sometimes disappears.
I think jot mode is also sometimes necessary, and I made it to use it too.^^

 

If I use the bsp file of jot mode 3622 as it is, it just works.
The environment file has been slightly modified.

 

TC Original does not support it, and can only be built with my M Shell.

./my.sh DS1621xs+

 

For VMs that require additional drivers, etc.

./myv.sh DS1621xs+

 

You can use it as

And you will surely meet the infinite recovery mode.
then

sudo ./my.sh DS1621xs+ postupdate

Please take care of it.

  • Like 1
Link to comment
Share on other sites

 

i made a test on a baremetal upgrade from 3615xs 6.2.3-u3 to 3622xs 7.1.0 ...on a Microserver Gen8  and all worked fine   using one disk

 

ok ... so i tried the stick that successfully worked on the test disk , but now the live update in "prod" is not working

 

i get the error to either check the network , or that the file is corrupted.

 

pulled all the disk out, put in the test disk ....and all boots fine to 7.1 update 1

 

SynologyNAS login: root

Synology strongly advises you not to run commands as the root user, who has
the highest privileges on the system. Doing so may cause major damages
to the system. Please note that if you choose to proceed, all consequences are
at your own risk.

 

BusyBox v1.30.1 () built-in shell (ash)

SynologyNAS> cat /var/log/*rc*
START /linuxrc.syno.impl
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "libphy.ko" for pocopico.tg3 (args: )
Loading kmod #1 "tg3.ko" for pocopico.tg3 (args: )
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-tg3.sh" for pocopico.tg3->on_boot
Loading module tg3 -> Module tg3 loaded succesfully
Ran "check-tg3.sh" for pocopico.tg3->on_boot - exit=0
Running "boot-wait.sh" for redpill-boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)
Still waiting for boot device (waited 2 of 30 seconds)
Still waiting for boot device (waited 3 of 30 seconds)
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
All disk ready or timeout execeed
Assemble args: -u 1db88863:19f94f8f:3017a5a8:c86610be /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: /dev/md0 has been started with 4 drives (out of 12).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0...
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_bromolow_3615xs
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_bromolow_3615xs
Exit on error [7] root not matched with junior...
Wed Jul 20 07:58:09 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0

 

 

 

any ideea on this ?

 

./my.sh DS3622xs+ with real mac   was used for boot loader creation i used the script from this thread

Link to comment
Share on other sites

  • 2 weeks later...

[NOTICE]

Add userdts (manual application of user-defined dts file) option function to m shell for TCRP.

 

 

------------------------------------------------------------ --------------------------------------
Usage: ./my.sh <Synology Model Name> <Options>

Options: postupdate, noconfig, noclean, manual, realmac, userdts

...

- userdts : Option to use the user-defined platform.dts file instead of auto-discovery mapping with dtcpatch.

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

 

The specific usage is as follows.

It is good to open the dts file you made in advance with notepad, etc.

Just give one userdts option and do something like below.

 

./my.sh DS920+ userdts

 

After some downloads and loading and the message goes by

user-define dts file make in progress...

copy and paste user dts contents here, press any key to continue...

 

Pressing any key in this message will open a blank content in the vi editor.

Here, I copied the content I copied to the clipboard earlier in Notepad.

Paste it.

Press the i key in the vi editor to enter input mode.

Paste shortcut in terminal or putty

Shift+insert key.

Once pasted, press the esc key once.

:wq!

Save and exit.

When the vi editor is closed, it will only back up and be done.

 

After that, you can build it as you did before.

 

./my.sh DS920+

 

Except for the dynamic dtbpatch driver instead

To use the dts file for that user

The loader is built by replacing it with the static redpill-dtb-static driver.

 

To make the dynamic dtbpatch driver be used again as usual

rm /home/tc/custom-module/ds920p.dts

or

rm /mnt/sd#3/auxfiles/ds920p.dts

must be erased with .

Edited by Peter Suh
  • Thanks 1
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.

×
×
  • Create New...