Jump to content
XPEnology Community

Automated RedPill Loader (ARPL)


fbelavenuto

Recommended Posts

12 hours ago, apriliars3 said:

I tested DVA1622 on baremetal with Lenovo ThinkCentre Edge 71 Intel i3 2120

 

I tesst DVA1622 with intel i7-3770, but it can not boot into DSM. How can you give me some experiences?

Edited by bluecatus
Link to comment
Share on other sites

I have selected DS 918+ and used a Lenovo X260 laptop. Install process works fine until I am asked for the .pat file used for installation. Which pat file should we use? Latest synology_apollolake_918+.pat for DSM 7.1-42661-3 is not working, I get the error that the file is corrupted.

Thank you for your amazing work!

And I am answering myself: the working pat is DSM_DS918+_42661.pat

Can we update to the latest version?

Edited by raduci
Link to comment
Share on other sites

Dear fbelavenuto,

Great work so far. Finally managed to get this up and running (bare metal) on an old HP IPM87-MP Mainboard(i5 Haswell, 8 GB RAM).
One thing keeps bugging me though ...
Generating of serial number doesnt seem to work properly (DS3615xs). Unable to register Synology Account (which seems to be nescessary to get VirtualMachineManager working)
Any advice / hint /tipp appreciated ;-)

  • Thanks 1
Link to comment
Share on other sites

@fbelavenuto  I want to ask one thing that might trigger a number of issues at some point in the future. 

 

Lets say, in a future upgrade, syno decides to upgrade kernel to a version other than the current, what will be the effect ?

 

I guess a recreation of the loader containing all the addons with newer compiled modules will solve the issues. Are all user setttings somehow backed up in the configuration file ? 

 

Edit: I see the addons are progressing fast ! Good ! 

Edited by pocopico
  • Like 2
  • Thanks 1
Link to comment
Share on other sites

@fbelavenuto Excuse me if that has already been implemented, You have to find a way to overcome a certain limitation of buildroot. The update of the local files. Can you use a file stored in p3 and extract that file into a location ? e.g. /opt/arpl ? 

 

That way you will not have to create the buildroot each time but just use the extra file in p3. You can then update that single file and have the latest version. You could also fetch that update file directly from github ?

 

 

 

Edited by pocopico
Link to comment
Share on other sites

6 minutes ago, sliders said:

hello, i have a problem I'm looking for help thank you

 

Capture d’écran 2022-07-07 201958.png

 

Is update server is masked in your /etc/synoinfo.conf ?

 

# grep examp /etc/synoinfo.conf

 

myds_region_api_base_url="https://example.com"
rss_server="http://example.com/null.xml"
rss_server_ssl="https://example.com/null.xml"
rss_server_v2="https://example.com/autoupdate/v2/getList"
security_version_server="https://example.com/smallupdate"
small_info_path="https://example.com/null"
update_server="http://example.com/"
update_server_ssl="https//example.com/"
updateurl="http://example.com/"

 

or /etc/hosts ?

 

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

7 hours ago, apriliars3 said:

@fbelavenuto Is it possible to get a loader.img with your arpl like as tinycore? I want to test my pendrive with other pcs on VMWare, because I can´t detect disks with tinycore.

 

Your arpl I think no works well with VMWare, follow test with the last alphas.

Yes, today I and @ikky_phoenix did several tests in vmware and discovered several bugs, so I'll pass a link with a new image for tests.

Link to comment
Share on other sites

6 hours ago, pocopico said:

@fbelavenuto  I want to ask one thing that might trigger a number of issues at some point in the future. 

 

Lets say, in a future upgrade, syno decides to upgrade kernel to a version other than the current, what will be the effect ?

 

I guess a recreation of the loader containing all the addons with newer compiled modules will solve the issues. Are all user setttings somehow backed up in the configuration file ? 

 

Edit: I see the addons are progressing fast ! Good ! 

I'm already testing new options to update online without having to redo the image.

I created scripts to automate the compilation of modules and recreate the addons, I even made it work in github actions, so it will be fast.

Link to comment
Share on other sites

3 hours ago, sliders said:

hello, i have a problem I'm looking for help thank you

 

Capture d’écran 2022-07-07 201958.png

Loader patches block access to updates, through /etc/synoinfo.conf as well as /etc/hosts.

I recommend keeping it that way, as it is not possible to guarantee that a future update will work, manually updating after testing is the best way.

  • Thanks 1
Link to comment
Share on other sites

3 hours ago, pocopico said:

@fbelavenuto Excuse me if that has already been implemented, You have to find a way to overcome a certain limitation of buildroot. The update of the local files. Can you use a file stored in p3 and extract that file into a location ? e.g. /opt/arpl ? 

 

That way you will not have to create the buildroot each time but just use the extra file in p3. You can then update that single file and have the latest version. You could also fetch that update file directly from github ?

 

 

 

Thanks pocopico, I studied the best way to update, this idea of yours crossed my mind, but I preferred to implement the rootfs update directly. There is already in the latest alpha images the upgrade option, which works for addons and LKMs and will work for arpl after releasing a non-pre-release

  • Like 1
Link to comment
Share on other sites

51 minutes ago, fbelavenuto said:

Try add more memory to your virtual machine

I have 2GB

 

47 minutes ago, fbelavenuto said:

Yes, today I and @ikky_phoenix did several tests in vmware and discovered several bugs, so I'll pass a link with a new image for tests.

v0.1-alpha7 Fix satadom (VMWare) only 2 assets (source code)

 

How can change mac? /mnt/p1/user-config.yml haven´t mac, only serial number. /mnt/p1/grub/grub.cfg haven´t mac.

 

Need I build other time to change mac for use other serial number and mac for activating Advanced Media Extensions and login with my Synology Account?

 

Edited by apriliars3
Link to comment
Share on other sites

55 minutes ago, apriliars3 said:

I have 2GB

 

v0.1-alpha7 Fix satadom (VMWare) only 2 assets (source code)

 

How can change mac? /mnt/p1/user-config.yml haven´t mac, only serial number. /mnt/p1/grub/grub.cfg haven´t mac.

 

Need I build other time to change mac for use other serial number and mac for activating Advanced Media Extensions and login with my Synology Account?

 

 

Github actions is still running, so it will generate the images.

 

To force a specific MAC, go to "cmdline menu", "Add/edit a cmdline item", enter "netif_num" as name, enter "1" as value. Repeat the process to add "mac1" with MAC value without symbols (ex: 001122334455).

No need to rebuild loader, add cmdline items and boot directly.

 

  • Thanks 1
Link to comment
Share on other sites

13 hours ago, fbelavenuto said:

 

Github actions is still running, so it will generate the images.

 

To force a specific MAC, go to "cmdline menu", "Add/edit a cmdline item", enter "netif_num" as name, enter "1" as value. Repeat the process to add "mac1" with MAC value without symbols (ex: 001122334455).

No need to rebuild loader, add cmdline items and boot directly.

 

Try now:

 

https://github.com/fbelavenuto/arpl/releases/download/v0.1-alpha7/arpl-0.1-alpha7.vmdk.zip

 

Link to comment
Share on other sites

@fbelavenuto FYI, A condition i fell into on my test system.

 

I configured the loader for DVA1622, I installed 42661 and updated to U3. I then went into configure the loader and recreated my loader. I then ended having a junior does not match root issue, cause my junior is 7.1 and root is 7.1 U3. Any ideas how to prevent that from happening ?

 

Edit : The recover button on DSM Gui seems to fix the issue , great :)

 

Also could we somehow cache the pat files that we use so that we dont need to download them again during build ? 

 

 

Edited by pocopico
Link to comment
Share on other sites

9 minutes ago, pocopico said:

@fbelavenuto FYI, A condition i fell into on my test system.

 

I configured the loader for DVA1622, I installed 42661 and updated to U3. I then went into configure the loader and recreated my loader. I then ended having a junior does not match root issue, cause my junior is 7.1 and root is 7.1 U3. Any ideas how to prevent that from happening ?

 

Edit : The recover button on DSM Gui seems to fix the issue , great :)

 

Also could we somehow cache the pat files that we use so that we dont need to download them again during build ? 

 

 

When you recreate the loader after a small update it causes this problem! I still don't know how to avoid this.

About the cache, if partition 3 is bigger than 2GB the loader uses it to save the .pats. If you burn to a big pendrive, the loader alone increases the third partition and already uses it.

Here at home I use proxmox, I increase the size of the image "arpl.img" to 4GB with a script, so in proxmox I can use the disk as cache.

  • Like 2
Link to comment
Share on other sites

25 minutes ago, fbelavenuto said:

When you recreate the loader after a small update it causes this problem! I still don't know how to avoid this.

About the cache, if partition 3 is bigger than 2GB the loader uses it to save the .pats. If you burn to a big pendrive, the loader alone increases the third partition and already uses it.

Here at home I use proxmox, I increase the size of the image "arpl.img" to 4GB with a script, so in proxmox I can use the disk as cache.

 

@fbelavenuto On VMware, when i increase the disk size 4GB , LKM does not pick it up as synoboot device. The issue goes down to this ->  https://github.com/RedPill-TTG/redpill-lkm/blob/061b3e643d4bca663f24fb3dee397ecb77d8e44c/config/runtime_config.c

 

.vid = VID_PID_EMPTY,
  .pid = VID_PID_EMPTY,
  .dom_size_mib = 1024, //usually the image will be used with ESXi and thus it will be ~100MB anyway

 

The size of the sata dom disk cannot be greater to what you set in the LKM runtime_config. 

 

 

Edited by pocopico
Link to comment
Share on other sites

1 minute ago, pocopico said:

 

@fbelavenuto On VMware, when i increase the disk size 4GB , LKM does not pick it up as synoboot device. The issue goes down to this ->  https://github.com/RedPill-TTG/redpill-lkm/blob/061b3e643d4bca663f24fb3dee397ecb77d8e44c/config/runtime_config.c

 

.vid = VID_PID_EMPTY,
  .pid = VID_PID_EMPTY,
  .dom_size_mib = 1024, //usually the image will be used with ESXi and thus it will be ~100MB anyway

 

The size of the sata dom disk cannot be greater to what you set in the LKM runtime_config. 

 

 

Ops, is true, I forgot this!

Add a cmdline entry: dom_szmax with value 4096 (or more if necessary)

  • Like 2
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...