Jump to content
XPEnology Community

pocopico

Developer
 View Profile  See their activity

  • Posts

    1,753

  • Joined

  • Last visited

  • Days Won

    123

 Content Type 

Everything posted by pocopico

  1. pocopico
    it’s no surprise that all different DT models use different syntax and support different sub component’s. If you decompile all model.dtb you can verify that.
  2. pocopico
    @daryl Device tree models and SAS i think is a no go. That been said ds3622xs and RS4021 is your best choice for SAS.
  3. pocopico
    On a hw system that i've tested both performance and default "userspace" scaling_governors the results are the same. Performance : 265 Single-Core Score 487 Multi-Core Score vs Userspace: 264 Single-Core Score 480 Multi-Core Score
  4. pocopico
    I saw in the past and was thinking where the problem lies. I need to fix redpill-misc to not comment out the acpi-cpufreq if cpu has scaling capabilities. Do you happen to know which CPU FLAG is it ? It has to be est ? https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/x86/include/asm/cpufeature.h?id=refs/tags/v4.1.3
  5. pocopico
    @nemesis122 what is your benchmarking process ? Can you describe please ? I want to replicate so i can test.
  6. pocopico
    If you are getting this disk issue then your loader config file does not seem to have the ramdisk-005-disable-disabled-ports.patch Edit the config file and add ramdisk-005-disable-disabled-ports.patch to the list of ramdisk patches. "patches": { "_comment": ".bsp patches are applied to FILES using bspatch(1); .patch are applied to DIRECTORIES using patch(1)", "zlinux": [ "zImage-001-4021xsp-42962-ramdisk-and-header.bsp" ], "ramdisk": [ "@@@COMMON@@@/ramdisk-001-disable-root-pwd.patch", "@@@COMMON@@@/v7.1.1/ramdisk-002-init-script.patch", "@@@COMMON@@@/v7.1.1/ramdisk-003-post-init-script-noatime.patch", "@@@COMMON@@@/ramdisk-004-network-hosts.patch", "@@@COMMON@@@/ramdisk-005-disable-disabled-ports.patch" ]
  7. pocopico
    I doesnt matter since i suggest you replace the build line with : ./rploader.sh build ds920p-7.1.1-42962 withfriend
  8. pocopico
    Check the following setting in user_config.json. internalportcfg Its well documented in several threads in the forum.
  9. pocopico
    @Peter Suh Thanks to @jimmmmm and with minor adjustments by myself, the RS4021xsp power supply issue is now gone. My repo LKM contains the fixes. @fbelavenuto please adjust your LKM repo.
  10. pocopico
    @nualexan 55% error is related to the non existence of synoboot. If you use USB on a physical system then you need to set the VID/PID to the ones of your USB Stick. On VMware we are using SATA boot option and we fake the SATA for SATADOM.
  11. pocopico
    yes you need to change the internalportcfg as well to "0xffffffff". Its the hexadecimal representation of 32 drives all set to enabled: Drives : 1111 1111 1111 1111 1111 1111 1111 1111 It has been discussed several times in this forum. We can look this up. I've also found this : https://github.com/fbelavenuto/arpl/issues/304#issuecomment-1306796079
  12. pocopico
    What was your maxdisks setting in user_confg.json when you were building the loader ? The default is 16. You will not see additional drives unless you modify that and re-create the loader. "internalportcfg": "0xffffff", "maxdisks": "24",
  13. pocopico
    FYI, I extracted the U3 update file and smallfixnumber is 2. majorversion="7" minorversion="1" major="7" minor="1" micro="1" productversion="7.1.1" buildphase="GM" buildnumber="42962" smallfixnumber="2" nano="2" base="42962" packing="nano" packing_id="2" derived="nano" derived_id="2" builddate="2022/10/18" buildtime="14:51:38" builddate="2022/10/18" buildtime="15:30:48" unique="synology_broadwellnk_3622xs+" extractsize=855480 partitionversionlimit=0 syno_supported_hwrevision="r0" indexdbextractsize=1428 synohdpackimgextractsize=23512 packagerootextractsize=0 packagevolumeextractsize=0 EDIT: After the update though, the /etc/VERSION file reports : # cat /etc/VERSION majorversion="7" minorversion="1" major="7" minor="1" micro="1" productversion="7.1.1" buildphase="GM" buildnumber="42962" smallfixnumber="3" nano="3" base="42962" builddate="2022/12/07" buildtime="17:44:52"
  14. pocopico
    Its will have no effect ...
  15. pocopico
    You are right -> https://github.com/XPEnology-Community/redpill-lkm5/blob/568db23d3a93e03a30c8a682d6456b50fdc8dea1/config/cmdline_opts.h#L38 LKM only supports 4 MACs
  16. pocopico
    I'll have to look at that. BTW, you dont have to specify the 5th MAC to enable a 5th network interface ?
  17. pocopico
    You have to move the second to a new controller. To do so, click advanced and then move Virtual device mode from NVMe 0:1 to NVMe 1:0.
  18. pocopico
    Hi, did you ever find out what was the reason for not detecting the hard drives ? These systems come with different kind of raid controllers with P400 been the most common. HPSA extension should work but i havent tested that. You also need the disks to be set to JBOD mode and not RAID1/5/10/x As for the CPU, it depends on the platform you decide to use, but i think 3622 is the most stable one and supports 24 CPU threads as per the table found here : 3622 supports fibre channel OOTB for FC disk provisioning and bonding but depends on the type of network interfaces you decide to use.
  19. pocopico
    Nothing really important for now.
  20. pocopico
    OK, just did. I used your igc extension and now it points directly to your repo.
  21. pocopico
    Hi, can you please be more specific ? Which platform on what kind of hardware, what king of error etc.
  22. pocopico
    I think, that it would be safer to edit grub.cfg manually with a command like : sudo sed -i "s/set root=(hd0,msdos1)/search --set=root --fs-uuid BF4E-ADE7 --hint hd0,msdos1/" /dev/sda1/boot/grub/grub.cfg sudo sed -i "s/set root=(hd0,msdos3)/search --set=root --fs-uuid 6234-C863 --hint hd0,msdos3/" /dev/sda1/boot/grub/grub.cfg
  23. pocopico
    You can create a new loader for DS3622xs. If this is your Microserver N54L due to some issues in buildroot you cannot use withfriend option but you will be fine with GRUB usb boot option. The DS3615xs installation will be recognized if you use your old disks or if they are new it will install DS3622xs.
  24. pocopico
    Well it should load the bzImage-friend and continue booting, for some reason it did not. How much is the space you have left on the third partition ? Maybe its too low ? You can check from Tinycore with a df -h |grep sd and check your sdx3 free space
  25. pocopico
    привет, в моем последнем обновлении была опечатка. Я исправил это. Обновите с помощью обновления ./rploader.sh и повторите попытку.
×
×
  • Create New...