 Show Posts
|
|
Pages: « 1 [2] 3 »
|
|
Maybe Intel Xeon D servers. Something like the barebones Supermicro SYS-E300-8D. More expensive ones are SYS-E200-8D and 5028D-TN4T. These servers are compact, low power, not too loud, with lots of ethernet ports.
Lots of ethernet ports so you can put the masternodes in an isolated or DMZ network separate from management and other VMs for security purposes. Use a hypervisor like VMWare or Hyper V. Can run many masternodes in VMs because those servers can take 128 GB ECC RDIMM.
Entry-level Dell PowerEdge is probably fine if you wanna go cheaper.
|
|
|
|
Use kernel 2 set up gpus in gpu_conf, there is an example on the first page
Thanks. It works now. |
|
|
|
|
I can't get the newest miner 1.6.5 to work. You can see the error below. Previous versions including 1.6.4 work fine.
I am using some older cards, Tahiti, and AMD driver 18.3.4.
GPU0: AMD Radeon R9 200 Series [Tahiti] [3072 MB][Intensity 27.0][W: 8][T: 2][K: 1][BUS: 1]
GPU1: AMD Radeon HD 7900 Series [Tahiti] [3072 MB][Intensity 38.0][W: 8][T: 2][K: 1][BUS: 2]
---------------------------------------------------------
SRBMiner Cryptonight AMD GPU miner 1.6.5
DevFee only 0.85%
Press 's' to get some stats
Press 'h' to get some hashrate
Press 'r' to reload pools
Press 0-9 to disable/enable GPU while mining
Give it a few minutes to reach maximum hashrate
---------------------------------------------------------
Total pools: 2
Please wait...
CryptonightV7 mode enabled
[2018-08-03 14:18:42] Heating up system, please wait...
[2018-08-03 14:18:42] Compiling kernel for DEVICE BUS ID 1 ...
[2018-08-03 14:18:42] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram for DeviceID 0 (Thread 0)
Stopping miner...Uno momento
Press any key to continue . . .
|
|
|
|
|
I still use my tahitis . Try cryptonight haven/heavy/tube.
|
|
|
|
|
For monero using Vega 64 I got improved performance upgrading from the first release.
00:49:36 | Hashrate GPU Thread 0: 1064.70 h/s
00:49:36 | Hashrate GPU Thread 1: 1063.73 h/s - Total GPU 0: 2128.42 h/s
Overclocks:
Core 1408 MHz @ 905 mV
Memory 1100 MHz @ 900 mV
This config.txt setting seems slightly better than the previous one I posted:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash":1936 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash":1936 },
I tried increasing intensity to 1952 but hashrate dropped, so maybe 1936 could be the max.
|
|
|
|
I've re-uploaded the 0.30b with the extra Nicehash fix. I recheck at every step the Job and the nonce is still valid. And again before sending the result to the pool. If nicehash after that still says the nonce is invalid or the job doesn't exist, well, i'm out of ideas.
i also added the total cpu hashrate in the log.
Maybe some problem with fixed difficulty added to wallet string? '.500000' is not recognized as an internal or external command, operable program or batch file. C:\Users\anwar\Desktop\jce_cn_gpu_miner.prototype.030b>jce_cn_gpu_miner64.exe -c config.txt --no-cpu --any --forever --variation 7 --low -o stellite.ingest.cryptoknight.cc:16223 -u Se3oCb3DbCzSUXnDeUtZq5gCbZ68ZmXahQaetshwYzun2pPhXPvfh3zSQhjFNjVjrtbjcA8hoKd5UAz YKFHoD4LR1Xi5a1M82 -p 6 |
|
|
|
JCE, You said you have no Vega to test, if you like, I can set up one rig with 1 or 2 Vegas with standard mining cofiguration and share the teamviewer with you if you like to test or whatever configuration is easy for you for testing (windows 10) as long as you don't touch the network or can influence my other rigs I tried to test this on my Vega rigs but have no idea how to set it up  Removed the --auto and tried some settings but then gave up Now I am back to STAK, because CAST and SRB both proved for me to report mucch higher hashrate than the pool, sometimes it can be up to 20% (no i am not talking about instant hash power but calculated over several weeks) 7x Vega rig on STAK has 13500 and more than 14000 on SRB and CAST but pool reports 13500 for STAK and sometimes as low as 11000 for SRB and CAST So I have high hopes for your miner and will happily switch all my rigs if the thing is ok My Vega settings are on page 28. There are two entries for each gpu in the config file. Sometimes the index starts from "0" and sometimes from "1". Basically have to run it and see if a GPU isn't working or recognized. Would be nice to get more opinions because there is probably room for improvement. In the bat file, instead of "auto" change to this: -c confgpu.txt --no-cpu |
|
|
|
Monero (Cryptonight V7) AMD Driver 18.6.1 7 x Vega 64 In castxmr and xmr-stak (intensity 1932 double threads) I get around 13800-13900 h/s. In JCE (intensity 1920) got 14300-14400 h/s. So a little bit better than those. Dunno about SRB. Probably gonna be same results as cast and stak. All this hashrate is what the mining software has reported. Also, I briefly tried haven algo but saw no significant improvement over competitors. Vega 64s
confgpu.txt
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash":1920 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash":1920 },
(etc.)
12:08:34 | Hashrate GPU Thread 0: 1019.38 h/s
12:08:34 | Hashrate GPU Thread 1: 1042.35 h/s
12:08:34 | Hashrate GPU Thread 2: 1022.37 h/s
12:08:34 | Hashrate GPU Thread 3: 1035.88 h/s
12:08:34 | Hashrate GPU Thread 4: 1026.74 h/s
12:08:34 | Hashrate GPU Thread 5: 1029.77 h/s
12:08:34 | Hashrate GPU Thread 6: 1030.88 h/s
12:08:34 | Hashrate GPU Thread 7: 1024.28 h/s
12:08:34 | Hashrate GPU Thread 8: 1020.92 h/s
12:08:34 | Hashrate GPU Thread 9: 1031.15 h/s
12:08:34 | Hashrate GPU Thread 10: 1007.70 h/s
12:08:34 | Hashrate GPU Thread 11: 1027.57 h/s
12:08:34 | Hashrate GPU Thread 12: 1019.47 h/s
12:08:34 | Hashrate GPU Thread 13: 1027.29 h/s
12:08:34 | Total: 14365.70 h/s - Max: 14388.12 h/s
It's need results from other miners like SRB and Cast XMR to compare with. And point algo and amount of video memory please. |
|
|
|
|
Vega 64s
confgpu.txt
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash":1920 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash":1920 },
(etc.)
12:08:34 | Hashrate GPU Thread 0: 1019.38 h/s
12:08:34 | Hashrate GPU Thread 1: 1042.35 h/s
12:08:34 | Hashrate GPU Thread 2: 1022.37 h/s
12:08:34 | Hashrate GPU Thread 3: 1035.88 h/s
12:08:34 | Hashrate GPU Thread 4: 1026.74 h/s
12:08:34 | Hashrate GPU Thread 5: 1029.77 h/s
12:08:34 | Hashrate GPU Thread 6: 1030.88 h/s
12:08:34 | Hashrate GPU Thread 7: 1024.28 h/s
12:08:34 | Hashrate GPU Thread 8: 1020.92 h/s
12:08:34 | Hashrate GPU Thread 9: 1031.15 h/s
12:08:34 | Hashrate GPU Thread 10: 1007.70 h/s
12:08:34 | Hashrate GPU Thread 11: 1027.57 h/s
12:08:34 | Hashrate GPU Thread 12: 1019.47 h/s
12:08:34 | Hashrate GPU Thread 13: 1027.29 h/s
12:08:34 | Total: 14365.70 h/s - Max: 14388.12 h/s
|
|
|
|
|
Seems to work fine on bytom to f2pool. Almost 1000 h/s on gtx 1080.
|
|
|
|
Best solution I found to reduce power is this command: sudo /opt/rocm/bin/rocm-smi --setsclk 0 1 2 3 4 5 --setfan 155 Could do 4 or 5 for the clock depending on how much power you feel like burning. Do not run at stock clocks. As you found out the power usage is crazy and your card's health will be a problem if you continue doing that. I do not think there is an easy solution for voltage. Probably involves modifying drivers/kernels or similar. Maybe someone knowledgeable will share. But I doubt it, as this kind of information tends to be kept private for some reason. Hello vega owners.. What about playing with pp_table in linux? Power consumption too much for lyra2z without ppt. 300w per card. rocm-smi cannot control voltage. May be other tools? I don't know. And can't find answers in google and forums about Vegas. Tools For RX5XX does not compatible to control vegs's. --- I try to change hex settings to control voltage. But when apply i see errors and nothing happened except system freeze and kernel panic. J
Jun 4 13:22:13 vega-ubuntu kernel: [ 236.914530] amdgpu: [powerplay] Failed to register high thermal interrupt!
Jun 4 13:22:13 vega-ubuntu kernel: [ 236.914550] amdgpu: [powerplay] amdgpu: powerplay initialization failed
Jun 4 13:22:34 vega-ubuntu kernel: [ 258.238591] BUG: unable to handle kernel paging request at 00000000000011a8
Jun 4 13:22:34 vega-ubuntu kernel: [ 258.238836] IP: vega10_thermal_disable_alert+0x16/0x90 [amdgpu]
Jun 4 13:22:34 vega-ubuntu kernel: [ 258.238918] PGD 80000002660a5067
Jun 4 13:22:34 vega-ubuntu kernel: [ 258.238920] P4D 80000002660a5067
Jun 4 13:22:34 vega-ubuntu kernel: [ 258.238968] PUD 266159067
Jun 4 13:22:34 vega-ubuntu kernel: [ 258.239015] PMD 0
Jun 4 13:22:34 vega-ubuntu kernel: [ 258.239054]
Jun 4 13:22:34 vega-ubuntu kernel: [ 258.239108] Oops: 0000 [#1] SMP PTI
Kernel 4.13.0-43. |
|
|
|
|
We need an AMD dev to take a look at this.
|
|
|
|
|
Does this work for 1070s and 1080s?
|
|
|
|
What's the best settings for R9 290/390? I was able to get 900H with v10.2 but only ~700 with 11.3, tried lots of -h
I have found that with the older R9 cards that I have that older versions of Claymore give a higher hashrate and have just stuck to using the older version, if it aint broke don't fix it. That's not gonna help unless he wants to mine bytecoin or etn... |
|
|
|
If you want to mine with vegas on ubuntu you need to use
16.04.3 version
4.16.0-996-lowlatency kernel
You also should delete intel-microcode and all i915 modules... I could write manual, but not today ...
Just go by whatever the ROCm github says for system requirements. Confirmed working on ubuntu 16.04 LTS + Linux 4.13.0-39-generic kernel. |
|
|
|
Sometimes a GPU will crash but mining with other GPUs will continue. 2 x Vegas with v2.2.1. Not sure why this happens. Need to shutdown system to fix this.
[2018-03-29 20:12:37] Stats GPU 0 - lyra2z: 5.279Mh/s (5.275Mh/s)
[2018-03-29 20:12:37] Stats GPU 1 - lyra2z: 6.101Mh/s (6.096Mh/s)
[2018-03-29 20:12:37] Stats Total - lyra2z: 11.380Mh/s (11.371Mh/s)
[2018-03-29 20:12:41] Pool us-east.lyra2z-hub.miningpoolhub.com received new job. (job_id: a47a)
[2018-03-29 20:12:51] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:13:15] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:13:34] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:13:36] Pool us-east.lyra2z-hub.miningpoolhub.com received new job. (job_id: a47b)
[2018-03-29 20:13:37] Stats GPU 0 - lyra2z: 5.286Mh/s (5.275Mh/s)
[2018-03-29 20:13:37] Stats GPU 1 - lyra2z: 3.932Mh/s (6.082Mh/s)
[2018-03-29 20:13:37] Stats Total - lyra2z: 9.218Mh/s (11.356Mh/s)
[2018-03-29 20:13:53] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:14:02] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:14:31] Pool us-east.lyra2z-hub.miningpoolhub.com received new job. (job_id: a47c)
[2018-03-29 20:14:37] Stats GPU 0 - lyra2z: 5.286Mh/s (5.275Mh/s)
[2018-03-29 20:14:37] Stats GPU 1 - lyra2z: 0.000Mh/s (6.042Mh/s)
[2018-03-29 20:14:37] Stats Total - lyra2z: 5.286Mh/s (11.317Mh/s)
[2018-03-29 20:14:56] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:15:26] Pool us-east.lyra2z-hub.miningpoolhub.com received new job. (job_id: a47d)
This is most likely due to the card crashing. This can happen due to unstable overclocks and/or underclocks. This can also happen if the GPU goes over temp. I suggest monitoring the GPU's power state and temperature. With the ROCm drivers installed, I find the rocm-smi tool to be the easiest way to do this. hi! is there any news about windows version of your super fast miner?
is there any progress on that? I'm really interested in it, and I'm sure not only me have such a live interest))
please, can you post and update about it?
Sorry crocozino, but I'm not actively working on the Windows version right now. All the time I've been able to put into the miner have go to fixing bugs lately. I will not be able to get a windows version out any time soon. I suggest trying one of the many linux mining distros and reading/following one of the many linux mining guides out there. Thanks Tod. I have been setting fan speed to 50 with ohgodatool and clocks with "sudo /opt/rocm/bin/rocm-smi --setsclk 0 1 2 3 4" to reduce power consumption. Any other tips to have stability? Also today, I am getting "Dev pool failed to connect." |
|
|
|
hi nice pepole
can someone help set a fail over for this ? . tried the folowing with no luck :
my bat : sgminer.exe --gpu-platform=2 --config failover.conf -w 64 -g 2 -X 256 --no-submit-stale
my conf :
{
"pools": [
{
"name": "Raven minepool",
"nfactor": "10",
"algorithm": "x16r",
"quota": "1;stratum+tcp://minepool.com:3636",
"user": "RFBMCANQkBpd6KRiTFizuf59TCZNUv8GbC.VegaFrontier",
"pass":
},
{
"name": "Raven Yiimp",
"nfactor": "10",
"algorithm": "x16r",
"quota": "1;stratum+tcp://yiimp.eu:3666",
"user": "RFBMCANQkBpd6KRiTFizuf59TCZNUv8GbC.VegaFrontier",
"pass":
},
{
"name": "Mining Panda",
"nfactor": "10",
"algorithm": "x16r",
"quota": "1;stratum+tcp://miningpanda.site:3666",
"user": "RFBMCANQkBpd6KRiTFizuf59TCZNUv8GbC.VegaFrontier",
"pass":
}
],
"api-port": "4028",
"failover-only": true
}
Maybe try a password like "c=RVN"? |
|
|
|
|
Sometimes a GPU will crash but mining with other GPUs will continue. 2 x Vegas with v2.2.1. Not sure why this happens. Need to shutdown system to fix this.
[2018-03-29 20:12:37] Stats GPU 0 - lyra2z: 5.279Mh/s (5.275Mh/s)
[2018-03-29 20:12:37] Stats GPU 1 - lyra2z: 6.101Mh/s (6.096Mh/s)
[2018-03-29 20:12:37] Stats Total - lyra2z: 11.380Mh/s (11.371Mh/s)
[2018-03-29 20:12:41] Pool us-east.lyra2z-hub.miningpoolhub.com received new job. (job_id: a47a)
[2018-03-29 20:12:51] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:13:15] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:13:34] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:13:36] Pool us-east.lyra2z-hub.miningpoolhub.com received new job. (job_id: a47b)
[2018-03-29 20:13:37] Stats GPU 0 - lyra2z: 5.286Mh/s (5.275Mh/s)
[2018-03-29 20:13:37] Stats GPU 1 - lyra2z: 3.932Mh/s (6.082Mh/s)
[2018-03-29 20:13:37] Stats Total - lyra2z: 9.218Mh/s (11.356Mh/s)
[2018-03-29 20:13:53] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:14:02] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:14:31] Pool us-east.lyra2z-hub.miningpoolhub.com received new job. (job_id: a47c)
[2018-03-29 20:14:37] Stats GPU 0 - lyra2z: 5.286Mh/s (5.275Mh/s)
[2018-03-29 20:14:37] Stats GPU 1 - lyra2z: 0.000Mh/s (6.042Mh/s)
[2018-03-29 20:14:37] Stats Total - lyra2z: 5.286Mh/s (11.317Mh/s)
[2018-03-29 20:14:56] Pool us-east.lyra2z-hub.miningpoolhub.com share accepted.
[2018-03-29 20:15:26] Pool us-east.lyra2z-hub.miningpoolhub.com received new job. (job_id: a47d)
|
|
|
|
|
He probably bought 56s which usually are Hynix nowadays. Every 64 I've seen comes with Samsung.
|
|
|
|
|
Anyone know how to adjust power level / TDP for Vega cards in linux? For fan speed, ohgodatool seems to work.
|
|
|
|
|
