Does dual mining really increase rewards that much?  I have always avoided it because the one time I did try, I found that mining a single chain actually produced better results.  Has the tech improved and everyone should be dual mining now, or are there certain cards where this makes sense while others do not?  I'm genuinely curious because all of the miners seem to have dual mining options these days, yet I can't seem to figure out how this would be beneficial when I consider my own results (admittedly a long time ago).  If anyone has any information or a resource to help me learn more about dual mining and if it is worth it, I would be appreciative.  Thanks!

Essentially people like us who missed earlier waves.

Hi guys i hope you are doing good

in my country there are constants power cuts, so the miners will restart. the thing is, everytime it does, as i didnt start the miner as administrator, it would run without the voltage mods, so it gets high temperatures


i created a shortcut and use the options for it to always run as administrator, and to not ask to click it, but it either wont boot (if i put it on sell:startup), or will run but not as admin so no mods

is there any way to do this?

to start the pc and it runs the miner as admin so the voltage and clock and power mods work?

thanks :=)

Thanks for the reply i will take a look at the link currently hoovering up info as want to solve the stale share problem which im sure is caused by being stuck on kernel 0 for now.

Actually had a breakthrough late last night just before bed it was a "what if a try this" whilst my inner voice was "dont mess about when your this tired just go to bed man" moment, but after a fk it, it turns out two of the 6800's dont like mclock @ 1075 and drop down to 10Mhs with it. I suspect it it could be throttling as when i drop mclock down to 1050 on those two cards they come back to 63Mhs but with hotter mem temps than the others so the following is how i went to bed and woke with the rig still purring away nice n stable at around 380Mhs. :-)


-clkernel 0
#-clNew


-cvddc -165
-cclock 1200
-mclock 1125,1050,1125,1125,1050,1125

-tmax 60
-tt -60,-70,-60,-50,-50,-50
#-gt 6

GPU1: cclock 1200 MHz, cvddc 868 mV, mclock 1074 MHz, Tj 58C, Tmem 72C, 420 kH/J
GPU2: cclock 1200 MHz, cvddc 862 mV, mclock 1049 MHz, Tj 56C, Tmem 78C, 388 kH/J
GPU3: cclock 1200 MHz, cvddc 868 mV, mclock 1074 MHz, Tj 62C, Tmem 76C, 398 kH/J
GPU4: cclock 1200 MHz, cvddc 862 mV, mclock 1074 MHz, Tj 62C, Tmem 70C, 390 kH/J
GPU5: cclock 1200 MHz, cvddc 868 mV, mclock 1049 MHz, Tj 58C, Tmem 66C, 414 kH/J
GPU6: cclock 1200 MHz, cvddc 868 mV, mclock 1074 MHz, Tj 53C, Tmem 60C, 416 kH/J
GPUs power: 941.0 W; total power: 1141.0 W; cost: 6.30 USD/day; 333 kH/J

Eth speed: 383.928 MH/s, shares: 1862/1/21, time: 14:51
GPUs: 1: 63.194 MH/s (285/2) 2: 63.477 MH/s (330/5) 3: 64.645 MH/s (330/2) 4: 64.643 MH/s (287/2) 5: 63.488 MH/s (320/4) 6: 64.482 MH/s (311/6)



Now the above is all running under Manajaro which is a new experience for me with subtle differences to Ubuntu like no @reboot under crontab lol.


I have a test rig running Ubuntu 20.04.3 with AMDGPU driver 21.20 working nice for one GPU but no more and with no stales as able to use optimized kernels. I would like it very much if PM could release next version to solve the multiGPU issue with latest rocr driver which according to link below is related to rocr driver having PCIE 3.0 atomics limitation and i suppose a skeptic might scowl at AMD for messing with miners in that way unlike Nvidia and there LHR darkness. I haven yet been able to get ubuntu working with multigpu but even if possible its obvious i will be back to driver 20.40 stuck on kernel 0 same as Manjaro... On a side note i did try driver 21.30 just for a test, it crashes after building DAG for single GPU.

https://www.reddit.com/r/gpumining/comments/ptmyjd/ubuntu_20043_amdgpu_2130_opencl_rocr_rocm/

Can someone read the script /hive/miners/phoenixminer/h-run.sh: line 23

And tell me what is in the line 23?

Thank you in advance

Can someone read the script /hive/miners/phoenixminer/h-run.sh: line 23

And tell me what is in the line 23?

Thank you in advance

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

PhoenixMiner_5.7a_Windows.zip (GitHub)
PhoenixMiner_5.7a_Linux.tar.gz (GitHub)



The new features in this release are:

• Added lock core clock
• The problem with the missing GPU temperatures on Nvidia GPUs is fixed
• Added native kernels for AMD RX6700 GPUs. These are faster than the generic kernels and produce a lot less stale shares
• Increase the max supported DAG epoch to 550 (should be enough to about Jan 2023)
• Full support for setting clocks, fan speeds, voltages, and memory timings of AMD RX6900/6800/6700 cards
• The specific hashrate is now shown in the form of kilo hashes per joule (kH/J). Example: if a GPU has hashrate of 30 MH/s with 100W power usage, the specific hashrate is 300 kH/J
• Added new command-line parameters -ttj and -ttmem, allowing automatic fan speed control based on GPU hotspot (junction), and memory temperatures respectively. Example: -ttmem 83 will keep the GPU
  
  memory temperature at or bellow 83C by increasing the fan speed as necessary. These parameters can be combined with -tt, as well as with each other. These options are supported only on AMD GPUs that report
  
  junction and memory temperatures
• Added new command-line parameters -tmaxj and -tmaxmem, allowing to decrease the GPU usage when the GPU hotspot (junction), or GPU memory temperatures are above the specified thresholds. These options
  
  are supported only on AMD GPUs that report junction and memory temperatures
• Added support for AMD Windows drivers 21.3.2, and 21.3.1
• Added support for AMD Linux drivers 20.50.x. Use this drivers only if you have Polaris or older GPUs, or the latest RX6x000 GPUs. WARNING: Vega, Radeon VII, and Navi GPUs won't work with these
  
  drivers!
• Turn off the zero fan feature on AMD cards whenever a fixed fan speed is used (e.g. -tt -40), or when an auto fan with min fan speed is used (e.g. -tt 63 -minfan 35). To disable this feature, add -
  
  fanstop 1 command-line parameter
• When -mcdag 1 is specified under Linux, the miner will not wait for the daggen.sh script to finish before starting to generate the DAGs. Instead it will for a fixed 7 seconds. This allows you to do all
  
  the following in the daggen.sh: turn off the overclocking of Nvidia GPUs, sleep for 30-60 seconds to allow time for DAG generation, and then re-apply the overclocking of the Nvidia GPUs
• Other small improvements and fixes

The support for -ttj, -ttmem, -tmaxj, and -tmaxmem for Nvidia 3090 and 3080 GPUs is not yet ready for release. We hope to have it ready for the final 5.7 release.

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.

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

What average hashrate do you end up with for your RX 6800?  Have you tried the April driver + 5.6b?

Hello.

Here im adding a shared spreadsheet of different RX cards configurations,their overclock and bios settings, hashrate and power draw from the wall or GPU-Z watt draw.

Everybody feel free to add your gpus but please keep it organized so we can all profit from the best configurations and hashrates for different cards.

https://docs.google.com/spreadsheets/d/1pH326fwnYWC5Jef2FdF4KnJ4CLj0cwDDtGjrlgekk1A/edit?usp=sharing

Enjoy:)