|
If you're running Windows and using the mobo graphics (IGD), running a dummy plug (or having a monitor connected to the mobo DVI/HDMI port), ensures that Windows itself will use the internal graphics for the desktop, and not steal resources from one of the GPU's used for mining.
If you RDP to a rig @ 4k, you can easily observe the hash rate dropping on one of your GPU's if the desktop is not being rendered by the IGD. Not a big deal if you have your rig set to auto log in and start mining and keep an eye on things pool side, and/or use something like Awesome Miner to monitor. But if you like to keep a RDP session going and monitor the rig that way, it makes sense to force the desktop to use the IGP. RDP'ing at a lower resolution like 1280x1024 doesn't have as much impact as doing it at 4k.
|
|
|
|
I have one S9 where one of the boards stopped hashing overnight. All the ASIC chips still look good. Here's a pic:  So the board is still there, it is just not hashing. I rebooted that unit, but that one board still would not start hashing. Board dying? This is a 13.5T model, got it from Bitmain in December. Never messed with the firmware. |
|
|
|
I have the same mobo. I can't find a way to change to Gen 3. I tried in the tool menu of bios.
Advanced/System Agent (SA) Configuration/Graphics Configuration/PEG Port Configuration / Gen3, Gen3, Auto Advanced/PCH Configuration/PCI Express Configuration/Gen3 |
|
|
|
I changed a 2nd Asus PRIME Z270-A from Gen2 to Gen3. This one is running Win10 and 7x 1080Tis. Unfortunately one of the GPUs dropped out after the change:  That one GPU is not being assigned an Interrupt Line. All 7 GPUs in this rig are identical and use identical risers. Switched back to Gen2, and all 7 GPUs are working again. I'll try this on another Win10 rig (identical this this one) to see if I run into the same issue. |
|
|
|
Yep, regular old USB risers with 24" blue USB cables. Here's a pic of this particular rig:  I'll go check out the actual version, but I believe they are either 006C or 007C ones. |
|
|
|
root@miner011:~# dmesg | grep pcieport
[ 0.674260] pcieport 0000:00:1c.6: hash matches
|
|
|
|
Dansker? root@miner011:~# lspci -vv | grep -E 'LnkCap'
LnkCap: Port #2, Speed 8GT/s, Width x8, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us
LnkCap: Port #3, Speed 8GT/s, Width x8, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us
LnkCap: Port #17, Speed 8GT/s, Width x2, ASPM L0s L1, Exit Latency L0s unlimited, L1 <4us
LnkCap: Port #21, Speed 8GT/s, Width x4, ASPM not supported, Exit Latency L0s <1us, L1 <16us
LnkCap: Port #1, Speed 8GT/s, Width x1, ASPM not supported, Exit Latency L0s <1us, L1 <16us
LnkCap: Port #2, Speed 8GT/s, Width x1, ASPM not supported, Exit Latency L0s <1us, L1 <16us
LnkCap: Port #5, Speed 8GT/s, Width x2, ASPM not supported, Exit Latency L0s <1us, L1 <16us
LnkCap: Port #7, Speed 8GT/s, Width x1, ASPM not supported, Exit Latency L0s <1us, L1 <16us
LnkCap: Port #8, Speed 8GT/s, Width x1, ASPM not supported, Exit Latency L0s <1us, L1 <16us
LnkCap: Port #9, Speed 8GT/s, Width x4, ASPM L0s L1, Exit Latency L0s unlimited, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #1, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #1, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <2us, L1 unlimited
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
|
|
|
|
I would go check in your operating sysatem if they are really doing 3.0, because its highly unlikely that you get 3.0 with usb3 cable risers  I know on my win10 rigs I can use HWiNFO to see the speed. Is there a command line option under Ubuntu that will show me? |
|
|
|
alll risers support 3.0 (x1). well if motherboard support only 2.0, than the riser will do 2.0 as well.
Holy shit that worked!  Above screenshot is from Asus PRIME Z270-A. And a screenshot from HIVE OS after running gen3 for the last 20 minutes with no issues:  I have 6 rigs with those mobos, so hopefully they will take to gen3 fine as well. |
|
|
|
|
So some risers support pcie 3.0? Most of my recent risers are VER 008C, so maybe they do. When I initially setup my rigs, the guides all said to configure for pcie 1.0 or 2.0. I'll change the 7x 1060 rig with the Z270 mobo to gen3 and see what happens.
Also, I'm curious if the sqrl miner is free. I know it doesn't have a dev fee, which is nice.
|
|
|
|
I ordered a pair of 215+ yesterday (order #290). I'm trying for figure how I should deploy them for the most bang for the buck, so to speak. These are the rigs I have:  My initial thought would be to throw them both in the rig with 7x 1060 3GB cards and 2 available M.2 slots. However, those GPU's are all on x1 risers running PCIe Gen2 mode (I don't think the risers would work if I switched to Gen3 in the BIOS). But maybe? My 2nd option would be to stick one in the rig with 4x 1080Ti that are plugged directly into PCIe Gen3 slots @ x8. That rig has a 40 lane CPU. How would you deploy a pair of 215+ given my available rig configurations? |
|
|
|
|
Just placed an order for 2 of the 215+ units. Shipping & Handling came to $21.90 FedEx ground.
The drop down to select the batch number did not work in Chrome, but once I switched to Edge, it did.
|
|
|
|
|
Thanks, that did the trick!
|
|
|
|
I see that the EWBF CUDA Equihash miner 0.3 is included in the current 5.3.1 version of AM. So Equihash BTG (144.5) is supported from a mining software standpoint.
However, if I create a pool to mine BTG using the new algo, I don't see BTG listed on the coins drop down menu. In fact under the Equihash algo, I only see the coins that have not forked yet.
So will an upcoming version of AM include the new Equihash algos on the Pool drop down menu?
I do see the new Equihash algos under Options/Algorithms, they are just not there to chose from when setting up a pool.
 I don't have that in my version (v5.3.1 Premium):  I do have them all checked under algos:  But I haven't been able to bench any of them since I can't associate them with a pool. |
|
|
|
|
I see that the EWBF CUDA Equihash miner 0.3 is included in the current 5.3.1 version of AM. So Equihash BTG (144.5) is supported from a mining software standpoint.
However, if I create a pool to mine BTG using the new algo, I don't see BTG listed on the coins drop down menu. In fact under the Equihash algo, I only see the coins that have not forked yet.
So will an upcoming version of AM include the new Equihash algos on the Pool drop down menu?
I do see the new Equihash algos under Options/Algorithms, they are just not there to chose from when setting up a pool.
|
|
|
|
I just got one rack with a couple of mid towers in front (white case has 4x MSI 1080Ti Sea Hawk EK with 2x 480 rads, black case spots a pair of MSI 1070/1080 Sea Hawk X). Most everything else is EVGA.  The 3 S9's and 2 L3+ ASICs are off right now waiting for better times. The 3 Z9 Mini's are rocking though, as are all the GPU rigs. Earnings are way down of course, but still not too bad all things considered.  |
|
|
|
|
Thanks, that did the trick!
|
|
|
|
|
Does the Z9 mini work on this pool?
If so, what do I put in the password field?
I have this for far:
URL: equihash.mine.zpool.ca:2142#xnsub
Worker: My BTC Address
Password: c=<BTC>,d=92
The d=92 is what a Bitmain D3 uses. I'm assuming the Z9 would use a different value?
|
|
|
|
I'm surprised you're letting them go. I got 3 of those rascals running at 750 MHz and doing great. I'll trade you 3x S9 13.5 and 2x L3+ of you're interested. |
|
|
|
|
For the ETH Pill, just create a task for it using Task Scheduler. Be sure to:
Run with highest privileges
Configure For: Windows 10 (assuming that is your OS)
Trigger at log on
Uncheck "Stop the task if it runs longer than:"
I do the same for Afterburner Remote Server. Works great for both.
|
|
|
|
|
Show Posts
