T-REX-XP

Thanks for your feedback. I also managed to test the installation on the Zimaboard, but I had no luck. Only one drive, that is, external sata ssd, is available to install. But generally the DSM 7.2 is pretty unstable on that HW—quite a slow boot. After a few attempts to install and boot the DSM, I didn't get any successful results. At the same time, under the proxmox, on that sbc, DSM is working fine.

Good news. Thanks for the update. Does any one tested emmc as a system installation disk? I would like to install DSM to zimaboard? Thanks

When you use arpl, you can add this parm to the loader. Jfyi: I have found alternative solution for quickconnect. Its localtunnel that is running in docker container. The final url will be like this: HTTPS://bla.loca.lt Where bla is your subdomain name. Its working fine when the ip address is not white.

Hi. Unfortunately no. It's not relevant for me right now. I left my home due to war((

Does DS3622xs supporting efficient HW transcoding with CPU ? Actually, I'm not sure. I had an Asus p10s-i with g4620 CPU, but with DSM ds918/1019 based on jun/redpill loader no one device inside /dev/dri/ folder is presented. So, that MB has Intel® C232 Chipset, that doesn't support that feature. Quick answer: the ability of the HW transcoding is based on the chipset functionality.

Actually no. I tried to do the same with atomic pi. There is no way to do it. P.s. as a workaround: install unraid, then use vm. It works.

You need to compile driver at first. Please find the good manual https://forums.unraid.net/topic/98064-support-blakeblackshear-frigate/

Hi, do you have any updates regarding your experiment ?) Does your modification stable ? Thanks in advance

I'm not sure that is a good idea to build web ui as a part of bootloader. Its completely different parts. I mean we can use any os as a way to load wizard of generating the bootloader image.

It seems like we have got great progress with autogenerating the loader. How about building web ui? I guess we can use nodejs or something the same to build web ui. It's more user-friendly then terminal commands.

I can't confirm that its working without patching the libs. Actually I have received the only cache device inside the storage manager. But it that case I can mount the ssd to the separate folder 📂.

Вы не правы. Я так ssd Samsung evo 250gb меньше чем за год угробил. И это у меня не было нагрузки. Для ss, точно не нужно чтоб она на раздел с кешем писала. Ресурс ссд сразу закончится

Is it make sens to create RP module with your approach?

Thank you for the solution. Is it possible to use google coral ai stick for HW acceleration?

The same for Samsung 860 evo 250gb

@WiteWulf,Thanks for your answer on my prev question. @ThorGroup Here is my result of the investigation: I have build my loader image with custom ext for igb driver made by pocopico using tool-chain 0.11, so during the boot log analyzing I have found that this module is broken and it is non necessary on my setup due to OOB driver is working fine. Here is an error from my boot log :: Loading kerne[ 7.057313] igb: Unknown symbol i2c_bit_add_bus (err 0) l modules from extensions ... Loading kmod #0 "igb.ko" for pocopico.igb (args: ) insmod: can't insert 'igb.ko': unknown symbol in module, or unknown parameter ERROR: kernel extensions "igb.ko" from pocopico.igb failed to load Exit on error [99] rp ext init exec failure... It seems like the root cause of my issue. After the removing custom driver, I have successfully updated DSM to 6.2.4 on my HW. Trust be told, am not sure that issue with modules is still valid now. The modules are already updated on the git repo. But the new one issue has appeared in the dmesg:

Guys, want to update 6.2.3 with jun loader to 6.2.4 redpill. I have already build an image with igb driver, and succesfuly boot from it, but installing process can't see previous setup (( so, advice me to install DSM from scratch(( May I miss something during building the loader any custom steps??

@ThorGroup, Here is a few things regarding the FAn control with PMU I've tested the following way to set speed of the CPU FAN on 6.2.3 insmod hwmon-vid.ko insmod nct6775.ko optional install sensors(lm-sensors) via ipkg Then the fan speed can be set like this: #default value echo 5 > /sys/devices/platform/nct6775.656/hwmon/hwmon1/pwm2_enable Here is a few userful commands: #find all pwm: find /sys/devices -type f -name "pwm*" #find beep /sys/devices/platform/nct6775.656/hwmon/hwmon1/beep_enable #enable /disable beep echo 0 > /sys/devices/platform/nct6775.656/hwmon/hwmon1/beep_enable | sensors | grep beep So, the vPMU can use it for manipulating the CPU FAN speed. But we need to resolve the following issues: - build nct6775 for dsm 7.0 (I now that this module is one of the many modules for different IO chips on motherboard), let's start from it, then add an additional one - build pcspeaker module - implement vPMU to use software methods for manipulating the FAN speed @pocopico, could you please build nct6775 module for 918 dsm 7.0 ?? Thanks. I will prepare the RP extension for that module Thanks in advance.

I pay 300 uah(12$) for 1000mbit. Its pretty small price for this speed in Ukraine)) Just wanna ask, which router should be for 2.5 or 5gbp ? Now I'm using custom pfsense based router on j3455.

1. modify entrypoint.sh as I mentioned before 2. run ./redpill_tool_chain.sh build apollolake-7.0-41890 # due to copying entrypoint.sh inside container 3. run ./redpill_tool_chain.sh auto apollolake-7.0-41890 4. See build logs then check logs inside VM during the boot. I have already checked it on my vm. So my custom modules are loaded during the boot.

Please use my repos. They are working - https://github.com/T-REX-XP/rp-ext-realtek/tree/main/r8169 https://github.com/T-REX-XP/rp-ext-realtek/tree/main/r8152 ./ext-manager.sh add https://github.com/T-REX-XP/rp-ext-realtek/raw/main/r8169/rpext-index.json ./ext-manager.sh add https://github.com/T-REX-XP/rp-ext-realtek/raw/main/r8152/rpext-index.json Also I have found that current version of toolchain 0.11 copying the entrypoint.sh to the container instead of passing from the host machine. I'm working on improved version of the toolkit right now TODO: How about to add the power button modules as extension?)

Also it seems to be the following repo should contains all available extensions in feature - https://github.com/RedPill-TTG/redpill-extensions. Like a marketplace or repository with a links. So it will be enough to define available extensions unique name inside extensions section in the config. "extensions": [ "thethorgroup.virtio", "example_dev.example_extension" ]

Quick answer: I have successfully fixed reported issue by adding the following line to the docker/entrypoint.sh before build_all echo "----Add ext modules" /opt/redpill-load/ext-manager.sh add "https://github.com/T-REX-XP/rp-ext-realtek/raw/main/r8169/rpext-index.json" But it's hardcode. Now the toolkit v0.11 do not have valid way to use ext loader. It seems to be a section inside platform config, with the links to the modules, then this modules should be installed before the build all.

Guys, i have created the repo based on popopico repo for adding the r8196 driver. but during the build the loader via toolchain 0.11 ./redpill_tool_chain.sh auto apollolake-7.0-41890 faced with error. [!] Extension "t-rex-xp.r8169" is not added/installed - did you misspell the name or forgot to do "ext-manager.sh add <URL>" first? I have done the following steps: 1. ./redpill_tool_chain.sh build apollolake-7.0-41890 2. ./redpill_tool_chain.sh run apollolake-7.0-41890 3. cd ./redpill-loader 4. ./ext-manager.sh add 'https://github.com/T-REX-XP/rp-ext-realtek/blob/main/r8169/rpext-index.json' The extension has been installed via the following command inside the container So, What is the right manual for toolkit to integrate the extensions? Thanks

Guys, Who can compile driver for RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) apollolake 7.0?