Jump to content
XPEnology Community

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal


Peter Suh

Recommended Posts

10 hours ago, haldi said:

Okay...

One more time please.

If you want to update a Working 7.0.1 Bootloader to 7.1 You need to build a new Bootloader, right?

But you don't need to generate a new Serial or stuff?

 

going by the 3615...



 [DS3615xs]
./rploader.sh update now
./rploader.sh fullupgrade now

./rploader.sh build bromolow-7.0.1-42218

./rploader.sh clean now

./rploader.sh build bromolow-7.1.0-42661


./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now; 

does it need the FullUpgrade after the update?

the Build Bromwlow 7.0.1 was already done last time so no more need for that?

So why does it need a clean before building the new 7.1?

and the last line with the remove stuff is to keep the usb stick clean right?

@Peter Suh correct me if I'm wrong, fullupgrade replaces the user_config.json, so his @haldi 7.0.1 serial/mac will be reset in user_config.json.. it should be stored in tc/home/old or you could simply copy it to local storage before doing any 7.1 loader building, and verify after fullupgrade that user_config.json is correct on tc/home and proceed. It probably a good idea to verify user config just before build 7.1 build to be 100% sure anyway, but I am overly cautious.

 

edit: to copy user config you can use winscp in windows and I think peter suggests portx for mac. (not sure about mac since I am windows, winscp for sure and is free download just google it)

Edited by phone guy
Link to comment
Share on other sites

51 minutes ago, phone guy said:

@nabito verify in bios, your sata is set to ahci (not raid or other options) and if you have a hot swap option, set to on/enable.

 

dont mess the 920 yet, its not quite ready yet. do as @gadreel suggests, try 3615 or 3617

I tried to change SATA mode from AHCI to IDE but still same error 

Edited by nabito
Link to comment
Share on other sites

it should be ahci. if you successfully booting to loader, and see ip:5000 and it says no disc detected in other model besides 920/1621 then your sata drivers are maybe not loading.  i know you can check from tc with lspci -nnqk (I think is the right options) and it will show sata controller (and all pci) and what driver is loaded if any, should say ahci

(short snip from one my boxes, just to show you)

 

root@DS:~# lspci -nnqk
0000:00:12.0 SATA controller [0106]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller [8086:5ae3] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
        Kernel driver in use: ahci

 

Edited by phone guy
Link to comment
Share on other sites

7 hours ago, Peter Suh said:

The last modification I asked @pocopico was not completed yet

Deploy to use this shell script instead.

This is a shell script that performs 15 first guided "Tinycore DSM 7.1 Build" commands at once.

For the instructions on how to use the attached file, you can copy this file into TC LINUX's /home/tc and do it as below.


./my.sh DS918+

./my.sh DS3617xs

./my.sh DS3615xs

./my.sh DS3622xs+

./my.sh DVA3221

./my.sh DS920+

./my.sh DS1621+
 

 

on tc Linux

 

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

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

your script has included with virtio drivers or not? if not, would u please add it?

Link to comment
Share on other sites

7 hours ago, nabito said:

After few I tried to re install using Ds920+, I finally see the IP. But again, it show no drive detected. 

Last time I tried it Ds918+, I can't find the IP

image.thumb.png.6c09384689a8f0be93fb0ac73e7f2447.png

 

For users who are new to XPENOLOGY, ds920+ using device-tree-compiler (dtc) may have difficulty.

And in TC, sata port auto-mapping has not been stabilized yet.
Manual mapping is possible, but this is more difficult.

 

It's amazing that 2nd generation Intel can find IP using ds920+.
Unlike JUN loader, is it possible to do red-pill?


I recommends using the most stable ds3622xs+ for platforms that can be sufficient even in the 2nd generation of Intel.
And can Hot Plug be turned on in the BIOS?
This is one of the ways to make the drive recognized while taking advantage of the SataportMap figures more flexible.

 

Link to comment
Share on other sites

6 hours ago, phone guy said:

@Peter Suh correct me if I'm wrong, fullupgrade replaces the user_config.json, so his @haldi 7.0.1 serial/mac will be reset in user_config.json.. it should be stored in tc/home/old or you could simply copy it to local storage before doing any 7.1 loader building, and verify after fullupgrade that user_config.json is correct on tc/home and proceed. It probably a good idea to verify user config just before build 7.1 build to be 100% sure anyway, but I am overly cautious.

 

edit: to copy user config you can use winscp in windows and I think peter suggests portx for mac. (not sure about mac since I am windows, winscp for sure and is free download just google it)

 

I overlooked the phenomenon that user_config.json is overwritten in the full upgrade process of tc.

If the content is not much different from the user_config.json in 0.4.6 img, I suddenly think that I should have let him receive it again.

Because of this phenomenon, it seems that the user_config file that entered old needs to be restored again. I was like, "m.sh / my.sh" will consider accepting this part as well.

Please restore it with the command below.
cp /home/tc/old/user_config.json /home/tc

  • Like 1
Link to comment
Share on other sites

5 hours ago, nabito said:

I tried to change SATA mode from AHCI to IDE but still same error 

 

AHCI should be maintained.
I am not talking about the transition between AHCI and IDE.
The Hot Plug or Hot Swap option should be found.
What is the model of your B75 main board?

Link to comment
Share on other sites

22 minutes ago, Peter Suh said:

 

There is no part of this script that the user adds the ext that they need individually.
If necessary, modify the above file directly and add a command.

it has working acpi ext for sata harddrive & network interface ? 

 

Link to comment
Share on other sites

Quote


tc@box:~$ lspci -nnqk
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Fami                             ly DRAM Controller [8086:0100] (rev 09)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000]
        Kernel driver in use: snb_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5007]
        Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:1c3a]
        Kernel driver in use: mei_me
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5006]
        Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:a002]
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
        Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4)
        Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5006]
        Kernel driver in use: ehci-pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a4)
00:1f.0 ISA bridge [0601]: Intel Corporation B75 Express Chipset LPC Controller [8086:1e49] (rev 04)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
        Kernel driver in use: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:b005]
        Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller [8086:1e22] (rev 04)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
        Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000]
        Kernel driver in use: r8169
tc@box:~$ ^C
tc@box:~$
tc@box:~$ tc@box:~$ lspci -nnqk
-sh: tc@box:~$: not found
tc@box:~$ 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Fami
          ly DRAM Controller [8086:0100] (rev 09)
-sh: syntax error: unexpected "("
tc@box:~$         Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000]
-sh: Subsystem:: not found
tc@box:~$         Kernel driver in use: snb_uncore
-sh: Kernel: not found
tc@box:~$ 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family In
tegrated Graphics Controller [8086:0102] (rev 09)
-sh: syntax error: unexpected "("
tc@box:~$         Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
-sh: Subsystem:: not found
tc@box:~$ 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host
Controller [8086:1e31] (rev 04)
-sh: syntax error: unexpected "("
tc@box:~$         Subsystem: Gigabyte Technology Co., Ltd Device [1458:5007]
-sh: Subsystem:: not found
tc@box:~$         Kernel driver in use: xhci_hcd
-sh: Kernel: not found
tc@box:~$ 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C216 Chipset Family MEI Control
ler #1 [8086:1e3a] (rev 04)
-sh: 00:16.0: not found
tc@box:~$         Subsystem: Gigabyte Technology Co., Ltd Device [1458:1c3a]
-sh: Subsystem:: not found
tc@box:~$         Kernel driver in use: mei_me
-sh: Kernel: not found
tc@box:~$ 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Con
troller #2 [8086:1e2d] (rev 04)
-sh: 00:1a.0: not found
tc@box:~$         Subsystem: Gigabyte Technology Co., Ltd Device [1458:5006]
-sh: Subsystem:: not found
tc@box:~$         Kernel driver in use: ehci-pci
-sh: Kernel: not found
tc@box:~$ 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio C
ontroller [8086:1e20] (rev 04)
-sh: syntax error: unexpected "("
tc@box:~$         Subsystem: Gigabyte Technology Co., Ltd Device [1458:a002]
-sh: Subsystem:: not found
tc@box:~$ 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 [
8086:1e10] (rev c4)
-sh: syntax error: unexpected "("
tc@box:~$         Kernel driver in use: pcieport
-sh: Kernel: not found
tc@box:~$ 00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root P
ort 5 [8086:1e18] (rev c4)
-sh: syntax error: unexpected "("
tc@box:~$         Kernel driver in use: pcieport
-sh: Kernel: not found
tc@box:~$ 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Con
troller #1 [8086:1e26] (rev 04)
-sh: 00:1d.0: not found
tc@box:~$         Subsystem: Gigabyte Technology Co., Ltd Device [1458:5006]
-sh: Subsystem:: not found
tc@box:~$         Kernel driver in use: ehci-pci
-sh: Kernel: not found
tc@box:~$ 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a4)
-sh: syntax error: unexpected "("
tc@box:~$ 00:1f.0 ISA bridge [0601]: Intel Corporation B75 Express Chipset LPC Controller [8086:1e49] (rev 04
)
-sh: syntax error: unexpected "("
tc@box:~$         Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
-sh: Subsystem:: not found
tc@box:~$         Kernel driver in use: lpc_ich
-sh: Kernel: not found
tc@box:~$ 00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA C
ontroller [AHCI mode] [8086:1e02] (rev 04)
-sh: syntax error: unexpected "("
tc@box:~$         Subsystem: Gigabyte Technology Co., Ltd Device [1458:b005]
-sh: Subsystem:: not found
tc@box:~$         Kernel driver in use: ahci
-sh: Kernel: not found
tc@box:~$ 00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller [8086:1e22] (
rev 04)
-sh: syntax error: unexpected "("
tc@box:~$         Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
-sh: Subsystem:: not found
tc@box:~$ 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express G
igabit Ethernet Controller [10ec:8168] (rev 06)
-sh: syntax error: unexpected "("
tc@box:~$         Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000]
-sh: Subsystem:: not found
tc@box:~$         Kernel driver in use: r8169
 

 This is what I got when type the command lspci -nnqk,

and below is my bios setting. I can't found any hot plug option also. 

I'm using Gigabyte B75 D3H with the latest fimware.

image.thumb.png.a6362ab5e34c632020e476a621d22faf.png

 

UPDATE: I tried change to Ds3622xs + and now this happen. I tried to change my HHD from port 1 to port 3, run command ./rploader.sh satamap now but still same error.

 

image.thumb.png.5e868b843d8baa9b6ed6278b3590b142.png

 

Edited by nabito
Link to comment
Share on other sites

35 minutes ago, phone guy said:

@pocopico@Peter Suh am I reading your script correctly, you can just build a 7.1.0-42661 loader alone, without TSU and first building 7.0.1-42218?

update

fullupgrade

serialgen/usbid/satamap

build

clean

reboot?

 

The building process in 7.0.1-42218 is omitted
Inside the 7.1.0-42661 building, the TSU is still operating internally.
You will be able to watch the process of downloading the pat file for 7.0.1-42218.

Link to comment
Share on other sites

48 minutes ago, nabito said:

 This is what I got when type the command lspci -nnqk,

and below is my bios setting. I can't found any hot plug option also. 

I'm using Gigabyte B75 D3H with the latest fimware.

image.thumb.png.a6362ab5e34c632020e476a621d22faf.png

 

 

According to this manual, hot plug is mentioned twice
I don't know if it means that the hot plug will work on its own even if it is kept as AHCI.

 

https://download1.gigabyte.com/Files/Manual/mb_manual_ga-b75m-d3h_e.pdf

 

First, modify the user_config.json file directly to SataportMap=1
Fix it with , physically install the HDD only in the Sata 1 port and proceed with the installation of ds3622xs+.

 

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

16 hours ago, Peter Suh said:

The last modification I asked @pocopico was not completed yet

Deploy to use this shell script instead.

This is a shell script that performs 15 first guided "Tinycore DSM 7.1 Build" commands at once.

For the instructions on how to use the attached file, you can copy this file into TC LINUX's /home/tc and do it as below.


./m.sh DS918+

./m.sh DS3617xs

./m.sh DS3615xs

./m.sh DS3622xs+

./m.sh DVA3221

./m.sh DS920+

./m.sh DS1621+


Upload it to TC Linux with SCP

[MAC OS]
rm ./.ssh/known_hosts
scp ~/Downloads/m.sh.gz tc@192.168.1.10:/home/tc

[WINDOWS]
scp [download path]/m.sh.gz tc@192.168.1.10:/home/tc


on tc Linux

tar -zxvf m.sh.gz

You can use the gz file after compressing it.

 

 

I made one more for those who don't even want to type in 'y'.

my.sh.gz

The usage of my.sh is the same.^^

 

 

m.sh.gz 701 B · 12 downloads

my.sh.gz 707 B · 5 downloads

 

Attached here are the old versions of "my.sh.tar" and "my.sh.tar".
Always use the latest version on github with wget.

Link to comment
Share on other sites

19 minutes ago, Peter Suh said:

 

According to this manual, hot plug is mentioned twice
I don't know if it means that the hot plug will work on its own even if it is kept as AHCI.

 

https://download1.gigabyte.com/Files/Manual/mb_manual_ga-b75m-d3h_e.pdf

 

First, modify the user_config.json file directly to SataportMap=1
Fix it with , physically install the HDD only in the Sata 1 port and proceed with the installation of ds3622xs+.

 

It's my stupid fault to not read the user manual, after turn on hot plug in ATA port information * I don't know why they need to hide it*, I can boot and install DSM, 

thank you so much and sorry for posting too much

  • Like 1
Link to comment
Share on other sites

8 hours ago, Peter Suh said:

 

I overlooked the phenomenon that user_config.json is overwritten in the full upgrade process of tc.

If the content is not much different from the user_config.json in 0.4.6 img, I suddenly think that I should have let him receive it again.

Because of this phenomenon, it seems that the user_config file that entered old needs to be restored again. I was like, "m.sh / my.sh" will consider accepting this part as well.

Please restore it with the command below.
cp /home/tc/old/user_config.json /home/tc

 

A function was added to ask if you want to restore your own "user_config.json" from the old directory.

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

Thank you so much for this guide!  I tried it three times without success, before properly reading it and realising my silly mistake!

 

On 4/13/2022 at 7:04 AM, Peter Suh said:

After 7.0.1 build, check if the custom-module -> /mnt/sdb3/auxfiles directory is created well with the ll command.

 

To anyone else struggling, PLEASE make sure you do this after doing the 7.0.1 build.  I found that the first time running the build didn't actually create this redirect in 100% of cases - okay, so that was twice to my knowledge and most likely three times prior to that, but I digress.  Running the build a second time did the trick.

Link to comment
Share on other sites

15 minutes ago, leopold said:

Thank you so much for this guide!  I tried it three times without success, before properly reading it and realising my silly mistake!

 

 

To anyone else struggling, PLEASE make sure you do this after doing the 7.0.1 build.  I found that the first time running the build didn't actually create this redirect in 100% of cases - okay, so that was twice to my knowledge and most likely three times prior to that, but I digress.  Running the build a second time did the trick.

I'm lucky I guess, I have done the tsu7.1 build 3 or 4 times and never checked, as it always worked. I have not used @Peter Suh m.sh or my.sh script yet. I just ordered some server stuff (mobo, cpu, ram, hba, etc) to build (for me) a beast nas so I will use his script next build.  I may make a proxmox machine just I can test future building methods before deploying on baremetal.

  • Like 1
Link to comment
Share on other sites

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

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

 

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

 

./myv.sh DS918+

./myv.sh DS3617xs

./myv.sh DS3615xs

./myv.sh DS3622xs+

./myv.sh DVA3221

./myv.sh DS920+

./myv.sh DS1621+
 

 

In TC Linux, you can download and decompress as below and use it in /home/tc.

 

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

 

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

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

19 minutes ago, pocopico said:

There was always a plan to use the dialog GUI for interactive actions. You can test it by running ./rploader.sh interactive <platform> 

 

If you could continue the work on that script it would be better i think. 

I tried the interactive script after seeing you mention it in another thread. the best part was being able to see the available ext for adding. otherwise (honestly) it seemed like it was kind of abandoned and didnt get a lot of thought. First thing should change is the background color, make it black easier to read. ;)

But a current interactive list of available modules, drivers, etc... that would be a welcomed step in the process. I dont remember when I tried it if that was part of the interactive shell? I think it was?  ANYWAY! Thanks to all who contribute to this project and these forums.

Edited by phone guy
Link to comment
Share on other sites

7 minutes ago, phone guy said:

I tried the interactive script after seeing you mention it in another thread. the best part was being able to see the available ext for adding. otherwise (honestly) it seemed like it was kind of abandoned and didnt get a lot of thought. First thing should change is the background color, make it black easier to read. ;)

But a current interactive list of available modules, drivers, etc... that would be a welcomed step in the process. I dont remember when I tried it if that was part of the interactive shell? I think it was?  ANYWAY! Thanks to all who contribute to this project and these forums.

 

Yes i've started that to see how it goes, then decided to focus on the rploader script, the extensions, the housekeeping of the repos etc. 

 

If anyone has the skills to continue the work,  then it would be great. 

  • Like 1
Link to comment
Share on other sites

Is this guide for the upgrade from 6.2? Previously there were 3 guides, now there're 2.

A remarkable difference was in this line:

./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now;

 

If I modify config (USB, S/N), should i rebuild or just save the file? I'm stuck at "Booting the kernel" with IP unavailable. [20min later]  Oh I got it by connecting back the bond. Likely advice - if you have bond of 2 cables, it won't work in Tiny OS, and vice versa in DSM. (Update: it seems that finally 1 cable worked but must be cable Nr.1). Also need to remove other USB devices during the setup.

 

I wonder if the bootloader could display something meaningful, like system info if not terminal:) Really sad to have a deaf barebone :)

Edited by nadiva
Link to comment
Share on other sites

UPDATE:   issue solved. It just takes a long while. Just wait for about 15 min. and the installation will finish :)

 

Getting the bootloader up and running was no big deal... everything seems working fine. However when installing DSM the installations get stuck at 55% every time.
 

i6xEW6S.jpg

 

kMxLMQm.jpg

 

anyone know what's causing this? Please let me know.

 

Thanks! 

 

Edited by cealis88
update / solution
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...