TinyCore RedPill Loader (TCRP)

[p3t3]

ds918p_42621 and ds920p_42621's exts are added?

[Peter Suh]

3 minutes ago, p3t3 said:

ds918p_42621 and ds920p_42621's exts are added?

 

Go to github's ext here and find out if you have the driver you want

 

https://github.com/pocopico/rp-ext

[titoum]

9 minutes ago, Peter Suh said:

So, I record the USB again and perform it as below.

 

./rploader.sh update now

./rploader.sh fullupgrade now

./rploader.sh clean now

./rploader.sh download broadwellnk-7.0.1-42218

./rploader.sh ext broadwellnk-7.0.1-42218 add https://github.com/jumkey/redpill-load/raw/develop/redpill-misc/rpext-index.json

./rploader.sh build broadwellnk-7.0.1-42218

./rploader.sh build broadwellnk-7.1.0-42621

 

same... i dont know what i am doing wrong

 

i was able to build 7.0.1 no problemo then i switched to 7.1

i got this first error:

Downloading pat file from URL : ds.pat
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host: ds.pat
Failed to download PAT file //mnt/sdf3/auxfiles/DS3622xs+_42621.pat from ds.pat

 

so i have copied the pat file directly in the cache:

/bin/syno_extract_system_patch: /usr/local/lib/libcurl.so.4: no version information available (required by /bin/syno_extract_system_patch)
Executed succesfully
Processing pat file  file
Checking for cached pat file
Found tinycore cache folder, linking to home/tc/custom-module
Found locally cached pat file /home/tc/custom-module/DSM_DS3622xs+_42621.pat
./rploader.sh: line 148: [: =: unary operator expected
./rploader.sh: line 152: [: =: unary operator expected
Something went wrong, please check cache files

 

which then fallback to other issue about testarchive.

 

time to cook  nothing urgent. i just like to dig into this.

[Peter Suh]

4 minutes ago, titoum said:

 

same... i dont know what i am doing wrong

 

i was able to build 7.0.1 no problemo then i switched to 7.1

i got this first error:

Downloading pat file from URL : ds.pat
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host: ds.pat
Failed to download PAT file //mnt/sdf3/auxfiles/DS3622xs+_42621.pat from ds.pat

 

so i have copied the pat file directly in the cache:

/bin/syno_extract_system_patch: /usr/local/lib/libcurl.so.4: no version information available (required by /bin/syno_extract_system_patch)
Executed succesfully
Processing pat file  file
Checking for cached pat file
Found tinycore cache folder, linking to home/tc/custom-module
Found locally cached pat file /home/tc/custom-module/DSM_DS3622xs+_42621.pat
./rploader.sh: line 148: [: =: unary operator expected
./rploader.sh: line 152: [: =: unary operator expected
Something went wrong, please check cache files

 

which then fallback to other issue about testarchive.

 

time to cook  nothing urgent. i just like to dig into this.

 

 

This is my last log when I built 7.1.0
At the end, the URL appears undefined.

 

 

 

[pocopico]

1 hour ago, titoum said:

super work as usual.

 

can you just give a hint how to add redpil misc extension if possible? i will try to do a build on bromllow after that
thx

 

I've upgraded and finally made use of the add_extension key of @haydibe, so now extentions are automatically added and parsed,  in case they are listed in the add_extensions part of the custom_config.json. 

 

Do a fullupgrade to download latest custom_config.json 

 

 

[Peter Suh]

@pocopico

 

The 7.0.1 build was successful, as shown in the log
Copy to the last cache directory and see something wrong.
Is it about authority?

 

 

And, when I proceed with the 7.1 build,
It seems that the pat file of the above cache directory cannot be found as below.

 

[pocopico]

14 minutes ago, Peter Suh said:

 

 

This is my last log when I built 7.1.0
At the end, the URL appears undefined.

 

 

 

 

You are missing the config file from the repo , can you check the following ?

 

customer_config.json contains valid repo

did you clean ? did you download ?

[pocopico]

Just now, Peter Suh said:

@pocopico

 

The 7.0.1 build was successful, as shown in the log
Copy to the last cache directory and see something wrong.
Is it about authority?

 

 

And, when I proceed with the 7.1 build,
It seems that the pat file of the above cache directory cannot be found as below.

 

 

 

Hm , i need to write more checks... please verify my msg above ^^^

[Peter Suh]

1 minute ago, pocopico said:

 

 

Hm , i need to write more checks... please verify my msg above ^^^

 

 

As you can see the file list below, all files have been updated to the latest files through fullupgrade.
The custom_config.json file is fine.

 

[Peter Suh]

@pocopico

 

I'm sorry. It's really time to go to bed.
I really appreciate your hard work.

[titoum]

25 minutes ago, Peter Suh said:

@pocopico

 

The 7.0.1 build was successful, as shown in the log
Copy to the last cache directory and see something wrong.
Is it about authority?

 

 

And, when I proceed with the 7.1 build,
It seems that the pat file of the above cache directory cannot be found as below.

 

exact same issue i faced

 

i did exact steps advise by pocopico and then redo steps from peter.

 

imo something is wrong with testarchive() which invalidate a couple of other steps.

[bc0421]

On 4/3/2022 at 8:55 PM, alirz1 said:

ok so after bumping the vm memory to 2GB it seems to have worked, the loader was built. Now when i reboot and choose the SATA boot option from the menu, it just sits at

"Decompressin linux, ...Parsing ELF...Done"

"Booting Kernel".

 

At this point, i cant seem to find the synology in synology assistant, so im not sure if its picking up an IP or not? Are we able to see any logs via some serial console etc? I know in the past with JUN's loader we wouldnt be able to see anything in the vm console after the kernel booting message..

Could this be due to possible incorrect sataport map etc? i have currently set it to 1 and diskid map to "0A00".

 

Note, as mentioned previosuly, this is all being setup in vmware working station. where, duting the tinycore uild process i have an IP etc..

This was they exact same problem I was experiencing. As i mentioned earlier you need to change the NIC driver from e1000 to vmxnet3. Yes, the VM will boot into TinyCore witjh the default NIC driver but once you build the DSM and try to boot into it via SATA it will no longer acqurie an IP address. You'll need to build the DSM again after changing the NIC driver so it downloads the correct extension for the vmxnet3. Give it a shot, worked for me.

[pocopico]

2 hours ago, titoum said:

exact same issue i faced

 

i did exact steps advise by pocopico and then redo steps from peter.

 

imo something is wrong with testarchive() which invalidate a couple of other steps.

 

Fixed several issues and tested. Please do a fullupgrade and test again.

[Dvalin21]

This is nice guide how to flash with all required tools. 
 
https://techmattr.wordpress.com/2016/04/11/updated-sas-hba-crossflashing-or-flashing-to-it-mode-dell-perc-h200-and-h310/
 
and movie [emoji4]
 

BTW thanks for the link. I was able to flash my card

Sent from my SM-T878U using Tapatalk

[RacerX]

I id a little vanilla test with DD3615  bromolow-7.0.1-2218

 

I'm getting this a the end of the build

 

Found /home/tc/redpill-load/cache/ds3615xs_42218.pat, copying to cache directory : /mnt                 /sdd3/auxfiles
cp: failed to preserve ownership for '/mnt/sdd3/auxfiles/ds3615xs_42218.pat': Operation                  not permitted

 

 

Edited April 5, 2022 by RacerX

[pocopico]

Added and have tested an on the fly (during build) patching process for jumkeys model.dtb. Its works regardless of the DSM version if its added in the add_extensions in custom_config.json file.

 

More testers please  

[pocopico]

2 minutes ago, RacerX said:

I id a little vanilla test with DD3615  bromolow-7.0.1-2218

 

I'm getting this a the end of the build

 

Found /home/tc/redpill-load/cache/ds3615xs_42218.pat, copying to cache directory : /mnt                 /sdd3/auxfiles
cp: failed to preserve ownership for '/mnt/sdd3/auxfiles/ds3615xs_42218.pat': Operation                  not permitted

sudo ./rploader.sh build bromolow-7.0.1-2218

 

 

Yes Its a cosmetic problem, its not an issue. FAT does not know anything about unix permissions ...

 

Do you mind also testing 7.1.0 for bromolow ? 

Edited April 5, 2022 by pocopico

[aliens]

Hi all,
HELP me!
 i tried to perform dsm 7 baremetal UEFI on old xpenology 6.0. 
I have a problem on installation of DSM, i find the xpenology with "find.synology.com" but after accept eula the system perform HDDS error.
I have tested different combination of "sataportmap"/"diskidxmap" on user_config, but the result is different hdds number error means.
With  automap i have:"SataPortMap": "512","DiskIdxMap": "000C". 
On mainboard her have 3 port SATA and onather pci with 6 port SATA.
I try:"SataPortMap": "36","DiskIdxMap": "0000" the resuilt is idem.

[pocopico]

6 minutes ago, aliens said:

Hi all,
HELP me!
 i tried to perform dsm 7 baremetal UEFI on old xpenology 6.0. 
I have a problem on installation of DSM, i find the xpenology with "find.synology.com" but after accept eula the system perform HDDS error.
I have tested different combination of "sataportmap"/"diskidxmap" on user_config, but the result is different hdds number error means.
With  automap i have:"SataPortMap": "512","DiskIdxMap": "000C". 
On mainboard her have 3 port SATA and onather pci with 6 port SATA.
I try:"SataPortMap": "36","DiskIdxMap": "0000" the resuilt is idem.

 

Dont worry, its totally fixable :

 

please provide the following output from tinycore :

 

tce-load -iw scsi-5.10.3-tinycore64.tcz
lsscsi -Hv

lspci -nnq 

 

 

[coint_cho]

Updated rploader to the latest version and cleaned everything before building again and currently stuck at this phase.

Enviroment proxmox, stuck at here twice after updating from a fresh image of tc.

[coint_cho]

2 minutes ago, coint_cho said:

Updated rploader to the latest version and cleaned everything before building again and currently stuck at this phase.

Enviroment proxmox, stuck at here twice after updating from a fresh image of tc.

And I'm pretty sure all my files is still there..

[pocopico]

Can you run a df -h /mnt/sd* ? 

 

 

11 minutes ago, coint_cho said:

And I'm pretty sure all my files is still there..

 

[alirz1]

5 hours ago, bc0421 said:

This was they exact same problem I was experiencing. As i mentioned earlier you need to change the NIC driver from e1000 to vmxnet3. Yes, the VM will boot into TinyCore witjh the default NIC driver but once you build the DSM and try to boot into it via SATA it will no longer acqurie an IP address. You'll need to build the DSM again after changing the NIC driver so it downloads the correct extension for the vmxnet3. Give it a shot, worked for me.

 

Thanks. But I don't see an option in VMware workstation pro to change nic type. Fr vmxnet to e1000.

 

 

[pocopico]

14 minutes ago, alirz1 said:

 

Thanks. But I don't see an option in VMware workstation pro to change nic type. Fr vmxnet to e1000.

 

 

you can add manually e1000 extension. There is a bug that I cannot solve in the auto detection for e1000

[bc0421]

8 minutes ago, alirz1 said:

 

Thanks. But I don't see an option in VMware workstation pro to change nic type. Fr vmxnet to e1000.

 

 

You need to modify the VMX file which is in the directory your VM files are stored. Find the ethernet0.virtualDev entry  and change it from e1000 to vmxnet3.    (ethernet0.virtualDev = "vmxnet3")