Jump to content
XPEnology Community

djvas335

Member
 View Profile  See their activity

  • Posts

    161

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by djvas335

    TinyCore RedPill Loader Build Support Tool ( M-Shell )

    in Software Modding

    Posted

    Thanks for replying, I checked the link however I did not find the relevant information, can you please point the relevant section ?

     

    What I need is to add some options to the mlx4_core driver like this, I am not sure how to do this, is this to be done at loader creation ? Or this can be done directly from DSM ?

      

    options mlx4_core roce_mode=2

     

    5 hours ago, Peter Suh said:

     

     

     

    Microserver N54L

    in Аппаратное обеспечение и совместимость

    Posted

    Наверное просто плохая или не подходящая память

     

    37 minutes ago, level001 said:

    Подскажите при добавлении памяти надо переконфигурировать arpl ?

    Ставлю 2 планки по 4 уходит в перезагрузку при загрузке dsm 7.1 , биос ее видит.

    Ставлю старые планки 2+1 всё нормально грузится.

    Просто новый arpl 1 хочет больше 4 памяти. И он тоже 4+4 не грузит dsm.

    1+2 ecc 4+4 non ecc.

     

     

     

    Cannot access NAS after update to 7.2

    in The Noob Lounge

    Posted

    If you are using tcrp, then you need to choose friend, so that friend can update your setup when you change firmware and leave it on that boot option

     

     

    On 6/27/2023 at 8:59 PM, TemplarB said:

    Update. I've decided to go cardinally and after saving last User_config.json and checking it (unsure why but it lacked e.g. serial number and had a different vid/pid even despite I haven't moved sd-card) and run all commands from this tutorial: 

    Namely: 

    ./rploader.sh clean
./rploader.sh update
./rploader.sh fullupgrade
./rploader.sh identifyusb
./rploader.sh serialgen DS3622xs+ 
./rploader.sh satamap
./rploader.sh build ds3622xsp-7.2.0-64570

    While I haven't specified "withfriend" it added it at the end according to thhe log.

     

    I rebooted and chose in GRUB last option (something with friend) It worked to the final message ("loading kexec...") no errors

    I opened Synology Assistant and it found the "recoverable" (no surprises, I rebuilt with new serial, so it is new). It has only one option "recover" I pressed it, it says "installing DSM" quickly goes from 0 to 100% and writes "restarting in 10:00" and counts down. Meanwhile the server reboots and I choose 1st option in GRUB (load USB, Verbose)

    it shows that "booting the kernel." like usual. However

    Synology Assistant does NOT initially sees it and later goes back to option "recover"

     

    • Thanks 1

    DSM Version: 7.2-64561 Released (The official version)

    in Readers News & Rumours

    Posted

    I had an issue like this, building fresh latest loader seems to have fixed it

     

    30 minutes ago, freddie said:

    hello, I do run ./rploader.sh postupdate ds3622xsp-7.2.0-64570 and he found the U1, I agreed twice and when i restart with usb boot, nothing always recuperable (recovery) and now telnet services activated for diagnostics !! where i do wrong ??

    and booting with TCRP friend my ip changed and my card network doesn't working !

     

    TinyCore RedPill Loader Build Support Tool ( M-Shell )

    in Software Modding

    Posted

    I had same message after upgrade, however my system just booted up with no issue

     

    On 6/27/2023 at 9:28 AM, Biocef said:

    Hello,

     

    I can't update from 7.1.1-42962-6 to 7.2-64570-1, DSM won't restart.

    I did the update from the DSM GUI, TCRP detects it but shows "Hunk1 FAILED 1/1".

    I tried redoing a new install in 42962-6 but same error when updating to 64570-1.

     

    Why do I have this error?

     

    Thanks

    2023-06-27_09h02_59.png

     

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    Please also note the systems are different, storage3 is a microserver gen10 Plus and storage7 is microserver gen8, you can see that mlx4 is not running at full pciex speed on storage7 because of cpu bus limitation.

     

    3 minutes ago, Peter Suh said:

     

    Using the vanilla mlx_compat.ko was effective in getting rid of the noise, but the loading of mlx4_ib.ko seems to be missing. In addition, the log indicates that the speed is also reduced without the loading of this module.
    After figuring out the characteristics of this module file a little more, let's find out how.

     

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    However something is still missing, please see screenshot from system running without mlx4 in all-modules, please note the part with mlx4_ib, its missing from screenshot from storage7

     

    Screenshot2023-06-27at15_14_58.thumb.png.645f86214febb798afab1d9d5e7677cf.png

    30 minutes ago, Peter Suh said:

     

     

    It seems that the response time of the nic module is also faster than the result of last noise.

     

    Screenshot2023-06-01at18_03_05.thumb.png.2057ddda51282c66408d99a474feda0f.png.a0d01c36893134d9b98fb55233d70cda.png

     

     

     

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    Tested, no more log noise

     

    Screenshot2023-06-27at14_18_19.thumb.png.772c2189f752c48ff62228f76b8bb34a.png

     

    1 hour ago, Peter Suh said:

     

    Don't use pocopico's TCRP img, rather re-record with MShell's img.

    There is no problem if you back up only the SN and MAC information and write them again.
    This seems like a quick way to switch to M SHELL.

     

    • Thanks 1

    Cannot access NAS after update to 7.2

    in The Noob Lounge

    Posted · Edited by djvas335

    Update to a latest version of the loader, clean the loader and build the loader again, better do it from scratch, after that just go to the new IP and do a recover system, the friend will update the bootloader and the system should boot normally, if it asks to install new dsm, latest loader is dsm7.2.0 update 1 so you will have to download and update your system after latest loader rebuild

    • Thanks 1

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    I will test later today, I need to build an additional system for testing as other systems are running in production as of now, also please note that mshell build requires partition size expansion as default partition size of tcrp is not sufficient for the mshell to build the loader.

     

    2 hours ago, Peter Suh said:

     

    There is one thing different from the last test with you.
    The link below is a place where vanilla modules related to mlx4 are kept.
    https://github.com/PeterSuh-Q3/arpl-modules/tree/main/vanilla/broadwellnk-4.4.302

     

    In addition to mlx4_en.ko and mlx4_core.ko , we have confirmed that mlx_compat.ko has additional dependencies.
    Have you tried the added version as a vanilla module up to mlx_compat.ko with MSHELL?
    Could you please confirm that this test also shows the logs you are concerned about?

     

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    But I do not want to exclude the module mlx4 from loading in DSM, I want that the mlx4 module included in all-modules in the loader do not load so that the module included in DSM loads, the mlx4 included in the all-modules does not work and crashes my system when I access after the system started up. So what I want is for the vanilla mlx4 driver in DSM take over from the mlx4 included in the all-modules pack.

     

    7 hours ago, pocopico said:

     

    Since we are using gnu tar to extract the modules at boot or at loader creation the exclusion of some modules is not a very difficult task.

     

    If you want to specify a module to be excluded from DSM you can add modprobe.blacklist=mlx4 at your linux command line. 

     

    I will include that in the next release of the HTML Builder.

     

    How we identify the module that actually cause KPs is the most difficult part cause you have to read the KP message.

     

     

     

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    Actually I did give feedback that modules worked but there was some log noise before driver load if you remember we had a conversation on that, I now built the new loader using HTML builder and had issues again with the mlx4 driver thus my forum message, I overcame this for now by removing the mlx4 driver from the tgz and copying the rebuilt tgz via scp to its final location after the loader is built and rebuilding the loader again.

     

     

    13 hours ago, Peter Suh said:

     

    Currently, this mlx4 has been removed from the DDSML method of MSHELL for TCRP.
    In this removed state, the built-in modules (vanilla modules) already included in DSM are used instead.It has already been reflected in M SHELL by your

     

    request a while ago, What other problems are there?

    I didn't have your last feedback, so I asked another user with the same nic to test it. There was nothing wrong with his feedback.

     

    In addition, if the user wants to exclude modules with additional issues,

    I am considering using modprobe.blacklist in MSHELL's DDSML method using modprobe.

     

     

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    Please can something be done with modules which crash system on startup when affected hardware is present ? The all-modules is creating issues each time the loader is recreated, is there an option to remove drivers which cause problems from it ? For me I need to remove the mlx4 driver as it crashes my system on startup. Any suggestions for this ?

    • Confused 1
×
×
  • Create New...