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

https://phoenixminer.info/downloads/PhoenixMiner_5.8a_Windows.zip
https://phoenixminer.info/downloads/PhoenixMiner_5.8a_Linux.tar.gz


Changes in version 5.8a :

• 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

Can second this. Their pool is paying me out just fine.

I can't get any of the BTCP pools to work. They all show up as dead

Edit: Disregard, I had a typo in my BTCP wallet address this entire time T_T

FOH with your graphic card discussion in an ASIC thread

Just got MiningPoolHub ZCL pool working (I think). I don't really trust this pool since the dashboard never seems to show my hashrate even though I'm getting accepted shares for the past 15-20 minutes.

Huh, you're right, re-enabled it today and it's taking my shares. Whatever I guess

How about ZCL pools? I've tried a couple with no luck myself

us.cmmmine.com:3032

worker is your CMM address

Couldn't figure out CryptoBridge, so the exchange I setup on is https://safe.trade

I'm not actively mining it, just have it setup in my auto-profit switch in case it decides to ranodmly skyrocket, but I can confirm that the pool is compatible with Z9s.




Now, my question is whether or not there are any ZEC pools that actually work with the Z9? I've tried antpool's but it rejected 100% of my shares.

Did the Lyra2RE algo finally die off over the weekend? I've noticed that that the stratum servers across multiple sites have been unresponsive for a few days now...

Hello!

My friend moved to another state and decided to leave me a couple of his USB bitcoin miners to play around with. To begin with, all my experience lies with scrypt mining and pi controllers (currently running ~50MH/s total of scrypt devices). With that said, I have next to zero experience with windows versions of mining software or sha256 devices/software for that matter. I know I'm not going to get rich or see any real profit off it, but it's more curiosity and exploration that is driving me to play around with this device. Please, do not post something useless such as "Throw it away!" or "Give up!" because that is not the point of my inquiry, obviously.

Anyway, the first device he gave me is an Antminer U2. I know this is obviously an ancient device in relative terms, but I just want to play around with it and see if I can get it working with my PC running Window 10. I was wondering if anyone has had any luck with getting one of these devices with Windows 10. I've tried following the guides that Google has led me to, but nothing I try seems to work. Both CG and BFG miners do not recognize my software either with the default drivers or with the zadig replaced drivers. The device shows up in device manager, though. I've tried using the most recent versions of CG/BFG as well as the Antminer version of CG. Also worth noting is that I'm only trying to run it at the stock frequency, so overclocked frequencies aren't preventing it from being detected. Any and all advice/experiences are welcome!

While I'm here, he also left behind a single Block Erupter (one of those small 333MH/s devices), but I haven't even plugged it in yet to fiddle around with. So, any advice/experiences related to those devices and Windows 10 are greatly appreciated as well!

Thanks in advance!

Update: I've managed to get the U2 detected by reinstalling the drivers, replacing them with zadig, and running the latest cgminer with the following settings: cgminer.exe --anu-freq 200 -o POOL -u USERNAME -p PASSWORD --expiry 1 --queue 0 --scan-time 1
Going to try the Erupter in the morning

LMAO, I literally just saw this listing, googled the name, and this thread was the first result I clicked on. I was like "12TH @ 1000W for no cost at all?! Did I jump forward into the future overnight?!"

I already reported the listing as a scam.

Update: The listing has already been removed lmao

I'm currently experiencing an issue where my Minera software seems to just crash every few hours. I honestly have no idea what's going on; I just know that the web interface becomes inaccessible and my miners report no hashrate even though everything is still powered on. I have to cut the power to my pi and restart it that way to get it working again. Going to do a fresh install and see what happens...

Update: Even after a fresh install and switching to a 2nd pi, it's still happening. Not sure how to fix this...

I just installed the latest minera image onto a new pi b+ I bought and I'm experiencing the php/layout issues that others have recently mentioned. This is off of a brand new install and the errors are visible on multiple devices even after clearing the cache. These errors make it impossible to configure minera.

I also updated another pi from 0.6.0 to 0.6.1 and now it's useless because of these issues as well.

I also run my 5 chips at 850, so that's why I started there as well. I'll try your settings with cpuminer for 24h and let you know how it works out. Thanks!

Update: I actually just tried these settings and CPUminer still won't detect any devices. Going back to dmaxl fork and giving that a whirl @ 800 instead.

You get 25+ out of 800MHz? O.o What's your command line look like, and do you also use the dmaxl fork?

I just got my hands on a used Gridseed G-Black, anyone got tips for setting it up with Minera? My current settings (with using the dmaxl fork of cgminer) areI'm gonna let it run overnight and see what the average hashrate is in the morning. Any tips or tweaks anyone can offer are welcome :-D



Edit: after about 8 hours of runtime, it's averaging a little over 22Mh/s but with like a 16% HW error rate. Gonna try dropping the frequency and seeing if I can get it more efficient.

What is the freq_value setting you're using for 281.25? Also, how did you find these values in the first place? This thread is the only place I managed to find the freq_values for these frequencies over 250.

I've actually installed your version twice, so my archive doesn't have the old lua in it either XD I didn't think to look there for the old settings, so I tried installing some other forks to mess around with, but ended up just going back to yours. For now, I found a thread that has a handful of settings for frequencies higher than 250 (https://bitcointalk.org/index.php?topic=750220.0) if you'd like to add some more to a future release like you mentioned. I have no idea how the OP found these settings though.


On a side note, I have a wifi antenna installed on my S3+, but I can't access the web interface unless I plug an ethernet in and access that IP instead. Same can be said for using my SSH and SCP utilites. However, when using the wifi, the unit still hashes fine and all that. What gives?

Edit:
I'm not sure how often it does this, but I just noticed that my device keeps killing and restarting cgminer with messages like these Is there a memory leak or something?

My bad, I thought I had read somewhere that the latest main branch included xnonce support (what can I say, I like beer). Anyway, I went ahead and installed your latest version for now and it seems to have overwritten the custom asic-freq file that included several other frequency settings up to 281MHz T_T Now, I realize I can manually set my freq/voltage (in fact, I am now doing so since I can't find a backup version of the asic-freq file I had before), but I have no idea what the regdata value (which is the 'freq_value' lines in the aforementioned file) should be for the frequencies higher than 250MHz. Also, what exactly is the "GH/S(paid)" column that gets added to the status page? Is it supposed to show my effective poolside rate or something? At any rate, your version is running smoothly, but I'm still not quite at the stable @ 500GH mark that I'm aiming for. Here's a screenshot of my current status for what it's worth.http://i.imgur.com/83ddM2i.png

I just want to preface this post by saying that I wholly apologize if this has been covered anywhere in this thread previously, but ~500 pages of posts to search through is extremely rough.

Anyway, I just purchased a used S3+ that arrived a couple days ago and I'm still figuring it out. My previous experience with mining lies wholly with small scrypt rigs and Pi controllers. I'm only a about 6-7 months into mining (late start, I know), but I'm picking up on things rather quickly. Regardless of my mini-scrypt rig experience, I'm struggling to get my S3+ to hash over 500GH, when it was advertised at a stable 566+GH when I purchased it from fleabay. To provide another tidbit of info, I'm using a 650W PSU to power the S3+, so I'm rather sure I'm providing enough power to the unit.

Anywho, to the main point of my post: My S3+ is currently running the latest firmware and started with the factory defaults (from Jan2015) which includes the 4.6.1 version of cgminer built for the S3 machines. I'm currently using a setting of 275MHz, and 815 voltage. However, I'm looking to include xnonce support while overclocking my S3+. This presented complications for me as soon as I began looking into it. I started by installing the cgminer 4.7 provided by westhash/mintsy/etc for S3 rigs that includes xnonce support. The problem that arises when using the provided "updated" version is that the '--bitmain-voltage' command line option no longer seems to work with this version, thusly cgminer fails to start unless I remove this specific option from S99cgminer's "PARAMS=" line. To further my inquiry, I am curious as to if/how I can get the latest cgminer version (4.9.2, or any version for that matter) working properly with xnonce support AND voltage options with my device, if at all possible.

I would greatly appreciate and welcome any advice on the matter as I am a complete noob when it comes to Bitmain devices and updated versions of cgminer (my scrypt rig uses a really old dmaxl fork of cgminer). Treat me like a complete idiot and berate me for all I care, as long as it helps me maximize the output of my device (aiming for at least a stable 500+GH). Feel free to ask me for anything to help you help me.

Awesome, you added exactly what I asked for :-D