Search content
Sort by
Showing 20 of 47 results by almartins
Re: PhoenixMiner 5.6d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
The new beta version is finally ready. You can download PhoenixMiner 5.6d from here:
PhoenixMiner_5.6d_Windows.zip (GitHub)
PhoenixMiner_5.6d_Linux.tar.gz (GitHub)
The new features in this release are:
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.6
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.6d.
PhoenixMiner_5.6d_Windows.zip (GitHub)
PhoenixMiner_5.6d_Linux.tar.gz (GitHub)
The new features in this release are:
- 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.6
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.6d.
Re: PhoenixMiner 5.6d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
The new beta version is finally ready. You can download PhoenixMiner 5.6d from here:
PhoenixMiner_5.6d_Windows.zip (GitHub)
PhoenixMiner_5.6d_Linux.tar.gz (GitHub)
The new features in this release are:
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.6 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.6d.
PhoenixMiner_5.6d_Windows.zip (GitHub)
PhoenixMiner_5.6d_Linux.tar.gz (GitHub)
The new features in this release are:
- 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.6 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.6d.
Nvidia's Virtualization Unlocked On Gaming GPUs via Hack
https://www.tomshardware.com/news/nvidia-gpu-virtualization-unlocked-on-client-gpus
How can this discovery change GPU mining?
https://www.tomshardware.com/news/nvidia-gpu-virtualization-unlocked-on-client-gpus
How can this discovery change GPU mining?
Re: NVIDIA is cutting the 3060's Hash Rate in Half & NEW Mining specific GPU's
I am thinking of buying this GPU.
From what I read, if the GPU is connected directly to the motherboard, the PCI x16 plug, and has a monitor connected, mining runs smoothly. That's it?
Or is it necessary to also use such a developer driver?
From what I read, if the GPU is connected directly to the motherboard, the PCI x16 plug, and has a monitor connected, mining runs smoothly. That's it?
Or is it necessary to also use such a developer driver?
Not necessary a monitor, the hdmi cable itself is enough. You can remove the monitor. Or use a hdmi dummy.
But, even using the main GPU, is it necessary to use the Beta driver?
Yes,
Is necessary to use the Beta driver 470.05 but other condition must be met:
- PCIe connections 16x 3.0 or higher (16x risers can be used)
I think the GPU bios check if the connection is 16x 3.0 or higher and if there is a monitor connected.
It would be good if someone figured out how to get around these restrictions ...
One of my two apollo batch 1 after being shut down, it didn't work anymore. When turning it on, only the fan runs for 1-2 s and stops. The front led has no activity and the network card leds appear to have normal activity. I already cleaned it and tried to find any signs of damage but I can't find any.
What else can I try?
What else can I try?
That front led is software controlled. It showing no activity suggests that the system doesn't boot at all or not correctly at least. In that situations your options are somewhat limited:
Option 1) Re-flash the sd card. In many cases that appears to help.
Option 2) Flash another sd card. The current one may be dead.
Option 3) The non-trivial option: Get a USB to TTL adapter and attach it to the uart of the mcu board. That will allow you to see what is happening during system boot and possibly give a clue what's wrong.
Thanks whiteogre,
Option 1 made everything light up. I thought that the front led would give some signal even with the card damaged but not. So my two 'apollos' continue to mine and soon reach 5 LTC.
One of my two apollo batch 1 after being shut down, it didn't work anymore. When turning it on, only the fan runs for 1-2 s and stops. The front led has no activity and the network card leds appear to have normal activity. I already cleaned it and tried to find any signs of damage but I can't find any.
What else can I try?
What else can I try?
@ShinyGG
Did a service on 1 of my rigs a few weeks ago.
Sorry about the cable management. Did it after the pics.
0: Gigabyte GTX 1080 8GB 86.04.3B.40.61 1607/4519 30.39 MH/s 101 W 61°C / 0%
1: Gigabyte GTX 1080 8GB 86.04.17.40.38 1620/4519 30.45 MH/s 101 W 62°C / 0%
2: Gigabyte GTX 1080 8GB 86.04.17.40.38 1582/4519 30.13 MH/s 101 W 60°C / 0%
3: Gigabyte GTX 1080 8GB 86.04.17.40.38 1645/4519 30.66 MH/s 101 W 56°C / 0%
4: Gigabyte GTX 1080 8GB 86.04.17.40.38 1582/4519 30.22 MH/s 102 W 55°C / 0%
5: Evga GTX 1080 8GB 86.04.17.00.80 1632/4519 30.66 MH/s 101 W 58°C / 0%
6: Gigabyte GTX 1080 8GB 86.04.17.40.38 1594/4519 30.42 MH/s 100 W 60°C / 0%
7: Gigabyte GTX 1080 8GB 86.04.17.40.38 1632/4519 30.65 MH/s 101 W 59°C / 0%
243.58 MH/s 848 W
Eth: Share actual difficulty: 226.8 GH (!)
Eth: Share accepted in 14 ms
Eth speed: 243.542 MH/s, shares: 19566/0/0, time: 199:06
GPUs: 1: 30.374 MH/s (2519) 2: 30.444 MH/s (2441) 3: 30.134 MH/s (2486) 4: 30.660 MH/s (2487) 5: 30.223 MH/s (2361) 6: 30.656 MH/s (2444) 7: 30.402 MH/s (2454) 8: 30.649 MH/s (2374)
Eth: New job #0d67a81a from eth.2miners.com:2020; diff: 8726MH
Eth speed: 243.555 MH/s, shares: 19566/0/0, time: 199:06
GPUs: 1: 30.379 MH/s (2519) 2: 30.445 MH/s (2441) 3: 30.139 MH/s (2486) 4: 30.660 MH/s (2487) 5: 30.225 MH/s (2361) 6: 30.657 MH/s (2444) 7: 30.404 MH/s (2454) 8: 30.648 MH/s (2374)
Eth: New job #34046e5a from eth.2miners.com:2020; diff: 8726MH
Eth speed: 243.563 MH/s, shares: 19566/0/0, time: 199:06
GPUs: 1: 30.375 MH/s (2519) 2: 30.444 MH/s (2441) 3: 30.142 MH/s (2486) 4: 30.660 MH/s (2487) 5: 30.223 MH/s (2361) 6: 30.657 MH/s (2444) 7: 30.412 MH/s (2454) 8: 30.649 MH/s (2374)
GPU1: 60C 0% 102W, GPU2: 62C 0% 101W, GPU3: 60C 0% 102W, GPU4: 56C 0% 103W, GPU5: 55C 0% 102W, GPU6: 58C 0% 101W, GPU7: 60C 0% 103W, GPU8: 59C 0% 102W
GPUs power: 815.7 W
Still collecting enough 3070 zotac edge for the next watercooled. Difficult to get for a good price.
Did a service on 1 of my rigs a few weeks ago.
Sorry about the cable management. Did it after the pics.
0: Gigabyte GTX 1080 8GB 86.04.3B.40.61 1607/4519 30.39 MH/s 101 W 61°C / 0%
1: Gigabyte GTX 1080 8GB 86.04.17.40.38 1620/4519 30.45 MH/s 101 W 62°C / 0%
2: Gigabyte GTX 1080 8GB 86.04.17.40.38 1582/4519 30.13 MH/s 101 W 60°C / 0%
3: Gigabyte GTX 1080 8GB 86.04.17.40.38 1645/4519 30.66 MH/s 101 W 56°C / 0%
4: Gigabyte GTX 1080 8GB 86.04.17.40.38 1582/4519 30.22 MH/s 102 W 55°C / 0%
5: Evga GTX 1080 8GB 86.04.17.00.80 1632/4519 30.66 MH/s 101 W 58°C / 0%
6: Gigabyte GTX 1080 8GB 86.04.17.40.38 1594/4519 30.42 MH/s 100 W 60°C / 0%
7: Gigabyte GTX 1080 8GB 86.04.17.40.38 1632/4519 30.65 MH/s 101 W 59°C / 0%
243.58 MH/s 848 W
Eth: Share actual difficulty: 226.8 GH (!)
Eth: Share accepted in 14 ms
Eth speed: 243.542 MH/s, shares: 19566/0/0, time: 199:06
GPUs: 1: 30.374 MH/s (2519) 2: 30.444 MH/s (2441) 3: 30.134 MH/s (2486) 4: 30.660 MH/s (2487) 5: 30.223 MH/s (2361) 6: 30.656 MH/s (2444) 7: 30.402 MH/s (2454) 8: 30.649 MH/s (2374)
Eth: New job #0d67a81a from eth.2miners.com:2020; diff: 8726MH
Eth speed: 243.555 MH/s, shares: 19566/0/0, time: 199:06
GPUs: 1: 30.379 MH/s (2519) 2: 30.445 MH/s (2441) 3: 30.139 MH/s (2486) 4: 30.660 MH/s (2487) 5: 30.225 MH/s (2361) 6: 30.657 MH/s (2444) 7: 30.404 MH/s (2454) 8: 30.648 MH/s (2374)
Eth: New job #34046e5a from eth.2miners.com:2020; diff: 8726MH
Eth speed: 243.563 MH/s, shares: 19566/0/0, time: 199:06
GPUs: 1: 30.375 MH/s (2519) 2: 30.444 MH/s (2441) 3: 30.142 MH/s (2486) 4: 30.660 MH/s (2487) 5: 30.223 MH/s (2361) 6: 30.657 MH/s (2444) 7: 30.412 MH/s (2454) 8: 30.649 MH/s (2374)
GPU1: 60C 0% 102W, GPU2: 62C 0% 101W, GPU3: 60C 0% 102W, GPU4: 56C 0% 103W, GPU5: 55C 0% 102W, GPU6: 58C 0% 101W, GPU7: 60C 0% 103W, GPU8: 59C 0% 102W
GPUs power: 815.7 W
Still collecting enough 3070 zotac edge for the next watercooled. Difficult to get for a good price.
You run a rig of 1080 Without using the enlargment pills ?
From what I read about this Pills, you should get 10 MH/s more per card
Where did you see the 1080 give more than 30 MH/s at 100 W?
Great thank you so much jstefanop for all the work !
Here is a feature request for next update :
For example, I'd like to have the possibility to set the miner on balanced mode from 07:00PM to 07:00 AM and on another mode for another amount of time set in hours.
What do you think ?
This would be very nice... By night (cheaper electricity) FULL MODE, by day ECO mode... Please jstefanop, think about it... Here is a feature request for next update :
For example, I'd like to have the possibility to set the miner on balanced mode from 07:00PM to 07:00 AM and on another mode for another amount of time set in hours.
What do you think ?
People (like me) with high electricity prices need this. And this will be a new feature no other ASIC has (pro miners don't need this, but hobby/home miners need it). Sure you are trying to build a "different miner"
.Don't forget this, please. Not sure if easy to add this feature. I have kwh price about 0,10 with sunlight. About 0.05 by night. You know
.I emphasize that this option is very important.
Vejam aqui:
https://eco.sapo.pt/2019/08/27/troca-e-remuneracao-de-criptomoedas-isentas-de-iva-e-irs/
O que acham ?
A mim parece-me que temos um bom enquadramento fiscal.
https://eco.sapo.pt/2019/08/27/troca-e-remuneracao-de-criptomoedas-isentas-de-iva-e-irs/
O que acham ?
A mim parece-me que temos um bom enquadramento fiscal.
Everything seems to be working ok now. It's almost like it need to "warm up". Odd
The same here after 6 days stopped, first hours hardware errors start high but decrease to normality.
"
New problem I clicked "shutdown" on the initial Apollo that popped up on futurebit.local, and now I can't figure out how to turn it back on. Because I don't know its IP Address...
"
You need turn it off wait 10s turn it on and will start mining.
"
Posted by: whiteogre
Optimizing efficiency using custom mode
"
I was doing the same but without control of the consumption and in one machine I reached the 710.4 mV and in another 722.85 mV keeping the hashrate and not having hardware errors> 1%.
Note: I think 1-2 min. it is not enough to check whether hashrate and hardware errors are reached. I think it is more correct to restart the miner and wait 15 min.
Very good job whiteogre
!
Posted by: whiteogre
Optimizing efficiency using custom mode
"
I was doing the same but without control of the consumption and in one machine I reached the 710.4 mV and in another 722.85 mV keeping the hashrate and not having hardware errors> 1%.
Note: I think 1-2 min. it is not enough to check whether hashrate and hardware errors are reached. I think it is more correct to restart the miner and wait 15 min.
Very good job whiteogre
!I'm thinking droping voltage, step by step, to find a minimum my miner can run at 589 MHz.
What problems will I encounter ?
Can I recover on my own?
What problems will I encounter ?
Can I recover on my own?
At some point when lowering the voltage, the hardware error rate will start increasing but nothing else should happen. Just in case you manage to still trip some undocumented failsafe and the unit ends up in a reboot loop due to the test settings having been saved, you'll still always have the option to re-flash the sd card and return back to the default settings.
Note that it may take some minutes for the hardware error rate to stabilize so don't be in too much hurry when making voltage changes.
Yea you can never cause any damage under-volting...youll just see HW errors spike, or the miner just wont startup at all.
The software is actually designed so you can do this live...ie start the miner in custom mode, then slowly increase or decrease the voltage while its mining...you can just lower the voltage and keep checking the dashboard HW errors...as long as you dont see the count go up faster than a few a minute your good.
Thank you whiteogre and jstefanop,
I'll spare some wh and fan noise. As I have expensive energy during the day this change is important.
Jstefanop I am waiting for the update that will allow the configuration change, at certain times of the day, to adapt the speed of the miner to the price of electricity.
Keep up the good work
."About saving power"
Hi jstefanop,
I'm thinking droping voltage, step by step, to find a minimum my miner can run at 589 MHz.
What problems will I encounter ?
Can I recover on my own?
Hi jstefanop,
I'm thinking droping voltage, step by step, to find a minimum my miner can run at 589 MHz.
What problems will I encounter ?
Can I recover on my own?
Here we go guys...new image release finally out! ...
Great thank you so much jstefanop for all the work !
Here is a feature request for next update :
For example, I'd like to have the possibility to set the miner on balanced mode from 07:00PM to 07:00 AM and on another mode for another amount of time set in hours.
What do you think ?
This would be very nice... By night (cheaper electricity) FULL MODE, by day ECO mode... Please jstefanop, think about it...
For me too will be a very nice update ... please jstefanop.
Hi jstefanop,
please give us the possibility to lower the fan rotation to near the 1000-1200 rpm. Currently the minimum is 10% which corresponds to 1400-1500 rpms near 60ºC. I want my Apollos to be quieter.
please give us the possibility to lower the fan rotation to near the 1000-1200 rpm. Currently the minimum is 10% which corresponds to 1400-1500 rpms near 60ºC. I want my Apollos to be quieter
.Order # 1209 was received at Portugal and two more Apollos are working.
The screws on the sides came without tightening but it was easy to tighten.
Only problem was having to pay an additional $ 95 for each at Customs
!
The screws on the sides came without tightening but it was easy to tighten.
Only problem was having to pay an additional $ 95 for each at Customs
!95 each?? Isnt import VAT ~17%? Should not be more than $50.
VAT is different from country to country here in the EU. Here is 23% and I paid even more $ 45 in administrative expenses! I will buy more when available from the your European retailer.