can someone explain to me what im doing wrong? ver 149
xmr-cast to same CCv7 coin and pool , vega 56 ref card, samsung memory, get 1960 HS,
with srb miner, intensity 0 - 1300Hs Intensity 56 - 1440hs intensity 58 - 1440hs intensity 60 - 1440hs
target temp is set to 56 C. 2 threads is TRUE
and im using powerplay tables GPU 1450 mhz and mem 950 mhz
GPU0: Radeon RX Vega [gfx900] [8094 MB][Intensity 58.0][W: 8][T: 2][K: 1][BUS: 3]
which intensity should i try?
The first problem I notice is that your card is reporting [gfx900] It should say [gfx901] But I have no idea why. Secondly, I would make W:16 and intensity 112
|
|
|
I have done the --pop-blocks 2000 and the add-exclusive mode as suggested,
The daemon is really slow, I am at 168597 (6 days) behind.
Is it normal to only be getting 100 blocks every 3 minutes?
|
|
|
Im curious if anyone is going to mine MoneroV? I dont even know if it will just work with regular CryptonightV7 or it needs specific compatibility...
Depends on the pools available, but, yeah, likely.
|
|
|
Yeah, I found the problem, Radeon Settings. It was set to have off the crossfire, but it was still on. Operator error, obviously. Now that I've gone back to Aug 23rd drivers, I am going to attempt to upgrade - and double check those pesky crossfire settings again!
|
|
|
Dok,
I am having an unusual problem. One of my win 10 rigs with 4 Vega56s had to have win10 reinstalled due to OS software screwup, so I thought I'd try your software without AMD Blockchain drivers using win10-64bit-radeon-software-adrenalin-edition-18.3.4-march23 drivers.
No matter what I do your miner will only hash on GPU 0 and 3, GPU 1 and 2 do not hash, they are recognized, but no hashing, I have tried very low intensity, but with no effect.
Any ideas?
Stupid question, but did you turn on computing mode on adrenalin drivers? Yes, to no avail. Doing clean reinstall and Aug 23 next.
|
|
|
Dok,
I am having an unusual problem. One of my win 10 rigs with 4 Vega56s had to have win10 reinstalled due to OS software screwup, so I thought I'd try your software without AMD Blockchain drivers using win10-64bit-radeon-software-adrenalin-edition-18.3.4-march23 drivers.
No matter what I do your miner will only hash on GPU 0 and 3, GPU 1 and 2 do not hash, they are recognized, but no hashing, I have tried very low intensity, but with no effect.
Any ideas?
Get back to Aug23. Me can't do shit in 18.3.4 either. Even disable/enable vega by my hand in device manger still making crash. No idea why. Yeah, I'm trying that now.
|
|
|
Dok,
I am having an unusual problem. One of my win 10 rigs with 4 Vega56s had to have win10 reinstalled due to OS software screwup, so I thought I'd try your software without AMD Blockchain drivers using win10-64bit-radeon-software-adrenalin-edition-18.3.4-march23 drivers.
No matter what I do your miner will only hash on GPU 0 and 3, GPU 1 and 2 do not hash, they are recognized, but no hashing, I have tried very low intensity, but with no effect.
Any ideas?
|
|
|
This is SRBMiner-CN mining Stellite (CNv7) with Robinhood's blockchain drivers for Win 7-64, Sapphire RX 470 Nitro+ 8Gb (Samsung) at 1260/2000, auto intensity, worksize 8, threads 2. GPUs are modded with something that is close to Ubermix 3.1. which software did you use to BIOS mod? PolarisBiosEditor
|
|
|
TO WHOEVER RUNS THE COMMUNITY POOL: Would you please send me my balance? I have 84 xtl sitting on your pool and I absolutely REFUSE to spend one more penny in electricity, or one more second mining on your pool. In 8 hours on cryptoknight.cc I mined about 4x what I mined all day yesterday on communitypool. It's not that 84xtl is that big of a deal, but it's the principle. I already wasted time and money on your pool, the added loss of 84xtl is just salt in the wound. I am always very cautious about yelling "scam", and this is no different. I like to give the benefit of the doubt at all times. That being said, your pool just plain sucks. That is as kind as I can be. There have been several other posts regarding this issue. Either fix what is obviously broken or remove the word "community" from your name or remove that pool from the xtl OP. I have been here since the beginning and I believe in xtl. However, this will leave a very bad taste in the mouth of new people and ultimately get xtl labeled a "scam coin". Se3e8QmBKB5TwfRhtiWGGwV1yUoVXp7CSEznMM3xbucq8hA8QT4UezuVDsCBvpFTQ77LveuWKumjaWB rXSc3uSGf214duXNvj
Oh, man, that's a good one. I actually laughed so hard I have coffee on my monitor and keyboard now. I agree with everything you wrote, But really, all this over $0.13?
|
|
|
vega 64 cryptonigh v7 or old hash 1950-2000 h/s new heavy algo hash 1450-1500 h/s rx 580 cryptonigh v7 or old hash 1000 h/s new heavy algo hash 1000 h/s
why bad performance for vega 64?
my vega 64 setup. i have 2890 h/s
{ "id" : 0, "intensity" : 58, "worksize" : 8, "threads" : 2}, { "id" : 1, "intensity" : 58, "worksize" : 8, "threads" : 2},
Try worksize 16 on Vegas
|
|
|
SRB on my RX 580 8Gb cards (hynix) gives on 1 card 10 h/s more than GGS, but 2nd card 10 h/s less )))) But GGS is open source... Thats mean that devfee can be disabled on them...
+10/hs per card + 0.85% of daily earnings will get you very very rich Every developer sets his fee. Some think their work worths more, while others are satisfied with less. Taking away that lets call it salary won't really motivate the dev to continue working. But it's non of my business what you use and how you use it As i just started this miner thing a few months ago, and see how much people support my work, im really motivated to continue working on it. Making it better every day. I get the 0.85% fee, but some people even mine on my account that i left in the config file. Just want to say thanks to everyone, it feels good that i have your support Keep it up, dok, I just pointed 40 more VEGAs your way, I was using a 0 fee XMR-Stak, but I want to support your efforts!
|
|
|
1995 h/s, cryptonight v 7 Sapphire Vega 56 reference (air) (samsung) - stock, SRBMiner-CN-V1-4-6, "intensity" : 112, "worksize" : 16, "threads" : 2, 1407/935, Power Play table mod to 900mV for all except the clock at 1407=935, win 10, blockchain AMD drivers, 145w
|
|
|
V1.4.6-fix-fixes - Fixed duplicate share sending fix - Fixed GPU core clock & memory display fix
Ok, try this now it should all be good. i shouldn't rush so much, then this wouldnt happen. sorry folks.
now when a duplicate share sending occures, there is info about it in the log :
[2018-04-19 18:32:22] miner_result: Duplicate share protection kicked in!
I still get "Your IP is banned" with v1.4.6 .. https://imgur.com/a/xwTOWxXInteresting. I haven't yet. Still monitoring.
|
|
|
V1.4.5- Added check of already sent result, so possibly no more duplicate shares should be sent to the pool - Added GPU core clock & memory display (ADL OverdriveN supported cards) Also added an experiimental kernel (4) , so if you guys with old gpu's could check it that would be great Dok, CC displays for me, but not MC Sapphire RX 470 8GB Nitro+ (Samsung), Win7-64, Robinhood AMD driver hack (22.19.659.1) yup just realised that myself, i tested on 570 & 580 before i uploaded the new v. After that tried on 480 and no mem clk, so in next version that will be fixed ) I was in a hurry to give you a new version with the duplicates check, so i hope no more bans. I will update all rigs now and let you know if dups aren't fixed. the critical moment could be after 2hrs when the devfee switches back to the user mining, as someone wrote Unfortunately, we still have a problem.
|
|
|
V1.4.5- Added check of already sent result, so possibly no more duplicate shares should be sent to the pool - Added GPU core clock & memory display (ADL OverdriveN supported cards) Also added an experiimental kernel (4) , so if you guys with old gpu's could check it that would be great Dok, CC displays for me, but not MC Sapphire RX 470 8GB Nitro+ (Samsung), Win7-64, Robinhood AMD driver hack (22.19.659.1) yup just realised that myself, i tested on 570 & 580 before i uploaded the new v. After that tried on 480 and no mem clk, so in next version that will be fixed ) I was in a hurry to give you a new version with the duplicates check, so i hope no more bans. I will update all rigs now and let you know if dups aren't fixed.
|
|
|
V1.4.5- Added check of already sent result, so possibly no more duplicate shares should be sent to the pool - Added GPU core clock & memory display (ADL OverdriveN supported cards) Also added an experiimental kernel (4) , so if you guys with old gpu's could check it that would be great Dok, CC displays for me, but not MC Sapphire RX 470 8GB Nitro+ (Samsung), Win7-64, Robinhood AMD driver hack (22.19.659.1)
|
|
|
i will add some logic to check if share was already sent, and if it was , don't send it again. Maybe sometimes a sneaky share is sent two times.
doktor83, Support by leafy at that pool support thinks that some duplicate shares are being submitted and this is why IP ban is being issued to me at times. Thanks for looking into this.
|
|
|
I have this problem. It is with Stellite Pool - CryptoKnight. It does it with this current miner AND xmr-stak-stellitequestion-compiled-0. And, no, it is NOT because of the incorrect algo being picked. So, I conclude that it is a POOL problem, not a config or miner problemI have brought it to the attention of the pool's thread.
|
|
|
|