Show Posts
|
Pages: « 1 [2] 3 »
|
So you switch core voltage in bios to +/- 1000mV(reprogramming stock bios)? Or just in any software program in OS(like -200mV, i think what it is not possible for stable work)?
I have modified bios yeah: unlocked 60CU, applied 400Mhz mem timings to 500MHz, undervolted for gaming, but for mining in most cases you can even lower on voltage with the same clock. And since I had to go lower on clock(P7-state) as well I just adjusted P-states and voltages in Wattman. I dunno if OverdriveNTool supports Fiji, when I was using one of my furies in my PC it hadn't existed yet). But AB is definitely no-go for tuning Fury since it doesn't read its P-states - basically same thing as curve OC for nvidia. Do you have a ready mod BIOS, or only manual tuning? What program is relevant for this today, I have not modified the BIOS for a long time (the last time it was Hawaii and I don’t remember exactly which programs were used). Maybe you have some link with manual of this question?
|
|
|
How can you do this? 135W? this is info from wattmeter? What settings?
HWinfo reports it yes, which is accurate since I compared its readings with wattmeter before. I've got 2 furies in rig with 6 nvidia cards. Their settings for lyra2r3 are: 900mhz core and voltages are 975mV/981mV per card. Under load it gives 938mV/944mV because of vdrop. At 1000Mhz it was 66Mhs@185Wt(though I didnt undervolt them properly) with v0.3.9, so now with 0.3.10 it's probably a bit more since with 900Mhz new version of miner gave me ~0.5mhs extra hashrate. I get more 200W with -125mV ! This is not much of undervolting considering vcore on stock bios on my cards was 1200mV+ on each card which is insane. With 1000mhz I tried randomly inputing 1100mV and as I said it gave me 185Wt and was stable, so I could probably dropped it even further, but the goal was to make them consume <150Wt so I realized it would never happen @1000Mhz so I didnt bother finetuning this clocks. So you switch core voltage in bios to +/- 1000mV(reprogramming stock bios)? Or just in any software program in OS(like -200mV, i think what it is not possible for stable work)?
|
|
|
I'm getting 58.8Mhs@135Wt with Fury cards in lyra2rev3. Though they are 60CU, not 56.
How can you do this? 135W? this is info from wattmeter? What settings? I get more 200W with -125mV !
|
|
|
Does this miner supports old Tahiti GPUs (Radeon 7950/R9 280)?
Unfortunately not, we support GCN 3 and up, Fiji and Tonga being the oldest archs supported. We wait kernel for hawaii!! This is strong and good GPUs!
|
|
|
Hi Dev - any plans dates for c31 support? Thanks
++++++++
|
|
|
Hi! What about C31 algo on Windows??
|
|
|
Hi everyone! We are glad to announce that we just donated half of the collected Grin devfee so far to Grin general fund. And we’ll keep doing donations to Grin general fund.We are proud to support the Grin developer team and the future of Grin.
What about C31 algo on Windows??
|
|
|
Hi Folks, sorry for the silence - I do not write so much when busy with coding. So, what I got for you is lolMiner 0.7 alpha 2 for mining BEAM. Changes over alpha 1:- Memory consumption reduced from 3.9 to 3.4G (so now more stable on 4G cards even with screen attached) - Performance increased about 15% - Experimentally the API now shows submitted and rejected shares per card Download link:https://github.com/Lolliedieb/lolMiner-preview/releases/tag/0.7_a2MD5 Hashes of release files:Windows: 12efcea8836eb7ec482a056c4b653fac Linux: c2529dd0e2dc2816a5cd51506938b075 Notes: - HiveOS, Pimp OS and others are informed - No idea yet about Nvidia performance - any comment welcome Regarding all here where the OpenSource miner was stable but this one not: Check out new version - the reduced memory usage should help in those cases where one card was slow (4G cards). Last version have a problem. when miner lost connection with pool he closes with message from windows"your app have a problem and will be close"! Many different rigs on win 10 and all closes when pool lost connection. On Win 7 it fine and miner reconnection sucsesfully after 3 second. Any idea what wrong? Submitting share Submitting share Submitting share Lost connection to stratum server beam-pool.beepool.org:9507 or server not reachable. Trying to connect in 3 seconds Device will be paused, waiting for new work Device will be paused, waiting for new work Device will be paused, waiting for new work Device will be paused, waiting for new work Device will be paused, waiting for new work Device will be paused, waiting for new work Average speed (30s): 15.1 sol/s | 15.4 sol/s 16.1 sol/s | 16.0 sol/s 16.1 sol/s | 16.8 sol/s Total: 95.5 sol/s Warning: resolve: ▌ЄюЄ їюёЄ эxшчтxёЄxэ Lost connection to stratum server beam-pool.beepool.org:9507 or server not reachable. Trying to connect in 3 seconds Warning: resolve: ▌ЄюЄ їюёЄ эxшчтxёЄxэ Lost connection to stratum server beam-pool.beepool.org:9507 or server not reachable. Trying to connect in 3 seconds Warning: resolve: ▌ЄюЄ їюёЄ эxшчтxёЄxэ Lost connection to stratum server beam-pool.beepool.org:9507 or server not reachable. Trying to connect in 3 seconds Average speed (30s): 0.0 sol/s | 0.0 sol/s 0.0 sol/s | 0.0 sol/s 0.0 sol/s | 0.0 sol/s Total: 0.0 sol/s Connected to beam-pool.beepool.org:9507 TLS Handshake sucess New job received: 1547985735 Difficulty 196 And then miner stop with notification from windows...(this happen on all rigs:6GPU,5GPU,3GPU no difference). It happens so often that I had to switch to another coin! We waiting for the new version with the correction of this error!
|
|
|
Last version have a problem. when miner lost connection with pool he closes with message from windows"your app have a problem and will be close"! Many different rigs on win 10 and all closes when pool lost connection. On Win 7 it fine and miner reconnection sucsesfully after 3 second. Any idea what wrong?
Same problem. Submitting share Submitting share Submitting share Lost connection to stratum server beam-pool.beepool.org:9507 or server not reachable. Trying to connect in 3 seconds Device will be paused, waiting for new work Device will be paused, waiting for new work Device will be paused, waiting for new work Device will be paused, waiting for new work Device will be paused, waiting for new work Device will be paused, waiting for new work Average speed (30s): 15.1 sol/s | 15.4 sol/s 16.1 sol/s | 16.0 sol/s 16.1 sol/s | 16.8 sol/s Total: 95.5 sol/s Warning: resolve: ▌ЄюЄ їюёЄ эхшчтхёЄхэ Lost connection to stratum server beam-pool.beepool.org:9507 or server not reachable. Trying to connect in 3 seconds Warning: resolve: ▌ЄюЄ їюёЄ эхшчтхёЄхэ Lost connection to stratum server beam-pool.beepool.org:9507 or server not reachable. Trying to connect in 3 seconds Warning: resolve: ▌ЄюЄ їюёЄ эхшчтхёЄхэ Lost connection to stratum server beam-pool.beepool.org:9507 or server not reachable. Trying to connect in 3 seconds Average speed (30s): 0.0 sol/s | 0.0 sol/s 0.0 sol/s | 0.0 sol/s 0.0 sol/s | 0.0 sol/s Total: 0.0 sol/s Connected to beam-pool.beepool.org:9507 TLS Handshake sucess New job received: 1547985735 Difficulty 196 And then miner stop with notification from windows...(this happen on all rigs:6GPU,5GPU,3GPU no difference). It happens so often that I had to switch to another coin! I am waiting for the new version with the correction of this error!
|
|
|
Hi Folks, sorry for the silence - I do not write so much when busy with coding. So, what I got for you is lolMiner 0.7 alpha 2 for mining BEAM. Changes over alpha 1:- Memory consumption reduced from 3.9 to 3.4G (so now more stable on 4G cards even with screen attached) - Performance increased about 15% - Experimentally the API now shows submitted and rejected shares per card Download link:https://github.com/Lolliedieb/lolMiner-preview/releases/tag/0.7_a2MD5 Hashes of release files:Windows: 12efcea8836eb7ec482a056c4b653fac Linux: c2529dd0e2dc2816a5cd51506938b075 Notes: - HiveOS, Pimp OS and others are informed - No idea yet about Nvidia performance - any comment welcome Regarding all here where the OpenSource miner was stable but this one not: Check out new version - the reduced memory usage should help in those cases where one card was slow (4G cards). Last version have a problem. when miner lost connection with pool he closes with message from windows"your app have a problem and will be close"! Many different rigs on win 10 and all closes when pool lost connection. On Win 7 it fine and miner reconnection sucsesfully after 3 second. Any idea what wrong?
|
|
|
same problem ({"code":-32501,"message":"Share rejected due to low difficulty"}) for me too.
bminer 12.1.0 at grin-pool.org worked perfectly since 2-3 days. is this low diff problem not also a huge think at grinmint.com pool since yesterday?
yes! Working on it.. the problem is that I always have problems to connect to grinmint / grin-pool, which makes it hard for me to validate. Will be fixed soon. Win 10 works stable and good, but win 7 not! Win 7, Rig with 6 1080ti - 1.95 G/s per GPU , gminer only 0.9 G/s per card. Rig with 5 1080ti - ~ 2.6G/s per card. Driver 417.35(was try 411 also). loading of GPU very unstable for Windows 7, its about 40-50% out of 100%. Can you fix it for win 7? windows 7 here too...1080ti's behave like 1070s.........the number of cards trigger this issue Yes. Exactly.
|
|
|
same problem ({"code":-32501,"message":"Share rejected due to low difficulty"}) for me too.
bminer 12.1.0 at grin-pool.org worked perfectly since 2-3 days. is this low diff problem not also a huge think at grinmint.com pool since yesterday?
yes! Working on it.. the problem is that I always have problems to connect to grinmint / grin-pool, which makes it hard for me to validate. Will be fixed soon. Win 10 works stable and good, but win 7 not! Win 7, Rig with 6 1080ti - 1.95 G/s per GPU , gminer only 0.9 G/s per card. Rig with 5 1080ti - ~ 2.6G/s per card. Driver 417.35(was try 411 also). loading of GPU very unstable for Windows 7, its about 40-50% out of 100%. Can you fix it for win 7?
|
|
|
note crosspost from bminer: v. 12.1.0
both windows 7 and driver 417.35
1080ti 1 card rig: ~6 G/s
1080ti 4 card rig: ~3 G/s per card
any possible problem with the 4 card rig?, power and temps are down too in the 4 card rig..nothing power limit and clocks can do, increasing to 120 power limit will gain 0.2 G/s max. with occasional miner crash/restart.
with 391.35 on 4 card rig, no occasional miner crash/restart but still ~3 G/s per card
while bminer turns my 4 card rig to 3 G/s per 1080ti, this one..gminer 1.19 gives only 1.5 G/s per card found the issue, to run at 5.x G/s for 1080ti ---->max of 3 cards only for bminer..seems amount of cards is an issue.. Yes! The same problem! Win 7, Rig with 6 1080ti - 1.95 G/s per GPU , gminer only 0.9 G/s per card. Rig with 5 1080ti - ~ 2.6G/s per card. Driver 417.35(was try 411 also).
|
|
|
Hi! We have several rigs on windows 7. Windows 10 rigs works fine on "Grin" algo, but on win 7 all GPU(1080Ti) show 0.9H/s with last driver also! You have any idea whats wrong?
|
|
|
for AMD minning BEAM, please support Fiji
YES!! PLEASE!! I have a many FIJI too!!
|
|
|
Hey Guys, I was pretty busy recently to prepare the first alpha version of lolMiner 0.7 for you The release files can be found here: https://github.com/Lolliedieb/lolMiner-preview/releases/tag/0.7_a1Internally the miner changes a lot, especially its getting a complete new mining backbone for more stability. Therefore the currently only supported coin is BEAM (Equihash 150/5) at a fee of 1%. Also the miner is currently only optimized for AMD cards – I guess for Nvidia the cuda alternatives are quicker and the new backbone code produces some high CPU load with them (on AMD is extremely low on contrast). Still, a 4G Nvidia GPU will run if you want to test it. With regard to the overall schedule: The next weeks I will introduce the other algorithms plus some new stuff that is still a surprise. What I can unveil: all lolMiner binary releases will have fee lowered for all algorithms to 1%! Hope that serves you well, have fun mining Beam I see after one day tests(Fury 4Gb) what on rigs with 2-5 GPU like all works stable(and first GPU also), but rigs with 6GPU not works good: first gpu always show 1 S/s and others some of 5 after some time stop good works also(speed drops to 1-2 S/s), but the funny thing is that electricity is consumed at the same level as before! If it is not possible to release a solution to the problem very quickly, you can quickly at least temporarily add an intensity parameter for each GPU separately with a large range, for example, 1-30 (it always helped with cryptonight algos). Any ideas how to fix it?
|
|
|
We’re pleased to release Bminer 11.4.0. The release provides experimental support mining beam with AMD cards. Please see https://www.bminer.me for more details. Happy mining! Its not work for Fury(fiji) and R9 390(hawaii), not have kernels for they. Why? We wait this!
|
|
|
your miner not working for r9 390/390x and fury... even old tahiti with awesome miner
This miner normal work with R9 270X. Therefore it will work this 390/390X, fury and tahiti. I dont know about V1.6.9, but V1.6.8 does not work with R9 390 but it works with Fury(she with HBM memory! If someone worked on optimization for R9 FURY, she would have performed very well on all CN algo!
|
|
|
the attrib trick is a stealth mode to bypass some antiviruses, and it's very documented in the doc: https://github.com/jceminer/cn_cpu_miner#privacy-and-securityIt doesn't: •Punch through your firewall: you have to open it manually if needed •Run any command, not even attrib (see below)
hard to be closer to what you experienced and yes it is safe and not new, just your firewall did its job i'm not done yet for v8 because i'm writing it in assembly. i think i've room for optimizations Hi, JCE! I want to send you a personal message with your permission! This is important.
|
|
|
Glad to hear it! We would love to have you stop by our discord, we can always use experienced miners to share knowledge points. My explanation was more for the benefit of everyone reading, in case they are newer - so good to hear experience talking, based on your past experience adding to the thread.
We can talk further about EU nodes also, sounds like we may be able work something out.
I am testing your pool XTL now, and want to receive notification on email when my workers will stop, how can i do this? In settings on site i only see : "pool will send out email notification when a block is found and whenever a payout happens"! WHAT THIS? What for? I do not want to receive payment notification, i want to receive notification on email when my workers will stop, it's the most important!
|
|
|
|