The problem is that the manufacturer wont admit that your card is faulty, I wonder what would you tell them to describe your problems? I'm pretty sure you wont tell them you are doing mining.
back to GPU prob, Ensure that you have a pretty decent PSU to handle those monstrous power hunger cards.
Yes, that is always the dilemma. 1600W supply with a 750W so power isn't the problem.... I have made some progress. These cards will do well over 800 h/s on equihash at 100% power... but there seems to be a relationship between core and mem. E.g. by default they overclock it appears so even a 0+ on core will run them at a 2000mhz core clock, they are garanteed for 2025 core. and can run up to 2100mhz. So I've backed the core clock back to +0 and the mem clock back to +550 (from the +850 I was running). Seems to have made a difference. I noticed however when I pushed the mem clock back down, the core clock decreased as well. Curious. haven't changed the power and maybe that is why it's limiting internally. Anyway, it will run DSTM just fine on any of the numbers above.... but this one card, when you stop DSTM, will go into in a race condition with it's IRQ's. So the battle continues, but I have made some progress |
|
|
|
|
I have a fairly new 6 GPU rig. It's on a Asus Prime Z270-A MB and uses risers. The GPU's are all EVGA Kingpin 1080 Ti's.
The problem is really rather strange and I'm looking to see what others might suggest as a form of debugging.
I can launch any of the mining software under either windows or Linux and the miner will perform flawlessly. Even OC it up to 800+ h/s per card on equihash with no issues.
But it's when I go to stop the software that I have a problem. One of the cards, and it seems to be the same one every time. Will then lock up the computer with an IRQ pending request. I can see this under linux as a stuck process called IRQ/XXX-nvidia (the XXX is a 3 digit number). Once I unplug the card from the riser, that will clear and the system utilization will return to normal. Same thing happens under windows 10.
Again, this does NOT effect the function when the mining software is running, just after... but any time you stop the software, this will happen and if you don't want to risk some hardware damage by unplugging that card, you have to do a hard reset.
I've done all the obvious stuff. swapped risers, swapped slots, etc and the problem always follows the card. As an aside I have noticed that this card is always the lowest of the batch of 6 from a h/s standpoint.
Once I remove this card from the system, I never see this issue on 5 cards.
Any thoughts on what I should try before I attempt to get warranty replacement from EVGA?
Thanks in advance,
|
|
|
|
How can i sell my s9s?
Haha, I'm thinking of selling my S9 or exchanging it for few 1070s lol. funny you mention that, I just did the math 30Th ASIC = ~30.00 a day (us), 6 1080 ti GPU = $40 a day  6x$1300=holy sh*t! 1x$4000=nice! By the way, to get 30TH you'd need more than 2 S9 and you'd be making like $40 a day at the current BTC price. I just think that GPUs are better in terms of options. You can mine whatever you want, lot quieter etc. yeah, luckily I bought my 1080 ti's *before* all this price stuff happened, even in the GPU area... so I'm into them *way* less than $1300/ea |
|
|
|
How can i sell my s9s?
Haha, I'm thinking of selling my S9 or exchanging it for few 1070s lol. funny you mention that, I just did the math 30Th ASIC = ~30.00 a day (us), 6 1080 ti GPU = $40 a day |
|
|
|
It's only faster in reported values on it's console. Run it for 24hs on a pool and it will be *less* than DSTM and with wild variation in the reported hash rate. |
|
|
|
|
has anyone made zpool work with profit mining?
I've now tried 2 different btc addresses and verified that the -p c=BTC is being sent on the commandline, But in both cases, the coins mined are in BCH not BTC and it doesn't matter what I do to correct that. yes I have the checkbox marked to force zpool to BTC, that's where the c= is coming from.
|
|
|
|
|
ok, seeing as the last time I - *jumped on the pool*, we found the block... In the same spirit, I added another 8TH. I suppose you could call it another 16TH as I added another 8 immediately after that last block.
Mine on!
|
|
|
|
ok, will do that and report any adjustments. I've never had to do that with any other miner software so far... But it doesn't really matter, because this is just a test anyway Software reports hashrates are up from the other miner software that I've ran in comparison, but that really doesn't tell you anything, what counts is what the pools shows. ps. can you talk to awesomeminer.com to see if they can support your miner - please?? |
|
|
|
I would strongly advise people to look at their mining pool hashrate for this miner and not the miners reported hashrate... Do the test...  I'm beginning to think the same thing but it's more than that, when you first run it you get really nice looking numbers, then after a couple of hours, what you say sets in. Here is the comparison of DSTM vs BMiner. First line is DSTM that had been running for a few days Next line is Bminer after 3 hours. I saw grossly deviating current hash as well. This was a GTX 950 that I just happened to have, but the two sets of number are on the same computer with the same hardware, etc. Current Hashrate Average Hashrate
0H/s 155.9H/s
80H/s 147.9H/s
As a final test, I'm going to leave it running in -nofee mode while I do some other work on a different miner Can you run your numbers again with devfee turned on? The miner will disable a number of optimizations if you disable devfee. Maybe I mis spoke - those numbers above are *with devfee turned ON* and are what FlyPool is reporting, not the miner software. Probably the biggest problem is that the radically changing instant hash rate, I see it cycle up and down by huge margins like over 100h/s in this case and this is just a small GPU. I'm running in -nofee mode right now just to see what happens |
|
|
|
I would strongly advise people to look at their mining pool hashrate for this miner and not the miners reported hashrate... Do the test... I'm beginning to think the same thing but it's more than that, when you first run it you get really nice looking numbers, then after a couple of hours, what you say sets in. Here is the comparison of DSTM vs BMiner. First line is DSTM that had been running for a few days Next line is Bminer after 3 hours. I saw grossly deviating current hash as well. This was a GTX 950 that I just happened to have, but the two sets of number are on the same computer with the same hardware, etc. Current Hashrate Average Hashrate
0H/s 155.9H/s
80H/s 147.9H/s
As a final test, I'm going to leave it running in -nofee mode while I do some other work on a different miner |
|
|
|
so not sure if something changed but I got a .001 BTC payout, maybe with the lower fees, the pool payed below the .01 which everyone had said was the threshold?
.01 is the threshold for slush...you sure you're on the right page? Ha, it's even more funny that that... I was wondering if a .001 would get paid from Kano, *BUT* I posted the question on the slush thread... duh, didn't even notice it until now. So keep on mining and ignore my idiocy... yeah was nice to see the .001 paid - from KANO - my first and only at about 20% ramp |
|
|
|
|
so not sure if something changed but I got a .001 BTC payout, maybe with the lower fees, the pool payed below the .01 which everyone had said was the threshold?
|
|
|
|
hopefully only a small bit of education. Jumped in a couple of days ago with 20THs. Scored on the first block from last night. Watched it mature, and the payment and reward show on my account. So when do the actual transfer happen to my wallet? Just checked and nothing so far? Is there a built in delay that I failed to read the memo on? Thanks in advance, you have to get up to .01 before getting paid...(you can get paid on smaller amounts but there's a fee). ah... perfect... Wasn't sure if there was a min. and I know that Kano is working on making that selectable... perfect, it was only .001 so it will just have to wait ... thanks for the reply |
|
|
|
hopefully only a small bit of education. Jumped in a couple of days ago with 20THs. Scored on the first block from last night. Watched it mature, and the payment and reward show on my account. So when do the actual transfer happen to my wallet? Just checked and nothing so far? Is there a built in delay that I failed to read the memo on? Thanks in advance, |
|
|
|
Been *reading the mail*. In for the haul. Added 20Th/s (wooo hooo ...) |
|
|
|
NOOB WARNING:
Just wanting to confirm. Moving over to Kano.
Created an account, that is all good
Miner setup: Stratum done
User/Worker: so I used my <username>.<funname>
passwd: x
Is that all that's required? I guess I thought my worker name would be sans the username, but maybe not as it shows up how I entered it in the workers list.
It's all working it shows up in workers, just wanting to confirm I didn't screw something up?
Thanks in advance,
that's it. is there any other post setup that I need to do? How do you set the payout threshold? I can't seem to find that setting |
|
|
|
|
NOOB WARNING:
Just wanting to confirm. Moving over to Kano.
Created an account, that is all good
Miner setup: Stratum done
User/Worker: so I used my <username>.<funname>
passwd: x
Is that all that's required? I guess I thought my worker name would be sans the username, but maybe not as it shows up how I entered it in the workers list.
It's all working it shows up in workers, just wanting to confirm I didn't screw something up?
Thanks in advance,
|
|
|
|
I logged in with it fine a few minutes ago.
Ok, got it... used a wrong app to generate the keys... Anychance you can support the Google Authenticator? (just because I have everything inside of it already ...) That is what I am using. No issues. Well I've no idea why sometimes people have trouble with Google Authenticator, but other times they don't, but the main advantage of the one I list on the web site is you can also manually setup a 2FA if you know the "Secret Key" It's all very clear about the settings it has but of course doesn't disclose the "Secret Key", and it's written by Red Hat so there's no trust issues Yeah it is just a simple "point your phone at the QRCode on the screen" for normal use, but it's also possible to look at the settings and manually set it up. Meanwhile Google Authenticator has been abandoned about 3 or 4 years ago  I'd suggested to use FreeOTP instead. What I did and it worked fine... guess I'll move over the others to it |
|
|
|
I logged in with it fine a few minutes ago.
Ok, got it... used a wrong app to generate the keys... Anychance you can support the Google Authenticator? (just because I have everything inside of it already ...) |
|
|
|
|
Show Posts
