Jump to content
XPEnology Community

djvas335

Member
 View Profile  See their activity

  • Posts

    161

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Everything posted by djvas335

  1. djvas335
    The address which appears there is not the same address that the DSM will have, just run synology assistant to find which is the ip address being acquired by the DSM
  2. djvas335
    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
  3. djvas335
    Hi, Peter, how can we pass parameters for kernel modules, I tried using modprobe.d however this did not work, I need to set some parameters for mlx4_core driver to be applied at boottime
  4. djvas335
    Hi guys, sorry for hijacking the thread, but can this be built for microserver gen10+ with ilo5 ? Thanks in advance
  5. djvas335
    Наверное просто плохая или не подходящая память
  6. djvas335
    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
  7. djvas335
    Just friend, with friend no postupdate necessary
  8. djvas335
  9. djvas335
    You need to run friend once or do a postupdate from tinycore
  10. djvas335
    What is your hardware ?
  11. djvas335
    Please clarify issue you need help with
  12. djvas335
    I had an issue like this, building fresh latest loader seems to have fixed it
  13. djvas335
    Yepp also baremetal Microserver Gen8
  14. djvas335
    I had same message after upgrade, however my system just booted up with no issue
  15. djvas335
    I have moved the connectx3 and loader + hdd to a microserver gen8 with a xeon processor so that we can have similar bus width, mlx4 is now running at full speed please see below screenshot
  16. djvas335
    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.
  17. djvas335
    I removed mlx4_core.ko and mlx4_en.ko
  18. djvas335
    storage3 is a system where I removed mlx4 from all-modules so its using internal DSM driver, storage7 is running mshell with no changes
  19. djvas335
    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
  20. djvas335
    Tested, no more log noise
  21. 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
  22. djvas335
    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.
  23. djvas335
    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.
  24. djvas335
    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.
  25. djvas335
    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 ?
×
×
  • Create New...