T-REX-XP
-
Posts
288 -
Joined
-
Last visited
-
Days Won
1
Posts posted by T-REX-XP
-
-
On 12/21/2023 at 1:15 AM, Peter Suh said:
This is RR’s current status as received from a community user.
RR seems to be continuously being updated under the name BLACK SYNOLOGY NAS SYSTEM.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
-
1 hour ago, zexx said:
I enabled SATA SSD cache by editing /etc.defaults/synoinfo.conf , just change "support_ssd_cache" from no to yes and reboot , i do not have nvme to check this case
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.
-
2
-
-
10 hours ago, ontheroad2008 said:
@T-REX-XPHello,Have you built the nct6775.ko driver module for DSM7.0.1?
Hi. Unfortunately no. It's not relevant for me right now. I left my home due to war((
-
6
-
-
On 3/23/2022 at 10:06 PM, RedwinX said:
@Orphée Just for my knowledge, do you think we can use the i915 driver on a redpill emulated synology without iGPU to get the HW transcoding? like a DS3622xs+, with a little insmod i915?
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.
-
1
-
-
26 minutes ago, lvagabond said:
Hi, I have a question about installing DSM on my single board computer. This is a Rock Pi X with 4GB of RAM. I managed to boot in DSM 6.1.x, I don't know what HW driver with, I tried many of them before the board caught up. Finally, I have the correct network card driver and I find the DSM on the network. Unfortunately, the board has no SATA controller, so DSM will not find any disk to install. I tried to connect the drive using a USB-SATA controller, unfortunately to no avail. The question is: can DSM somehow be commissioned using an external drive connected to USB or not? Thank you all for your answer. Lukas
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.
-
1 hour ago, bartik22 said:
Hello
I connected the Coral Accelerator via the pcie adapter. (I know that only one TPU can be seen through this adapter)
Does anybody know how i can run on xpenology? I need in docker for frigata
The device is unknown but visible.$ lspci -nn | grep 089a 0000:02:00.0 Class [0000]: Device [1ac1:089a]There are probably missing drivers that I can't install.
Looking at the manual, it should look like this:
https://coral.ai/docs/m2/get-started/#2a-on-linuxbut I can't find anywhere:
/ dev / apex_0Can someone help me?
You need to compile driver at first. Please find the good manual https://forums.unraid.net/topic/98064-support-blakeblackshear-frigate/
-
1
-
-
On 1/29/2022 at 10:53 PM, Alonia said:
I managed to run SS for 3 hours with 3 cameras!
Hi, do you have any updates regarding your experiment ?) Does your modification stable ? Thanks in advance
-
15 minutes ago, haydibe said:
... whoever gets the idea to build a web ui: make sure the runtime it needs is available/works on tiny core and fits into the bootloader image.
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.
-
1 hour ago, maqros said:
it's possible to create a volume on nvme and use for smth. here is HOWTO
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 📂.
-
1 hour ago, XPEH said:
На практике современный SSD переживет ваш сервер
Вы не правы. Я так ssd Samsung evo 250gb меньше чем за год угробил. И это у меня не было нагрузки. Для ss, точно не нужно чтоб она на раздел с кешем писала. Ресурс ссд сразу закончится
-
1
-
-
3 hours ago, jumkey said:
Use `LD_PRELOAD` to inject the `IsSupported` function to turn off GPU face recognition
Tested on DS918+ 7.0.1
Synology Photos Version: 1.1.0-0224/1.0.1-0194preload.c
// preload.c #include <stdio.h> long long _ZN9synophoto6plugin7network9IeNetwork11IsSupportedEv() { printf("synophoto::plugin::network::IeNetwork::IsSupported return 0\n"); return 0LL; } __attribute__((constructor)) void main() { printf("module inject success\n"); }
preload.so 6.48 kB · 8 downloads
shell
Make CHROOT@ds.apollolake[/source]# gcc -fPIC -shared -o preload.so preload.c Install root@DSM:~# cp preload.so /usr/lib/preload.so or root@DSM:~# cp preload.so /volume1/@appstore/SynologyPhotos/lib/preload.so root@DSM:~# systemctl edit pkg-SynologyPhotos-face-extraction [Service] Environment="LD_PRELOAD=preload.so" root@DSM:~# systemctl restart pkg-SynologyPhotos-face-extraction Uninstall root@DSM:~# rm /usr/lib/preload.so or root@DSM:~# rm /volume1/@appstore/SynologyPhotos/lib/preload.so root@DSM:~# rm /etc/systemd/system/pkg-SynologyPhotos-face-extraction.service.d/override.conf root@DSM:~# systemctl daemon-reload root@DSM:~# systemctl restart pkg-SynologyPhotos-face-extraction
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?
-
22 hours ago, smoothmove said:
I tried the NVMe cache with the 918+. HUGE WARNING- I used Western Digital SN750 black drives. I burned 2 of them within 3 months. I haven't tried other brands. Just a heads up
The same for Samsung 860 evo 250gb
-
1
-
-
@WiteWulf,Thanks for your answer on my prev question.
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:
Spoiler[ 110.393405] docker-c2c86e43: port 5(docker8ca98a7) entered forwarding state [ 130.428284] invalid opcode: 0000 [#1] PREEMPT SMP [ 130.433239] Modules linked in: pci_stub vhost_net(O) tun kvm_intel kvm irqbypass xt_ipvs ip_vs_rr ip_vs xt_mark iptable_mangle br_netfilter bridge stp aufs macvlan veth xt_conntrack xt_addrtype ipt_MASQUERADE xt_REDIRECT nf_nat_masquerade_ipv4 xt_nat iptable_nat vhost_scsi(O) vhost(O) nf_nat_ipv4 nf_nat_redirect nf_nat snd_usb_hiface snd_pcm_oss snd_mixer_oss snd_usb_audio snd_pcm snd_timer snd_hwdep snd_usbmidi_lib snd_rawmidi snd_seq_device snd soundcore nct6775(E) hwmon_vid(E) ti_usb_3410_5052(OE) ch341(OE) pl2303(OE) cp210x(OE) ftdi_sio(OE) usbserial(E) cifs udf isofs loop nfsd exportfs rpcsec_gss_krb5 tcm_loop(O) iscsi_target_mod(O) target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) hid_generic usbhid hid [ 130.506625] usblp uhci_hcd ehci_pci ehci_hcd xt_mac xt_geoip(O) compat_xtables(O) nf_conntrack_ipv6 ip6table_filter ip6_tables xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables x_tables openvswitch gre nf_defrag_ipv6 nf_conntrack apollolake_synobios(PO) exfat(O) btrfs i915 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cfbfillrect cfbcopyarea cfbimgblt drm drm_panel_orientation_quirks iosf_mbi fb fbdev video backlight button synoacl_vfs(PO) hfsplus md4 hmac r8168(O) igb(O) i2c_algo_bit e1000e(O) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave [ 130.579488] cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd usb_storage xhci_pci xhci_hcd usbcore usb_common redpill(OE) [last unloaded: apollolake_synobios] [ 130.604950] CPU: 0 PID: 9030 Comm: udevd Tainted: P OE 4.4.59+ #25556 [ 130.612653] Hardware name: ASUSTeK COMPUTER INC. P10S-I Series/P10S-I Series, BIOS 4602 09/11/2020 [ 130.621890] task: ffff880766822400 ti: ffff8807689c0000 task.ti: ffff8807689c0000 [ 130.629527] RIP: 0010:[<ffffffffa0753c27>] [<ffffffffa0753c27>] GetHwCapability+0x7/0xe0 [apollolake_synobios] [ 130.639889] RSP: 0018:ffff8807689c3d00 EFLAGS: 00010282 [ 130.645331] RAX: ffffffffa0753c20 RBX: ffff88084652e800 RCX: 000000000000007d [ 130.652671] RDX: 0000000000000008 RSI: ffff88082ff27199 RDI: ffff8807689c3d10 [ 130.659978] RBP: ffff8807689c3d00 R08: 000000000000000a R09: 000000000000fffb [ 130.667343] R10: 0000000000000000 R11: 000000000000000f R12: 0000000000000000 [ 130.674656] R13: ffff88082ff27000 R14: ffff88084652e890 R15: 0000000000000001 [ 130.681910] FS: 00007f1c79867780(0000) GS:ffff88086dc00000(0000) knlGS:0000000000000000 [ 130.690220] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 130.696062] CR2: 00007ffd4ce13f88 CR3: 0000000764bbe000 CR4: 00000000003606f0 [ 130.703340] Stack: [ 130.705464] ffff8807689c3d30 ffffffffa002eaa0 0000000000000008 ffff88084a0ef4c0 [ 130.713117] ffff88084652e8a0 ffff88082ff27000 ffff8807689c3d80 ffffffff81390595 [ 130.720777] 0000880846773b40 0000000000000000 ffff8807686d9b60 ffff88084a0ef4c0 [ 130.728409] Call Trace: [ 130.730907] [<ffffffffa002eaa0>] usb_uevent+0xe0/0x140 [usbcore] [ 130.737109] [<ffffffff81390595>] dev_uevent+0x155/0x2d0 [ 130.742558] [<ffffffff8138f375>] uevent_show+0x85/0x100 [ 130.748054] [<ffffffff8138e8dc>] dev_attr_show+0x1c/0x50 [ 130.753634] [<ffffffff811afba0>] sysfs_kf_seq_show+0xc0/0x1b0 [ 130.759605] [<ffffffff811ae54b>] kernfs_seq_show+0x1b/0x20 [ 130.765308] [<ffffffff8115f63d>] seq_read+0xcd/0x380 [ 130.770471] [<ffffffff811aed47>] kernfs_fop_read+0x107/0x160 [ 130.776364] [<ffffffff811347b3>] __vfs_read+0x13/0x40 [ 130.781632] [<ffffffff81135283>] vfs_read+0x83/0x130 [ 130.786823] [<ffffffff81136a9c>] SyS_read+0x5c/0xc0 [ 130.791893] [<ffffffff81578b8a>] entry_SYSCALL_64_fastpath+0x1e/0x92 [ 130.798423] Code: ff ff ff ff eb bf 48 c7 c7 3a 80 75 a0 31 c0 e8 cf f4 98 e0 b8 ff ff ff ff eb aa 66 0f 1f 84 00 00 00 00 00 48 b8 c0 99 00 a0 ff <ff> ff ff ff e0 00 83 3f 08 c7 47 04 00 00 00 00 0f 87 ae 00 00 [ 130.818977] RIP [<ffffffffa0753c27>] GetHwCapability+0x7/0xe0 [apollolake_synobios] [ 130.826891] RSP <ffff8807689c3d00> [ 130.832911] ---[ end trace cdb9f97530677868 ]--- [ 157.269130] invalid opcode: 0000 [#2] PREEMPT SMP [ 157.274117] Modules linked in: pci_stub vhost_net(O) tun kvm_intel kvm irqbypass xt_ipvs ip_vs_rr ip_vs xt_mark iptable_mangle br_netfilter bridge stp aufs macvlan veth xt_conntrack xt_addrtype ipt_MASQUERADE xt_REDIRECT nf_nat_masquerade_ipv4 xt_nat iptable_nat vhost_scsi(O) vhost(O) nf_nat_ipv4 nf_nat_redirect nf_nat snd_usb_hiface snd_pcm_oss snd_mixer_oss snd_usb_audio snd_pcm snd_timer snd_hwdep snd_usbmidi_lib snd_rawmidi snd_seq_device snd soundcore nct6775(E) hwmon_vid(E) ti_usb_3410_5052(OE) ch341(OE) pl2303(OE) cp210x(OE) ftdi_sio(OE) usbserial(E) cifs udf isofs loop nfsd exportfs rpcsec_gss_krb5 tcm_loop(O) iscsi_target_mod(O) target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) hid_generic usbhid hid [ 157.347620] usblp uhci_hcd ehci_pci ehci_hcd xt_mac xt_geoip(O) compat_xtables(O) nf_conntrack_ipv6 ip6table_filter ip6_tables xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables x_tables openvswitch gre nf_defrag_ipv6 nf_conntrack apollolake_synobios(PO) exfat(O) btrfs i915 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cfbfillrect cfbcopyarea cfbimgblt drm drm_panel_orientation_quirks iosf_mbi fb fbdev video backlight button synoacl_vfs(PO) hfsplus md4 hmac r8168(O) igb(O) i2c_algo_bit e1000e(O) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave [ 157.420467] cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd usb_storage xhci_pci xhci_hcd usbcore usb_common redpill(OE) [last unloaded: apollolake_synobios] [ 157.445850] CPU: 2 PID: 26696 Comm: udevd Tainted: P D OE 4.4.59+ #25556 [ 157.453615] Hardware name: ASUSTeK COMPUTER INC. P10S-I Series/P10S-I Series, BIOS 4602 09/11/2020 [ 157.462756] task: ffff88075c271000 ti: ffff880766874000 task.ti: ffff880766874000 [ 157.470436] RIP: 0010:[<ffffffffa0753c27>] [<ffffffffa0753c27>] GetHwCapability+0x7/0xe0 [apollolake_synobios] [ 157.480808] RSP: 0018:ffff880766877d00 EFLAGS: 00010282 [ 157.486267] RAX: ffffffffa0753c20 RBX: ffff880843317800 RCX: 0000000000000078 [ 157.493582] RDX: 0000000000000006 RSI: ffff8807649f2194 RDI: ffff880766877d10 [ 157.500921] RBP: ffff880766877d00 R08: 000000000000000a R09: 000000000000fffb [ 157.508236] R10: 0000000000000000 R11: 000000000000000f R12: 0000000000000000 [ 157.515490] R13: ffff8807649f2000 R14: ffff88083f066830 R15: 0000000000000001 [ 157.522840] FS: 00007f1c79867780(0000) GS:ffff88086dd00000(0000) knlGS:0000000000000000 [ 157.531166] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 157.537077] CR2: 00007ffd4ce15728 CR3: 000000076485c000 CR4: 00000000003606f0 [ 157.544425] Stack: [ 157.546505] ffff880766877d30 ffffffffa002eaa0 0000000000000008 ffff88084a0ef4c0 [ 157.554137] ffff88083f066840 ffff8807649f2000 ffff880766877d80 ffffffff81390595 [ 157.561849] ffff8808452f0040 ffff880815ca7b98 ffff88079c071260 ffff88084a0ef4c0 [ 157.569590] Call Trace: [ 157.572112] [<ffffffffa002eaa0>] usb_uevent+0xe0/0x140 [usbcore] [ 157.578450] [<ffffffff81390595>] dev_uevent+0x155/0x2d0 [ 157.583909] [<ffffffff8138f375>] uevent_show+0x85/0x100 [ 157.589387] [<ffffffff8138e8dc>] dev_attr_show+0x1c/0x50 [ 157.594942] [<ffffffff811afba0>] sysfs_kf_seq_show+0xc0/0x1b0 [ 157.600955] [<ffffffff811ae54b>] kernfs_seq_show+0x1b/0x20 [ 157.606675] [<ffffffff8115f63d>] seq_read+0xcd/0x380 [ 157.611874] [<ffffffff811aed47>] kernfs_fop_read+0x107/0x160 [ 157.617759] [<ffffffff811347b3>] __vfs_read+0x13/0x40 [ 157.623055] [<ffffffff81135283>] vfs_read+0x83/0x130 [ 157.628253] [<ffffffff81136a9c>] SyS_read+0x5c/0xc0 [ 157.633349] [<ffffffff81578b8a>] entry_SYSCALL_64_fastpath+0x1e/0x92 [ 157.639923] Code: ff ff ff ff eb bf 48 c7 c7 3a 80 75 a0 31 c0 e8 cf f4 98 e0 b8 ff ff ff ff eb aa 66 0f 1f 84 00 00 00 00 00 48 b8 c0 99 00 a0 ff <ff> ff ff ff e0 00 83 3f 08 c7 47 04 00 00 00 00 0f 87 ae 00 00 [ 157.660294] RIP [<ffffffffa0753c27>] GetHwCapability+0x7/0xe0 [apollolake_synobios] [ 157.668253] RSP <ffff880766877d00> [ 157.681710] ---[ end trace cdb9f97530677869 ]---
-
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.kooptional 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_enableHere 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 beepSo, 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.
-
1
-
-
1 hour ago, nemesis122 said:
i pay for 1000mbit down and 100 mbit up 100 chf in this case 100 Dollar per month but when is available i can have 10 gbit up down for 99 chf but is not available here
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.
-
16 minutes ago, haydibe said:
Uhm, so you didn't ask before what the next commands would be to follow up on the steps you posted before?
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.
-
8 minutes ago, haydibe said:
I already had the implementation for configurable ext-manager support finished on wednesday, but had no extension repos to test.
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.jsonAlso 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?)
-
1
-
5 minutes ago, T-REX-XP said:
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.
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" ]-
1
-
-
16 minutes ago, haydibe said:
For time beeing this is the approach, until it's sorted out with TTG on how to implement the integration.
To build the bootloader you then simply have to execute the command `make -C /opt/ build_all` or follow the steps in the redpill-load documentation.
As per my understanding, the bootloader should be build with the added extension.
As a quick solution to get rid of step 3. I could embbed the symlink to the ext-manager.sh like TTG suggested.
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.
-
48 minutes ago, pocopico said:
I think i've got all shorted out .. the extensions is a bit heavier work than just dumping all mods to a file like extra.lzma in the past
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-41890faced 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
-
3
-
-
Guys, Who can compile driver for RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) apollolake 7.0?
Automated RedPill Loader (ARPL)
in Loaders
Posted
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.