RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

20 hours ago, ThorGroup said:

In the previous versions we've missed save call for 3615 (whoops!) but the newest release should save it. Can you confirm it's still not working?

 

Generated new image with latest redpill-load and saving of the boot option does not work still.

Link to post
Share on other sites
3 hours ago, mcdull said:

need to change the global_config.json 

update last redpill_load to 

https://github.com/RedPill-TTG/redpill-load.git

and branch = master

Seems yumkey removed his branch, I was to lazy to create a 0.5.4 release to adjust the sources. Been buisy with migrating my three ESXi cluster nodxs one by one to Proxmox. I still need to figure out how to migrate my existing ESXi boxes to Proxmos, especialy the one with the HBA controller in passthrough mode.

Link to post
Share on other sites
21 minutes ago, ilovepancakes said:

 

Generated new image with latest redpill-load and saving of the boot option does not work still.

Even with disk mode "independent - persistant" for the bootloader drive? 

Link to post
Share on other sites

.. and another update of the tool chain loader with fixed repo details for redpill-load and apollolake-7.0-41890

 

# Inofficial redpill toolchain image builder

- Creates a OCI Container (~= Docker) image based tool chain.

- Takes care of downloading (and caching) the required sources to compile redpill.ko and the required os packages that the build process depends on.

- Caches .pat downloads inside the container on the host.

- Configuration is done in the JSON file `global_config.json`; custom <platform_version> entries can be added underneath the `building_configs` block. Make sure the id is unique per block!

 

## Changes

-  Changes redpill-load sources for apollolake-7.0-41890 to https://github.com/RedPill-TTG/redpill-load.git and the master branch.

 

## Usage

 

1. Create `user_config.json` according https://github.com/RedPill-TTG/redpill-load and place it in the same folder as redpill_tool_chain.sh

2. Build the image for the platform and version you want:

   `./redpill_tool_chain.sh build <platform_version>`

3. Run the image for the platform and version you want:

   `./redpill_tool_chain.sh auto <platform_version>`

 

The "old way" with `./redpill_tool_chain.sh auto <platform_version>` and executing `make build_all` is still available.

 

Note: run `./redpill_tool_chain.sh` to get the list of supported ids for the <platform_version> parameter.

 

After step 3. the redpill load image should be build and can be found in the host folder "images".

 

Examples:

### See Help text

 

```

./redpill_tool_chain.sh

Usage: ./redpill_tool_chain.sh <action> <platform version>

 

Actions: build, auto, run

 

- build:    Build the toolchain image for the specified platform version.

 

- auto:     Starts the toolchain container using the previosuly build toolchain image for the specified platform.

            Updates redpill sources and builds the bootloader image automaticaly. Will end the container once done.

 

- run:      Starts the toolchain container using the previously built toolchain image for the specified platform.

            Interactive Bash terminal.

 

Available platform versions:

---------------------

bromolow-6.2.4-25556

bromolow-7.0-41222

apollolake-6.2.4-25556

apollolake-7.0-41890

```

 

### Build toolchain image

 

For Bromolow 6.2.4   : `./redpill_tool_chain.sh build bromolow-6.2.4-25556`

For Bromolow 7.0     : `./redpill_tool_chain.sh build bromolow-7.0-41222`

For Apollolake 6.2.4 : `./redpill_tool_chain.sh build apollolake-6.2.4-25556`

For Apollolake 7.0   : `./redpill_tool_chain.sh build apollolake-7.0-41890`

 

### Create redpill bootloader image

 

For Bromolow 6.2.4   : `./redpill_tool_chain.sh auto bromolow-6.2.4-25556`

For Bromolow 7.0     : `./redpill_tool_chain.sh auto bromolow-7.0-41222`

For Apollolake 6.2.4 : `./redpill_tool_chain.sh auto apollolake-6.2.4-25556`

For Apollolake 7.0   : `./redpill_tool_chain.sh auto apollolake-7.0-41890`

 

redpill-tool-chain_x86_64_v0.5.4.zip

Edited by haydibe
  • Like 4
  • Thanks 4
Link to post
Share on other sites
7 minutes ago, haydibe said:

If someone shares the required details about how it's done, then we can give it a try :)  

 

 

Here is the modules and installer

 

 

Thanks to the @loomes))
 

Quote

 

Edited by T-REX-XP
Link to post
Share on other sites

I have no idea how to automate the downloads from a page that heavily relies on javascript.

Unless the files are on Github or a public available webpage with a direct download, it will be messy and brittle. 

 

So if someone else is up to the task, feel free to incorporate it and publish the result here.

Edited by haydibe
Link to post
Share on other sites
30 minutes ago, mcdull said:

I can hardly find any major issue on the new loader under proxmox.

Anyone starts using this as daily driver?

 

No its to early. And i found that the new Photos App Face Detection is not working (Some checks for real Syno Hardware or something?!)

Link to post
Share on other sites
1 hour ago, loomes said:

No its to early. And i found that the new Photos App Face Detection is not working (Some checks for real Syno Hardware or something?!)

In old jun's loader, it is also related to cpu instruction set and cpu core assignment after a specific version.

i.e. intel gpu is required. Since I am using AMD it will NOT work anyway.

 

My hope is to support AMD machine type, e.g. DS1621+

Edited by mcdull
Link to post
Share on other sites
9 hours ago, haydibe said:

.. and another update of the tool chain loader with fixed repo details for redpill-load and apollolake-7.0-41890

 

# Inofficial redpill toolchain image builder

- Creates a OCI Container (~= Docker) image based tool chain.

- Takes care of downloading (and caching) the required sources to compile redpill.ko and the required os packages that the build process depends on.

- Caches .pat downloads inside the container on the host.

- Configuration is done in the JSON file `global_config.json`; custom <platform_version> entries can be added underneath the `building_configs` block. Make sure the id is unique per block!

 

## Changes

-  Changes redpill-load sources for apollolake-7.0-41890 to https://github.com/RedPill-TTG/redpill-load.git and the master branch.

 

## Usage

 

1. Create `user_config.json` according https://github.com/RedPill-TTG/redpill-load and place it in the same folder as redpill_tool_chain.sh

2. Build the image for the platform and version you want:

   `./redpill_tool_chain.sh build <platform_version>`

3. Run the image for the platform and version you want:

   `./redpill_tool_chain.sh auto <platform_version>`

 

The "old way" with `./redpill_tool_chain.sh auto <platform_version>` and executing `make build_all` is still available.

 

Note: run `./redpill_tool_chain.sh` to get the list of supported ids for the <platform_version> parameter.

 

After step 3. the redpill load image should be build and can be found in the host folder "images".

 

Examples:

### See Help text

 

```

./redpill_tool_chain.sh

Usage: ./redpill_tool_chain.sh <action> <platform version>

 

Actions: build, auto, run

 

- build:    Build the toolchain image for the specified platform version.

 

- auto:     Starts the toolchain container using the previosuly build toolchain image for the specified platform.

            Updates redpill sources and builds the bootloader image automaticaly. Will end the container once done.

 

- run:      Starts the toolchain container using the previously built toolchain image for the specified platform.

            Interactive Bash terminal.

 

Available platform versions:

---------------------

bromolow-6.2.4-25556

bromolow-7.0-41222

apollolake-6.2.4-25556

apollolake-7.0-41890

```

 

### Build toolchain image

 

For Bromolow 6.2.4   : `./redpill_tool_chain.sh build bromolow-6.2.4-25556`

For Bromolow 7.0     : `./redpill_tool_chain.sh build bromolow-7.0-41222`

For Apollolake 6.2.4 : `./redpill_tool_chain.sh build apollolake-6.2.4-25556`

For Apollolake 7.0   : `./redpill_tool_chain.sh build apollolake-7.0-41890`

 

### Create redpill bootloader image

 

For Bromolow 6.2.4   : `./redpill_tool_chain.sh auto bromolow-6.2.4-25556`

For Bromolow 7.0     : `./redpill_tool_chain.sh auto bromolow-7.0-41222`

For Apollolake 6.2.4 : `./redpill_tool_chain.sh auto apollolake-6.2.4-25556`

For Apollolake 7.0   : `./redpill_tool_chain.sh auto apollolake-7.0-41890`

 

redpill-tool-chain_x86_64_v0.5.4.zip 6.61 kB · 46 downloads

 

Since 0.5.3, i am getting this error with appololake 7.0 41890

 

DiskStation login: [  105.240719] random: nonblocking pool is initialized
[  149.122345] <redpill/rtc_proxy.c:37> MfgCompatTime raw data: sec=58 min=17 hr=2 wkd=4 day=19 mth=7 yr=121
[  149.125335] <redpill/rtc_proxy.c:95> Writing BCD-based RTC
[  149.127232] RTC time set to 2021-08-19  2:17:58 (UTC)
[  152.224158] md: bind<sdg1>
[  152.224657] md/raid1:md0: active with 1 out of 16 mirrors
[  152.226020] md0: detected capacity change from 0 to 2549940224
[  155.232955] md: bind<sdg2>
[  155.233801] md/raid1:md1: active with 1 out of 16 mirrors
[  155.235740] md1: detected capacity change from 0 to 2147418112
[  155.457248] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[  155.459884] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  155.471937] <redpill/rtc_proxy.c:222> Got an invalid call to rtc_proxy_set_auto_power_on
[  155.475880] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[  155.478460] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  155.491308] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[  155.493820] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)

 

Installation of VM will be failed at 55%.

image.png.6735db17e4c2ae3a11bb092adb5579d4.png

 

The same loader if used by existing configured DSM7 it will then boot correctly.

 

by the way 0.5.3 did not load virtio driver and 0.5.4 is loading correctly! bravo, thank you for the great work!

Link to post
Share on other sites

2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so

Link to post
Share on other sites
3 hours ago, taiziccf said:

by the way 0.5.3 did not load virtio driver and 0.5.4 is loading correctly! bravo, thank you for the great work!


The tool chain loader is realy just a simple wrapper that coordinates the creation of a build environment and the build, but is not involved in how redpill-lkm or redpill-load work.

Thus said, I am sure ThorGroup/jumkey are happy to read about it. Its the outcome of their doing in redpill-load :) Fully agree: they do a great job!

 

Update: I missed to address that the installation is now stuck on 55%, I am sure ThorGroup will see the post - or you might raise an issue on Github with attached serial connection logs.

 

Edited by haydibe
Link to post
Share on other sites
32 minutes ago, renyi said:

2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: /source/synophoto-plugin-face/src/face_plugin/lib/face_detection.cpp:214 Error: (face plugin) load network failed
2021-08-19T12:57:25+08:00 U820 synofoto-face-extraction[5952]: uncaught thread task exception /source/synofoto/src/daemon/plugin/plugin_worker.cpp:90 plugin init failed: /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-face.so

 

did you use intel platform with igpu? And if you are using hypervisor did you passthrough the gpu?

the library should require intel opencv.  Which is also the same in 6.2.3

Link to post
Share on other sites
19 minutes ago, s1oz said:

@gadreel

hi,

Can you share your unRAID XML file?

Definitely,

 

find attached...

 

The key areas for me are, change bios to sea bios, machine (Q35 ~ if u choose i440fx I do not think there is difference), USB Controller to 3.0 (XHCI), the 1st disk is red pill image as usb and 2nd disk as a SATA, edit the virtio ethernet to e1000e and you can add 2 aditional serials (total 3) like mine to monitor the console using "virsh console (name of VM) serial2"

redpill.xml

Edited by gadreel
Link to post
Share on other sites
2 minutes ago, gadreel said:

Definitely,

 

find attached...

 

The key areas for me are, change bios to sea bios, machine (Q35 ~ if u choose i440fx I do not think there is difference), USB Controller to 3.0 (XHCI), the first disk is red pill as usb ans 2ns disk as a SATA, edit the virtio ethernet to e1000e and you can add 2 aditional serials (total 3) like mine to monitor the console using "virsh console (name of VM) serial2"

redpill.xml 4.85 kB · 0 downloads

thanks bro!

  • Like 1
Link to post
Share on other sites
58 minutes ago, gadreel said:

Definitely,

 

find attached...

 

The key areas for me are, change bios to sea bios, machine (Q35 ~ if u choose i440fx I do not think there is difference), USB Controller to 3.0 (XHCI), the 1st disk is red pill image as usb and 2nd disk as a SATA, edit the virtio ethernet to e1000e and you can add 2 aditional serials (total 3) like mine to monitor the console using "virsh console (name of VM) serial2"

redpill.xml 4.85 kB · 11 downloads

AFAIK, no need to use e1000e which has less performance.  latest loader is capable of doing virtio.

Link to post
Share on other sites
1 hour ago, mcdull said:

 

did you use intel platform with igpu? And if you are using hypervisor did you passthrough the gpu?

the library should require intel opencv.  Which is also the same in 6.2.3

dou you have a link

Link to post
Share on other sites
On 8/7/2021 at 9:37 PM, haydibe said:

Never though about that its actualy possible to bind the serial port to a telnet port. Thanks!

 

I ended up adding three serial ports, exposing them from 10021 to 10023 and then settings custom firewall rules for them:

 

On the ESXi Host shell:
$ esxcli network firewall set --enabled false
$ esxcli network firewall unload
$ chmod 644 /etc/vmware/firewall/service.xml
$ vi /etc/vmware/firewall/service.xml

$ chmod 444 /etc/vmware/firewall/service.xml

$ esxcli network firewall load

$ esxcli network firewall set --enabled true

 

Thanks again for the info!

Can't do it anymore with ESXI 7.0.x ... write protected even with root.

 

[root@] chmod 644 /etc/vmware/firewall/service.xml
chmod: /etc/vmware/firewall/service.xml: Operation not permitted

 

Did not find a workaround yet

 

Edit : Actually I did : https://levelup.gitconnected.com/how-to-get-your-firewall-rules-to-stick-on-esxi-v7-961efcb58d8d

Edited by Orphée
Link to post
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.