PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 35.

Lafu

legendary

Activity: 3136

Merit: 3213

Quote from: VRMdude on October 02, 2021, 12:43:33 PM

Yes they do i can testify to it.

My intention was to provide newer members an opportunity to see what one of these dodgy posts with fake scamware actually looks like rather than have mods nuke them into a blackhole. It would seem every time i come here there is one of these freshly posted my report button is fatigued.

Normaly this posts dosnt stay much long as the reporting bot from Mitchell catching them really fast .
If want to see something crazy read the last pages of my thread here about the fake miner post , https://bitcointalksearch.org/topic/m.58078144 .
I already watching and reporting them too now for a longer time like 2 years nearly and also reporting them on github.

VRMdude

member

Activity: 106

Merit: 31

Quote from: UserU on October 02, 2021, 10:45:45 AM

Quote from: VRMdude on October 02, 2021, 08:26:34 AM

IF YOU SEE ANYTHING LIKE THIS HERE DO NOT TRUST IT ONLY DOWNLOAD PM FROM POST 1 OF THIS THREAD OR THE PROPER PM URL GIVEN THERE AND ALWAYS CHECK THE SIGNATURE AFTER DOWNLOAD AGAINST OFFICAL KEYS or you will have a bad week.

Just report them. Mods usually take swift action against these kind of posts.

Yes they do i can testify to it.

My intention was to provide newer members an opportunity to see what one of these dodgy posts with fake scamware actually looks like rather than have mods nuke them into a blackhole. It would seem every time i come here there is one of these freshly posted my report button is fatigued.

UserU

hero member

Activity: 2128

Merit: 532

FREE passive income eBook @ tinyurl.com/PIA10

Quote from: VRMdude on October 02, 2021, 08:26:34 AM

IF YOU SEE ANYTHING LIKE THIS HERE DO NOT TRUST IT ONLY DOWNLOAD PM FROM POST 1 OF THIS THREAD OR THE PROPER PM URL GIVEN THERE AND ALWAYS CHECK THE SIGNATURE AFTER DOWNLOAD AGAINST OFFICAL KEYS or you will have a bad week.

Just report them. Mods usually take swift action against these kind of posts.

VRMdude

member

Activity: 106

Merit: 31

Quote from: ?? on ??

The new version is finally ready. You can download PhoenixMiner 5.8a from here:

PhoenixMiner_5.8a_Linux.tar.gz Github

URL REMOVED

Changes in version 5.8a :

LHR disable mode -lhrdis 1 - yes (default), 0 - no
Added lock core clock
Fixed an issue causing crashing with some RTX 3060/3080/3090 cards
Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will
provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused
Increased the maximum supported DAG epoch to 600 (i.e. until about Sep 2023)
Implemented full hardware control for AMD RX6900/6800/6700 cards under Linux. Note that with these cards under Linux you need to specify relative core voltage: e.g. -
cclock -50 will set the core voltage to be 50 mV under the default value
Added ROCr kernels for Vega, Radeon VII and Navi cards. With these kernels you will be able to run these cards with Linux drivers 20.45 and later but the performance will
be lower than with the older PAL drivers and kernels. We recommend using AMD Linux driver 20.30 for all cards except RX6900/6800/6700
Fixed an issue causing crashing with some RX6900/6800/6700 cards under Linux (there is no need to run these cards with -clkernel 0 anymore)
Added support for AMD Windows drivers up to 21.8.1. Note that Radeon VII cards will not work with drivers 21.6.1 or higher - you need to use older drivers for proper
operation of these cards
Added support for AMD Linux drivers up to 21.20 (use older drivers for Vega or Radeon VII cards as they will not work with 21.20). Note that the latest 21.30 drivers are
not supported (and the initial testing shows that even the older Polars cards are not working properly with them, so avoid 21.30 for now)
Numerous other fixes and small improvements

Please let us know if you have any problems or questions related to PhoenixMiner 5.8a

IF YOU SEE ANYTHING LIKE THIS HERE DO NOT TRUST IT ONLY DOWNLOAD PM FROM POST 1 OF THIS THREAD OR THE PROPER PM URL GIVEN THERE AND ALWAYS CHECK THE SIGNATURE AFTER DOWNLOAD AGAINST OFFICAL KEYS or you will have a bad week.

VRMdude

member

Activity: 106

Merit: 31

Quote from: Rickirs on September 30, 2021, 09:53:01 PM

I am on Linux.

For me, it looks like none of the options work, I have been to readme many times.
For example, I want to keep temperature of GPU about 65C , what should be conf ?

Code:

./PhoenixMiner -ttj 65 -ttmem 70

Hi, I am mining with Linux but using AMD cards and to get control of the cards for undervolting and overclocking i have to tell the kernel to unlock AMD power play and of course run PM as root. This may not solve your nvidia issue but perhaps offer a clue AND Are you running PM as root? Pay attention to PM screen when starting or changing settings on the fly or even when shutting it down as it will tell you in yellow writing when there are problems with root permissions.

Also consider placing the variables in the config.txt file of PM and it becomes possible to tweek things in real time by opening the config.txt file in another shell or window at the same time PM is running and then press 'c' in PM to load the new settings. Some settings do require PM restart to take hold but you will have to play to determine for self...

Rickirs

member

Activity: 206

Merit: 20

Quote from: relax69 on October 01, 2021, 02:02:17 AM

What you mean "no effect"? I have P106-100 and changes the clocks, but makes difference in the hashrate only about 1 MH/s.

Here is the format of these commands from the readme.txt:

Code:

-tt
Set fan control target temperature (special values: 0 - no fan
control, negative - fixed fan speed at n %)

-cclock
Set GPU core clock in MHz (0 for default). For Nvidia cards use
relative values (e.g. -300 or +400)

-mclock
Set GPU memory clock in MHz (0 for default). For Nvidia cards use
relative values (e.g. -300 or +400)

I am on Linux.

For me, it looks like none of the options work, I have been to readme many times.
For example, I want to keep temperature of GPU about 65C , what should be conf ?

Code:

./PhoenixMiner -ttj 65 -ttmem 70

[/quote]

Sorry, I'm not familiar with Linux, but anyway "-ttj " and " -ttmem " are not supported for GTX1060.

Code:

Release notes

PhoenixMiner 5.6b
-----------------
- Added support for showing GPU hotspot (junction), and video memory temperatures for
Nvidia GPUs. Note that the video memory temperature is only shown by some GPUs
(3080, 3090, possibly 2080Ti)
- The options -ttj, -ttmem, -tmaxj, and -tmaxmem now also work with Nvidia GPUs

For setting core temperature to 65 C you need to use " -tt 65 "
Also maybe try these options too:

Code:

-fcm
Set fan control mode (0 - auto, 1 - use VBIOS fan control, 2 -
forced fan control; default: 0)

-fanidle
(*Linux only*) Set idle fan speed in % (-1 is auto, the default is
20)

-fpwm
(*Linux only*) Fan PWM mode (0 - auto, 1 - direct, 2 - Polaris, 3 -
Vega, 4 - Radeon VII, Navi; default: 0)

[/quote]

As per my understanding, none of the directives are working apart of -log 0 as now it not writing any logs. Whether I add -tt 65 or add -fcm, I see just no effect on gpus mining status.

micdee

newbie

Activity: 11

Merit: 3

Quote from: swogerino on September 24, 2021, 01:42:51 AM

Quote from: janding on September 23, 2021, 08:57:42 PM

Quote from: micdee on September 23, 2021, 02:27:08 AM

Well PM 5.7b is finally running.. with the AMD 21.1.8.1
I know I am an impatient person..
With 5.5c it was about 10-20 seconds I had to wait before I could see the openCL drivers were loaded and the rest of the config file was executed.

but waiting for 5-6 minutes to finally see that the miner is actually start to load the openCL drivers and read the rest of the config file...
Is the long waiting period all have to do with the extra setting features in PM?

I understand it has something to do with the pentium (3,3Ghz) CPU I use, but from 10-20 sec to 5-6 minutes waiting is a bit much in my opinion.. Anything I can do to shorten this? without upgrading my CPU..
I also use 16Gb of RAM..

any help much appreciated

I think is something else other than the CPU processor.
This is what I'm using and 5.7b comes up and runs in seconds for me.

Processor Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, 3312 Mhz, 2 Core(s), 2 Logical Processor(s)
Also same memory 16Gb

I have even a slower processor that I use which is G3900 Celeron which is the lowest of Gen 6 processors and it works perfectly well with the Rx 6800 XT cards I have.The processor is ruled out here and I think you need to uninstall drivers and reinstall them once again,installing a new version of driver like 21.8.1 over an old one does not always run smoothly so this is the first thing to check.Also the HDD is not a problem as the difference between an SSD and an HDD is big enough but surely not 6 minutes.

The system I use is only for mining, so nothing other then software used for installing of preparing the GPU's is on that machine.. I always use DDU to do a full un install of the drivers and delete all (AMD) folders when there still are any left.. ( I have not cleaned the registry, as I thought DDU would do this for me).
I installed the 21.8.1 which are latest compatible drivers with 5.7b (as I read on page 1). I did the full monty install (as I need the AMD software to do the settings for the 6800 I have in the rig.).

It now runs for a while quite smooth again.. so as long as it runs I leave it.. ;-)
But thank you all for your comments... I understand now it is not normal to take that long for PM to start up... I will let you know when I think I found the issue.

relax69

member

Activity: 61

Merit: 40

Quote from: Rickirs on September 30, 2021, 09:53:01 PM

Quote from: relax69 on September 28, 2021, 10:52:43 PM

Quote from: Rickirs on September 28, 2021, 02:57:24 PM

It seems that there is no effect of -tt , -mclock , -cclock etc. on my nvidia 1060 based rig.
I can only manage these through nvida-settings and nvidia-smi

Any advice ?

Windows or Linux?

What you mean "no effect"? I have P106-100 and changes the clocks, but makes difference in the hashrate only about 1 MH/s.

Here is the format of these commands from the readme.txt:

Code:

-tt
Set fan control target temperature (special values: 0 - no fan
control, negative - fixed fan speed at n %)

-cclock
Set GPU core clock in MHz (0 for default). For Nvidia cards use
relative values (e.g. -300 or +400)

-mclock
Set GPU memory clock in MHz (0 for default). For Nvidia cards use
relative values (e.g. -300 or +400)

I am on Linux.

For me, it looks like none of the options work, I have been to readme many times.
For example, I want to keep temperature of GPU about 65C , what should be conf ?

Code:

./PhoenixMiner -ttj 65 -ttmem 70

Sorry, I'm not familiar with Linux, but anyway "-ttj " and " -ttmem " are not supported for GTX1060.

Code:

Release notes

PhoenixMiner 5.6b
-----------------
- Added support for showing GPU hotspot (junction), and video memory temperatures for
Nvidia GPUs. Note that the video memory temperature is only shown by some GPUs
(3080, 3090, possibly 2080Ti)
- The options -ttj, -ttmem, -tmaxj, and -tmaxmem now also work with Nvidia GPUs

For setting core temperature to 65 C you need to use " -tt 65 "
Also maybe try these options too:

Code:

-fcm
Set fan control mode (0 - auto, 1 - use VBIOS fan control, 2 -
forced fan control; default: 0)

-fanidle
(*Linux only*) Set idle fan speed in % (-1 is auto, the default is
20)

-fpwm
(*Linux only*) Fan PWM mode (0 - auto, 1 - direct, 2 - Polaris, 3 -
Vega, 4 - Radeon VII, Navi; default: 0)

relax69

member

Activity: 61

Merit: 40

Quote from: nguyenhathienphu on September 30, 2021, 03:58:10 AM

Quote from: relax69 on September 28, 2021, 10:52:43 PM

Quote from: Rickirs on September 28, 2021, 02:57:24 PM

It seems that there is no effect of -tt , -mclock , -cclock etc. on my nvidia 1060 based rig.
I can only manage these through nvida-settings and nvidia-smi

Any advice ?

Windows or Linux?

What you mean "no effect"? I have P106-100 and changes the clocks, but makes difference in the hashrate only about 1 MH/s.

Here is the format of these commands from the readme.txt:

Code:

-tt
   Set fan control target temperature (special values: 0 - no fan
   control, negative - fixed fan speed at n %)

-cclock
   Set GPU core clock in MHz (0 for default). For Nvidia cards use
   relative values (e.g. -300 or +400)

-mclock
   Set GPU memory clock in MHz (0 for default). For Nvidia cards use
   relative values (e.g. -300 or +400)

can you use the -cvddc

-cvddc Set GPU core voltage in mV (0 for default). For Nvidia cards use relative values (e.g. -300 or +400)

i tried to undervol my 1660s but unsuccessed. it still run with default vcore.

To the best of my knowledge, the voltages are locked in VBIOS for Nvidia cards. To lower voltage use :

Code:

-powlim
Set GPU power limit in % (from -75 to 75, 0 for default)

I would recommend you to use -20% to -30%. For example -powlim -30 will bring voltage in the 800-900 range.

Rickirs

member

Activity: 206

Merit: 20

Quote from: relax69 on September 28, 2021, 10:52:43 PM

Quote from: Rickirs on September 28, 2021, 02:57:24 PM

It seems that there is no effect of -tt , -mclock , -cclock etc. on my nvidia 1060 based rig.
I can only manage these through nvida-settings and nvidia-smi

Any advice ?

Windows or Linux?

What you mean "no effect"? I have P106-100 and changes the clocks, but makes difference in the hashrate only about 1 MH/s.

Here is the format of these commands from the readme.txt:

Code:

-tt
Set fan control target temperature (special values: 0 - no fan
control, negative - fixed fan speed at n %)

-cclock
Set GPU core clock in MHz (0 for default). For Nvidia cards use
relative values (e.g. -300 or +400)

-mclock
Set GPU memory clock in MHz (0 for default). For Nvidia cards use
relative values (e.g. -300 or +400)

I am on Linux.

For me, it looks like none of the options work, I have been to readme many times.
For example, I want to keep temperature of GPU about 65C , what should be conf ?

Code:

./PhoenixMiner -ttj 65 -ttmem 70

Call_Me_Bambi

sr. member

Activity: 574

Merit: 261

Quote from: ?? on ??

The new version is finally ready. You can download PhoenixMiner 5.8a from here:

PhoenixMiner_5.8a_Windows.zip
PhoenixMiner_5.8a_Linux.tar.gz

DON'T download these. They are fake versions. Check the first page of this forum for links to the real PhoenixMiner.

nguyenhathienphu

newbie

Activity: 3

Merit: 0

Quote from: relax69 on September 28, 2021, 10:52:43 PM

Quote from: Rickirs on September 28, 2021, 02:57:24 PM

It seems that there is no effect of -tt , -mclock , -cclock etc. on my nvidia 1060 based rig.
I can only manage these through nvida-settings and nvidia-smi

Any advice ?

Windows or Linux?

What you mean "no effect"? I have P106-100 and changes the clocks, but makes difference in the hashrate only about 1 MH/s.

Here is the format of these commands from the readme.txt:

Code:

-tt
   Set fan control target temperature (special values: 0 - no fan
   control, negative - fixed fan speed at n %)

-cclock
   Set GPU core clock in MHz (0 for default). For Nvidia cards use
   relative values (e.g. -300 or +400)

-mclock
   Set GPU memory clock in MHz (0 for default). For Nvidia cards use
   relative values (e.g. -300 or +400)

can you use the -cvddc

-cvddc Set GPU core voltage in mV (0 for default). For Nvidia cards use relative values (e.g. -300 or +400)

i tried to undervol my 1660s but unsuccessed. it still run with default vcore.

relax69

member

Activity: 61

Merit: 40

Quote from: Rickirs on September 28, 2021, 02:57:24 PM

It seems that there is no effect of -tt , -mclock , -cclock etc. on my nvidia 1060 based rig.
I can only manage these through nvida-settings and nvidia-smi

Any advice ?

Windows or Linux?

What you mean "no effect"? I have P106-100 and changes the clocks, but makes difference in the hashrate only about 1 MH/s.

Here is the format of these commands from the readme.txt:

Code:

-tt
Set fan control target temperature (special values: 0 - no fan
control, negative - fixed fan speed at n %)

-cclock
Set GPU core clock in MHz (0 for default). For Nvidia cards use
relative values (e.g. -300 or +400)

-mclock
Set GPU memory clock in MHz (0 for default). For Nvidia cards use
relative values (e.g. -300 or +400)

Rickirs

member

Activity: 206

Merit: 20

It seems that there is no effect of -tt , -mclock , -cclock etc. on my nvidia 1060 based rig.
I can only manage these through nvida-settings and nvidia-smi

Any advice ?

Rickirs

member

Activity: 206

Merit: 20

Quote from: Notyoursbuisness on September 28, 2021, 01:24:40 PM

for some reason my gpu stopped mining and now I get "debugger detected error".
tried several versions but get same error
is this result of some nasty virus that is roaming on my pc or something ?

Try DDU and then install latest driver again.
DDU : https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Notyoursbuisness

full member

Activity: 214

Merit: 100

for some reason my gpu stopped mining and now I get "debugger detected error".
tried several versions but get same error
is this result of some nasty virus that is roaming on my pc or something ?

Rickirs

member

Activity: 206

Merit: 20

Nevermind.

FineJuice

newbie

Activity: 43

Merit: 0

LHR improvements like nbminer would be lovely if possible.

janding

jr. member

Activity: 170

Merit: 6

One of the most important items you mentioned was READ THE readme.txt FILE.
I see so many that do not read it and many times their issues would be solved if they just would
Read and Study that information. Read that info dozens of times and let it sink in. Then
read it again.

dastardlyman12

newbie

Activity: 21

Merit: 0

this is the config.txt from one of our rigs

-pool eu1.ethermine.org:4444
-wal 0xXXXXXXXXXXXXXXXXXXXXXXXXXXXX.chippy
-proto 3
-eworker chippy
-lidag 1
-gser 1
-acm
-tt -90
-amd
-dbg -1
-hstats 2
-cdm 0
-rmode 2
-ttli 65
-dagrestart 1
-gpus 12345

-mclock 1760,1760,1750,1760,2040
-cclock 1200,1200,920,940,1120
-cvddc 830,830,830,830,875
-mvddc 800,815,815,830,875
-mi 12,12,11,11,11

the rig is rx5700, rx5600, rx5500 and rx570
everything in the config.txt does something useful
the readme.txt provided with phoenix miner will tell you what all the things in the config.txt do.
anybody who doesn't understand should read the readme.txt
once you understand you can look at my config.txt and decide what is right for your amd rig

we have a lot of rigs .our main issue this summer has been heat -ttli have saved us from a lot of headaches
everything we have is bios modded and was dialed back at the start of summer so for instance this rig can run with vram faster
during the winter.
we use windows 10 ghost spectre on every rig. no updates no bloat no telemetry.
we use dwagent for remote access
and yes every rig is also on raptoreum or turtle or monero ocean
you can cpu mine without affecting ethereum hashrate at all.
do some tests find out what works. ive found that cpus with onboard graphics
like xeon e3-1245-v3 or i5 4440 can have all threads on raptoreum at cpu priority 1 without affecting eth hash .
cpus without onboard graphics like ryzen 3600 - you need to mine on 11 threads - keep one for phoenixminer.

read the readme.txt get knowledge
best wishes to the community
im dastardlyman on youtube and the same on discord.
my videos are out of date

Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 35. (Read 784950 times)