TinyCore RedPill loader (TCRP) - Development release 0.9

[pocopico]

I'm planning to introduce the tcrpfriend buildroot that will act the same way as jumkeys build root but a bit more enhanced to automatically detect any updates and perform the patching just like ARPL does. I'm in the testing phase and I will release it on 0.9.2.0 

 

[Peter Suh]

3 hours ago, pocopico said:

I'm planning to introduce the tcrpfriend buildroot that will act the same way as jumkeys build root but a bit more enhanced to automatically detect any updates and perform the patching just like ARPL does. I'm in the testing phase and I will release it on 0.9.2.0 

 

 

 

@pocopico

There seems to be a typo in ./rplaoder.sh line 2482 .

It looks like you are trying to delete loader.img , but the load path is wrong.

 

     sudo rm -f /home/tc/redpill_load/loader.img

     sudo rm -f /home/tc/redpill-load/loader.img

[Peter Suh]

@pocopico

 

TC 0.9.1.9 as below
I saw the friend entry, so I tested it after the build.
It is impossible to enter due to an error as below.
Do you still have more work to add?

 

 

 

[pocopico]

1 hour ago, Peter Suh said:

@pocopico

 

TC 0.9.1.9 as below
I saw the friend entry, so I tested it after the build.
It is impossible to enter due to an error as below.
Do you still have more work to add?

 

 

 

oh, crap I didn’t comment that ? The buildroot is not ready yet. 

[-iliya-]

@pocopico please 😰 see my post about 20+ HDD and USB flash\HDD problem - maybe can it resolve in 0.9 TCRP? 😇

 

[dimakv2014]

21 час назад, Peter Suh сказал:

 

We already released the DVA3219 Jot loader last Thursday.
Try it out.
https://xpenology.com/forum/topic/61839-tinycore-redpill-loader-build-support-tool-m-shell/?do=findComment&comment=337219

Yes I know, I am eager to test but I dont have spare hardware to test it out yet, its all in the process

[pocopico]

I need some testers for TCRP Friend. TCRP Friend adds a buildroot boot option that will automatically patch your initrd and kernel after an update. Thats the same process that is used on ARPL and (jumkey) JUN mode but with my modified buildroot.

 

While on TCRP You need to run

 

./rploader.sh upgrade
./rploader.sh fullupgrade
./rploader.sh clean
./rploader.sh build broadwellnk-7.0.1-42218 withfriend

 

Then at boot select the last entry and test any upgrades.  It will be saved as default once you select it once. Please leave the boot option to TCRP Friend for any future upgrades.

 

 

[keasee]

hi Poco
Would Like to join withfriend with baremetal HP 400 G2 and hp microserver g8

Best keasee

[Peter Suh]

I tried it in virtualbox.

There is a problem that the IP address cannot be expressed in the beginning.

However, IP is normally assigned in DHCP.

I connected to a known IP and connected to DSM normally.

( DSM was installed with the existing TCRP loader. Then I booted into the friend loader. )

 

Edited September 20, 2022 by Peter Suh

[Peter Suh]

And, if I want to proceed with an update in the future, I wanted to perform an automatic update like Jun's Mod.
Isn't it impossible under the following conditions?

 

Edited September 20, 2022 by Peter Suh

[Peter Suh]

And, there is one more problem.

 

I proceeded to install DSM through a TCRP friend with two formatted disks.

 

I requested 7.1.1-42621 and completed the installation of that version.

 

However, I was asked to reinstall DSM.

 

The second boot after reinstallation requires migration again.

 

After migration, log in to DSM normally.

[pocopico]

1 hour ago, Peter Suh said:

And, if I want to proceed with an update in the future, I wanted to perform an automatic update like Jun's Mod.
Isn't it impossible under the following conditions?

 

it will be introduced soon. Can you continue testing with this priority ? 

 

DS918+

DS920+

DS1621xs+

 

Edited September 20, 2022 by pocopico

[Peter Suh]

I tested the DS3622xs+ again with the updated 0.9.2.1 again 7 hours ago. Similarly, the Virtualbox VM environment.

 

As the captured result, the IP address is checked normally in the TCRP friend loader.

 

With two disks formatted, DSM 7.1.1-42962 is installed normally.
No reinstallation is required this time.

The first operation for DSM account creation is abnormal.
It seems that the pre-work speed of TCRP friend loader is much slower than 0.9.2.0.
When I was able to connect, I was expecting an account creation screen,
I will be connected from the login window.
In the login window, it is impossible to access root without a password.
I can access the admin without a password.
After that, I will enter the account creation screen I normally see.
New accounts can be created normally.
After that, everything is normal.

 

 

 

 

Edited September 21, 2022 by Peter Suh

[Peter Suh]

This time, I tried changing the method while building with DS918+.

 

As you guide, I used 7.1.1-42962 directly instead of using the command below as 7.0.1-42218, which is the required version of Jun's Mod.

 

./rploader.sh build broadwellnk-7.0.1-42218 withfriend

 

./rploader.sh build apollolake-7.1.1-42962 withfriend

 

As before, the situation where you have to log in from admin is gone.

 

It starts from the normal account creation request screen.

 

Let's go back to the DS3622xs+ and do the same test.

 

The same result is expected.

 

[pocopico]

I've tested and fixed all issues on DS3615xs and i wenr from 7.0.1 update 5 to 7.1.0 update 4 to 7.1.1 fine. I will continue to test. The main issue is the config patches are not up to dete.

 

 

[Peter Suh]

2 hours ago, pocopico said:

I've tested and fixed all issues on DS3615xs and i wenr from 7.0.1 update 5 to 7.1.0 update 4 to 7.1.1 fine. I will continue to test. The main issue is the config patches are not up to dete.

 

 

 

in config.json
https://example.com was still recorded,
Will there be any changes after the final stabilization check?

[pocopico]

35 minutes ago, Peter Suh said:

 

in config.json
https://example.com was still recorded,
Will there be any changes after the final stabilization check?

 

Yes.

[Peter Suh]

3 hours ago, pocopico said:

I've tested and fixed all issues on DS3615xs and i wenr from 7.0.1 update 5 to 7.1.0 update 4 to 7.1.1 fine. I will continue to test. The main issue is the config patches are not up to dete.

 

 

 

I tried manually installing DSM with 42218->42661->42962 as you tested.

 

When the loader was built with 42218, the backup of about 480mb was performed without cleaning the lkm and load directories.

 

As such, 42218 was successfully installed.

 

After that, in the process of manually installing 42661 DSM, an insufficient space message was checked in the log, and the kernel stopped itself.

 

When I returned to TC Linux, I found that only the load directory was left under the home directory and it was damaged.

 

Restore files again, build with 42218 loader, and this time clean and back up.

 

After re-entering the friend loader, recovery was requested at once, and after that, normal DSM login was possible.

 

In the process of further testing, we will repeat the test several times and report the results to see if we encounter the message of insufficient space again.

[Peter Suh]

5 minutes ago, Peter Suh said:

 

I tried manually installing DSM with 42218->42661->42962 as you tested.

 

When the loader was built with 42218, the backup of about 480mb was performed without cleaning the lkm and load directories.

 

As such, 42218 was successfully installed.

 

After that, in the process of manually installing 42661 DSM, an insufficient space message was checked in the log, and the kernel stopped itself.

 

When I returned to TC Linux, I found that only the load directory was left under the home directory and it was damaged.

 

Restore files again, build with 42218 loader, and this time clean and back up.

 

After re-entering the friend loader, recovery was requested at once, and after that, normal DSM login was possible.

 

In the process of further testing, we will repeat the test several times and report the results to see if we encounter the message of insufficient space again.

 

misunderstood
Even after recovery, it was not possible to enter DSM.
Attempts to delete the 10GB nic driver were repeated as shown below, and eventually the kernel died again.

 

This is a situation where 42661 DSM was manually installed in the DS3622xs+ 42218 bootloader.

 

[aportnov]

Is it possible to boot into tiny core without having access to a physical machine, for example, when you are loaded into DSM, send a command with a reboot and login to tiny core?

[Peter Suh]

7 minutes ago, aportnov said:

Is it possible to boot into tiny core without having access to a physical machine, for example, when you are loaded into DSM, send a command with a reboot and login to tiny core?

 

When DSM boots in junior mode, connect to the root account (no password) via ttyd console for TCRP or telnet otherwise.

Another way is to connect with a serial cable (including virtual) and proceed with the same process.

Edited September 21, 2022 by Peter Suh

[pocopico]

@Peter Suh I've tested the whole 3622xs install/update process and enhanced the buildroot script to bringover the new friend if it exists.

 

Can you please verify the ds3622xs and test again going from 42218 to 42962 ?  

[sbv3000]

2 hours ago, aportnov said:

Is it possible to boot into tiny core without having access to a physical machine, for example, when you are loaded into DSM, send a command with a reboot and login to tiny core?

server mobos generally have this feature, an ip kvm, there are add on cards based on r-pi might work https://www.youtube.com/watch?v=cVWF3u-y-Zg

other option is to run in esxi if your hardware supports it, you always have 'console access' so could access grub menu

[Peter Suh]

1 hour ago, pocopico said:

@Peter Suh I've tested the whole 3622xs install/update process and enhanced the buildroot script to bringover the new friend if it exists.

 

Can you please verify the ds3622xs and test again going from 42218 to 42962 ?  

 

Sure.

[Peter Suh]

 

1 hour ago, pocopico said:

@Peter Suh I've tested the whole 3622xs install/update process and enhanced the buildroot script to bringover the new friend if it exists.

 

Can you please verify the ds3622xs and test again going from 42218 to 42962 ?  

 

 

I built DS3622xs+ 7.0.1-42218,
This is not possible because of the following error.