Good job, When you will in other exchanges? Soon in Cryptopia. News in on twister already. hope so  |
|
|
|
Good job, When you will in other exchanges? |
|
|
|
Hi guys can i use srbminer to mine using my ryzen 3 2200g with 8 vega units?
Thanks
Why don't you just try it instead of asking? Just tryed and didn t work, Thats why i asked..  |
|
|
|
|
Hi guys can i use srbminer to mine using my ryzen 3 2200g with 8 vega units?
Thanks
|
|
|
|
Hi got some problems too with this board,  I got one rig with 10 gpus (rx580, 560, 2 vega 56) - no problems at all. all gen2, onboard graphic etc.. I mount another rig with 10 vega 64 but only can connect 9, if i installed the 10 gpu, i have no post on poweron.. Any ideia too what could i check? I changed to 16 gb ram its the same, have a lot of power too.. No problems in risers too, my solution was to put one vega in my desktop pc.. but its frustating  Regards, Also, do you have power connected to all THREE PCIe PWR headers near the PCIe slots? There will be one "Molex" 4-pin PCIE_PWR1 near PCIE1_1, one "Molex" 4-pin PCIE_PWR2 near PCIE7_1 and another SATA Power Connector called SATA_POW1. All three should be powered from (connected to) the same PSU supplying power to your motherboard ATXPWR1. Just noticed the SATA_POW1, is this required? http://www.asrock.com/support/faq.asp?id=454I would say running VEGAs, yes. Absolutely. And it should be from the same PSU powering your motherboard. Hi Savage, Yes all connected, I have one rig working with 10 gpus using what you suggested Thanks for help Awesome! No problem! Glad you got it working! hi, already worked in my 1st rig, That's what I meant. In my only vega 64 rig i only can put 9, but no problem i put the 10 in my desktop pc.. Thanks |
|
|
|
Hi got some problems too with this board, I got one rig with 10 gpus (rx580, 560, 2 vega 56) - no problems at all. all gen2, onboard graphic etc.. I mount another rig with 10 vega 64 but only can connect 9, if i installed the 10 gpu, i have no post on poweron.. Any ideia too what could i check? I changed to 16 gb ram its the same, have a lot of power too.. No problems in risers too, my solution was to put one vega in my desktop pc.. but its frustating Regards, Also, do you have power connected to all THREE PCIe PWR headers near the PCIe slots? There will be one "Molex" 4-pin PCIE_PWR1 near PCIE1_1, one "Molex" 4-pin PCIE_PWR2 near PCIE7_1 and another SATA Power Connector called SATA_POW1. All three should be powered from (connected to) the same PSU supplying power to your motherboard ATXPWR1. Just noticed the SATA_POW1, is this required? http://www.asrock.com/support/faq.asp?id=454I would say running VEGAs, yes. Absolutely. And it should be from the same PSU powering your motherboard. Hi Savage, Yes all connected, I have one rig working with 10 gpus using what you suggested Thanks for help |
|
|
|
Hi got some problems too with this board, I got one rig with 10 gpus (rx580, 560, 2 vega 56) - no problems at all. all gen2, onboard graphic etc.. I mount another rig with 10 vega 64 but only can connect 9, if i installed the 10 gpu, i have no post on poweron.. Any ideia too what could i check? I changed to 16 gb ram its the same, have a lot of power too.. No problems in risers too, my solution was to put one vega in my desktop pc.. but its frustating Regards, |
|
|
|
hi guys is normal to windows defender detect srbminer.exe like: Trojan:Win32/Occamy.C I was mining for 2 weeks but today had detected and kill the .exe Thanks Yes. Happened to every single miner I've ever used. Someone with a trojan will package the miner in it and mine for them on the infected PC. I just have a wallets folder that I white list. I thought was an false positive!! Dont understand your sentence :" Someone with a trojan will package the miner in it and mine for them on the infected PC" I just add an exclution to windows defender, Hello guys, I see this is a very good miner. However, come to my attention this post, what does the community says about this. Can we trust in this miner if it is download from the officials sites?? Thanks for answer im waiting too |
|
|
|
Hello guys! I have recently came across one thing - Paytomat. It’s whitepaper is surprisingly good. They already have a product that works, as well as POS-solutions to pay with crypto! It deserves to be checked!
is mineable? |
|
|
|
Hi glph3k, Im using the 110 version of your miner. This is very stable , after this version i have some hangs. When i start up the miner, it show me an rx560 on gpu9. I have one connected but is mining using claymore. Analysing the Hashes is working like an rx580. So is fine i think. What could this be? error in enumerating the devices? i only discover this today, maybe im mining in this way for weeks. Im using last 18.6.1 drivers, but wiht 18.5.x i got the same problem! Image: https://ibb.co/hSS3aThttps://ibb.co/j8Eo9oRegards |
|
|
|
hi guys is normal to windows defender detect srbminer.exe like: Trojan:Win32/Occamy.C I was mining for 2 weeks but today had detected and kill the .exe Thanks Yes. Happened to every single miner I've ever used. Someone with a trojan will package the miner in it and mine for them on the infected PC. I just have a wallets folder that I white list. I thought was an false positive!! Dont understand your sentence :" Someone with a trojan will package the miner in it and mine for them on the infected PC" I just add an exclution to windows defender, |
|
|
|
hi guys is normal to windows defender detect srbminer.exe like: Trojan:Win32/Occamy.C I was mining for 2 weeks but today had detected and kill the .exe Thanks |
|
|
|
V1.6.1
- Changed IPBC/Bittube old algo to new BitTubeV2 algo (from block 110000)
- Max difficulty reconnecting mechanism is now triggering instantly
- Added 'worksize' option in config.txt, that is applied to every GPU (only if not set in gpu_conf)
- Hopefuly fixed a bug with job timeout reconnecting
- Hashrate watchdog now triggers even when user not connected to pool
+ BitTube (former IPBC) forks on block 110.000, and their new algo will be BitTube V2.
You can use the new algo only after they forked, use "cryptonight_type" : "bittubev2". The old IPBC algo has been removed, so until the fork please use the previous version of SRBMiner.
+ Added 'worksize' option in config.txt (use it on top of config.txt , where intensity and double_threads is). If set, it will be applied to every GPU that is found. Of course if you have a gpu_conf set, those settings will be used, insted of this global setting.
+ Some had app crash on job_timeout triggering, i hope i managed to fix it
+ Hashrate watchdog was set to trigger only if user is connected to the pool. Now this is changed, watchdog will monitor GPU'S all the time.
Doktor can you improve one problem that happen if miner crashes and when windows restart if for an reason one gpu is not recognized and if we have set in gpu_conf: (9 gpus, but when restaring only recognizes  The miner wont start, and gives us an error. With that if happen in night when restart at least we hash with 8 gpus. And when wake up we solve the problem. (restart again hehe) "gpu_conf" : [ { "id" : 0, "intensity" : 61, "worksize" : 8, "threads" : 2}, // Máximo que dá é 63 de intensity no heavy!! a partir de 62 perde performance!! { "id" : 1, "intensity" : 56, "worksize" : 8, "threads" : 2}, // Maximo vega 56 é 57 { "id" : 2, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 3, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 4, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 5, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 6, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 7, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 8, "intensity" : 61, "worksize" : 8, "threads" : 2}, ] Regards could you provide me a log? Windows does not recognize a card on system restart? If so i can't do anything lol Hi doktor, Thanks for help. I know, its not a miner problem. But sometime some gpu crash and when restart its not recognized (only if i restart again) and it was nice if your miner could ignore oneplus id. For example if i have 9 gpus and put 10 in gpu_conf, your miner crashes. Could it ignore the +id if if this gpu doesnt exist? This will avoid te situation i described.. Regards |
|
|
|
V1.6.1
- Changed IPBC/Bittube old algo to new BitTubeV2 algo (from block 110000)
- Max difficulty reconnecting mechanism is now triggering instantly
- Added 'worksize' option in config.txt, that is applied to every GPU (only if not set in gpu_conf)
- Hopefuly fixed a bug with job timeout reconnecting
- Hashrate watchdog now triggers even when user not connected to pool
+ BitTube (former IPBC) forks on block 110.000, and their new algo will be BitTube V2.
You can use the new algo only after they forked, use "cryptonight_type" : "bittubev2". The old IPBC algo has been removed, so until the fork please use the previous version of SRBMiner.
+ Added 'worksize' option in config.txt (use it on top of config.txt , where intensity and double_threads is). If set, it will be applied to every GPU that is found. Of course if you have a gpu_conf set, those settings will be used, insted of this global setting.
+ Some had app crash on job_timeout triggering, i hope i managed to fix it
+ Hashrate watchdog was set to trigger only if user is connected to the pool. Now this is changed, watchdog will monitor GPU'S all the time.
Doktor can you improve one problem that happen if miner crashes and when windows restart if for an reason one gpu is not recognized and if we have set in gpu_conf: (9 gpus, but when restaring only recognizes The miner wont start, and gives us an error. With that if happen in night when restart at least we hash with 8 gpus. And when wake up we solve the problem. (restart again hehe) "gpu_conf" : [ { "id" : 0, "intensity" : 61, "worksize" : 8, "threads" : 2}, // Máximo que dá é 63 de intensity no heavy!! a partir de 62 perde performance!! { "id" : 1, "intensity" : 56, "worksize" : 8, "threads" : 2}, // Maximo vega 56 é 57 { "id" : 2, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 3, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 4, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 5, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 6, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 7, "intensity" : 61, "worksize" : 8, "threads" : 2}, { "id" : 8, "intensity" : 61, "worksize" : 8, "threads" : 2}, ] Regards |
|
|
|
|
Hi,
How can i use SRBPolaris-CN.exe --listdevices ? any example ?
Thanks
|
|
|
|
Hi guys, Anyone had tryed SRBminer with 10-12 gpus vega 64 ? Im using one with 120 intensity and no problems.. With more can i expect the same stability ? P.S- of course we have silicon lottery and have to adjust oc etc.. Thanks I'm using 120 intensity too on my 2xVega64. Have you tried increase it a bit? Have you tried using other workersize than 8? Hi, yes but this is my sweet spot Anything > or < give me lower hashes |
|
|
|
|
any miner for windows?
Thanks
|
|
|
|
This program keeps freezing on my vega rigs, anyone else have this problem or have a fix? on v100 and v110
same here, miner just stops hashing for me  but if i come back and hit enter/space or whatever itll spit out that it has old shares or w/e and shit and then get back to mining current shares or whatever https[Suspicious link removed] well miner still gets stuck for me and stops hashing ;( Same here, and i have de edition mode off in cmd options.. |
|
|
|
Hi guys, Anyone had tryed SRBminer with 10-12 gpus vega 64 ? Im using one with 120 intensity and no problems.. With more can i expect the same stability ? P.S- of course we have silicon lottery and have to adjust oc etc.. Thanks if you are mining cn v7 or stellite try : intensity : 112 worksize : 16 threads : 2 I got 2080 H s with this: { "id" : 0, "intensity" : 120, "worksize" : 8, "threads" : 2}, How much you got? Thanks |
|
|
|
|
Show Posts
