Jump to content
XPEnology Community

djvas335

Member
  • Posts

    161
  • Joined

  • Last visited

  • Days Won

    2

djvas335 last won the day on June 27 2023

djvas335 had the most liked content!

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

djvas335's Achievements

Advanced Member

Advanced Member (4/7)

43

Reputation

  1. 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. 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. 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. Hi guys, sorry for hijacking the thread, but can this be built for microserver gen10+ with ilo5 ? Thanks in advance
  5. Наверное просто плохая или не подходящая память
  6. 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. I had an issue like this, building fresh latest loader seems to have fixed it
  8. I had same message after upgrade, however my system just booted up with no issue
  9. 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
×
×
  • Create New...