 Show Posts
|
|
Pages: [1] 2 3 »
|
Here's my current settings and results: CPU: Intel Xeon E5-2660v2 GPU Driver version: 390.144 CUDA version: 9.0, CUDA runtime: 8.0 sudo nvidia-smi -pl 158 DISPLAY=:0 nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[2]=+145 DISPLAY=:0 nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[2]=1850 => 48C P2 161W / 158Wethminer 0.18 or PhoenixMiner 5.4c both need ethlargement (-straps 2 does nothing) => 36.7Mh/sThanks for the info! System was installed in 2019 -- used nvidia-driver from debian repo and CUDA toolkit had to be installed from nvidia website at the time. Already watercooled  Tried settings from : https://miningchamber.com/gpu-mining/gtx-1080-ti-mining-settings/Core Voltage (VDD): NA Power Limit: 130w Core Clock (CClock): +40 Memory Clock (MClock): +1600 Result: 33 Mh/s As of today:  mind sharing your miner, settings and driver version? try to set mem -502, core +200/220 pl 75... |
|
|
|
Hi!
I have a vega 56 sapphire nitro+ samsung that in the heat always sends the rig down.. with the cool it was ok. it has to be said that it went constant at 54mhs .. 52mhs now it doesn't give any more problems :-)
Alex
Mine is hynix memory and im using Teamred miner, now I can only use the following settings on this RX Vega 56 for stable performance at 43MH Core clock 950 VDD 825 VDDCI 930 MVDD 1275 Mem Clock 860 Tweak config amdmemtweak --CL 18 --RC 34 --RP 13 --WR 11 --CWL 7 --FAW 12 --RAS 23 --REF 15600 --RFC 164 --RTP 6 --RRDL 4 --RRDS 3 --WTRL 4 --WTRS 4 --RCDRD 19 --RCDWR 11 Anything more than 860 on memory this card will crash try push core clock to 1100 and check this config --CL 20 --RC 35 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 20 --REF 65535 --RFC 248 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 12 --RCDWR 12 Alex I doubt that this will work on a graphic card thats crashing when memory OC can't even go up than 860, the problem is the GPU can't unleash its full power probably because of bad thermal pad, before I fixed my 3080 heat issue I noticed that my 3080 can work at lower OC outputing 40MH only, the mem temp is also lower at this state... Its always the temp bro. maybe card was unstable because of the low core or low VDD.. Mine go from 1050 to 1150.. and crash with VDD under 853.. |
|
|
|
Hi!
I have a vega 56 sapphire nitro+ samsung that in the heat always sends the rig down.. with the cool it was ok. it has to be said that it went constant at 54mhs .. 52mhs now it doesn't give any more problems :-)
Alex
Mine is hynix memory and im using Teamred miner, now I can only use the following settings on this RX Vega 56 for stable performance at 43MH Core clock 950 VDD 825 VDDCI 930 MVDD 1275 Mem Clock 860 Tweak config amdmemtweak --CL 18 --RC 34 --RP 13 --WR 11 --CWL 7 --FAW 12 --RAS 23 --REF 15600 --RFC 164 --RTP 6 --RRDL 4 --RRDS 3 --WTRL 4 --WTRS 4 --RCDRD 19 --RCDWR 11 Anything more than 860 on memory this card will crash try push core clock to 1100 and check this config --CL 20 --RC 35 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 20 --REF 65535 --RFC 248 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 12 --RCDWR 12 Alex |
|
|
|
|
Hi!
I have a vega 56 sapphire nitro+ samsung that in the heat always sends the rig down.. with the cool it was ok. it has to be said that it went constant at 54mhs .. 52mhs now it doesn't give any more problems :-)
Alex
|
|
|
|
|
Give me a mail in pm for the bios. I haven't tested it.
Alex
|
|
|
|
|
With all gpu (nvidia and amd) lolminer works without crash but my rig is losing 20mhs.. :-(
i tried to select only one nvidia device to make a test.. but lolminer crash the same my w5700 ..
any solution?
ok.I solved!
i start first lolminer and after teamredminer and it works.
thanks
alex
|
|
|
|
|
Hi!
is there a mode to force lolminer to no check all cards in a rig?
i have a rig with 3 amd and 14 nvidia.. and i try to use lolminer with --devices NVIDIA option but lolminer crash one of my amd card..a radeon w5700 with special bios (that goes with other 2 amd card with teamredminer)..message is like dead gpu etc etc ...other 2 amd cards are ok and continue mining..
i tried to force only one nvidia device in lolminer with same result..
thanks
alex
|
|
|
|
PhoenixMiner 6.0c is officially released. You can find the download links and the checksums in this post, or in the first post of this thread. You can download PhoenixMiner 6.0c from here: PhoenixMiner_6.0c_Windows.zipPhoenixMiner_6.0c_Linux.tar.gzTo check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows): File: PhoenixMiner_6.0c_Windows.zip
===================================
SHA-1: ae8819916641a500b9837d2cf921d059db3aab5e
SHA-256: d77c667ffc3275a51bcfd5a53c7799a32a17386154cec1f87c44a626586027c0
SHA-512: 92f257489d702db8c19670659231c4e3d8b17a301259d00f07fcda7e8a0369a4633c315a226aedbab962d341a5edb83c4b4837ef239aebaa30a830a1e0f3b6f7
File: PhoenixMiner_6.0c_Linux.tar.gz
====================================
SHA-1: ff4498c8c3e42a887ea103a2e9e18ec11dc85b48
SHA-256: 9e6bfbdb37b1c41f6d7254d3f1560a42d2dc316a68a36cfbacee0aba95835afb
SHA-512: d330bcfc7b04550264022bd11da20a81f61b3d0c0bfd30f78bab7eabd4c6e0d6348bc33986f8c758b57bc65992fe1dc65f3f90083bea0db09a74af04ca792938
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are (since the last official release 5.9d): - Implemented partial unlocking of Nvidia LHR cards. By default they are detected automatically, and unlocked with the default unlock intensity (520). If you want to try higher (or lower) LHR unlock intensity, use the new -lhr command line parameter. For example -lhr 580 will try more aggressive unlocking than the default 520 unlock intensity. This parameter may (and should) be specified for each GPU separately as some GPUs can support higher unlocked speeds.
- If an Nvidia LHR card locks up because of high -lhr (the default 520 will work with most cards), the card will be unlocked again, and the -lhr value will be lowered if necessary
- Added support for new AMD Windows drivers up to latest driver version 22.2.3
- Added support for new AMD Linux drivers up to latest driver version 21.50
- Multiple other small fixes and improvements
The updated list of known issues (driver incompatibilities, etc.) and workarounds: - The new Nvidia 3050 and 3080 12GB cards have different kind of LHR lock, which is not supported yet by PhoenixMiner.
- When mining with LHR cards, the hashrate will start lower and will go up to its normal value in about 2-4 minutes (similar to the auto-tune process on AMD cards).
- AMD Linux driver 21.40.1 has a bug preventing proper setting of clocks and voltages on older cards (RX4x0/RX5x0/Vega/RadeonVII). Given that these drivers are also usually slower than the older drivers for these cards, we recommend using Linux drivers 20.30 for anything older than RX6000 series.
- If you are using Linux drivers 21.40.1 with Radeon VII cards, you need to add the option -fpwm 1 in order to have proper fan control.
- AMD Linux drivers 21.40.1 has finally removed the requirement of PCIe atomics but there are problems when you try to mix Polaris (RX4x0/5x0) cards and Vega or newer cards on the same rig.
- Some Nvidia cards will report a lot of stale shares under Windows 11. Using the same driver version under Windows 10 resolves the issue.
For more robust integrity check, you can use our GPG public key, which was verifyed with ETH transaction from our main devfee account as explained here: https://bitcointalk.org/index.php?topic=2647654.msg56755869#msg56755869. Here are the signatures for the files in this release: Please disregard any posts with "new" versions of PhoenixMiner in this thread unless they are from our user account, and the files are hosted on our web server: https://phoenixminer.info/ Hi PhoenixMiner! I have a strange problem with a vega 56 .. missing 10 mhs (about 41mhs).. the nvidias, my other vega 64 and the amd 5700 work great! usually for my amds i use amd memory tweaker with TRM and all are fine.. what can it be? any suggestions? win10, driver 27.20.1017.1011 |
|
|
|
Hi sp_!
What about vega 64? This is the last problematic card with your miner, the others are ok :-)
Getting 33.5 MH/s in ethereum vs 50.5 with trm :-(
The Vega needs a program called memtweak. It's buildt into hiveos. I don't know the optimal parameters, because I have never owned a Vega. I use amdmemtweak under windows, tbm 1.43 cuda 11.4.. it works with Trm, Gminer and lolminer but not for Tbm! in Trm/gminer/lolminer vega64 gives me similar result..50.5mhs! thanks alex |
|
|
|
|
Hi sp_!
What about vega 64? This is the last problematic card with your miner, the others are ok :-)
Getting 33.5 MH/s in ethereum vs 50.5 with trm :-(
please help me!
Alex
|
|
|
|
|
Hi! whats a good setting for my p104-8gb to mine eth?
i have no problem with etc.. but with eth i have strange result..
now they are going with PL 75% + 225 core - 350 mem...33/34 mhs..
any attempt to put positive mem leads me to loss hashrate..
they are Asus p104-100 with bios 86.04.7A.00.19 and driver 471.96.
thanks
alex
|
|
|
|
|
Any news on lhr side of cminer?
thanks
alex
|
|
|
|
Hi sp_! Finally with 1.38 my rig is ok! one stupid question... it is possible to install in win10 the cuda 11.5 without install new driver 49x from nvidia? my rig doesnt like anything over 472.. thanks alex |
|
|
|
Hi!
My rig ( 2x1060+9xp104+3060ti+4000) works only with dagintensity 1 in 1.35
any suggestions to solve the problem?
alex
Dag verification failed? you can try to halve the xintensity and use --dagintensity 2 13 cards need alot of virtual memory in the rig i have no luck with --dagintensity >1 with mine p104-100 despite low xintensity. with other cards seems ok. if i turn off overclock should they work? thanks alex |
|
|
|
This is my config
-d -K 1 --dagintensity 1 --xintensity 284 -a ethash -H eu1.ethermine.org -p 4444 -r 40 -y 20 -t 120 -W ETH_WALLET -w $rigName -P x --maintenance-wallet MAINTENANCE_WALLET --maintenance-percent 5
As I understood dagintensity should be lower in higher clocks. Has this changed in new version?
yes. The dagintensy has changed. 1 is too low. try 2 or 4 or more. Previously the dagintensity only set the config for the dag creation, but now we use this setting for the solver as well. Default is 0 (9 on nvidia) Hi! My rig ( 2x1060+9xp104+3060ti+4000) works only with dagintensity 1 in 1.35 any suggestions to solve the problem? alex |
|
|
|
|
Hi
Whats a good start setting for a 3060ti lhr v3?
I have it as device 0 so i added --lhr-unlock [1] on bat file, its okay?
thanks
alex
|
|
|
|
On 2miners.com ppl have reported good returns on the 6800xt rigs with --xintensity 800 or --xintensity 1024.
The defeult 0 is dynamic which is also good. The intensity will adjust itself. Note that high intensity can use a little more power, and can create stale shares on some mining pools. Thats why we use --xintensty 24 as default on pools that doesn't pay for or reject stale shares.
Hi sp_ Any solution for the eth ZET pool? thanks alex |
|
|
|
|
Hi!
Maybe a error in ZET etc and eth config file.
pool address is eth.zetpool.org:8005 not eth.pool.zet-tech.eu:8005.
thanks
Alex
|
|
|
|
We see new special super fast miner every day and so much of this new miners are scam or phishing software. We need more proofs and thats it.
If this is a real miner, keep up your work and show us some tests and proofs.
I understand that - it makes perfect sense. Also we are fully aware that with missing LHR support (most customer Nvidia cards sold recently) and a missing API (hard to integrate into a mining OS) the usability is limited to only some users at the moment. But both is been worked on and I am sure we can deliver that both before the year is ending. If you take into account what it needs to build a full miner from scratch in total, we already come quite some way and I hope we see some intrepid users trying out the FHR code in the next few days and reporting back to us. Especially with regard to poolside share counts its ok for me!
I'm testing it in the last 24h on my old rig..
At this point I am the skeptic, because we released this thing only 14 hours before your test - Maybe you did a test over night, but surely no full 24 hours yet  Never the less thank you for the positive feedback. Hi ComputeLabs! I checked the uptime and was only 12h :-) now I'm at 22h and the pool side results are very good. at least for my 'old' cards! Good job! Alex MH/s A/R Power Core Mem Temp Fan 0: GTX 1060 6G 21.1 440/0 82.0 1749 4104 48 81 1: P104-100 32.8 583/0 125.9 1923 5215 48 86 2: P104-100 32.6 582/0 127.8 1923 5215 54 91 3: P104-100 32.8 640/0 125.4 1936 5215 46 86 4: P104-100 33.1 590/0 128.2 1949 5215 39 88 5: P104-100 27.8 542/0 990.9 911 5094 44 90 6: P104-100 32.4 573/0 129.4 1898 5215 57 88 7: P104-100 33.0 642/0 125.8 1923 5215 45 89 8: P104-100 33.0 616/0 127.5 1949 5215 50 90 9: GTX 1060 6G 19.3 334/0 68.4 1587 4016 59 100 10: P104-100 33.3 605/0 123.8 1961 5215 44 90 --------------------------- Summary 331.2 6147/0 2155.3 Online since: 22h 32m 23s |
|
|
|
|
its ok for me!
I'm testing it in the last 24h on my old rig..
9xp104+2p106...
hashrates reported are similar to gminer or tbm but shares seem slightly superior on pool :-)
thanks
Alex
|
|
|
|
|
Just kidding..
