I'd like to ask the community, though - what coin would you like to see next for SGMiner-GM?
ZCash would be awesome, but i am aware it's highly improbable
XMR support has been added!
Keep in mind folks, this is a pre-release version. Currently, there is a bug with Windows where it crashes upon mining. We're able to reproduce it, but not able to
find it.
I'd like to ask the community, though - what coin would you like to see next for SGMiner-GM?
I'm getting steady 30MH/s on each Fury X on stock clocks (1050/500). Claymore's can only get about 28MH.
A 390 at 1040Mhz gets 29Mh, with some overclocking I can surely can 32-33MH, but my cards warm up too much. Definitely the best miner out there.
The only issue I can spot is the CPU usage, which makes this miner basically worthless on weak CPUs. I couldn't run it on a single-core AMD CPU and a friend of mine had his rig crashing with a dual core Celeron installed. most mining rigs have very weak CPUs, and if this miner gets updated to support them, I am sure it will get much more traction.
Has it been determined that this issues running on systems with weak CPUs is real? Is there a fix coming? I am wondering if this is the problem I am having on my multi-gpu mining rigs. One GPU run at the right hash rate while the others run at half. No matter what I do with the settings I cannot resolve this issue. Both rigs have single core AMD CPUs. I would love to use sgminer with its RPC capabilities but I am not going to invest in bigger CPUs for it.
Thanks.
If you search Wolf0's post in this thread, you will find that he posted a fix for the CPU usage bug.
Here it is again for those that don't want to look back through the thread. I can confirm it no longer hogs the CPU on one core.
https://ottrbutt.com/miner/downloads/sgminer-gm/sgminer-gm-wolf-09222016.zipcopy sgminer.exe from the zip to the existing install directory.
I've gone ahead and added Wolf's fixed sgminer.exe to the release page, here:
https://github.com/genesismining/sgminer-gm/releases/tag/5.3.0-gmI would like to see the bugs in the current version fixed. sometimes it just says "found a block" at random times. additionally the miner has a bug where it stops showing the hashrates and shares if click on the miner's window. other than that it's a great miner.
Maybe Zcash? I'm sure it will make it really popular.
Zcash is not improbable. However, we wouldn't have something available on Zcash's launch. We'll look into it. I can't promise anything, but I can't deny we won't add it, either.
XMR support has been added!
Keep in mind folks, this is a pre-release version. Currently, there is a bug with Windows where it crashes upon mining. We're able to reproduce it, but not able to
find it.
I'd like to ask the community, though - what coin would you like to see next for SGMiner-GM?
I'm getting steady 30MH/s on each Fury X on stock clocks (1050/500). Claymore's can only get about 28MH.
A 390 at 1040Mhz gets 29Mh, with some overclocking I can surely can 32-33MH, but my cards warm up too much. Definitely the best miner out there.
The only issue I can spot is the CPU usage, which makes this miner basically worthless on weak CPUs. I couldn't run it on a single-core AMD CPU and a friend of mine had his rig crashing with a dual core Celeron installed. most mining rigs have very weak CPUs, and if this miner gets updated to support them, I am sure it will get much more traction.
Has it been determined that this issues running on systems with weak CPUs is real? Is there a fix coming? I am wondering if this is the problem I am having on my multi-gpu mining rigs. One GPU run at the right hash rate while the others run at half. No matter what I do with the settings I cannot resolve this issue. Both rigs have single core AMD CPUs. I would love to use sgminer with its RPC capabilities but I am not going to invest in bigger CPUs for it.
Thanks.
If you search Wolf0's post in this thread, you will find that he posted a fix for the CPU usage bug.
Here it is again for those that don't want to look back through the thread. I can confirm it no longer hogs the CPU on one core.
https://ottrbutt.com/miner/downloads/sgminer-gm/sgminer-gm-wolf-09222016.zipcopy sgminer.exe from the zip to the existing install directory.
I've gone ahead and added Wolf's fixed sgminer.exe to the release page, here:
https://github.com/genesismining/sgminer-gm/releases/tag/5.3.0-gmSEGMENTATION FAULTS WITH CRYPTONIGHT--
Segmentation faults and a hard reboot result when attempting to mine CryptoNight under Ubuntu 14.04 with R9 280X GPUs. The archives on the release page do not contain "cryptonight.cl", and while I was able to dig the file out of the git source, I was not able to mine successfully.
I took the solo Ubuntu binary from the opening page, substituted it in the miner directory, sourced "cryptonight.cl" from git, and was able to boot the miner and generate "bin" files, but then I got a hard hang requiring a reboot. The error message stated "Error 61...". Taking a clue from Wolf's other XMR project, I used work sizes of 8 and 16, with xIntensities of 320, 640, and 1024. Lots of reboots and USB riser jiggling.
A sample configuration file for mining CryptoNight with this miner would be helpful. I simply adapted the sample Ethereum configuration, setting "cryptonight" algo as default for a single pool. --scryptr
EDIT: I am able to mine with Wolf's other XMR project, but not on NiceHash. NiceHash has specific extranonce requirements for CryptoNight. --scryptr
First: Cryptonight.cl is in the directory.
Second: Intensity of 320 will kill your 280x. Please don't use that. That's a RawIntensity of 32x64x320. That's 655360! That is a hell of a lot of work for your poor GPU.
Third: You're not mining successfully because of your settings. Don't reuse settings from Wolf's other projects with sgminer-gm. They're two separate entities. One is a custom made, stand-alone miner. The other is, well, sgminer.
Fourth: Don't ever use xIntensity. Rawintensity only. Try 448, move upwards from there.
The formula for rawintensity is #(CUs) x worksize x 4 - so, for a 280x, you'd have 32 x 4 x 4. That gives us
512. Now, keep in mind, memory latency and bandwidth will come into play here, so you will need to tinker.
Here is a sample configuration:
{
"pools": [{
"name": "MoneroWorld",
"url": "stratum+tcp://pool.minexmr.com:4444",
"user": "41dPExBcrTjHU5fY41NLeKN3Zm6JFmxcC5BiEzGXC2WH1mj9hQV1VzLVcxeQVxavdURzXNCHmXLSgeH7KEfzLUFhPhidXJB",
"pass": "x",
"profile": "xmr"
}],
"profiles": [{
"name": "xmr",
"algorithm": "cryptonight",
"rawintensity": "448",
"worksize": "4",
"gpu-threads": "2"
}],
"default-profile": "xmr",
"no-extranonce": true
}