Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About blackmanga

  • Rank

Recent Profile Visitors

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

  1. Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-update 5 - Loader version and model: Jun's v1.04b - DS918+ - Using custom extra.lzma: YES - extra918plus_v0.13.3 - Installation type: BAREMETAL - MB: Gigabyte H97N WiFi, CPU: Intel Xeon E3 1245 v3, onboard Intel and Atheros NIC, 10 GB Mellanox connectx-3 dual card - Additional Comments: Reboot required; Everything worked except the issue with eth2/eth3 (solution below) ~ Added to be safe; ~ /dev/dri exists - i.e. HW transcoding is working; ~ changes for extra LAN ports m
  2. I get the following error when i use extra.lzma v0.6 on DSM 6.2.2 U5 918+ Juns 1.04b loader. MB: Gigabyte H97N WiFi CPU: Intel Xeon E3 1245 v3, 16GB Ram Onboard NICs are working fine, but when i load the modules for Mellanox Connectx-3, i have a segmentation fault and the system crashes. Any insights will be really appreciated. [ 163.275915] Compat-mlnx-ofed backport release: f36c870 [ 163.275918] Backport based on mlnx_ofed/mlnx-ofa_kernel-4.0.git f36c870 [ 163.275919] compat.git: mlnx_ofed/mlnx-ofa_kernel-4.0.git [ 163.286603] mlx4_core: Mellanox
  3. Thank you very much ! Happy for the thread to be closed. cheers
  4. Hi Olegin, thank you for your reply. So dynamic scaling doesn't exist for powersave/performance governos. i.e. the CPU will always run at the fixed frequency when its in those modes. Is my understanding correct ? I am not too fussed about HW transcoding at the moment, so I will revert to 3617xs and DSM 6.2 if that is the case.
  5. My bad. its @Polanskimanwho has the same MB and not @Olegin. Sorry about the confusion, but any advice is welcome.
  6. Hi, I have read through most of the threads on CPU power throttling and am still not sure I have a proper solution to reduce CPU dynamic scaling. I can only use the following governors (powersave/performance) - which as someone pointed out, are the only ones available with intel_pstates. However, when I choose either of them, my CPU is stuck at 3.4Ghz (performance) or 800Mhz (powersave) without any dynamic scaling or boost. Specs HW: CPU: Xeon E3 1245 v3, MB: Gigabyte H97N WiFi, RAM: 16GB - 2x8GB 1600Mhz I am using 1.04b bootloader and running DSM 6.2.1 - 23824 updat