BUG REPORT! Mixed rigs 8gpus(6 470 4GB,2 480 4GB) 480 4Gb cards have less hashes. 470's 32mh-s 480's 28mh-s ,ON CM 15.0 all hashes 32mh-s..4.7c and 4.5 all same.
I think you didn't find best -gt vaules for each card. Just press "z" during mining and wait about 10 minutes. After finishing auto-tune process you can see best -gt parameters for adding them to .bat after pressing "s" key. On the detail statistics you will see this string: "Current -gt 34,36,42 etc." Add this parameter to command line. Tried, with any -Gt value 480's hashrate low, if leave it with empty it comes back to 32+ hashes.alrady tried miners best finding gt values.Strange stuation.
|
|
|
BUG REPORT! Mixed rigs 8gpus(6 470 4GB,2 480 4GB) 480 4Gb cards have less hashes. 470's 32mh-s 480's 28mh-s ,ON CM 15.0 all hashes 32mh-s..4.7c and 4.5 all same.
|
|
|
Turtle ağına saldırı oluyor sürekli. Ağ düzgün çalışmadığında turtle node ağ ile bağlantı kuramıyor ve bu hatayı alıyorsunuz.
Ağ stabilleşti gibi fork öncesi sıkıntılı olduğunu okumuştum. Bu arada daha önce vardı sanırım bloc+haven merge pool yeniden düşünüyormusunuz?
|
|
|
turtle poolda a çok fazla sayıda duplicated share alıyorum.Network hatasımı var?pm atamıyorum mecburen buradan yazdım.
|
|
|
my ref 5700 cvddc didn't change 750,760,770,780,790 or 800mv always 800mv. İt's couse of miner or driver level problem?
|
|
|
I have 2 RX5700, Windows 10, AMD 19.9.1 drivers and Phoenix 4.6b... I don't know how people are getting them to run at 100W, I can't get it to run reliably even at 130W. When I try to undervolt to anything bellow 1V, after few hours hashrate drops to 0.00 and needs system reboot. Anyone else experiencing the same?
no problem so far with 800mv (20+ hours) but i have just 1 card.miner shows 112W consumption, from wall system+1 card 170W(gold) psu
|
|
|
Quick test on ref 5700 non XT cclock:1300 mclock:920 53mh on phoenix 51.1mh on Claymore 15:0
930 and 950 mclock drops hash speed to under 50mh ,i think it changes mem straps and timings..
|
|
|
Anyone didn't try new driver on cnr?interesting that noone still don'tshare....
|
|
|
It seems, 5700 come swith Micron D9WCW MT61K256M32JE-14:A they are specified to run at 1750 MHz (14 Gbps GDDR6 effective). 5700xt comes with Samsung K4Z80325BC-HC14 : they are specified to run at 1750 MHz (14 Gbps GDDR6 effective) too.
waiting for results with optimised kernels...
|
|
|
What about monero hashrates, any thoughts?
soon we will se all.I wonder how performs nvidia dominate algos like x16r,equhash..
|
|
|
Why this error? Unable to query number of CUDA devices! Is an nVidia driver installed?
|
|
|
Why warning msg at the top of page.Djm one of the best miner coder i ever seen.Will try miner soon.
what warning ? (don't see any) Warning: One or more bitcointalk.org users have reported that they strongly believe that the creator of this topic is a scammer. (Check their trust page to see the detailed trust ratings.) While the bitcointalk.org administration does not verify such claims, you should proceed with extreme caution.
|
|
|
Why warning msg at the top of page.Djm one of the best miner coder i ever seen.Will try miner soon.
|
|
|
0.4.3 CNR algo GPU initialization(very low hash or no start) problem on half my rigs.0.4.2 no problem so far.
|
|
|
Any update on when the rejected shares problem on nanopool will be fixed.
I have two systems running TMR 0.4.1 (one with 2x Vega 56's, one with 3x Vega 56's) and both are showing about 2% rejects on nanopool.
2x Vega 56: a:1254 r:26 hw:0 - 2% rejection rate 3x Vega 56: a:1842 r:34 hw:0 - 1.8% rejection rate
Can confirm the "--no_cpu_check" helped a bit on Nanopool. Went from 2% rejected to 1.75% (tested over 24 hours). Nothing revolutionary but hey. Probably worth switching pool though. Thinking about the big picture here... Adding up dev fee + pool fee + rejects and you're losing ~5% of your hash. Left nanopool ,3hours on supportxmr almost %0 rejects.
|
|
|
--no_cpu_check parameter not helps on nanopool. %3 rejected share 0 hw error.
|
|
|
i think it's huge improvement.
|
|
|
Konuyla ilgili açıklama yapmışlar @everyone
Happy new year Haven community! I've been away for the last few weeks for the xmas and new years break. Sorry if that was any cause for concern. Although I needed to step away for the break I should have announced what my plan was more officially rather than just some dms. Back in action as of this week and was greeted with a DDOS attack on our network. It effected some pools and our explorer, which raised alarm bells at Bittrex.
As of now the crisis averted, the Bittrex haven daemon is syncing correctly and wallets are back online. However still having some issues with our explorer which I'm trying to assist with
Birçok havuz altchain'e kaymış. Official havuzları hala altchain'de. Ben kendi açımdan problemi çözdüm. Şuan sorun yok. Problem dewam ediyor görünüyor.düzelene kadar pooldan ayrılıyorum karlılık zaten yok boşuna kazmayalım.
|
|
|
Kafanızdaki fiyat nedir? Belirtirseniz daha efektif olacaktır.
|
|
|
|