Jump to content

Samishere

Member
  • Posts

    81
  • Joined

  • Last visited

Awards

This user doesn't have any awards

1 Follower

Profile Information

  • Gender
    Male
  • Location
    New York, USA
  • Interests
    Mostly donkeys, but other things as well.
  • Biography
    Born.
    Currently living.
    Not yet reported dead.
  • Occupation
    Network Administrator

System

  • CPU
    Intel Xeon W3670 @ 4.3GHz
  • Motherboard
    ASUS Rampage III Extreme
  • RAM
    48GB (6 x 8GB) DDR3 @ 903MHz G.Skill 10-11-10-30 2T
  • GPU
    NVidia GTX 980 Ti by MSI
  • Case
    Cooler Master Stacker 830
  • Storage
    2 x 480GB Crucial CT480M500SSD in RAID0, 2 x 1TB WD1002F9YZ in RAID0
  • PSU
    Rosewill Photon 750W
  • Display(s)
    1 x Dell S2716DG 27" GSYNC 144Hz, 2 x Dell 2007FP 20.1" 60Hz
  • Cooling
    Corsair H80i with push/pull fan config
  • Keyboard
    Cooler Master QuickFire Rapid-i
  • Mouse
    Gigabyte Aivia Uranium
  • Sound
    Logitech G930
  • Operating System
    Windows 10 Pro x64

Recent Profile Visitors

936 profile views
  1. Also worth noting that RDMA now works great on these cards when using Windows 10 for Workstations.
  2. Not to beat a dead thread, but I had to revisit this subject yesterday when I added a MHQH29C-XTR to one of my servers. It's one of the dual port QDR adapters. Below are the resources needed to flash the MHQH29C-XTR and the popular MHQH19B-XTR adapters to firmware 2.10.720 (RDMA supported) Things have gotten a bit more tricky than I last remember. You need to install WinMFT 4.3.0.25 for burning firmware to the ConnectX-2 cards. Later versions dropped support, namely the mic.exe binary and it's associated libraries. Install the above WinMFT version Open elevated command prompt, run command mst status Copy the device ID, for example mt26428_pci_cr0 Run the command flint -d mt26428_pci_cr0 query (substitute your device id if different) Note your Board ID or PSID. My cards only showed a PSID. If your ID is different than MT_0D90110009 or MT_0FC0110009 than I would refer to this guide for information about attempting to modify the firmware build for your specific card. Extra the firmware for the card from the appropriate attached ZIP to a easy to locate folder. Navigate to that folder in your command window. Run the following command, substituting your device ID if neccessary mlxburn.exe -dev mt26428_pci_cr0 -fw fw-ConnectX2-rel.mlx Once the process completes you can reboot the system and check the driver properties or run ibstat from a command window to check that the new firmware is running. Hope this saves someone some time, as I had to blindly try software versions and make modifications to the firmware until I got my adapter to take v2.10.720. MHQH19B-XTR Firmware 2.10.720.zip MHQH29C-XTR Firmware 2.10.720.zip
  3. I am using ConnectX-2 cards on 3 Windows 2012 R2 servers, and 1 Windows 10 workstation. I am using a Voltaire 4036 switch. At the moment I am just utilizing Infiniband for file transfers. Here are some of the nuggets from my experience. If you are using the MHQH19B-XTR or any ConnectX-2 gen card, firmware is very important. The "latest" firmware offered by Mellanox is something like 2.9.1000, however RDMA is NOT functional on this firmware version. There is newer firmware that is no longer available that you need to flash in order to support RDMA. I am using 2.10.720 on my MHQH19B-XTR adapters and RDMA is functioning just fine. I found this firmware EXTREMELY hard to find so for your convenience it is attached, and the flashing instructions in the OP still apply for this firmware. In the OP, an older version of WinOF was recommended. I am not sure why, but WinOF 5.35 for ConnectX-2 works just fine for me, and actually displays the connection as 40Gbps instead of 32Gbps even though there is no difference. RDMA is not available on Windows 10 professional so you will not be able to utilize the maximum line speed unless you are using a Windows Server operating system (version 2012 or newer). Using a Voltaire 4036 switch? You will need to be on firmware version 3.9.1 for RDMA to function properly. Google yourself a guide to do so, but in my quest I will say that most guides are written around using the serial management port and PuTTy, but the path of least resistance (and eBaying serial adapters) is SSH-ing into the eth port using PuTTy. My eth port wanted to request a new IP address from DHCP every 10 minutes or so, so I would also recommend giving it a DHCP reservation so you can keep a stable PuTTy connection. EDIT: I would also add that cable length is important in achieving stable and maximum speeds. If using copper cable, I wouldn't go over 3 meters if you intend on running your link at QDR. If using fiber length isn't an issue, but prices go way up. If you are having cable issues you aren't going to get a notification that the cable is bad, if you manage to get a 40G link your transfers will stall out and you'll see protocol errors in the SMBClient event logs. MHQH19B-XTR Firmware 2.10.720.zip
  4. Unfortunately you would need a new CPU. If you wanted to test you could pop in another CPU from another rig or borrowed, and if everything works with that RAM then the CPU is screwed.
  5. Try different RAM, if that RAM works then either the RAM is bad or isn't supported on that mobo. If the other RAM doesn't work too, then your motherboard might be damaged or the CPU's memory controller might be damaged.
  6. EDIT: nm sry, even the rev 1.2 board can only run up to 95w.
  7. Your motherboard can only support up to the FX8300 95W CPU since BIOS version F6. the FX8350 is a 125W CPU. Your board doesn't have the ability to supply enough power the run the chip properly. You can fix that without getting a new motherboard that can support 125W chips.
  8. Gotcha, I assumed linusmediagroup because of the forum@linusmediagroup.com posts.
  9. I just used mxtoolbox.com to do an SPF record lookup of linusmediagroup.com and it says no record.
  10. The problem appears to be on Microsoft's end, and we have been looking into solutions. Just my two cents, I know you use GoogleApps but you guys don't have an SPF record for your domain. Some SPAM filters can be fickle about that. You could also do a health check of your domain with the Outbound SMTP tool here: https://testconnectivity.microsoft.com/ I've had issues with Time Warner and Microsoft on email domains before because of missing or messed up SPF records or reverse DNS.
  11. If your board is FM2 check out this CPU (though it out of stock at a lot of places because it's out of production): http://www.newegg.com/Product/Product.aspx?Item=N82E16819113348 If your board is FM2+ then check out this CPU: http://www.newegg.com/Product/Product.aspx?Item=N82E16819113379 It's the best you are going to do on your board. The A8 A10 etc APUs just include a GPU that you won't be using.
  12. Check out OwnCloud. it's like Dropbox, but a private server version. It's fairly easy to set up and has a lot of awesome features.
  13. Run GPU-Z or afterburner to check your GPU utilization. If you are leaving your FPS uncapped in CS:GO and your GPU isn't getting pinged then there might be something wrong.
  14. That FPS doesn't look too bad for a 970 at that res, and remember that shadowplay leverages some of your GPU power for realtime recording. The FPS dips seem to happen during fast motion, which could be explained by shadowplay encoding.
×