RedPill - the new loader for 6.2.4 - Discussion

[WiteWulf]

1 hour ago, ghtester said:

AFAIK 2543branch/bromolow-source is 3.10.105, as 3.10.108 was not published yet.

I wonder which parameters for compilation with toolchain you are using to get working .ko modules for DSM 7.0.1 RC. I have always failed - despite the compilation was finished, the bromolow modules were unusable for me. With 2543branch sources the compiled modules have 3.10.105 magic and when the common kernel sources 3.10.108 are used, there're kernel exceptions when I try to load modules. On the other side, there are some working network drivers for bromolow & DSM 7.0.1 shared here earlier by some people. So what's the trick I am missing? 😕

As Haydibe pointed out, it's not actually using the kernel source at the moment, it's using the toolkit instead, so the kernel source line is actually irrelevant.

[ghtester]

33 minutes ago, WiteWulf said:

As Haydibe pointed out, it's not actually using the kernel source at the moment, it's using the toolkit instead, so the kernel source line is actually irrelevant.

Yes I know but I don't know how to get (compile) necessary modules with toolkit/toolchain only, without kernel sources (can anybody share a command with specific parameters to get - for instance - the ata_piix.ko compiled (ich7 sata support - CONFIG_ATA_PIIX) without kernel sources and working in DSM 7.0.1 (based on kernel 3.10.108) on bromolow/ DS3615xs ?).

[pocopico]

2 hours ago, ghtester said:

Yes I know but I don't know how to get (compile) necessary modules with toolkit/toolchain only, without kernel sources (can anybody share a command with specific parameters to get - for instance - the ata_piix.ko compiled (ich7 sata support - CONFIG_ATA_PIIX) without kernel sources and working in DSM 7.0.1 (based on kernel 3.10.108) on bromolow/ DS3615xs ?).

 

You need to compile modules for 3.10.108 SMP mod_unload  but anyway, here it is

 

  

 

 

 

Edited September 24, 2021 by pocopico
Wrong file

[ghtester]

23 minutes ago, pocopico said:

 

You need to compile modules for 3.10.108+ SMP mod_unload  but anyway, here it is

 

  ata_piix.7z 96.79 kB · 0 downloads  

 

 

 

Thank you but it does not work for bromolow - the correct version magic is 3.10.108 SMP ( 3.10.108 #42214 SMP Sat Aug 28 02:41:43 CST 2021 x86_64 GNU/Linux synology_bromolow_3615xs), not 3.10.108+ SMP mod_unload

That's why load attempt leads to error message:

insmod: ERROR: could not insert module ata_piix/ata_piix.ko: Invalid module format

So the question is still the same - is there anybody who could share a compilation command with proper parameters I should use to compile bromolow modules for DSM 7.0.1 RC with toolchain only please?

Edited September 24, 2021 by ghtester

[pocopico]

25 minutes ago, ghtester said:

Thank you but it does not work for bromolow - the correct version magic is 3.10.108 ( 3.10.108 #42214 SMP Sat Aug 28 02:41:43 CST 2021 x86_64 GNU/Linux synology_bromolow_3615xs), not 3.10.108+

That's why load attempt leads to error message:

insmod: ERROR: could not insert module ata_piix/ata_piix.ko: Invalid module format

So the question is still the same - is there anybody who could share a compilation command with proper parameters I should use to compile bromolow modules for DSM 7.0.1 RC please?

 

True sorry, i mixed things up a bit. DS918+ 7. uses 4.4.180+ and DS3615xs DSM 7 uses 3.10.108 here you are : 

 

 

Edited September 24, 2021 by pocopico
Not cross compiled

[ghtester]

15 minutes ago, pocopico said:

 

True sorry, i mixed things up a bit. DS918+ 7. uses 4.4.180+ and DS3615xs DSM 7 uses 3.10.108 here you are : 

 

ata_piix.7z 96.72 kB · 0 downloads

Thanks again, this module can be load but leads to crash so I suppose it was compiled with generic kernel 3.10.108 sources. I tried that as well (and none of modules I needed was working) but as already confirmed by @ThorGroup, this is not a proper way (although maybe some drivers can work).

 insmod ata_piix/ata_piix.ko
Killed

[91701.976157] WARNING: module 'ata_piix' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
[91701.987932] ata_piix 0000:00:1f.5: version 2.13
[91701.993164] ata_piix 0000:00:1f.5: MAP [
[91701.997551]  P0 -- P1 -- ]
[91702.151055] BUG: unable to handle kernel NULL pointer dereference at 000000000000001b
[91702.152013] IP: [<ffffffffa0edfdc7>] piix_init_one+0x527/0x8dd [ata_piix]
[91702.152013] PGD 78e74067 PUD 977a2067 PMD 0
[91702.152013] Oops: 0000 [#1] SMP
[91702.152013] Modules linked in: ata_piix(F+) 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) evdev(OF) button(OF) 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)
[91702.190422]  dm_mod cryptd arc4 sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq mperf processor thermal_sys cpufreq_stats freq_table vxlan ip_tunnel etxhci_hcd usb_storage xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common redpill(OF) [last unloaded: bromolow_synobios]
[91702.190422] CPU: 0 PID: 10438 Comm: insmod Tainted: PF        C O 3.10.108 #42214
[91702.190422] Hardware name: HP ProLiant ML110 G5/ProLiant ML110 G5, BIOS O15    10/25/2010
[91702.190422] task: ffff88009b585040 ti: ffff880071020000 task.ti: ffff880071020000
[91702.190422] RIP: 0010:[<ffffffffa0edfdc7>]  [<ffffffffa0edfdc7>] piix_init_one+0x527/0x8dd [ata_piix]
[91702.190422] RSP: 0018:ffff880071023b98  EFLAGS: 00010206
[91702.190422] RAX: ffffffffa0ee26b0 RBX: ffff8800b9793000 RCX: ffff8800a8efea58
[91702.190422] RDX: ffffffffa0ee26b0 RSI: 0000000000000282 RDI: ffffffff819b7080
[91702.190422] RBP: 0000000000000000 R08: ffff880071020000 R09: 0020ee39e1f9050d
[91702.190422] R10: ffffffffffffffff R11: 0000000225c17d03 R12: 0000000030000002
[91702.190422] R13: ffff8800b9793098 R14: 0000000000000000 R15: ffff8800b9793098
[91702.190422] FS:  00007fcfc8b3b540(0000) GS:ffff8800bda00000(0000) knlGS:0000000000000000
[91702.190422] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[91702.190422] CR2: 000000000000001b CR3: 0000000071e50000 CR4: 00000000000007f0
[91702.190422] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[91702.190422] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[91702.190422] Stack:
[91702.190422]  ffff880035e95358 ffffffffa0ee26a0 0000000000000000 00000003000000d0
[91702.190422]  ffff020281121167 ffff8800a8efea58 ffff880071023bd8 ffff880071023c10
[91702.190422]  0000000030000002 0000000000000000 000000000000001f 0000000000000007
[91702.190422] Call Trace:
[91702.190422]  [<ffffffff812b2f11>] ? pci_device_probe+0x71/0xb0
[91702.190422]  [<ffffffff81326431>] ? driver_probe_device+0x81/0x3e0
[91702.190422]  [<ffffffff8132684b>] ? __driver_attach+0x7b/0x80
[91702.190422]  [<ffffffff813267d0>] ? __device_attach+0x40/0x40
[91702.190422]  [<ffffffff8132458d>] ? bus_for_each_dev+0x5d/0x90
[91702.190422]  [<ffffffff81325a68>] ? bus_add_driver+0x208/0x2a0
[91702.190422]  [<ffffffffa0ee6000>] ? 0xffffffffa0ee5fff
[91702.190422]  [<ffffffff81326e49>] ? driver_register+0x69/0x170
[91702.190422]  [<ffffffffa0ee6000>] ? 0xffffffffa0ee5fff
[91702.190422]  [<ffffffffa0ee601a>] ? piix_init+0x1a/0x29 [ata_piix]
[91702.190422]  [<ffffffff810002ea>] ? do_one_initcall+0x2a/0x170
[91702.190422]  [<ffffffff81095149>] ? load_module+0x1b89/0x2540
[91702.190422]  [<ffffffff812a2cb0>] ? ddebug_proc_write+0xf0/0xf0
[91702.190422]  [<ffffffff81095c9d>] ? SYSC_finit_module+0x7d/0xc0
[91702.190422]  [<ffffffff814affbe>] ? system_call_fastpath+0x1c/0x21
[91702.190422]  [<ffffffff814aff11>] ? system_call_after_swapgs+0xae/0x13f
[91702.190422] Code: 4c 8b 71 70 48 89 04 24 48 8b 00 48 8d 50 10 83 38 ff 74 40 48 83 c0 04 48 39 c2 75 f2 41 81 7d a4 86 80 20 29 0f 84 f9 01 00 00 <41> f6 46 1b 20 74 22 49 8b 85 d0 02 00 00 48 85 c0 74 16 49 8b
[91702.190422] RIP  [<ffffffffa0edfdc7>] piix_init_one+0x527/0x8dd [ata_piix]
[91702.190422]  RSP <ffff880071023b98>
[91702.190422] CR2: 000000000000001b
[91702.582086] ---[ end trace a9f85e2570baadf7 ]---

 

 

I'll try to inject this driver to bootloader to see if it crashes there as well...

And also I'll try to run it on a proper hardware (tried on ML110G5 by mistake...)

Edited September 24, 2021 by ghtester

[pocopico]

22 minutes ago, ghtester said:

Thanks again, this module can be load but leads to crash so I suppose it was compiled with generic kernel 3.10.108 sources. I tried that as well (and none of modules I needed was working) but as already confirmed by @ThorGroup, this is not a proper way (although maybe some drivers can work).

 insmod ata_piix/ata_piix.ko
Killed

[91701.976157] WARNING: module 'ata_piix' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
[91701.987932] ata_piix 0000:00:1f.5: version 2.13
[91701.993164] ata_piix 0000:00:1f.5: MAP [
[91701.997551]  P0 -- P1 -- ]
[91702.151055] BUG: unable to handle kernel NULL pointer dereference at 000000000000001b
[91702.152013] IP: [<ffffffffa0edfdc7>] piix_init_one+0x527/0x8dd [ata_piix]
[91702.152013] PGD 78e74067 PUD 977a2067 PMD 0
[91702.152013] Oops: 0000 [#1] SMP
[91702.152013] Modules linked in: ata_piix(F+) 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) evdev(OF) button(OF) 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)
[91702.190422]  dm_mod cryptd arc4 sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq mperf processor thermal_sys cpufreq_stats freq_table vxlan ip_tunnel etxhci_hcd usb_storage xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common redpill(OF) [last unloaded: bromolow_synobios]
[91702.190422] CPU: 0 PID: 10438 Comm: insmod Tainted: PF        C O 3.10.108 #42214
[91702.190422] Hardware name: HP ProLiant ML110 G5/ProLiant ML110 G5, BIOS O15    10/25/2010
[91702.190422] task: ffff88009b585040 ti: ffff880071020000 task.ti: ffff880071020000
[91702.190422] RIP: 0010:[<ffffffffa0edfdc7>]  [<ffffffffa0edfdc7>] piix_init_one+0x527/0x8dd [ata_piix]
[91702.190422] RSP: 0018:ffff880071023b98  EFLAGS: 00010206
[91702.190422] RAX: ffffffffa0ee26b0 RBX: ffff8800b9793000 RCX: ffff8800a8efea58
[91702.190422] RDX: ffffffffa0ee26b0 RSI: 0000000000000282 RDI: ffffffff819b7080
[91702.190422] RBP: 0000000000000000 R08: ffff880071020000 R09: 0020ee39e1f9050d
[91702.190422] R10: ffffffffffffffff R11: 0000000225c17d03 R12: 0000000030000002
[91702.190422] R13: ffff8800b9793098 R14: 0000000000000000 R15: ffff8800b9793098
[91702.190422] FS:  00007fcfc8b3b540(0000) GS:ffff8800bda00000(0000) knlGS:0000000000000000
[91702.190422] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[91702.190422] CR2: 000000000000001b CR3: 0000000071e50000 CR4: 00000000000007f0
[91702.190422] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[91702.190422] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[91702.190422] Stack:
[91702.190422]  ffff880035e95358 ffffffffa0ee26a0 0000000000000000 00000003000000d0
[91702.190422]  ffff020281121167 ffff8800a8efea58 ffff880071023bd8 ffff880071023c10
[91702.190422]  0000000030000002 0000000000000000 000000000000001f 0000000000000007
[91702.190422] Call Trace:
[91702.190422]  [<ffffffff812b2f11>] ? pci_device_probe+0x71/0xb0
[91702.190422]  [<ffffffff81326431>] ? driver_probe_device+0x81/0x3e0
[91702.190422]  [<ffffffff8132684b>] ? __driver_attach+0x7b/0x80
[91702.190422]  [<ffffffff813267d0>] ? __device_attach+0x40/0x40
[91702.190422]  [<ffffffff8132458d>] ? bus_for_each_dev+0x5d/0x90
[91702.190422]  [<ffffffff81325a68>] ? bus_add_driver+0x208/0x2a0
[91702.190422]  [<ffffffffa0ee6000>] ? 0xffffffffa0ee5fff
[91702.190422]  [<ffffffff81326e49>] ? driver_register+0x69/0x170
[91702.190422]  [<ffffffffa0ee6000>] ? 0xffffffffa0ee5fff
[91702.190422]  [<ffffffffa0ee601a>] ? piix_init+0x1a/0x29 [ata_piix]
[91702.190422]  [<ffffffff810002ea>] ? do_one_initcall+0x2a/0x170
[91702.190422]  [<ffffffff81095149>] ? load_module+0x1b89/0x2540
[91702.190422]  [<ffffffff812a2cb0>] ? ddebug_proc_write+0xf0/0xf0
[91702.190422]  [<ffffffff81095c9d>] ? SYSC_finit_module+0x7d/0xc0
[91702.190422]  [<ffffffff814affbe>] ? system_call_fastpath+0x1c/0x21
[91702.190422]  [<ffffffff814aff11>] ? system_call_after_swapgs+0xae/0x13f
[91702.190422] Code: 4c 8b 71 70 48 89 04 24 48 8b 00 48 8d 50 10 83 38 ff 74 40 48 83 c0 04 48 39 c2 75 f2 41 81 7d a4 86 80 20 29 0f 84 f9 01 00 00 <41> f6 46 1b 20 74 22 49 8b 85 d0 02 00 00 48 85 c0 74 16 49 8b
[91702.190422] RIP  [<ffffffffa0edfdc7>] piix_init_one+0x527/0x8dd [ata_piix]
[91702.190422]  RSP <ffff880071023b98>
[91702.190422] CR2: 000000000000001b
[91702.582086] ---[ end trace a9f85e2570baadf7 ]---

 

 

I'll try to inject this driver to bootloader to see if it crashes there as well...

 

Can you try this as well ? It has been compiled with the toolchain. The same process indeed works for some compiled modules and some not. 

 

ata_piix.7z

 

Yeah ... this panics as well .... 

 

Edited September 24, 2021 by pocopico

[ghtester]

1 hour ago, pocopico said:

 

Can you try this as well ? It has been compiled with the toolchain. The same process indeed works for some compiled modules and some not. 

 

ata_piix.7z 96.72 kB · 0 downloads

Thank you for another attempt, tried on the same (a bit improper) hardware with the same (crash) result. I'll try to put the module to bootloader and test on baremetal which has ICH7 controller.

 

[  342.304251] WARNING: module 'ata_piix' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
[  342.316049] ata_piix 0000:00:1f.5: version 2.13
[  342.321262] ata_piix 0000:00:1f.5: MAP [
[  342.325649]  P0 -- P1 -- ]
[  342.479052] BUG: unable to handle kernel NULL pointer dereference at 000000000000001b
[  342.480013] IP: [<ffffffffa0ef6dc7>] piix_init_one+0x527/0x8dd [ata_piix]
[  342.480013] PGD b650e067 PUD 80d53067 PMD 0
[  342.480013] Oops: 0000 [#1] SMP
[  342.480013] Modules linked in: ata_piix(F+) 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) evdev(OF) button(OF) 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)
[  342.557731]  dm_mod cryptd arc4 sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq mperf processor thermal_sys cpufreq_stats freq_table vxlan ip_tunnel etxhci_hcd usb_storage xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common redpill(OF) [last unloaded: bromolow_synobios]
[  342.557731] CPU: 0 PID: 12307 Comm: insmod Tainted: PF        C O 3.10.108 #42214
[  342.557731] Hardware name: HP ProLiant ML110 G5/ProLiant ML110 G5, BIOS O15    10/25/2010
[  342.557731] task: ffff88009e583820 ti: ffff8800b8264000 task.ti: ffff8800b8264000
[  342.557731] RIP: 0010:[<ffffffffa0ef6dc7>]  [<ffffffffa0ef6dc7>] piix_init_one+0x527/0x8dd [ata_piix]
[  342.557731] RSP: 0018:ffff8800b8267b98  EFLAGS: 00010206
[  342.557731] RAX: ffffffffa0ef96b0 RBX: ffff8800b9713000 RCX: ffff8800a49aae58
[  342.557731] RDX: ffffffffa0ef96b0 RSI: 0000000000000282 RDI: ffffffff819b7080
[  342.557731] RBP: 0000000000000000 R08: ffff8800b8264000 R09: 0036edc6ec893e1d
[  342.557731] R10: ffffffffffffffff R11: 0000000225c17d03 R12: 0000000030000002
[  342.557731] R13: ffff8800b9713098 R14: 0000000000000000 R15: ffff8800b9713098
[  342.557731] FS:  00007ff4166a0540(0000) GS:ffff8800bda00000(0000) knlGS:0000000000000000
[  342.557731] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  342.557731] CR2: 000000000000001b CR3: 0000000080bbe000 CR4: 00000000000007f0
[  342.557731] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  342.557731] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  342.557731] Stack:
[  342.557731]  ffff8800b83159d8 ffffffffa0ef96a0 0000000000000000 00000003000000d0
[  342.557731]  ffff020281121167 ffff8800a49aae58 ffff8800b8267bd8 ffff8800b8267c10
[  342.557731]  0000000030000002 0000000000000000 000000000000001f 0000000000000007
[  342.557731] Call Trace:
[  342.557731]  [<ffffffff812b2f11>] ? pci_device_probe+0x71/0xb0
[  342.557731]  [<ffffffff81326431>] ? driver_probe_device+0x81/0x3e0
[  342.557731]  [<ffffffff8132684b>] ? __driver_attach+0x7b/0x80
[  342.557731]  [<ffffffff813267d0>] ? __device_attach+0x40/0x40
[  342.557731]  [<ffffffff8132458d>] ? bus_for_each_dev+0x5d/0x90
[  342.557731]  [<ffffffff81325a68>] ? bus_add_driver+0x208/0x2a0
[  342.557731]  [<ffffffffa0efd000>] ? 0xffffffffa0efcfff
[  342.557731]  [<ffffffff81326e49>] ? driver_register+0x69/0x170
[  342.557731]  [<ffffffffa0efd000>] ? 0xffffffffa0efcfff
[  342.557731]  [<ffffffffa0efd01a>] ? piix_init+0x1a/0x29 [ata_piix]
[  342.557731]  [<ffffffff810002ea>] ? do_one_initcall+0x2a/0x170
[  342.557731]  [<ffffffff81095149>] ? load_module+0x1b89/0x2540
[  342.557731]  [<ffffffff812a2cb0>] ? ddebug_proc_write+0xf0/0xf0
[  342.557731]  [<ffffffff81095c9d>] ? SYSC_finit_module+0x7d/0xc0
[  342.557731]  [<ffffffff814affbe>] ? system_call_fastpath+0x1c/0x21
[  342.557731]  [<ffffffff814aff11>] ? system_call_after_swapgs+0xae/0x13f
[  342.557731] Code: 4c 8b 71 70 48 89 04 24 48 8b 00 48 8d 50 10 83 38 ff 74 40 48 83 c0 04 48 39 c2 75 f2 41 81 7d a4 86 80 20 29 0f 84 f9 01 00 00 <41> f6 46 1b 20 74 22 49 8b 85 d0 02 00 00 48 85 c0 74 16 49 8b
[  342.557731] RIP  [<ffffffffa0ef6dc7>] piix_init_one+0x527/0x8dd [ata_piix]
[  342.557731]  RSP <ffff8800b8267b98>
[  342.557731] CR2: 000000000000001b
[  342.910060] ---[ end trace 5be877b7c1576729 ]---

 

 

Edit - I can confirm the driver is crashing during the boot as well:

[   16.166975] WARNING: module 'ata_piix' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
[   16.236788] ata_piix 0000:00:1f.2: version 2.13
[   16.241627] ata880019ba4000
[   16.400001] RIP: 0010:[<ffffffffa00ffdc7>]  [<ffffffffa00ffdc7>] piix_init_one+0x527/0x8dd [ata_piix]
[   16.400001] RSP: 0018:ffff880019ba7b98  EFLAGS: 00010287
[   16.400001] RAX: ffffffffa0102788 RBX: ffff88001a44f800 RCX: ffff88001ece6618
[   16.400001] RDX: ffffffffa0102788 RSI: 0000000000000282 RDI: ffffffff819b7080
[   16.400001] RBP: 0000000000000000 R08: 0000000000000002 R09: 0000000000015d50
[   16.400001] R10: ffff88001f25eff0 R11: 0000000225c17d03 R12: 0000000010000002
[   16.400001] R13: ffff88001a44f898 R14: 0000000000000000 R15: ffff88001a44f898
[   16.400001] FS:  00007f9fc4b50740(0000) GS:ffff88001f400000(0000) knlGS:0000000000000000
[   16.400001] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   16.400001] CR2: 000000000000001b CR3: 000000001956c000 CR4: 00000000000007f0
[   16.400001] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   16.400001] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   16.400001] Stack:
[   16.400001]  ffff88001edf92d8 ffffffffa0102778 0000000000000000 00000003000000d0
[   16.400001]  ffff001181121167 ffff88001ece6618 ffff880019ba7bd8 ffff880019ba7c10
[   16.400001]  0000000010000003 0000000000000000 000000000000001f 0000000000000007
[   16.400001] Call Trace:
[   16.400001]  [<ffffffff812b2f11>] ? pci_device_probe+0x71/0xb0
[   16.400001]  [<ffffffff81326431>] ? driver_probe_device+0x81/0x3e0
[   16.400001]  [<ffffffff8132684b>] ? __driver_attach+0x7b/0x80
[   16.400001]  [<ffffffff813267d0>] ? __device_attach+0x40/0x40
[   16.400001]  [<ffffffff8132458d>] ? bus_for_each_dev+0x5d/0x90
[   16.400001]  [<ffffffff81325a68>] ? bus_add_driver+0x208/0x2a0
[   16.400001]  [<ffffffffa0106000>] ? 0xffffffffa0105fff
[   16.400001]  [<ffffffff81326e49>] ? driver_register+0x69/0x170
[   16.400001]  [<ffffffffa0106000>] ? 0xffffffffa0105fff
[   16.400001]  [<ffffffffa010601a>] ? piix_init+0x1a/0x29 [ata_piix]
[   16.400001]  [<ffffffff810002ea>] ? do_one_initcall+0x2a/0x170
[   16.400001]  [<ffffffff81095149>] ? load_module+0x1b89/0x2540
[   16.400001]  [<ffffffff812a2cb0>] ? ddebug_proc_write+0xf0/0xf0
[   16.400001]  [<ffffffff81095c9d>] ? SYSC_finit_module+0x7d/0xc0
[   16.400001]  [<ffffffff814affbe>] ? system_call_fastpath+0x1c/0x21
[   16.400001]  [<ffffffff814aff11>] ? system_call_after_swapgs+0xae/0x13f
[   16.400001] Code: 4c 8b 71 70 48 89 04 24 48 8b 00 48 8d 50 10 83 38 ff 74 40 48 83 c0 04 48 39 c2 75 f2 41 81 7d a4 86 80 20 29 0f 84 f9 01 00 00 <41> f6 46 1b 20 74 22 49 8b 85 d0 02 00 00 48 85 c0 74 16 49 8b
[   16.400001] RIP  [<ffffffffa00ffdc7>] piix_init_one+0x527/0x8dd [ata_piix]
[   16.400001]  RSP <ffff880019ba7b98>
[   16.400001] CR2: 000000000000001b
[   16.697324] ---[ end trace 68cf778a0238a203 ]---
Killed

Edited September 24, 2021 by ghtester

[Orphée]

Hello,

 

With @haydibe help and validation, here is the redpill_tool_chain v0.11

 

redpill-tool-chain_x86_64_v0.11.zip

 

New feature :

- Supports to bind a local redpill-lkm folder into the container (set `"docker.local_rp_lkm_use": "true"` and set `"docker.local_rp_lkm_path": "path/to/rp-lkm"`)

 

Thanks @haydibe

 

Tested with 6.2.4 and 7.0 both bromolow

I can't test for DS918+ as I don't have the CPU for. But it should be OK

[toyanucci]

Can someone recommend a compatible nic?

 

I waited all week for a HP NC360T to be delivered only to realize it's a pcie x4 and my j4105 motherboard only has a pcie x1 slot 😑

 

The onboard realtek nic should be compatible but for some reason it isn't working for me so I want to try using another nic.

[dodo-dk]

give Proxmox a chance

[toyanucci]

23 minutes ago, dodo-dk said:

give Proxmox a chance

It seems the onboard nic is working after all!

 

All along I had a sata drive connected when I tried to boot up and it would't boot at all. I unplugged the drive just now and could access the setup page within 2 minutes.  Now it's to figure out how to get the sata drive to work 😀

[toyanucci]

I let the usb boot up then I hot plugged the sata drive and hit refresh at the setup page and it came up.  Installing currently.

 

Everything is working with the test drive I'm using.  After installing it works perfectly on reboot as well and takes just about a minute from power on to when the DSM can be accessed.  Now to try to update my normal setup

Edited September 24, 2021 by toyanucci

[dateno1]

redpill-tool-chain_x86_64_v0.11 Build Tested

 

6.2.4 is no warning or error but 7.0 has warning

 

usb.h warning is seemed easy to fix

 

Can you fix it at next version?

[toyanucci]

Ok.  So I tried to update from within DSM 6.2 and it tried but hung at updating programs for over an hour so I hard reset.  I put the redpill usb in and it loaded up and said it needed to be reinstalled.  I reinstalled and kept settings and it updated and updated programs and now I'm on 7.0 baremetal.  Docker and everything is running great.

 

Thanks to everyone who helped me figure all this out and especially to everyone who contributed to redpill. I know all this takes a LOT of time to figure out, time that could be spent doing so many other things but the dedication to the community is what keeps the progress going here.

 

Thanks again!

[rok1]

6 hours ago, toyanucci said:

Can someone recommend a compatible nic?

 

I waited all week for a HP NC360T to be delivered only to realize it's a pcie x4 and my j4105 motherboard only has a pcie x1 slot 😑

 

The onboard realtek nic should be compatible but for some reason it isn't working for me so I want to try using another nic.

The HP360T is a great card, you can still make it work..

2 options...

1. Modify the slot with an exacto-knife or

2. Buy this: https://www.amazon.com/StarTech-com-Express-Profile-Extension-Adapter/dp/B0039XPS5W

 

 

Edited September 25, 2021 by rok1

[Orphée]

5 hours ago, dateno1 said:

redpill-tool-chain_x86_64_v0.11 Build Tested

 

6.2.4 is no warning or error but 7.0 has warning

 

usb.h warning is seemed easy to fix

 

Can you fix it at next version?

 

 

warning "Using compatibility file for drivers/usb/storage/usb.h - if possible do NOT compile using toolkit"

 

Actually, we ARE using toolkit to compile the loader for DSM 7.

@haydibe will probably confirm.

It is not an error, but a warning. Am I wrong ?

[Orphée]

On 9/22/2021 at 5:35 PM, ThorGroup said:

in short we want to explore adding platform like DVA3221

If you are able to acheive this, you will be my heros! (You already are guys ;))

[haydibe]

1 hour ago, Orphée said:

Actually, we ARE using toolkit to compile the loader for DSM 7.

@haydibe will probably confirm.

It is not an error, but a warning. Am I wrong ?

Affirmative. Everything right on spot!

 

DSM6.2.4 builds use the kernel sources that are publicly available - thus the condition checks for the kernel sources beeing used is met and there is noreason to throw the warning.

 

From my perspective there is nothing wrong with the warning on DSM7 builds, as it's a constant reminder that we need to switch from toolkit-dev to the kernel sources as soon as they are publicly available. This warning is a functional warning, not a technical warning.

 

@dateno1 To "fix" this warning you just need to convince Synology to publish the DSM7 kernel sources 😃

 

 

Edited September 25, 2021 by haydibe

[Patt92]

Thanks for all the great work of all of you guys.

Got 7.0.1-42214 DS918+ running on KVM Virtualization (Qemu) on a Ryzen 5 Pro 4650G system.

For anyone struggling with it, I just used the toolkit for building the redpill image.

- DiskIdxMap 0C

- Redpill image on Sata 0:0 (Controller 0, Unit 0)

- HDDs on Sata Controller 2 (on 1 you can't find them)

- VID/PID should be irrelevant but I went for V: 0x46f4 and P: 0x0001

 

[imdgg]

when i launch a container in Docker, the ds3615xs vm will crash

dsm version is 7.0.1

ds3615xs runs in esxi 6.7

cpu:E3 1265L v2

MB: DQ77KB

message.log:

2021-09-25T22:31:49+08:00 DS3615xs synofinderdb[12022]: synofinderdb.cpp:103 (main) synofinderdb tool desc: update synofinder.db
2021-09-25T22:31:50+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:31:55+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:32:00+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:32:25+08:00 DS3615xs synostgd-cache[5439]: SYSTEM:	Last message 'cache_monitor.c:2074' repeated 6 times, suppressed by syslog-ng on DS3615xs
2021-09-25T22:32:25+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:32:30+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:32:35+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:33:00+08:00 DS3615xs synostgd-cache[5439]: SYSTEM:	Last message 'cache_monitor.c:2074' repeated 6 times, suppressed by syslog-ng on DS3615xs
2021-09-25T22:33:00+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:33:05+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:33:10+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:33:35+08:00 DS3615xs synostgd-cache[5439]: SYSTEM:	Last message 'cache_monitor.c:2074' repeated 6 times, suppressed by syslog-ng on DS3615xs
2021-09-25T22:33:35+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:33:40+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:33:45+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:34:10+08:00 DS3615xs synostgd-cache[5439]: SYSTEM:	Last message 'cache_monitor.c:2074' repeated 6 times, suppressed by syslog-ng on DS3615xs
2021-09-25T22:34:10+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:34:15+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:34:20+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:34:45+08:00 DS3615xs synostgd-cache[5439]: SYSTEM:	Last message 'cache_monitor.c:2074' repeated 6 times, suppressed by syslog-ng on DS3615xs
2021-09-25T22:34:45+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:34:50+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:34:55+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:35:20+08:00 DS3615xs synostgd-cache[5439]: SYSTEM:	Last message 'cache_monitor.c:2074' repeated 6 times, suppressed by syslog-ng on DS3615xs
2021-09-25T22:35:20+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:35:25+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:35:30+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)
2021-09-25T22:35:50+08:00 DS3615xs synostgd-cache[5439]: SYSTEM:	Last message 'cache_monitor.c:2074' repeated 5 times, suppressed by syslog-ng on DS3615xs
2021-09-25T22:35:50+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Reach cache monitor error message limit

 

docker.log

2021-09-25T22:31:49+08:00 DS3615xs docker[11656]: time="2021-09-25T22:31:49.988360829+08:00" level=warning msg="Your kernel does not support cgroup blkio throttle.read_bps_device"
2021-09-25T22:31:49+08:00 DS3615xs docker[11656]: time="2021-09-25T22:31:49.988541818+08:00" level=warning msg="Your kernel does not support cgroup blkio throttle.write_bps_device"
2021-09-25T22:31:49+08:00 DS3615xs docker[11656]: time="2021-09-25T22:31:49.988720078+08:00" level=warning msg="Your kernel does not support cgroup blkio throttle.read_iops_device"
2021-09-25T22:31:49+08:00 DS3615xs docker[11656]: time="2021-09-25T22:31:49.988899380+08:00" level=warning msg="Your kernel does not support cgroup blkio throttle.write_iops_device"
2021-09-25T22:31:49+08:00 DS3615xs docker[11656]: time="2021-09-25T22:31:49.989077648+08:00" level=warning msg="Unable to find pids cgroup in mounts"
2021-09-25T22:31:50+08:00 DS3615xs docker[11656]: time="2021-09-25T22:31:50.296260650+08:00" level=error msg="failed to load container mount" container=a6774be8f04dff2e4331042223aa75400a7cbd9844261d6e7556c7d7f0e00df7 error="mount does not exist"
2021-09-25T22:31:52+08:00 DS3615xs docker[11656]: time="2021-09-25T22:31:52.414314874+08:00" level=warning msg="Failed to delete conntrack state for 172.17.0.2: invalid argument"
2021-09-25T22:31:52+08:00 DS3615xs docker[11656]: time="2021-09-25T22:31:52.550692280+08:00" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint 7e3883ed93a23971685b1e68b3b0b933e39822d49c155e8e1b530fbc3ce04e4f dffd96d61caa97732569427dcb32acfd4941374e389cbfde4d7db78b9f7f915f], retrying...."
2021-09-25T22:31:53+08:00 DS3615xs docker[11656]: time="2021-09-25T22:31:53.184749410+08:00" level=warning msg="Could not get operating system name: Error opening /usr/lib/os-release: open /usr/lib/os-release: no such file or directory"
2021-09-25T22:31:53+08:00 DS3615xs docker[11656]: time="2021-09-25T22:31:53.185005296+08:00" level=warning msg="Could not get operating system version: Error opening /usr/lib/os-release: open /usr/lib/os-release: no such file or directory"

 

but ds918 is running stable in qnap Virtualization Station.

 

 

[ilovepancakes]

On 9/22/2021 at 11:35 AM, ThorGroup said:

Add support for GPU acceleration: in short we want to explore adding platform like DVA3221

 

+1 for this! Would be great to run Surveillance Station with all those deep learning features.

[Orphée]

@imdgg

https://github.com/RedPill-TTG/redpill-lkm/issues/21

[WiteWulf]

@imdgg as Orphée pointed, there's an ongoing issue with databases and/or docker crashing the DS3615xs image, both on baremetal and virtualised platforms, that's not present on 918+. However that may not be the root of your problem. Your logs are full of the following message:

2021-09-25T22:31:50+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)

At a guess your ESXi guest only has one vCPU configured? Try increasing it to 2 and see how you get on. You've got 4 cores on that CPU (8 with hyperthreading), show it some love 😁

[sebg35]

il y a 38 minutes, WiteWulf a dit :

@imdgg as Orphée pointed, there's an ongoing issue with databases and/or docker crashing the DS3615xs image, both on baremetal and virtualised platforms, that's not present on 918+. However that may not be the root of your problem. Your logs are full of the following message:

2021-09-25T22:31:50+08:00 DS3615xs synostgd-cache[9725]: cache_monitor.c:2074 [Error] Can't support DS with cpu number (1)

At a guess your ESXi guest only has one vCPU configured? Try increasing it to 2 and see how you get on. You've got 4 cores on that CPU (8 with hyperthreading), show it some love 😁

Hi, 

 

Same logs on my baremetal gen10 plus, using the 3615xs and 7.0.1. My cpu is xeon e-2224.

 

FYI always crashing When i try to log in. 

 

I rollback to 6.2.3.