Jump to content
XPEnology Community

RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

il y a 17 minutes, nemesis122 a dit :

Has anyone gen 8 working ?

thanks

Yes.

 

My hardware is :

Gen8 HP microserver with Xeon E3-1220L CPU update

6Gb of RAM

 

I am using le last env (redpill-tool-chain_x86_64_v0.7.2) to build the image with MAC OS big sur platform., and docker installed.

 

My bromolow_user_config.json:

content is (xx and yy are replacing real values and pid/vid are the one from my USB key):

{
  "extra_cmdline": {
    "pid": "0xFFF7",
    "vid": "0x203A",
    "sn": "yyyyyyyyyyyyy",
    "mac1": "xxxxxxxxxxxx"
  },
  "synoinfo": {},
  "ramdisk_copy": {}
}

 

Commands to build the image:

cd ~/Desktop/redpill-tool-chain_x86_64_v0.7.2
sudo chmod 777 redpill_tool_chain.sh

sh ./redpill_tool_chain.sh build bromolow-7.0.1-42214
sh ./redpill_tool_chain.sh auto bromolow-7.0.1-42214
 

The image is written on USB key with BalenaEtcher

 

To have it working,(booting)  I set the 1st (FAT32) partition as active  (with MiniTool Partition Wizard).

  • Thanks 1
Link to comment
Share on other sites

1 hour ago, p33ps said:

 

Sorry but, can someone give me with this?

 

Thanks!

 

I have the same problem with DSM 7.0.1 RC -> Bug CPU, see log.

With 6.2.x it works.

 

[  260.026023] BUG: soft lockup - CPU#0 stuck for 41s! [synofoto-face-e:12009]
[  260.026023] Modules linked in: fuse 8021q vhost_scsi(O) vhost(O) 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) udf isofs loop synoacl_vfs(PO) btrfs zstd_decompress ecryptfs zstd_compress xxhash xor raid6_pq zram(C) glue_helper lrw gf128mul ablk_helper bromolow_synobios(PO) hid_generic usbhid hid usblp bnx2x(O) mdio mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) qede(O) qed(O) atlantic_v2(O) atlantic(O) tn40xx(O) i40e(O) ixgbe(O) be2net(O) i2c_algo_bit igb(O) dca e1000e(O) sg dm_snapshot crc_itu_t crc_ccitt psnap p8022 llc zlib_deflate libcrc32c hfsplus md4 hmac sit tunnel4 ipv6 flashcache_syno(O) flashcache(O) syno_flashcache_control(O) dm_mod cryptd arc4 sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance mperf processor thermal_sys cpufreq_stats freq_table vxlan ip_tunnel virtio_scsi(OF) virtio_net(OF) virtio_blk(OF) virtio_pci(OF) virtio_ring(OF) virtio(OF) etxhci_hcd usb_storage xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common redpill(OF) [last unloaded: bromolow_synobios]
[  260.026023] CPU: 0 PID: 12009 Comm: synofoto-face-e Tainted: PF        C O 3.10.108 #42214
[  260.026023] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
[  260.026023] task: ffff880048620040 ti: ffff880051fcc000 task.ti: ffff880051fcc000
[  260.026023] RIP: 0010:[<ffffffff81090492>]  [<ffffffff81090492>] smp_call_function_many+0x262/0x290
[  260.026023] RSP: 0000:ffff880051fcfc68  EFLAGS: 00000202
[  260.026023] RAX: ffff88007dd15cc8 RBX: 0000000000000000 RCX: 0000000000000002
[  260.026023] RDX: ffff88007dd15cc8 RSI: 0000000000000008 RDI: 00000000000000ff
[  260.026023] RBP: ffff88007dd95cc8 R08: ffff88007dc139c8 R09: 0000000000000020
[  260.026023] R10: 0000000000004f5c R11: 0000000000000000 R12: 0000000000000000
[  260.026023] R13: 0000000000000000 R14: 0000000000000000 R15: ffffffff81893940
[  260.026023] FS:  00007f6a7dffb700(0000) GS:ffff88007dc00000(0000) knlGS:0000000000000000
[  260.026023] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  260.026023] CR2: 00007f6a22001048 CR3: 00000000486c0000 CR4: 00000000000006f0
[  260.026023] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  260.026023] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  260.026023] Stack:
[  260.026023]  ffff88007dc139c8 ffff88007dd93980 0000000181893940 0000000000013980
[  260.026023]  ffff88007a0c0400 ffff880051fcfcf8 ffff88007a0c06d8 00007f6a22001048
[  260.026023]  ffffea0000f97bc0 ffff88004747e008 ffffffff81030372 ffff88007a0c0400
[  260.026023] Call Trace:
[  260.026023]  [<ffffffff81030372>] ? flush_tlb_page+0x72/0x130
[  260.026023]  [<ffffffff81117572>] ? ptep_clear_flush+0x22/0x30
[  260.026023]  [<ffffffff81106a0d>] ? do_wp_page+0x2ad/0x8c0
[  260.026023]  [<ffffffff81107e6d>] ? handle_pte_fault+0x38d/0x9e0
[  260.026023]  [<ffffffff81108775>] ? handle_mm_fault+0x135/0x2e0
[  260.026023]  [<ffffffff814aba0a>] ? __do_page_fault+0x14a/0x500
[  260.026023]  [<ffffffff8128e94c>] ? rwsem_wake+0x3c/0x50
[  260.026023]  [<ffffffff81294ee7>] ? call_rwsem_wake+0x17/0x30
[  260.026023]  [<ffffffff814aff11>] ? system_call_after_swapgs+0xae/0x13f
[  260.026023]  [<ffffffff814a8883>] ? error_swapgs+0xa4/0xba
[  260.026023]  [<ffffffff814a8877>] ? error_swapgs+0x98/0xba
[  260.026023]  [<ffffffff814a8883>] ? error_swapgs+0xa4/0xba
[  260.026023]  [<ffffffff814a8877>] ? error_swapgs+0x98/0xba
[  260.026023]  [<ffffffff814a8883>] ? error_swapgs+0xa4/0xba
[  260.026023]  [<ffffffff814a8877>] ? error_swapgs+0x98/0xba
[  260.026023]  [<ffffffff814a8883>] ? error_swapgs+0xa4/0xba
[  260.026023]  [<ffffffff814a8877>] ? error_swapgs+0x98/0xba
[  260.026023]  [<ffffffff814a8883>] ? error_swapgs+0xa4/0xba
[  260.026023]  [<ffffffff814a8592>] ? page_fault+0x22/0x30
[  260.026023] Code: 8d 81 00 89 c1 0f 8e 1e fe ff ff 48 98 48 8b 13 48 03 14 c5 e0 8d 8a 81 f6 42 20 01 48 89 d0 74 c8 0f 1f 84 00 00 00 00 00 f3 90 <f6> 40 20 01 75 f8 eb b6 66 0f 1f 44 00 00 48 89 ea 4c 89 fe 44 

 

 

Link to comment
Share on other sites

12 hours ago, FiberInternetUser said:

After updating to the latest loader from @ThorGroup for apollolake-7.0.1-42214 on bare metal.  Getting the following continuous output from the serial console port after the login prompt.

 

 

Getting this notification from the USB Boot Thumbdrive.

 

USB_Drive_Error.JPG.968cf149af5e9403a2abb6894b72387c.JPG

 

I too have the same behaviour. It sees the usb boot stick.

 

[  919.179145] Initializing XFRM netlink socket
[  919.208029] Netfilter messages via NETLINK v0.30.
[  919.250782] audit: type=1325 audit(1631632358.130:13): table=nat family=2 entries=7
[  919.263884] audit: type=1325 audit(1631632358.143:14): table=nat family=2 entries=11
[  919.283309] audit: type=1325 audit(1631632358.162:15): table=filter family=2 entries=12
[  919.391771] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
[  921.892097] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sda
[  921.892479] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  922.134939] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdb
[  922.135304] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  922.294586] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdc
[  922.294954] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  922.329003] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdd
[  922.329449] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  927.976524] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sda
[  927.976892] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  928.210894] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdb
[  928.211301] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  928.424925] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdc
[  928.425326] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  928.430552] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdd
[  928.430919] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  929.973230] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sda
[  929.973598] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  930.207479] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdb
[  930.207873] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  930.449786] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdc
[  930.450221] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  930.455797] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdd
[  930.456246] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  938.389994] audit_printk_skb: 84 callbacks suppressed
[  938.390268] audit: type=1123 audit(1631632377.270:44): pid=15145 uid=0 auid=4294967295 ses=4294967295 msg='cwd="/" cmd=7069686F6C652D46544C2074657374 terminal=? res=success'
[  945.354303] <redpill/smart_shim.c:794> Handling ioctl(0x128b) for /dev/sdq
[  945.354684] <redpill/smart_shim.c:809> sd_ioctl(0x128b) - not a hooked ioctl, noop
[  945.398283] <redpill/smart_shim.c:794> Handling ioctl(0x128b) for /dev/sdq
[  945.398665] <redpill/smart_shim.c:809> sd_ioctl(0x128b) - not a hooked ioctl, noop
[  945.646231] <redpill/smart_shim.c:794> Handling ioctl(0x128b) for /dev/sdq
[  945.646619] <redpill/smart_shim.c:809> sd_ioctl(0x128b) - not a hooked ioctl, noop
[  945.649615] <redpill/smart_shim.c:794> Handling ioctl(0x128b) for /dev/sdq
[  945.649980] <redpill/smart_shim.c:809> sd_ioctl(0x128b) - not a hooked ioctl, noop
[  945.839342] <redpill/smart_shim.c:794> Handling ioctl(0x5331) for /dev/sdq
[  945.839709] <redpill/smart_shim.c:809> sd_ioctl(0x5331) - not a hooked ioctl, noop
[  945.845348] <redpill/smart_shim.c:794> Handling ioctl(0x5331) for /dev/sdq
[  945.845716] <redpill/smart_shim.c:809> sd_ioctl(0x5331) - not a hooked ioctl, noop
[  946.061469] <redpill/smart_shim.c:794> Handling ioctl(0x5331) for /dev/sdq
[  946.061834] <redpill/smart_shim.c:809> sd_ioctl(0x5331) - not a hooked ioctl, noop
[  952.472659] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sda
[  952.473047] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  952.639016] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdb
[  952.639381] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  952.723082] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdc
[  952.723448] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  952.728590] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdd
[  952.729015] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  953.209624] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sda
[  953.210028] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  953.391592] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdb
[  953.391989] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  953.608714] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdc
[  953.609107] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  953.618258] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdd
[  953.618626] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  962.993685] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sda
[  962.994052] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  962.999312] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdb
[  962.999702] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  963.003186] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdc
[  963.003600] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  963.004214] <redpill/smart_shim.c:794> Handling ioctl(0x2285) for /dev/sdd
[  963.004628] <redpill/smart_shim.c:809> sd_ioctl(0x2285) - not a hooked ioctl, noop
[  965.265597] <redpill/smart_shim.c:794> Handling ioctl(0x128b) for /dev/sdq
[  965.265963] <redpill/smart_shim.c:809> sd_ioctl(0x128b) - not a hooked ioctl, noop
[  965.289347] <redpill/smart_shim.c:794> Handling ioctl(0x128b) for /dev/sdq
[  965.289730] <redpill/smart_shim.c:809> sd_ioctl(0x128b) - not a hooked ioctl, noop

 

xpeno error.png

Edited by ct85msi
  • Like 1
Link to comment
Share on other sites

On 9/13/2021 at 11:42 AM, WiteWulf said:

Do I need to be in a different directory in the docker container to run the git fetch?

 

*edit it was @pocopico I was meant to quote not Witewulf. apologies

It was Bromolow , I found them thank you (search not working for tg3, but tg3.ko works :)

 

So I need to insmod libphy.ko and tg3.ko .

do you know can I unpack rd.qz with 7z in windows (after mounting first partition of the .img file) 

then add the modules . 

then add insmod lines (any issue with waiting for libphy.ko to load first )

repack rd.qz with 7z 

Edited by scoobdriver
Wrong user
Link to comment
Share on other sites

I've tried and tried to get the most recent redpill version for bromolow 7.0.1-RC1 to build with @haydibe's 0.7.2 and 0.7.3 docker scripts on macOS 11.5.2 and it kept failing with Docker Desktop for macOS. I installed docker from home-brew instead and still got the same failure when building the image at the end. I gave up and created a Debian 10 VM in VMware Fusion and built it on there (using haydibe's docker script again) and it worked first time.. I know others have reported this working on a similar Mac setup, but I just couldn't make it work for some reason.

 

If you're having similar issues and don't have access to VMware fusion you could give virtualbox a go instead.

 

I've not tried booting my Gen8 off the new image yet, I'll give that a go tomorrow

Link to comment
Share on other sites

Il y a 2 heures, Rikk a dit :

My hardware is :

Gen8 HP microserver with Xeon E3-1220L CPU update

6Gb of RAM

PCI network card with 82574L chip

 

I am using le last env (redpill-tool-chain_x86_64_v0.7.2) to build the image with MAC OS big sur platform., and docker installed.

 

My bromolow_user_config.json:

content is (xx and yy are replacing real values and pid/vid are the one from my USB key):

{
  "extra_cmdline": {
    "pid": "0xFFF7",
    "vid": "0x203A",
    "sn": "yyyyyyyyyyyyy",
    "mac1": "xxxxxxxxxxxx"
  },
  "synoinfo": {},
  "ramdisk_copy": {}
}

 

Commands to build the image:

cd ~/Desktop/redpill-tool-chain_x86_64_v0.7.2
sudo chmod 777 redpill_tool_chain.sh

sh ./redpill_tool_chain.sh build bromolow-7.0.1-42214
sh ./redpill_tool_chain.sh auto bromolow-7.0.1-42214
 

The image is written on USB key with BalenaEtcher

 

To have it working,(booting)  I set the 1st (FAT32) partition as active  (with MiniTool Partition Wizard).

 

it is working well .

 

Great work, really.

Congratulation to the Team.

 

Edited by Rikk
Link to comment
Share on other sites

1 hour ago, scoobdriver said:

 

*edit it was @pocopico I was meant to quote not Witewulf. apologies

It was Bromolow , I found them thank you (search not working for tg3, but tg3.ko works :)

 

So I need to insmod libphy.ko and tg3.ko .

do you know can I unpack rd.qz with 7z in windows (after mounting first partition of the .img file) 

then add the modules . 

then add insmod lines (any issue with waiting for libphy.ko to load first )

repack rd.qz with 7z 

 

Try this and see if it works for you. Its for 3615 v7.0.1. Extract and rename to rd.gz on first partition if you are booting with legacy bios or second if you are booting with EFI.

 

- I have added inetd start by default (telnet will work as soon as you get ip from DHCP for troubleshooting)

- modules tg3, mptsas, mpt3sas, vmxnet3.ko, libphy.ko

 

Of course there is another way to load extra modules but i havent had the time to try yet.

 

rd.gz.microserver.7z

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

50 minutes ago, pocopico said:

Try this and see if it works for you. Its for 3615 v7.0.1. Extract and rename to rd.gz on first partition if you are booting with legacy bios or second if you are booting with EFI.

 

Fantastic I will try this out .. 

I tried adding myself but I'm not sure I am unpacking / repacking rd.gz correctly . 

 

When I Extract your file you have just posted rd.gz appears as a folder , can I just copy that and its contents , or does it need packing and how? . 

 

I am booting Legacy, I don't believe G8 supports EFI,   (My Gen8 has a HBA card, is the mptsas, mpt3sas enough , or do I need to add a parameter ? )

 

I am using serial port via the ilo to monitor . 

The below was the output of my attempt , I don't think it was seeing rd.gz after me modifying it . 

 

[    2.575384] RAMDISK: Couldn't find valid RAM disk image starting at 0.
[    2.606204] EXT3-fs (md0): error: unable to read superblock
[    2.632985] EXT2-fs (md0): error: unable to read superblock
[    2.660127] EXT4-fs (md0): unable to read superblock
[    2.683766] List of all partitions:
[    2.700178] No filesystem could mount root, tried:  ext3 ext2 ext4
[    2.729188] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)
[    2.768735] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 3.10.108 #42214
[    2.799245] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019
[    2.832391]  ffffffff814a2759 ffffffff814a16b1 ffff880300000010 ffff8803f522feb0
[    2.867941]  ffff8803f522fe48 ffff8803f522fea0 ffff8803f522feb8 0000000000000012
[    2.903870]  0000000000000000 000000000000000a ffffffff8171374b ffff8803f259c00f
[    2.939102] Call Trace:
[    2.950629]  [<ffffffff814a2759>] ? dump_stack+0xc/0x15
[    2.975263]  [<ffffffff814a16b1>] ? panic+0xbb/0x1df
[    2.998704]  [<ffffffff818c42ec>] ? mount_block_root+0x33e/0x33e
[    3.027430]  [<ffffffff818c3762>] ? loglevel+0x31/0x31
[    3.051687]  [<ffffffff818c45c1>] ? prepare_namespace+0x162/0x198
[    3.080371]  [<ffffffff818c3f01>] ? kernel_init_freeable+0x1cb/0x1d8
[    3.110889]  [<ffffffff81495bf0>] ? rest_init+0x70/0x70
[    3.135962]  [<ffffffff81495bf5>] ? kernel_init+0x5/0x170
[    3.161040]  [<ffffffff814afe0d>] ? ret_from_fork+0x5d/0xb0
[    3.187694]  [<ffffffff81495bf0>] ? rest_init+0x70/0x70

 

Link to comment
Share on other sites

I think 7.0.1 has more under the hood changes than 7.0 or more under the hood bugs. Thinking to revert to 6.2.4-25556 and apply update 2 to mitigate Synology-SA-21:22 DSM but leaves still vulnerable to Synology-SA-21:25. 21:25 isn`t that important, only local users can exploit the vulnerability.

Edited by ct85msi
Link to comment
Share on other sites

42 minutes ago, WiteWulf said:

If you're extracting using the built in archive tools in Finder it will always extract to a new folder with the name of the archive file.


it’s the “keep expanding if possible” option that appears to be set by default which was causing it. It extracted and then further extracted automatically, 

sorted it by using windows , but good to have found the cause and the option to disable that. 

Link to comment
Share on other sites

"clean all" removed all images (last build + orphaned), but did only remove the build cache of orhaned images, but not the latest.

Now "clean all" will clean the build cache for the last build image as well.

 

re-uploaded with yumkey fix

 

 

redpill-tool-chain_x86_64_v0.7.4_fix.zip

Edited by haydibe
needed fix for apollolake-7.0.1-42214
  • Like 3
  • Thanks 2
Link to comment
Share on other sites

13 hours ago, haydibe said:

Seems I missed to test the bromolow-7.0.1 image... So this is the one that caused this mystery behavior. 

I disabled the build cache now by default - it can be turned on again in global_settings.json.

Now "clean all" deletes all images, including the last build one.

 

changes in v0.7.3 :

- fixed usage of label that determins the redpill-tool-chain images for clean up

- add `"docker.use_build_cache": "false"` to global_settings.json

- add `"docker.clean_images": "all"` to global_settings.json (set to orphaned to cleanup everything except the latest build)

 

See README.md for usage.

 

When I introduced labels, I must have made a last adjustment to the Dockerfile, which actual resulted in all images beeing created using the correct key, but with the wrong value (=all  identical) .

 

Please clean up your build cache and images to benefit from the fix:


docker builder prune --all --filter label=redpill-tool-chain
docker image ls --filter label=redpill-tool-chain --quiet | xargs docker image rm

 

 

redpill-tool-chain_x86_64_v0.7.3.zip 8.08 kB · 136 downloads

Can we please create a separate thread for this tool chain? Also it would be great if we were provided link to the github repository (if it's not already here or even created).

Link to comment
Share on other sites

26 minutes ago, haydibe said:

"clean all" removed all images (last build + orphaned), but did only remove the build cache of orhaned images, but not the latest.

Now "clean all" will clean the build cache for the last build image as well.

 

 

 

redpill-tool-chain_x86_64_v0.7.4.zip 8.08 kB · 6 downloads

 

I think there`s a problem, @jumkeydoesn`t have 7.0.1-42214 in master branch, only in devel.

 

         "id": "apollolake-7.0.1-42214",
            "platform_version": "apollolake-7.0.1-42214",
            "user_config_json": "apollolake_user_config.json",
            "docker_base_image": "debian:10-slim",
            "compile_with": "toolkit_dev",
            "download_urls": {
                "kernel": "https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/apollolake-source/linux-4.4.x.txz/download",
                "toolkit_dev": "https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.apollolake-7.0.dev.txz/download"
            },
            "redpill_lkm": {
                "source_url": "https://github.com/RedPill-TTG/redpill-lkm.git",
                "branch": "master"
            },
            "redpill_load": {
                "source_url": "https://github.com/jumkey/redpill-load.git",
                "branch": "master"
            }

it should be changed to develop branch or change to what was in 0.7.3 , @chchia`s repo.

 

        {
            "id": "apollolake-7.0.1-42214",
            "platform_version": "apollolake-7.0.1-42214",
            "user_config_json": "apollolake_user_config.json",
            "docker_base_image": "debian:10-slim",
            "compile_with": "toolkit_dev",
            "download_urls": {
                "kernel": "https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/apollolake-source/linux-4.4.x.txz/download",
                "toolkit_dev": "https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.apollolake-7.0.dev.txz/download"
            },
            "redpill_lkm": {
                "source_url": "https://github.com/RedPill-TTG/redpill-lkm.git",
                "branch": "master"
            },
            "redpill_load": {
                "source_url": "https://github.com/chchia/redpill-load.git",
                "branch": "master"
            }
#############################################
/opt/redpill-load /opt
[#] Checking runtime for required tools... [OK]
[!] There doesn't seem to be a config for DS918+ platform running 7.0.1-42214 (checked /opt/redpill-load/config/DS918+/7.0.1-42214/config.json)

*** Process will exit ***
make: *** [Makefile:33: build_redpill_load] Error 1
root@zen:/home/msi/Downloads/xpeno# 

L.E. what I was saying ..

Edited by ct85msi
Link to comment
Share on other sites

4 hours ago, dodo-dk said:

 

I have the same problem with DSM 7.0.1 RC -> Bug CPU, see log.

With 6.2.x it works.

 


[  260.026023] BUG: soft lockup - CPU#0 stuck for 41s! [synofoto-face-e:12009]
[  260.026023] Modules linked in: fuse 8021q vhost_scsi(O) vhost(O) 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) udf isofs loop synoacl_vfs(PO) btrfs zstd_decompress ecryptfs zstd_compress xxhash xor raid6_pq zram(C) glue_helper lrw gf128mul ablk_helper bromolow_synobios(PO) hid_generic usbhid hid usblp bnx2x(O) mdio mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) qede(O) qed(O) atlantic_v2(O) atlantic(O) tn40xx(O) i40e(O) ixgbe(O) be2net(O) i2c_algo_bit igb(O) dca e1000e(O) sg dm_snapshot crc_itu_t crc_ccitt psnap p8022 llc zlib_deflate libcrc32c hfsplus md4 hmac sit tunnel4 ipv6 flashcache_syno(O) flashcache(O) syno_flashcache_control(O) dm_mod cryptd arc4 sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance mperf processor thermal_sys cpufreq_stats freq_table vxlan ip_tunnel virtio_scsi(OF) virtio_net(OF) virtio_blk(OF) virtio_pci(OF) virtio_ring(OF) virtio(OF) etxhci_hcd usb_storage xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common redpill(OF) [last unloaded: bromolow_synobios]
[  260.026023] CPU: 0 PID: 12009 Comm: synofoto-face-e Tainted: PF        C O 3.10.108 #42214
[  260.026023] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
[  260.026023] task: ffff880048620040 ti: ffff880051fcc000 task.ti: ffff880051fcc000
[  260.026023] RIP: 0010:[<ffffffff81090492>]  [<ffffffff81090492>] smp_call_function_many+0x262/0x290
[  260.026023] RSP: 0000:ffff880051fcfc68  EFLAGS: 00000202
[  260.026023] RAX: ffff88007dd15cc8 RBX: 0000000000000000 RCX: 0000000000000002
[  260.026023] RDX: ffff88007dd15cc8 RSI: 0000000000000008 RDI: 00000000000000ff
[  260.026023] RBP: ffff88007dd95cc8 R08: ffff88007dc139c8 R09: 0000000000000020
[  260.026023] R10: 0000000000004f5c R11: 0000000000000000 R12: 0000000000000000
[  260.026023] R13: 0000000000000000 R14: 0000000000000000 R15: ffffffff81893940
[  260.026023] FS:  00007f6a7dffb700(0000) GS:ffff88007dc00000(0000) knlGS:0000000000000000
[  260.026023] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  260.026023] CR2: 00007f6a22001048 CR3: 00000000486c0000 CR4: 00000000000006f0
[  260.026023] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  260.026023] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  260.026023] Stack:
[  260.026023]  ffff88007dc139c8 ffff88007dd93980 0000000181893940 0000000000013980
[  260.026023]  ffff88007a0c0400 ffff880051fcfcf8 ffff88007a0c06d8 00007f6a22001048
[  260.026023]  ffffea0000f97bc0 ffff88004747e008 ffffffff81030372 ffff88007a0c0400
[  260.026023] Call Trace:
[  260.026023]  [<ffffffff81030372>] ? flush_tlb_page+0x72/0x130
[  260.026023]  [<ffffffff81117572>] ? ptep_clear_flush+0x22/0x30
[  260.026023]  [<ffffffff81106a0d>] ? do_wp_page+0x2ad/0x8c0
[  260.026023]  [<ffffffff81107e6d>] ? handle_pte_fault+0x38d/0x9e0
[  260.026023]  [<ffffffff81108775>] ? handle_mm_fault+0x135/0x2e0
[  260.026023]  [<ffffffff814aba0a>] ? __do_page_fault+0x14a/0x500
[  260.026023]  [<ffffffff8128e94c>] ? rwsem_wake+0x3c/0x50
[  260.026023]  [<ffffffff81294ee7>] ? call_rwsem_wake+0x17/0x30
[  260.026023]  [<ffffffff814aff11>] ? system_call_after_swapgs+0xae/0x13f
[  260.026023]  [<ffffffff814a8883>] ? error_swapgs+0xa4/0xba
[  260.026023]  [<ffffffff814a8877>] ? error_swapgs+0x98/0xba
[  260.026023]  [<ffffffff814a8883>] ? error_swapgs+0xa4/0xba
[  260.026023]  [<ffffffff814a8877>] ? error_swapgs+0x98/0xba
[  260.026023]  [<ffffffff814a8883>] ? error_swapgs+0xa4/0xba
[  260.026023]  [<ffffffff814a8877>] ? error_swapgs+0x98/0xba
[  260.026023]  [<ffffffff814a8883>] ? error_swapgs+0xa4/0xba
[  260.026023]  [<ffffffff814a8877>] ? error_swapgs+0x98/0xba
[  260.026023]  [<ffffffff814a8883>] ? error_swapgs+0xa4/0xba
[  260.026023]  [<ffffffff814a8592>] ? page_fault+0x22/0x30
[  260.026023] Code: 8d 81 00 89 c1 0f 8e 1e fe ff ff 48 98 48 8b 13 48 03 14 c5 e0 8d 8a 81 f6 42 20 01 48 89 d0 74 c8 0f 1f 84 00 00 00 00 00 f3 90 <f6> 40 20 01 75 f8 eb b6 66 0f 1f 44 00 00 48 89 ea 4c 89 fe 44 

 

 

 

Hmm, maybe we should report it. Idk what's the way to do it.

Link to comment
Share on other sites

Hello,

 

I would like to know if there is a documentation about how to start with this amazing loader.

In the past, I used jun loader on my actual xpenology but I want to install a new one on dsm7.

 

If someone have a link are few explanation, I really appreciate.

 

 

 

Link to comment
Share on other sites

47 minutes ago, SpiRe said:

Can we please create a separate thread for this tool chain?

Thought about it... but this is rather an addition to redpill, than XPE development, isn't it? 

 

47 minutes ago, SpiRe said:

Also it would be great if we were provided link to the github repository (if it's not already here or even created).

I understand that you volunteer to push it to github? Be my guest :)

Everyone is free to modify the sources, publish modifications here or push them to github.

 

I claim no ownership of the toolchain builder - as such I would appreciate if my name is not mentioned in the github repo.  I prefer to not leave my marks on Github with it... 

 

Update: I forget to mention that I uploaded the fix for 0.7.4 in the original post pointing to the development branch for apollolake-7.0.1-42214.

 

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

Guest
This topic is now closed to further replies.
×
×
  • Create New...