madelectron

Members
  • Posts

    15
  • Joined

  • Last visited

About madelectron

  • Birthday 04/19/1978

Converted

  • Gender
    Male

Recent Profile Visitors

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

madelectron's Achievements

Noob

Noob (1/14)

3

Reputation

  1. using the watch command as it reboots and spins up 15 windows VM's, it is indeed turbo boosting threads up to 3.3Ghz, seems to be an issue with netdata and not the cpu scheduler. Thank you for helping me figure this out.
  2. I'm monitoring the cpu frequency per thread in Netdata. The returned result from your command is 1. As you can see with the attached image, every thread that has a burst load it being hard capped at 2.4Ghz, when it should be boosting up to 2.8-3.3Ghz, depending on the overall CPU load.
  3. I have two unraid servers both running epyc 2nd gen cpus, one is running a 7532 and the other one is running a 7282. This problem exists on both servers. Testing was done on the server with the 7532 32c/64t 2.4ghz base, 3.3ghz turbo. While running unraid, with running cpu govenor at on-demand, frequency scaling works but never goes above base clock of 2.4ghz. If I set it to performance, all cores/threads top out at 2.4ghz and statically stay there. Never any turbo boost. Using the same server, only changing boot drive from unraid usb to a HiveOS usb, and try to cpu mine crypto with the server. Mining on 1 thread, that thread runs at 3.3ghz, at 16 threads it's running at 3.2ghz, at 32 threads it's down to 3ghz on the mining threads, and finally with all 64 threads mining the cpu frequency is at 2.8ghz. So the server is properly configured to handle boost clocks from the cpu, but for some reason it is not happening in UnRaid. Is there any update that can enable this for EPYC cpus? Maybe a newer cpu frequency scaling driver?
  4. Could you add in sedutil suite? It was in the old version, and is needed so we can remove protection on SAS hard drives so they can be used in unraid. Thank you!
  5. When I run intel_gpu_top this is the result: Failed to initialize PMU! (No such file or directory) and yes I have IOMMU enabled.
  6. For some reason I can't get intel_gpu_top to display anything. At the command line all I get is file not found.
  7. I will give this a try today or tomorrow. Thank you!
  8. Ok, I'm officially drooling.......
  9. No worries, I'll be here patiently waiting. I figured the reported metrics would be less since it's an igpu and not a dGPU, honestly I'd be happy with just seeing the current load on it, especially with the emergence of 4k tone mapping transcoding.
  10. Are we able to restart the development of this plugin with IGPU quicksync support? I can help beta test if needed.
  11. The new generation of gigabyte z490 boards are using two super IO chips to gather temperature, fan speed, and pwm control. The in kernel driver is 3 years old, thus only supports the IT8792E Super IO chip, but doesn't have updated support for the IT9699E Super IO chip. I'm not that good around linux doing make commands and don't want to mess up my install. Is there a way to include this updated driver in one of the 6.9 betas? https://github.com/gamanakis/it87/tree/it8688E This info is gathered from this github issue discussion: https://github.com/lm-sensors/lm-sensors/issues/154 Thank you devs!
  12. I recently upgraded my system with a Gigabyte Z490 Vision D motherboard and a 10700k. I also upgraded my install from 6.8.3 to 6.9 beta25 right before the hardware upgrade so the system will support intel 9th/10th gen cpu's for hardware transcoding with IGPU. So I'm not sure if this is a beta issue, or a hardware issue. Help with the attached diagnostics please. thanos-diagnostics-20200831-0508.zip
  13. I recently had a HDD fail on my array for the first time, and decided to video the process of dealing with the issue and moving forward. This is filmed in a no nonsense, don't freak out style. I hope it helps you when this inevitably happens everyone.
  14. I love the fact that Limetech actually listens to it's userbase and tries to implement what we desire. In the short term I would have to say having multiple arrays would be my next goto addition to unraid.