buggy25200

Hi, This module and many others are already integrated into the system by arpl. First update from menu.sh "update arpl" and "Update addons", then check that addon "acpid" is selected before generate the build loader. And It must works

Hello, I think the problem come from a general failure caused by udevadm binary absence in eudev addon package release I made a merge request yesterday https://github.com/fbelavenuto/arpl-addons/pull/29 An addon release has been produced here https://github.com/jimmyGALLAND/arpl-addons/releases/tag/v2.90-jimmygalland Maybe try replace in bootloader image partition 3 directory addon by this release.

You can add an addon like this example url for maxdisk addon https://raw.githubusercontent.com/fbelavenuto/arpl-addons/main/maxdisks/manifest.yml But Modules are already "package" in releases https://github.com/fbelavenuto/arpl-modules/releases For example this is the modules list in pack appollake crc-ccitt.ko crc-itu-t.ko hwmon-vid.ko microchip.ko plusb.ko r8153_ecm.ko gl620a.ko mdio.ko cdc_subset.ko eeprom_93cx6.ko huawei_cdc_ncm.ko net1080.ko cdc_eem.ko ch9200.ko int51x1.ko mdio-octeon.ko lg-vl600.ko kalmia.ko mii.ko smsc.ko mvmdio.ko zaurus.ko auxiliary.ko cx82310_eth.ko raid_class.ko ehci-pci.ko virtio_mmio.ko cdc_mbim.ko mcs7830.ko cpsw_ale.ko sr9700.ko virtio_ring.ko button.ko virtio.ko rndis_host.ko cdc_ether.ko nicpf.ko ec_bhf.ko ipheth.ko dm9601.ko am53c974.ko a100u2w.ko ks8851_mll.ko megaraid_mm.ko catc.ko sr9800.ko dnet.ko dmx3191d.ko rtl8150.ko thunder_bgx.ko sierra_net.ko sungem_phy.ko cdc-wdm.ko virtio_blk.ko virtio_pci.ko virtio_scsi.ko ks8851.ko fdomain.ko ks8842.ko kaweth.ko ax88179_178a.ko wd719x.ko aqc111.ko mptspi.ko stex.ko amd8111e.ko initio.ko yellowfin.ko ns83820.ko tehuti.ko hp100.ko epic100.ko sis190.ko uli526x.ko smsc95xx.ko vmw_pvscsi.ko hptiop.ko cdc_ncm.ko starfire.ko hamachi.ko winbond-840.ko smsc9420.ko atp870u.ko dmfe.ko scsi_transport_spi.ko eata.ko smsc75xx.ko pegasus.ko dl2k.ko mptscsih.ko de2104x.ko sundance.ko virtio_net.ko qla1280.ko 3w-sas.ko typhoon.ko macb.ko sungem.ko 3w-xxxx.ko natsemi.ko usbnet.ko et131x.ko acenic.ko asix.ko alx.ko esp_scsi.ko smsc911x.ko usbserial.ko mptctl.ko mvumi.ko lan78xx.ko atl1e.ko atl1.ko b44.ko tlan.ko via-velocity.ko skge.ko dc395x.ko igbvf.ko scsi_transport_sas.ko libphy.ko atl1c.ko megaraid_mbox.ko jme.ko BusLogic.ko ksz884x.ko dpt_i2o.ko 3w-9xxx.ko arcmsr.ko qla3xxx.ko qmi_wwan.ko ehci-hcd.ko de4x5.ko samsung-sxgbe.ko ixgb.ko ssb.ko cassini.ko vmxnet3.ko mptsas.ko megaraid.ko nicvf.ko 3c59x.ko libiscsi.ko advansys.ko nct6775.ko ips.ko sky2.ko myri10ge.ko cnic.ko mvsas.ko vmw_vmci.ko gdth.ko pmcraid.ko forcedeth.ko libsas.ko tulip.ko i40evf.ko ixgbevf.ko cxgb4vf.ko cxgb.ko bnxt_en.ko bnx2.ko mptbase.ko enic.ko sym53c8xx.ko s2io.ko niu.ko r8169.ko qlge.ko ftdi_sio.ko liquidio.ko aic94xx.ko esas2r.ko hpsa.ko fm10k.ko mlx5_core.ko vxge.ko mlx4_en.ko snic.ko netxen_nic.ko e1000.ko qed.ko isci.ko megaraid_sas.ko be2net.ko ipr.ko iavf.ko bna.ko cxgb3.ko aacraid.ko aic7xxx.ko r8125.ko tg3.ko aic79xx.ko r8152.ko pm80xx.ko igb.ko mlx4_core.ko atlantic.ko cxgb4.ko qlcnic.ko ixgbe.ko qla4xxx.ko i40e.ko mpt3sas.ko bnx2x.ko ice.ko

@fbelavenuto There are missing files in module eudev v2.9. ( bin udev missing ) https://github.com/fbelavenuto/arpl-addons/releases/download/v2.9/addons.zip So no module load at boot ! Maybe this commit : https://github.com/fbelavenuto/arpl-addons/commit/df12a5549a449538ab1756350e35b33fd94a73f7 No probleme with eudev v2.8 Thank you, for your very good work!

Good evening It seems to me There are missing files in module eudev v2.9. https://github.com/fbelavenuto/arpl-addons/releases/download/v2.9/addons.zip They are present in v2.8 If you can take a look. Thank you, for all your work!

Patience, Yes there is a way ! And the work is being done by @pocopico with @jumkey 's help. I'm working on a ncurses interface with pocopico, maybe ... in a few weeks !

Installation must be done with original PAT from synology download center. But the loader for the reboot have to be done with generate PAT

Hello, Be careful: update to 7.1 beta is for the development purpose only . It's not working !! .... yet ??? Indeed, we have seen with Yanjun that an security has been added by Synology, which requires, i think, requires a lot of research. After the update, the problem is that a connection to the GUI causes an immediate system restart. 7.1 beta support for 3617xs is available on my github. To update you must use the same method as for 7.0.1u2 (via the creation of its PAT file)

I just added the support ACPI for DS3622xs+, "ds3622xsp_42218" and "ds36222xsp_42218u2" Try it and tell me if it works for you ! https://raw.githubusercontent.com/jimmyGALLAND/redpill-ext/master/acpid/rpext-index.json

On a DSM 7.0.1 3617xs+ My prod server has been running for 44 days, no crashes, 10SATA disk, 9 dockers including 1 mariasql 1.3Go DBB/ with nextcloud. 1 VM under ubuntu server "mailinabox", 11 machines on hyperbackup including 3 under linux! It rock !

Yes, I will do it in the coming days

I updated the repository https://github.com/jimmyGALLAND/redpill-ext/raw/master/acpid/rpext-index.json It works now.

Hello, DSM 6.2.4 update 4 is out! https://www.cachem.fr/synology-dsm-6-2-4-25556-update-4/ No kernel modification so Update from loader make with 624-25556u2 should work (Same sha256sum for zimage platform918+/3617xs/3615xs)

On control panel => update & restore => DSM update => update setting, to avoid future unrequested update, It is better to check the third option, if it is not done yet: Notify me and let me decide whether to install the new update

@apiros try this DiskStation> mkdir /root/tmproot DiskStation> mount /dev/md0 /root/tmproot/ DiskStation> chroot /root/tmproot /bin/bash DiskStation> sha256sum /.syno/patch/zImage DiskStation> sha256sum /.syno/patch/rd.gz and post here the two results Thx

root not matched with junior you must boot with the correct version of loader. If you try to update to 701u2 you have to read my previous post. Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk

Sorry, I haven't received your message !

@apiros Can you PM me result of cat /var/log/junior cat /var/log/message Thx

For those allergic to DSM 7 ! I forgot to add support for u2 / u3 intermediate updates for the DS918p platform, it's done. "6.2.4-25556u2" on develop branch https://github.com/jimmyGALLAND/redpill-load Update 3 works without having to redo a new loader than this one, there was no kernel update to go to version 3 from 2. In the same way update 2 of DSM 6.2.4 works with update 3 on platforms ds3615xs and ds3617xs. Some modules are available on https://github.com/jimmyGALLAND/redpill-ext ( like acpi, virtio, redpill-boot_wait ). A request has been sent for "6.2.4-25556u2" on pocopico modules github https://github.com/pocopico/rp-ext In the meantime you can use the branch: "add_support_ds918p_25556u2" on https://github.com/jimmyGALLAND/rp-ext

Hello @apiros There was a dependency problem with the dpkg package that is not present with the pocopico's tool . This dependency was removed which caused the impossibility of generating an image for ds3617xs. However I send an alternative two days ago on the develop branch https://github.com/jimmyGALLAND/redpill-load . You can try and make your feedback

Ok it's done !

Hi, @dodo-dk Exact ! Be carreful do not update ds3617xs to DSM 7.0.1-42218 Update 1 or 2 without reading this more, There is a new zimage and rd, you can see the pat size is more weight than ds3615xs or 918+ synology_broadwell_3617xs.pat 26.98MB synology_bromolow_3615xs.pat 10.10MB synology_apollolake_918+.pat 10.53MB And there is a problem (a problem for futur ?!) A priori, the new pat file on synology download site are no longer gz type archive! And so they are no longer usable by our current scripts. It is possible that all pat files will be distributed in this new format. I have prepared the bsp for update 2, you can up to update 2 without going through update 1. But to be able to use it, you will have to produce a PAT file yourself! WHAT ?! 😢 And this as long as we do not have a tool allowing extraction of these pat files with a script. I cannot provide you the PAT file i made, because it contains proprietary data. In order to produce your PAT file, here is a procedure to follow: Prerequisites You must have a machine with a ds3617xs 701 already install, on the LAN, and with a serial connection capability. (A virtual machine is the best choice) And another machine to receive the PAT file (with ssh server un this procedure). Launch a manual migration to update 2 from GUI DSM 7.0.1. After the reboot which will fail! Connect to the serial port You can see why it didn't work... DiskStation> cat /var/log/junior_reason Exit on error [7] root not matched with junior... Which means that your bootloader is no longer usable with the current version. DiskStation> mkdir /root/tmproot DiskStation> mount /dev/md0 /root/tmproot/ DiskStation> mount /dev /root/tmproot/dev DiskStation> chroot /root/tmproot /bin/bash DiskStation> chroot /root/tmproot /bin/bash bash-4.4# cd /.syno/patch bash-4.4# tar -zcvf mypat.pat * bash-4.4# scp mypat.pat yourlogin@ipremotemachine:~ Here you have your PAT file ! In this tutorial I work with the rp-helper tool but you can use what you prefer. Put your PAT file in the cache download directory so that it can be used without downloading synology's one, or host your file on a server and modify the pat_url! Add in your global_config.json ... { "id": "broadwell-7.0.1-42218u2-test", "platform_version": "broadwell-7.0.1-42218u2", "user_config_json": "USERCONFIG.json", "docker_base_image": "debian:9-slim", "redpill_lkm_make_target": "test-v7", "compile_with": "toolkit_dev", "downloads": { "kernel": { "url": "https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.4.180.tar.gz", "sha256": "519ff74ceaa52462d6b9a8452d90ba5cd009807830134de5e1df269b44dd380b" }, "toolkit_dev": { "url": "https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.broadwell-7.0.dev.txz/download", "sha256": "e050987fbbab0c246aff2af935b1d8a4140ce490915aa4c92f3c8d163eea970c" } }, "redpill_lkm": { "source_url": "https://github.com/jimmyGALLAND/redpill-lkm.git", "branch": "develop" }, "redpill_load": { "source_url": "https://github.com/jimmyGALLAND/redpill-load.git", "branch": "develop" } } .... I advise you to clone develop branch https://github.com/jimmyGALLAND/redpill-lkm.git in a directory and modify global_config.json to set "local_rp_load_use" to true in order to be able to use a modify config.json file ... "docker": { "use_buildkit": "true", "image_name": "redpill-tool-chain", "download_folder": "docker/downloads", "local_rp_lkm_use": "false", "local_rp_lkm_path": "./redpill-lkm", "local_rp_load_use": "true", "local_rp_load_path": "./redpill-load", ... In redpill-load edit config.json file under config/DS3617xs/7.0.1-42218u2/config.json ... { "os": { "id": "ds3617xs_42218u2", "pat_url": "https://global.download.synology.com/download/DSM/criticalupdate/update_pack/42218-2/synology_broadwell_3617xs.pat", "sha256": "XXXXXXXXXXXXXXXXXXX" put here the sha256sum of your PAT file }, .... In order to use virtio or redpill-boot-wait for ds3617xs_42218u2 You can use https://github.com/jimmyGALLAND/redpill-ext I will update the @pocopico ext repo coming days. Good night people

@Kwn_nos I am preparing rp-ext to help @pocopico, maybe tomorrow it will be done.

Yo, I noticed a very weird thing about adding ds3615xs-6.2.4-25556 update 2. The kernel boot of this update failed start with kernel panic. [ 0.000000] console [ttyS0] enabled, bootconsole disabled [ 0.000000] allocated 16777216 bytes of page_cgroup [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.000000] tsc: Fast TSC calibration using PIT [ 0.001000] tsc: Detected 3600.041 MHz processor [ 0.000004] Calibrating delay loop (skipped), value calculated using timer frequency.. 7200.08 BogoMIPS (lpj=3600041) [ 0.001716] pid_max: default: 32768 minimum: 301 [ 0.002349] Security Framework initialized [ 0.002915] AppArmor: AppArmor initialized [ 0.003410] Mount-cache hash table entries: 256 [ 0.004049] Initializing cgroup subsys memory [ 0.004569] Initializing cgroup subsys devices [ 0.005197] Initializing cgroup subsys freezer [ 0.005719] Initializing cgroup subsys blkio [ 0.006316] CPU: Physical Processor ID: 0 [ 0.006770] CPU: Processor Core ID: 0 [ 0.018907] mce: CPU supports 0 MCE banks [ 0.020151] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0 [ 0.020151] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0 [ 0.020151] tlb_flushall_shift: 6 [ 0.023730] FEATURE SPEC_CTRL Not Present [ 0.024490] FEATURE IBPB_SUPPORT Not Present [ 0.025039] Spectre V2 : Vulnerable [ 0.025701] Freeing SMP alternatives: 24k freed [ 0.026615] ACPI: Core revision 20130328 [ 0.027942] ACPI: All ACPI Tables successfully acquired [ 0.029688] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.040437] smpboot: CPU0: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (fam: 06, model: 9e, stepping: 09) [ 0.143698] Performance Events: unsupported p6 CPU model 158 no PMU driver, software events only. [ 0.146451] NMI watchdog: disabled (cpu0): hardware events not enabled [ 0.147710] smpboot: Booting Node 0, Processors #1 OK [ 0.170011] mce: CPU supports 0 MCE banks [ 0.173168] Brought up 2 CPUs [ 0.173742] smpboot: Total of 2 processors activated (14400.16 BogoMIPS) [ 0.177981] devtmpfs: initialized [ 0.179998] xor: automatically using best checksumming function: [ 0.190623] avx : 24696.000 MB/sec [ 0.191802] NET: Registered protocol family 16 [ 0.193958] ACPI: bus type PCI registered [ 0.195320] PCI: Using configuration type 1 for base access [ 0.206402] bio: create slab <bio-0> at 0 [ 0.224568] raid6: sse2x1 gen() 10300 MB/s [ 0.241539] raid6: sse2x1 xor() 6560 MB/s [ 0.259508] raid6: sse2x2 gen() 13101 MB/s [ 0.276517] raid6: sse2x2 xor() 9031 MB/s [ 0.294446] raid6: sse2x4 gen() 14382 MB/s [ 0.312414] raid6: sse2x4 xor() 10251 MB/s [ 0.330399] raid6: avx2x1 gen() 24433 MB/s [ 0.348355] raid6: avx2x2 gen() 29914 MB/s [ 0.366334] raid6: avx2x4 gen() 31464 MB/s [ 0.367125] raid6: using algorithm avx2x4 gen() (31464 MB/s) [ 0.368422] raid6: using avx2x2 recovery algorithm [ 0.370714] ACPI: Added _OSI(Module Device) [ 0.371857] ACPI: Added _OSI(Processor Device) [ 0.372462] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.373179] ACPI: Added _OSI(Processor Aggregator Device) [ 0.374349] ACPI: EC: Look up EC in DSDT [ 0.374956] ACPI: Executed 1 blocks of module-level executable AML code [ 0.377528] ACPI: Interpreter enabled [ 0.377981] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S4_] (20130328/hwxface-568) [ 0.379083] ACPI: (supports S0 S5) [ 0.379620] ACPI: Using IOAPIC for interrupt routing [ 0.380527] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug [ 0.381969] ACPI: No dock devices found. [ 0.389084] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.391257] acpi PNP0A03:00: Unable to request _OSC control (_OSC support mask: 0x1e) [ 0.392302] acpi PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored) [ 0.393158] acpi PNP0A03:00: host bridge window [io 0x0d00-0xffff] (ignored) [ 0.394040] acpi PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored) [ 0.394976] acpi PNP0A03:00: host bridge window [mem 0xe0000000-0xfdffffff] (ignored) [ 0.395921] PCI: root bus 00: using default resources [ 0.396676] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge. [ 0.401518] PCI host bridge to bus 0000:00 [ 0.403111] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.404984] pci_bus 0000:00: root bus resource [io 0x0000-0xffff] [ 0.406280] pci_bus 0000:00: root bus resource [mem 0x00000000-0x7fffffffff] [ 0.407356] pci 0000:00:00.0: [8086:1237] type 00 class 0x060000 [ 0.408729] pci 0000:00:01.0: [8086:7000] type 00 class 0x060100 [ 0.410609] pci 0000:00:02.0: [15ad:0405] type 00 class 0x030000 [ 0.412742] pci 0000:00:02.0: reg 10: [io 0xd000-0xd00f] [ 0.414963] pci 0000:00:02.0: reg 14: [mem 0xe0000000-0xe0ffffff pref] [ 0.416790] pci 0000:00:02.0: reg 18: [mem 0xf0000000-0xf01fffff] [ 0.424715] pci 0000:00:04.0: [80ee:cafe] type 00 class 0x088000 [ 0.428253] pci 0000:00:04.0: reg 10: [io 0xd020-0xd03f] [ 0.431701] pci 0000:00:04.0: reg 14: [mem 0xf0400000-0xf07fffff] [ 0.435234] pci 0000:00:04.0: reg 18: [mem 0xf0800000-0xf0803fff pref] [ 0.442077] pci 0000:00:07.0: [8086:7113] type 00 class 0x068000 [ 0.444128] pci 0000:00:07.0: address space collision: [io 0x4000-0x403f] conflicts with ACPI PM1a_EVT_BLK [??? 0x00004000-0x00004003 flags 0x80000000] [ 0.446401] pci 0000:00:07.0: quirk: [io 0x4100-0x410f] claimed by PIIX4 SMB [ 0.448110] pci 0000:00:0c.0: [8086:1e31] type 00 class 0x0c0330 [ 0.450677] pci 0000:00:0c.0: reg 10: [mem 0xf0810000-0xf081ffff] [ 0.461007] pci 0000:00:0d.0: [8086:2829] type 00 class 0x010601 [ 0.464729] pci 0000:00:0d.0: reg 10: [io 0xd040-0xd047] [ 0.466692] pci 0000:00:0d.0: reg 14: [io 0xd048-0xd04b] [ 0.469644] pci 0000:00:0d.0: reg 18: [io 0xd050-0xd057] [ 0.471641] pci 0000:00:0d.0: reg 1c: [io 0xd058-0xd05b] [ 0.473637] pci 0000:00:0d.0: reg 20: [io 0xd060-0xd06f] [ 0.475679] pci 0000:00:0d.0: reg 24: [mem 0xf0820000-0xf0821fff] [ 0.479415] pci 0000:00:11.0: [8086:100f] type 00 class 0x020000 [ 0.483134] pci 0000:00:11.0: reg 10: [mem 0xf0840000-0xf085ffff] [ 0.487105] pci 0000:00:11.0: reg 18: [io 0xd070-0xd077] [ 0.496525] pci_bus 0000:00: on NUMA node 0 [ 0.498536] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 9 10 *11) [ 0.499860] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 9 *10 11) [ 0.500944] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 *9 10 11) [ 0.501726] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 9 10 *11) [ 0.502725] ACPI: Enabled 2 GPEs in block 00 to 07 [ 0.503296] acpi root: \_SB_.PCI0 notify handler is installed [ 0.503969] Found 1 acpi root devices [ 0.504839] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none [ 0.505801] vgaarb: loaded [ 0.506113] vgaarb: bridge control possible 0000:00:02.0 [ 0.507211] SCSI subsystem initialized [ 0.507674] ACPI: bus type ATA registered [ 0.508418] libata version 3.00 loaded. [ 0.509290] pps_core: LinuxPPS API ver. 1 registered [ 0.509897] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.511236] PTP clock support registered [ 0.511945] PCI: Using ACPI for IRQ routing [ 0.512445] PCI: pci_cache_line_size set to 64 bytes [ 0.513336] e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff] [ 0.514126] e820: reserve RAM buffer [mem 0xdfff0000-0xdfffffff] [ 0.515162] e820: reserve RAM buffer [mem 0x11a000000-0x11bffffff] [ 0.516609] Switching to clocksource refined-jiffies [ 0.517311] AppArmor: AppArmor Filesystem Enabled [ 0.518000] pnp: PnP ACPI init [ 0.518356] ACPI: bus type PNP registered [ 0.519036] pnp 00:00: Plug and Play ACPI device, IDs PNP0303 (active) [ 0.519842] pnp 00:01: [dma 4] [ 0.522613] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active) [ 0.524453] pnp 00:02: Plug and Play ACPI device, IDs PNP0f03 (active) [ 0.527031] pnp 00:03: Plug and Play ACPI device, IDs PNP0501 (active) [ 0.527975] pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active) [ 0.528968] pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active) [ 0.530072] pnp: PnP ACPI: found 6 devices [ 0.530659] ACPI: bus type PNP unregistered [ 0.545678] Switching to clocksource acpi_pm [ 0.546793] pci 0000:00:07.0: BAR 13: [io 0x4000-0x403f] has bogus alignment [ 0.548656] pci_bus 0000:00: resource 4 [io 0x0000-0xffff] [ 0.552376] pci_bus 0000:00: resource 5 [mem 0x00000000-0x7fffffffff] [ 0.554142] NET: Registered protocol family 2 [ 0.555943] TCP established hash table entries: 32768 (order: 7, 524288 bytes) [ 0.556852] TCP bind hash table entries: 32768 (order: 7, 524288 bytes) [ 0.557654] TCP: Hash tables configured (established 32768 bind 32768) [ 0.558806] TCP: reno registered [ 0.559205] UDP hash table entries: 2048 (order: 4, 65536 bytes) [ 0.560242] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes) [ 0.561097] NET: Registered protocol family 1 [ 0.561837] RPC: Registered named UNIX socket transport module. [ 0.562620] RPC: Registered udp transport module. [ 0.563377] RPC: Registered tcp transport module. [ 0.564087] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.565017] pci 0000:00:00.0: Limiting direct PCI/PCI transfers [ 0.565883] pci 0000:00:01.0: Activating ISA DMA hang workarounds [ 0.566865] pci 0000:00:02.0: Boot video device [ 0.568272] PCI: CLS 0 bytes, default 64 [ 0.659845] Trying to unpack rootfs image as initramfs... [ 1.955079] rootfs image is not initramfs (unexpected EOF); looks like an initrd [ 1.958678] Freeing initrd memory: 6956k freed [ 1.960111] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 1.961033] software IO TLB [mem 0xdbff0000-0xdfff0000] (64MB) mapped at [ffff8800dbff0000-ffff8800dffeffff] [ 1.962811] platform rtc_cmos: registered platform RTC device (no PNP device found) [ 1.966246] Initialise module verification [ 1.966834] audit: initializing netlink socket (disabled) [ 1.967469] type=2000 audit(1639781529.844:1): initialized [ 1.968840] bounce pool size: 64 pages [ 1.969881] VFS: Disk quotas dquot_6.5.2 [ 1.970387] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 1.971802] NFS: Registering the id_resolver key type [ 1.972416] Key type id_resolver registered [ 1.973068] Key type id_legacy registered [ 1.973584] msgmni has been set to 7655 [ 1.974779] async_tx: api initialized (async) [ 1.975310] Key type asymmetric registered [ 1.975854] Asymmetric key parser 'x509' registered [ 1.976796] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 1.978437] io scheduler noop registered [ 1.978969] io scheduler deadline registered [ 1.979547] io scheduler cfq registered [ 2.077923] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 2.100756] serial8250: ttyS0 at I/O 0x2f8 (irq = 3) is a 16550A [ 2.122572] serial8250: ttyS1 at I/O 0x3f8 (irq = 4) is a 16550A [ 2.145074] serial8250: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A [ 2.150550] brd: module loaded [ 2.151528] Loading iSCSI transport class v2.0-870. [ 2.153053] rdac: device handler registered [ 2.153905] ahci 0000:00:0d.0: version 3.0 [ 2.154915] ahci: SSS flag set, parallel bus scan disabled [ 2.155859] ahci 0000:00:0d.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode [ 2.156885] ahci 0000:00:0d.0: flags: 64bit ncq stag only ccc [ 2.157785] ahci 0000:00:0d.0: setting latency timer to 64 [ 2.159079] scsi0 : ahci [ 2.159777] scsi1 : ahci [ 2.160391] ata1: SATA max UDMA/133 abar m8192@0xf0820000 port 0xf0820100 irq 21 [ 2.161671] ata2: SATA max UDMA/133 abar m8192@0xf0820000 port 0xf0820180 irq 21 [ 2.163996] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [ 2.165331] rtc_cmos rtc_cmos: alarms up to one day, 114 bytes nvram [ 2.166272] i2c /dev entries driver [ 2.167401] md: linear personality registered for level -1 [ 2.168081] md: raid0 personality registered for level 0 [ 2.168775] md: raid1 personality registered for level 1 [ 2.169451] md: raid10 personality registered for level 10 [ 2.170387] md: raid6 personality registered for level 6 [ 2.172374] md: raid5 personality registered for level 5 [ 2.173302] md: raid4 personality registered for level 4 [ 2.175066] md: raidF1 personality registered for level 45 [ 2.176160] device-mapper: ioctl: 4.25.0-ioctl (2013-06-26) initialised: dm-devel@redhat.com [ 2.177430] cpuidle: using governor ladder [ 2.178089] cpuidle: using governor menu [ 2.178939] TCP: cubic registered [ 2.180108] NET: Registered protocol family 17 [ 2.180729] Key type dns_resolver registered [ 2.561256] ata1: SATA link up ps (SStatus 123 SControl 300) [ 2.798761] ata1.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133 [ 2.799471] ata1.00: 262144 sectors, multi 128: LBA48 NCQ (depth 31/32) [ 2.800317] ata1.00: SN:VBba94cf0b-f44d12c1 [ 2.801045] ata1.00: configured for UDMA/133 [ 2.801822] ata1.00: Find SSD disks. [VBOX HARDDISK] [ 2.802468] I/O scheduler elevator not found [ 2.803149] scsi 0:0:0:0: Direct-Access VBOX HARDDISK 1.0 PQ: 0 ANSI: 5 [ 2.804898] sd 0:0:0:0: [sda] 262144 512-byte logical blocks: (134 MB/128 MiB) [ 2.806395] sd 0:0:0:0: [sda] Write Protect is off [ 2.807112] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 2.807881] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.811291] sda: sda1 sda2 sda3 [ 2.813595] sd 0:0:0:0: [sda] Attached SCSI disk [ 2.983585] tsc: Refined TSC clocksource calibration: 3600.004 MHz [ 2.985363] Switching to clocksource tsc [ 3.112897] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 3.115176] ata2.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133 [ 3.115885] ata2.00: 67108864 sectors, multi 128: LBA48 NCQ (depth 31/32) [ 3.116715] ata2.00: SN:VB3037da75-5f763e75 [ 3.117349] ata2.00: configured for UDMA/133 [ 3.117900] ata2.00: Find SSD disks. [VBOX HARDDISK] [ 3.118497] I/O scheduler elevator not found [ 3.119180] scsi 1:0:0:0: Direct-Access VBOX HARDDISK 1.0 PQ: 0 ANSI: 5 [ 3.120877] sd 1:0:0:0: [sdb] 67108864 512-byte logical blocks: (34.3 GB/32.0 GiB) [ 3.122046] sd 1:0:0:0: [sdb] Write Protect is off [ 3.122683] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 3.123469] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 3.125529] sdb: sdb1 sdb2 [ 3.127154] sd 1:0:0:0: [sdb] Attached SCSI disk [ 3.127978] Loading module verification blacklist certificates [ 3.128706] Loading module verification certificates [ 3.129509] MODSIGN: Loaded cert 'Synology SDG kernel module signing key: 7bd0b0d6bcd31651c22ce3978bdc8c8bdc417329' [ 3.131473] MODSIGN: Loaded cert 'Synology Root Certification Authority: f2c075361f168425f8b5ef31b796406c3aab2089' [ 3.133047] MODSIGN: Loaded cert 'Synology Kernel Module Signing Certification Authority: 600839b5d127e0e11d817a31f0575d323a7c0e28' [ 3.134646] MODSIGN: Loaded cert 'Synology kernel module signing key: 4646ce54489669338118a3b1286da156ac366fa5' [ 3.136129] registered taskstats version 1 [ 3.137214] rtc_cmos rtc_cmos: setting system clock to 2021-12-17 22:52:11 UTC (1639781531) [ 3.138698] md: Waiting for all devices to be available before autodetect [ 3.142062] md: If you don't use raid, use raid=noautodetect [ 3.144483] md: Autodetecting RAID arrays. [ 3.145445] md: Scanned 2 and added 2 devices. [ 3.146067] md: autorun ... [ 3.146551] md: considering sdb1 ... [ 3.147116] md: adding sdb1 ... [ 3.147507] md: sdb2 has different UUID to sdb1 [ 3.148097] md: created md0 [ 3.148436] md: bind<sdb1> [ 3.148820] md: running: <sdb1> [ 3.149592] md/raid1:md0: active with 1 out of 15 mirrors [ 3.154486] md0: detected capacity change from 0 to 2549940224 [ 3.156118] md: considering sdb2 ... [ 3.156684] md: adding sdb2 ... [ 3.157874] md: created md1 [ 3.158313] md: bind<sdb2> [ 3.158776] md: running: <sdb2> [ 3.160055] md/raid1:md1: active with 1 out of 15 mirrors [ 3.162766] md1: detected capacity change from 0 to 2147418112 [ 3.164388] md: ... autorun DONE. [ 3.164950] RAMDISK: lzma image found at block 0 [ 4.263221] List of all partitions: [ 4.263814] 0800 131072 sda driver: sd [ 4.265616] 0801 49152 sda1 f110ee87-01 [ 4.266367] 0802 76800 sda2 f110ee87-02 [ 4.267004] 0803 4096 sda3 f110ee87-03 [ 4.267740] 0810 33554432 sdb driver: sd [ 4.268829] 0811 2490240 sdb1 df15ded8-01 [ 4.269456] 0812 2097152 sdb2 df15ded8-02 [ 4.270057] 0900 2490176 md0 (driver?) [ 4.270576] 0901 2097088 md1 (driver?) [ 4.271117] No filesystem could mount root, tried: ext3 ext2 ext4 [ 4.272371] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0) [ 4.273642] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.105 #25556 [ 4.274641] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 4.275745] ffffffff814c908d ffffffff814c8161 ffff880100000010 ffff88011219be98 [ 4.276775] ffff88011219be30 ffff88011219be88 ffff88011219bea8 0000000000000012 [ 4.278412] 0000000000000001 000000000000000a 000000000000fffb ffffffffffffffff [ 4.279302] Call Trace: [ 4.279643] [<ffffffff814c908d>] ? dump_stack+0xc/0x15 [ 4.280457] [<ffffffff814c8161>] ? panic+0xbb/0x1ce [ 4.281186] [<ffffffff8188929a>] ? mount_block_root+0x340/0x340 [ 4.281879] [<ffffffff81889d13>] ? initrd_load+0xcb/0x2e8 [ 4.282690] [<ffffffff818894e7>] ? prepare_namespace+0xda/0x19e [ 4.283587] [<ffffffff81888eb5>] ? kernel_init_freeable+0x1b2/0x1bb [ 4.284528] [<ffffffff814bca00>] ? rest_init+0x70/0x70 [ 4.285276] [<ffffffff814bca05>] ? kernel_init+0x5/0x180 [ 4.286057] [<ffffffff814cfc0d>] ? ret_from_fork+0x5d/0xb0 [ 4.286936] [<ffffffff814bca00>] ? rest_init+0x70/0x70 So I forced with the bsp file patch, go back to the previous kernel version (certainly not ideal!). And this time redpill boot failed with message explain the serial ports aren't swap. I disable port swapping in ds3615xs config platform in redpill-lkm, and it works! First, it's weird that the boot of this version hangs at this point, and why ?! And another problem is the fact redpill-lkm does not manage several types of configuration for the same platform! I think an improvement on this point should be considered! Volunteers ?

If you want touse redpill-helper, you have to add in docker/Makefile this 4 last lines .PHONY: build_redpill_load build_redpill_load: @mkdir -p $(REDPILL_LOAD_SRC)/ext/rp-lkm/ @echo "#############################################" && \ echo "Using user_config.json:" && cat $(REDPILL_LOAD_SRC)/user_config.json && \ echo "#############################################" @read -a KVERS <<< "$$(modinfo --field=vermagic redpill-lkm/redpill.ko)" && \ cp -f $(REDPILL_LKM_SRC)/redpill.ko $(REDPILL_LOAD_SRC)/ext/rp-lkm/redpill-linux-v$${KVERS[0]}.ko @if [ "$(TARGET_PLATFORM)" == "bromolow" ]; then \ pushd $(REDPILL_LOAD_SRC) && \ ./build-loader.sh 'DS3615xs' '$(TARGET_VERSION)-$(TARGET_REVISION)'; \ fi @if [ "$(TARGET_PLATFORM)" == "apollolake" ]; then \ pushd $(REDPILL_LOAD_SRC) && \ ./build-loader.sh 'DS918+' '$(TARGET_VERSION)-$(TARGET_REVISION)'; \ fi @if [ "$(TARGET_PLATFORM)" == "broadwell" ]; then \ pushd $(REDPILL_LOAD_SRC) && \ ./build-loader.sh 'DS3617xs' '$(TARGET_VERSION)-$(TARGET_REVISION)'; \ fi