Boot mode problem RedPill DS918+ v7.1.1-43962 (USB, Verbose)

[adrlucho]

Hello, I have installed the image tinycore-redpill-uefi.v0.9.3.0.img and everything is perfect. Connecting an hdmi from the Nas to the TV I have observed that it always boots in "Tiny Core Friend" mode. In this mode, the serial number and the mac that the system uses is the one that is generated automatically when entering the commands. In my case, I always use an original Synology serial number and to solve it I always modify the grub.cfg file with notepad++ and substitute the serial number and the Mac, being solved. In this version of Tiny Core Friend that doesn't happen and it doesn't allow me to boot with my serial number in "RedPill DS918+ v7.1.1-43962 (USB, Verbose)" mode, instead it always boots in "Tiny Core Friend" mode and I come back to start. My question is:
Is there a way to modify the boot so that it always boots like previous Tiny Core versions in "RedPill DS918+ v7.1.1-43962 (USB, Verbose)" mode so that I can make use of my original serial number? Synology and my ddns synology.me account? Could this be corrected for future updates of the Tiny Core image?

[Peter Suh]

I recommend you to try M SHELL for TCRP FRIEND, which I developed.

 

It has evolved a lot from the old TCRP and has been changed to enable loader builds using convenient MENU.

 

In the process of using this menu, there is a process to enter your SN and MAC address.

 

A user guide is also shared on Github at the link below.

 

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

[adrlucho]

Would the commands to be sent the same? Would you just have to record the new image on a 3.0 flash drive?

[Peter Suh]

Just write the same to a USB 3.0 stick.

 

Using the menu as in the guide below is sufficient.

 

https://github.com/PeterSuh-Q3/tinycore-redpill/blob/main/README.md

 

Command methods are also supported.

[painkiller895]

On 12/16/2022 at 11:10 AM, Peter Suh said:

I recommend you to try M SHELL for TCRP FRIEND, which I developed.

 

It has evolved a lot from the old TCRP and has been changed to enable loader builds using convenient MENU.

 

In the process of using this menu, there is a process to enter your SN and MAC address.

 

A user guide is also shared on Github at the link below.

 

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

please check bnx2 which does not work,

[Peter Suh]

On 12/22/2022 at 11:49 PM, painkiller895 said:

please check bnx2 which does not work,

 

The problem of TCRP not getting an IP from DHCP is

 

It may be an environmental problem rather than a program problem.

 

Is IP assigned when testing with an OS other than TCRP LINUX?

[painkiller895]

34 minutes ago, Peter Suh said:

 

The problem of TCRP not getting an IP from DHCP is

 

It may be an environmental problem rather than a program problem.

 

Is IP assigned when testing with an OS other than TCRP LINUX?

Yes, I have tested TrueNas on this machine and it works with no problem, also a live version of Ubuntu also works....

Edited December 24, 2022 by painkiller895

[painkiller895]

7 minutes ago, painkiller895 said:

Yes, I have tested TrueNas on this machine and it works with no problem, also a live version of Ubuntu also works....

So this image show a error, how do you fix this? I added a intel nic card to it. I have a ds3622 woking on this machine with ARPL loader, with your loader I'm getting this error on a bearmetal install.  On my ESXI server all works well with your loader using DS923+ on VMWare.

 

[Peter Suh]

11 hours ago, painkiller895 said:

 

 

If you look at the cmdline on your screen, only one mac1 is used, but netif_num=4 is recorded.
It should be netif_num=1 .

 

Go back to TCRP, edit the user_config.json file and rebuild the loader.
You can edit user_config.json directly with the vi editor.

You can also use the function "Edit user config fule manually" in my menu.sh. After confirming with OK, it should be saved.

[painkiller895]

On 12/24/2022 at 11:06 AM, Peter Suh said:

 

If you look at the cmdline on your screen, only one mac1 is used, but netif_num=4 is recorded.
It should be netif_num=1 .

 

Go back to TCRP, edit the user_config.json file and rebuild the loader.
You can edit user_config.json directly with the vi editor.

You can also use the function "Edit user config fule manually" in my menu.sh. After confirming with OK, it should be saved.

O.K. I rebuilt the loader as stated running RS4021xs+ it working great with the added Intel nic .  Thanks for the help...... bnx2 still no good... 

Edited December 28, 2022 by painkiller895

[painkiller895]

 

I made a new usb stick with your loader using a Dell R320, built it and I got and ip address from my DHCP server.  After building it I rebooted and was never able to install DSM RS4021 because I couldnt find it with Find.synology.com or using the assistant. 

 

After building rebooted I see ip address but could never connect...   Something is wrong with the network portion of your loader...

 

I made another usb stick using APRL Loader and all worked well....

 

 

[painkiller895]

 

ARPL worked with no problem.... no lan card was added.

[rojoone2]

21 hours ago, painkiller895 said:

 

ARPL worked with no problem.... no lan card was added.

 

Do you get the power supply warning on this build? I am curious if @fbelavenuto figured out a fix...  I built a RS4021xs+ with the original M Shell on a Dell R620 that has two power supplies, but I get the warning. I haven't tried rebuilding with a new method.

Edited December 30, 2022 by rojoone2

[painkiller895]

I'll get back to you on this regarding the R320,  My R410 has only 1 power supply and I get that power supply error.  Would be nice to turn it off...

 

[painkiller895]

Same problem, was this ever fixed ?