Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)

pocopico

By pocopico
in Loaders

 Share

Recommended Posts

Peter Suh Guru Master

Peter Suh

Posted
Posted
14 hours ago, wirdo said:

Hi Peter,

 

I'm trying to switch over to your version of the loader (currently using arpl) but I cannot get it to boot after building the loader. 

The reason for the switch is because I want to give 7.2 a shot. I've tried both 7.2 loaders and both give me the same outcome.

Using 918+ with real mac.

Thanks for all your efforts!

IMG_1137.jpg

 

 

There are three FAT partitions on the USB stick built with the loader, but the automatic mounting of these partitions seems to have failed.

 

The cause of this has not been accurately identified.

 

However, what you can try is to exclude other devices from the USB port and leave only the USB stick for this loader and do not use any other devices at the same time.

 

Also, if possible, we recommend using a USB stick with a speed of USB 3 or higher and a USB port of 3 or higher.

 

A good brand of USB stick is SANDISK.

Link to comment
Share on other sites
The_Mole Newbie

The_Mole

Posted
Posted

Hi,

 

I've been trying to add a Mellanox MCX311A to the system, and at least in TC, all looks good:

  

lspci -v
07:00.0 Ethernet controller: Mellanox Technologies MT27500 Family [ConnectX-3]
        Subsystem: Mellanox Technologies Device 0055
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at f7900000 (64-bit, non-prefetchable) [size=1M]
        Memory at fbf000000 (64-bit, prefetchable) [size=8M]
        Expansion ROM at f7800000 [disabled] [size=1M]
        Capabilities: [40] Power Management version 3
        Capabilities: [48] Vital Product Data
        Capabilities: [9c] MSI-X: Enable+ Count=128 Masked-
        Capabilities: [60] Express Endpoint, MSI 00
        Capabilities: [c0] Vendor Specific Information: Len=18 <?>
        Capabilities: [100] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [148] Device Serial Number e4-1d-2d-03-00-dc-39-70
        Capabilities: [154] Advanced Error Reporting
        Capabilities: [18c] #19
        Kernel driver in use: mlx4_core


dmesg |grep mlx
[    1.539474] mlx4_core: Mellanox ConnectX core driver v4.0-0
[    1.539498] mlx4_core: Initializing 0000:07:00.0
[    8.793114] mlx4_core 0000:07:00.0: DMFS high rate steer mode is: disabled performance optimized steering
[    8.793495] mlx4_core 0000:07:00.0: 16.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x4 link at 0000:00:1c.4 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[    8.838848] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0
[    8.839075] mlx4_en 0000:07:00.0: Activating port:1
[    8.841547] mlx4_en: 0000:07:00.0: Port 1: Using 8 TX rings
[    8.841549] mlx4_en: 0000:07:00.0: Port 1: Using 8 RX rings
[    8.842023] mlx4_en: 0000:07:00.0: Port 1: Initializing port
[    8.842589] mlx4_en 0000:07:00.0: registered PHC clock
[   30.145433] mlx4_en: eth4: Steering Mode 1


ifconfig
eth4      Link encap:Ethernet  HWaddr E4:1D:2D:DC:39:70
          inet addr:192.168.11.51  Bcast:192.168.11.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:328 errors:0 dropped:102 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:34448 (33.6 KiB)  TX bytes:684 (684.0 B)

 

God's in his heaven — All's right with the world.
However, after I build the loader and boot into DSM, it looks like this:

  

lspci -v
0000:07:00.0 Class 0200: Device 15b3:1003
        Subsystem: Device 15b3:0055
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at f7900000 (64-bit, non-prefetchable) [size=1M]
        Memory at fbf000000 (64-bit, prefetchable) [size=8M]
        Expansion ROM at f7800000 [disabled] [size=1M]
        Capabilities: [40] Power Management version 3
        Capabilities: [48] Vital Product Data
        Capabilities: [9c] MSI-X: Enable+ Count=128 Masked-
        Capabilities: [60] Express Endpoint, MSI 00
        Capabilities: [c0] Vendor Specific Information: Len=18 <?>
        Capabilities: [100] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [148] Device Serial Number e4-1d-2d-03-00-dc-39-70
        Capabilities: [154] Advanced Error Reporting
        Capabilities: [18c] Secondary PCI Express
        Kernel driver in use: mlx4_core


dmesg | grep mlx
[    8.244251] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
[    8.244454] mlx4_core: Initializing 0000:07:00.0
[   15.451927] mlx4_core 0000:07:00.0: PCIe BW is different than device's capability
[   15.452082] mlx4_core 0000:07:00.0: PCIe link speed is 5.0GT/s, device supports 8.0GT/s
[   15.452234] mlx4_core 0000:07:00.0: PCIe link width is x4, device supports x4

 

Seems like DSM doesn't load mlx4_en and I'm a bit stuck, here. Can anyone help me out?

Link to comment
Share on other sites
alirz1 Super Member

alirz1

Posted
Posted
49 minutes ago, Dvalin21 said:

Hey guys, like @alirz1 I too wonder is it safe to update to the latest update?  But more so, my question is, I want to update my server to a 10 core/20 thread Xeon cpu. I know this is more than what DS3622xs+ normally has. Will upgrading to this cpu, will it cause an issue with my Xpenology? Thanks.

Number of cpus shouldn't cause any issues. I'm running a ds918 xpenology on a 12 core i7 and it's fine. Dsm doesn't seem all cores but from what I understand in the background all cores should work as normal, at least that's my understanding 

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
Posted
On 10/1/2023 at 8:35 PM, vista1967 said:

Hello,

 

I see in some screenshots Junior Mode in TCRP, what is it for and how is it done, do I need to install something? 

 

THANKS

 

 

obraz.png.95adbfd52fdd9eb2eb33311e4f87b72c.png

 

 

Junior mode is rarely used on a daily basis.
You can think of the step of installing the DSM Pat file as Junior mode.

 

If you absolutely need to reinstall DSM, enter junior mode with the J key.
You can reinstall the DSM Pat file by accessing port 5000 with a web browser.

 

REDPILL developers sometimes enter Junior to diagnose problems.

  • Like 1
Link to comment
Share on other sites
alirz1 Super Member

alirz1

Posted
Posted
6 hours ago, Dvalin21 said:

Hey guys, like @alirz1 I too wonder is it safe to update to the latest update?  But more so, my question is, I want to update my server to a 10 core/20 thread Xeon cpu. I know this is more than what DS3622xs+ normally has. Will upgrading to this cpu, will it cause an issue with my Xpenology? Thanks.

 

4 hours ago, dj_nsk said:

it doesn't exist :)

 

Ok ok. It's 6 cores, 12 threads!. Happy

  • Haha 1
Link to comment
Share on other sites
vista1967 Advanced Member

vista1967

Posted
Posted
13 hours ago, Peter Suh said:

 

 

Junior mode is rarely used on a daily basis.
You can think of the step of installing the DSM Pat file as Junior mode.

 

If you absolutely need to reinstall DSM, enter junior mode with the J key.
You can reinstall the DSM Pat file by accessing port 5000 with a web browser.

 

REDPILL developers sometimes enter Junior to diagnose problems.

Thanks for the answer, I'll test it once, it's a new experience for me with this great tool that you provide us with!

  • Thanks 1
Link to comment
Share on other sites
ilovepancakes Advanced Member

ilovepancakes

Posted
Posted

Been a while since I have updated DSM or had time to visit here. Wondering if someone can outline for me the proper steps to get on DSM 7.2. I am currently running TinyCore Redpill Friend 0.9.3.0 loader image and am on DSM 7.1.1 Update 5.

 

What is the order and steps I need to do to get on latest DSM 7.2 along with getting to latest TCRP loader?

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
Posted
6 hours ago, ilovepancakes said:

Been a while since I have updated DSM or had time to visit here. Wondering if someone can outline for me the proper steps to get on DSM 7.2. I am currently running TinyCore Redpill Friend 0.9.3.0 loader image and am on DSM 7.1.1 Update 5.

 

What is the order and steps I need to do to get on latest DSM 7.2 along with getting to latest TCRP loader?

 

Please follow this sequence.

 

 

 

However, pocopico's TCRP does not support the latest version.
I recommend using TCRP-mshell, which I maintain.

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

 

Instead, you will need to re-record this loader to USB.
Since it is the same TCRP, existing DSMs are compatible with each other.

 

 

Link to comment
Share on other sites
ilovepancakes Advanced Member

ilovepancakes

Posted
Posted
10 hours ago, Peter Suh said:

 

Please follow this sequence.

 

 

 

However, pocopico's TCRP does not support the latest version.
I recommend using TCRP-mshell, which I maintain.

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

 

Instead, you will need to re-record this loader to USB.
Since it is the same TCRP, existing DSMs are compatible with each other.

 

 

 

Thanks Peter. I remember a while ago you mentioning you were going to make an mshell version of TCRP, nice to see it now!! So, if I understand correctly, I should first switch from my current loader to your loader, without even updating DSM, just to get the loader itself switched? And I assume this just involves replacing the current loader VMDK (I am on ESXi) with your loader VMDK, then building in your loader using same settings as current loader/DSM?

 

Then once that is all complete and DSM is working on 7.1.1 using your loader, then follow the steps you outlined to rebuild again for 7.2.1, then reboot, and then it will prompt to install 7.2.1? Do I have that all correct?

  • Like 1
Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
Posted
15 hours ago, ilovepancakes said:

 

Thanks Peter. I remember a while ago you mentioning you were going to make an mshell version of TCRP, nice to see it now!! So, if I understand correctly, I should first switch from my current loader to your loader, without even updating DSM, just to get the loader itself switched? And I assume this just involves replacing the current loader VMDK (I am on ESXi) with your loader VMDK, then building in your loader using same settings as current loader/DSM?

 

Then once that is all complete and DSM is working on 7.1.1 using your loader, then follow the steps you outlined to rebuild again for 7.2.1, then reboot, and then it will prompt to install 7.2.1? Do I have that all correct?

 

Yes, everything is correct.
Proceed as expected.

Link to comment
Share on other sites
ilovepancakes Advanced Member

ilovepancakes

Posted
Posted
8 hours ago, Peter Suh said:

 

Yes, everything is correct.
Proceed as expected.

 

I was able to get all my instances of 7.1.1 updated to 7.2.1 pretty smoothly using that method. In fact, I changed loaders and re-built to 7.2.1 all in one step to save time, and that worked okay. The only hiccup I noticed when using your loader is that the SataPortMap and DiskIdxMap values set in your loader or even by manual editing of the user_config.json file are NOT saved when building the loader. After the build, both those values in the user_config.json file are reset to nothing and just show "". And when rebooting to boot into DSM, the loader SATA boot options line also shows no set values for these. I have to hit "e" add them in that screen manually to the SATA boot line, and then it seems to save them and use them in the future. Why would setting them in your loader build settings or user_config.json before build not be honored and actually save the values for use when booting DSM?

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
Posted
2 hours ago, ilovepancakes said:

 

I was able to get all my instances of 7.1.1 updated to 7.2.1 pretty smoothly using that method. In fact, I changed loaders and re-built to 7.2.1 all in one step to save time, and that worked okay. The only hiccup I noticed when using your loader is that the SataPortMap and DiskIdxMap values set in your loader or even by manual editing of the user_config.json file are NOT saved when building the loader. After the build, both those values in the user_config.json file are reset to nothing and just show "". And when rebooting to boot into DSM, the loader SATA boot options line also shows no set values for these. I have to hit "e" add them in that screen manually to the SATA boot line, and then it seems to save them and use them in the future. Why would setting them in your loader build settings or user_config.json before build not be honored and actually save the values for use when booting DSM?

 

In the VM, it is forced not to set any values to SataPortMap and DiskIdxMap, which is recommended by TTG.

If there is no value, it dynamically searches for the SATA PORT setting.


Unless there is a special reason, the default setting to increase the success rate for beginners is to leave these two values blank.
If you absolutely need to modify it, you should use "e" as you discovered.

Link to comment
Share on other sites
Cornelius_drebbel Newbie

Cornelius_drebbel

Posted
Posted (edited)

Hi all.

@Peter Suh I have a problem with second NIC on your loader 0.9.5.0 and DSM 7.2.1.I have these parameters in user config:
  

.... 
 "extra_cmdline": {
    "mac1": "0011327b3c19",
    "mac2": "0011327b3c1a",
    "netif_num": "2"
....

But second NIC not change mac-address in DSM. With previous version of DSM and tcrpl 0.9.4.9 everything worked fine. What i`m doing wrong?

 

1111.JPG

Edited by Cornelius_drebbel
Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
Posted
8 hours ago, envision said:

Hey @Peter Suh, do you have instructions on how to migrate from the traditional tinycore-redpill to your fork/method (I'm using ESXi method). Sorry if this question was already answered - i didn't find it.

 

Thanks in advance

 

popopico's original TCRP and my TCRP-mshell are compatible with each other because they are the same TCRP.
Please migrate in the order below.
For migrations that require maintaining the same revision, the process below is the same.

 

https://xpenology.com/forum/topic/61839-tinycore-redpill-loader-build-support-tool-m-shell/?do=findComment&comment=450273

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
Posted (edited)
17 hours ago, Cornelius_drebbel said:

Hi all.

@Peter Suh I have a problem with second NIC on your loader 0.9.5.0 and DSM 7.2.1.I have these parameters in user config:
  

.... 
 "extra_cmdline": {
    "mac1": "0011327b3c19",
    "mac2": "0011327b3c1a",
    "netif_num": "2"
....

But second NIC not change mac-address in DSM. With previous version of DSM and tcrpl 0.9.4.9 everything worked fine. What i`m doing wrong?

 

1111.JPG

 

I211AT has been a chipset that has had issues since the past.
https://github.com/pocopico/rp-ext/issues/77
https://forum.asrock.com/forum_posts.asp?TID=8542&title=x370-taichi-disable-onboard-lan


This chipset uses the igb module, and it seems that a stabilized version was accidentally used for a while.
I think we need to track the integrated module version history used at the time version 0.9.4.9 was used.


What Synology model did you build?
Are you still using H370M-ITX/ac?


0.9.4.9 refers to pocopico's original TCRP
Does 0.9.5.0 mean my Mshell?


There is too little information you need to provide in advance.

Edited by Peter Suh
Link to comment
Share on other sites
Cornelius_drebbel Newbie

Cornelius_drebbel

Posted
Posted
16 часов назад, Peter Suh сказал:

 

I211AT has been a chipset that has had issues since the past.
https://github.com/pocopico/rp-ext/issues/77
https://forum.asrock.com/forum_posts.asp?TID=8542&title=x370-taichi-disable-onboard-lan


This chipset uses the igb module, and it seems that a stabilized version was accidentally used for a while.
I think we need to track the integrated module version history used at the time version 0.9.4.9 was used.


What Synology model did you build?
Are you still using H370M-ITX/ac?


0.9.4.9 refers to pocopico's original TCRP
Does 0.9.5.0 mean my Mshell?


There is too little information you need to provide in advance.

Thanks for answer, Peter.

Yes, i`m still using H370M-ITX/ac.

Right, 0.9.4.9 it`s pocopico's original TCRP, 0.9.5.0 - your Mshell.

I try with 918+ and 3622xs+ models, not working. But today I tried build for 1621xs+ and second nic finally changed mac-address.

For now I will use this version.

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
Posted

[NOTICE]

 

How to permanently install tcz extension package on Tinycore Linux 12.0
(Firmware for the module and various utilities can be installed.
Caution, only possible if there are no dependencies for each package)

 

tce-load -iw [tcz extension package name]
Extension packages installed in this way are volatile and are not permanently installed.


Check the list of downloadable tcz extension packages at the link below.
(Detailed information about each expansion package can be found in Apps -> Cloud (remove) -> Browse in the TaskBar at the bottom of the TC,

and select remote extension -> Info tab.)


http://tinycorelinux.net/12.x/x86_64/tcz/

 


Specify the desired tcz extension package name
tczpack="firmware-broadcom_bnx2x.tcz"
tcrpdev=$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)
cd /mnt/${tcrpdev}3/cde/optional
sudo curl -kLO# http://tinycorelinux.net/12.x/x86_64/tcz/${tczpack}
sudo md5sum ${tczpack} > ${tczpack}.md5.txt
echo "${tczpack}" >> /mnt/${tcrpdev}3/cde/onboot.lst
cd ~
echo "y" |./rploader.sh backup

 


Use the command below to re-check whether the desired processing has been performed correctly.
If this is not done correctly, TCRP may not boot as usual.
 

tczpack="firmware-broadcom_bnx2x.tcz"
tcrpdev=$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)
cat /mnt/${tcrpdev}3/cde/onboot.lst | grep "${tczpack}"
ll /mnt/${tcrpdev}3/cde/optional/${tczpack}*


If there is a more convenient way to use it, I will share it later.

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...