Monday, January 9, 2017
When I read discussions about video card temperatures, the vast majority are about the GPU core temperature. With older GPUs like the R9 290, temperature-based throttling when the GPU core temperature hits 94C can be a problem. With newer GPUs like the R9 380 and especially with the Rx series cards, there is rarely issues with GPU core temperatures, even with low-end cooling systems. While the GPU core is always cooled with a heatsink and fans, often the RAM is not. The infrared image above shows how much of a difference that can make in RAM temperatures.
The image was taken of a 4GB MSI R9 380 card with the memory clocked at 1600Mhz while running ethminer-nr. The memory chips above the GPU are connected to the heatsink through a thermal pad, but the chips to the left of the GPU are not. Using an infrared thermometer I measured temperatures between 95 and 100C on the back side of the PCB from the RAM, so the RAM die temperatures are likely well in excess of 100C.
Keeping RAM cool can make a material difference in the clock speeds that can be achieved. Instead of 1600Mhz, I have found that 1500Mhz-rated GDDR5 can reach stable speeds of 1700Mhz when connected to a basic heat spreader. The brand of the memory, Elpida, Hynix, or Samsung, makes little difference in performance when compared to cooling.
While manufacturers will rarely provide enough detail in their specifications or product images to determine if the RAM is cooled, card tear-down reviews will often show the connection between the heatsink and RAM. Of the cards I have used, only a MSI R9 380 Gaming card had all the RAM cooled. Neither MSI Armor2X cards nor Gigabyte Windforce cards have all the RAM chips cooled with a heatsink or heat spreader. I also own an Asus Rx 470 Strix card, and that also lacks active cooling for some of the memory chips.
Saturday, October 29, 2016
Zcash is the hottest coin this month, after going live on October 28th, following several of months of testing. Zcash promises private transactions, so that they cannot be viewed on the public blockchain like bitcoin or ethereum.
I did not expect zcash mining to be immediately profitable, since mining rewards are being ramped up over the first month. However the first hour of trading on Poloniex saw zcash (ZEC) trading at insane values of over 1000 bitcoin per ZEC. Even after 24 hours, 1 ZEC is trading for about 6 BTC, or US$4300. Despite the low mining reward rate, mining pool problems, and buggy mining software, I was able to earn 0.005 ZEC in one day with a couple rigs.
Zcash has both private address starting with "z", and public or transparent address starting with "t". A bug in the zcash network software has meant problems with private transfers, so it is recommended for miners to use only transparent wallet addresses until the bug is fixed. Miners using the "z" address have apparently had problems receiving their zcash payouts from mining pools.
I have been using eXtremal's miner version 0.2.2, which uses OpenCL kernels from the zcash open-source miner competition. Windows and Linux binaries can be downloaded from coinsforall.io, the pool the software is designed for. I get the best performance with the silentarmy kernel, but with only one instance as running 2 instances results in a crash. On Windows running driver version 16.10.1 I get about 26 solutions/s with a Rx 470. Under Ubuntu with fglrx drivers I get about 11 solutions/s for both R7 370 and R9 380 cards.
I experimented with the worksize and threads values in config.txt, but was unable to improve performance compared to the default 256/8192. Increasing the core clock on the R9 380 cards from 900Mhz to 1Ghz increased the performance by 3-4%.
Genoil has released a miner, but only Windows binaries with tromp's kernel at this time. A version including silentarmy's kernel is in the works.
I was unable to find any zcash mining calculators, so I wrote a short python calculator. Here's an example based on the network hashrate (in thousands) at block 1072, for a rig mining 140 solutions/s:
./zec.py 1072 1840 140
Daily ramped mining reward in blocks: 308
Your estimated earnings: 0.0234347826087
At the current price of 6BTC/ZEC, the earnings work out to about US$100. Even if the price drops to 3BTC/ZEC, the daily earnings are still more than double what the same hardware could make mining ethereum. Apparently many other ethereum miners have realized this, since the ethereum network hashrate has dropped by about 25% in less than 30 hours. I expect this trend to continue in the coming days, and eventually reach an equilibrium as the ZEC price continues to drop until it is below parity with BTC.
Coinsforall is still having stability problems, and now 1 ZEC is worth about 1.2 BTC. Therefore I've switched back to eth mining for all my cards except one Rx 470. With Genoil's ZECminer I'm getting about 26 sol/s. I started using zcash.miningpoolhub.com, and after an hour of mining the pool has been stable. Reported hashrate on the pool is about 12H/s, or half the solution rate as expected.
Sunday, September 18, 2016
I recently decided to spend some time to figure out some of the low-level details of how the BIOS works on my R9 380 cards. A few months ago I had found Tonga Bios Editor, but hadn't done anything more than modify the memory frequency table so the card would default to 1500Mhz instead of 1375. My goal was to modify the memory timing and to reduce power usage.
The card I decided to test the memory timing mods on was a Club3D 4GB R9 380 with Elpida W4032BABG-60-F RAM. Although the RAM is rated for 6Gbps/1.5Ghz, the default memory clock is 1475Mhz. In my previous testing I found that the card was stable with the memory overclocked well above 1.5Ghz, but the mining performance was actually slower at 1.6Ghz compared to 1.5Ghz. Unfortunately Tonga Bios Reader does not provide a way to edit the memory timings aka straps, so I'd have to use a hex editor.
I've highlighted the 1500Mhz memory timing in the screen shot above. I found it by searching for the string F0 49 02, which you first have to convert from little-endian to get 249F0, and then from hex to get 150,000, which is expressed in increments of .01Mhz. The timing for up to 1625Mhz (C4 7A 02) comes after it, and then 1750Mhz (98 AB 02). The Club3D BIOS actually has 2 sets of timings, one for memory type 01 (the number after F0 49 02), as and for memory type 02 (not shown). This is so the same BIOS can be used on a card that can be made with different memory. Obviously one type of memory the BIOS supports is Elpida, and from comparing BIOS images from other cards, I determined that memory type 02 is for Hynix.
To reduce the chance of bricking my card, the first time I modified only the 1625Mhz memory timing. Since the default memory timing is 1475Mhz, my modified timing would only be used when overclocking the memory over 1500Mhz. So if the the card crashed on the 1625Mhz timing, it would be back to the safe 1500Mhz timing after a reboot. To actually make the change I copied the 1500Mhz timing (starting with 77 71) to the 1625Mhz timing. After the change, the BIOS checksum is invalid, so I simply loaded the BIOS in Tonga Bios Reader and re-saved it in order to update the checksum.
I used Atiflash 2.71 to flash the BIOS since I have found no DOS or Linux flash utilities for Tonga GPUs. After flashing the updated BIOS, I overclocked the RAM to 1625Mhz, and my eth mining speed went from just under 21Mh to about 22.5Mh. To get even faster timings, I copied the 1375Mhz timings from a MSI R9 380 with Elpida RAM to the Club3d 1625Mhz memory timing. That boosted my mining speed at 1625Mhz to slightly over 23Mh
I then tried a number of ways to improve the timing beyond 1625Mhz, but I found nothing that was both stable and faster at 1700Mhz. Different cards may overclock better, depending on both the GPU asic and the memory. Hynix memory seems to overclock a bit better than Elpida, while Samsung memory, which seems rather rare on R9 380 cards, tends to overclock the best. The memory controller on the GPU also needs to be able overclock from 1475Mhz. Unlike the simple voltage modding the Hawaii BIOS, there is no easy way to modify the memory controller voltage (VDDCI) on Tonga. The ability to over-volt the memory controller would make it easier to overclock the memory speed beyond 1625Mhz.
Since the Club3D BIOS supports both Elpida and Hynix memory, I improved the timing for both memory types. This allows me to use a single BIOS image for cards that have either Elpida or Hynix memory. It's also dependent on the card having a NCP81022 voltage controller, but all my R9 380 cards have the same voltage controller. I've shared it on my google drive as 380NR.ROM if you want to try it (at the possible risk of bricking your card). Atiflash checks the subsystem ID of the target card against the BIOS to be flashed, so it is necessary to use the command-line version of atiflash with the "-fs" option:
atiflash -p 0 380RN.ROM -fs
In addition to improving memory speeds, I wanted to reduce power usage of my 380 cards. On Windows it is possible to use a tool like MSI Afterburner to reduce the core voltage (VDDC), but on Linux there is no similar tool. To reduce the voltage in the BIOS, modify value0 in Voltage Table2 for the different DPM states. After a lot of experimenting, I made two different BIOSes with different voltage levels since some cards under-volt better than others. The first one has 975, 1050, and 1100 mV for dpm 5, 6, & 7, while the other has 1025, 1100, & 1150 mV. These are also shared on my google drive as 380NR1100.ROM and 380NR1150.ROM.
With the faster RAM timing and voltage modifications I've improved my eth mining hashrates by about 10%, without any material change in power use. I've tried my custom ROM on four different cards. Although two of them seem to be OK with 900/1650Mhz clocks, I'm playing it safe and running all four at 885/1625Mhz. If you are lucky and have a card that is stable at 925/1700Mhz, you can mine eth at almost 25Mh/s. With most cards you can expect to get between 23 and 24Mh/s.
Sunday, September 11, 2016
When using Hawaii GPUs such as the R9 290 on Linux, aticonfig does not provide the ability to modify voltages. Even under windows, utilities such as MSI Afterburner usually have limits on how much the GPU voltage can be increased or decreased. In order to reduce power consumption I decided to create a custom BIOS with lower voltages for my MSI R9 290X.
The best tool I have found for Hawaii BIOS mods is Hawaii Bios Reader. For reading and writing the BIOS to Hawaii cards, I use ATIFlash 2.71. It woks from DOS, so I can use the FreeDOS image included in SystemRescueCD.
In the screen shot above, I've circled two voltages. The first, VDDCI, is the memory controller voltage. Reducing it to 950mV gives a slight power reduction.
The second voltage is the DPM0 GPU core voltage. DPM0 is the lowest power state, when the GPU is clocked at 300Mhz, and powered at approximately 968mV. I say approximately because the actual voltage seems to be close to the DPM0 value, but not always exact. This may be related to the precision of the voltage regulator on the card, or the BIOS may be using more than just the DPM0 voltage table to control the voltage. The rest of the DPM values are not voltages, but indexes into a table that has a formula for the BIOS to calculate the increase in voltage based on the leakage characteristics of the GPU. I do not change them.
For reasons I have not yet figured out, the DPM0 voltage in each of the limit tables has to match the PowerPlay table. After modifying the four limit tables, the BIOS can be saved and flashed to the card.
I've created modified BIOS files for a MSI R9 290X 4GB card with DM0 voltages of 868, 825, and 775. With the 775mV BIOS I was able to reduce power consumption by over 20% compared to 968mV.
Wednesday, September 7, 2016
With Monero's recent jump in price to over $10, it's the new hot coin for GPU mining. Monero has been around for a couple years now, so there are a couple options for mining. There's a closed-source miner from Claymore, and the open-source miner from Wolf that I used.
I used the same Ubuntu/AMD rig that I set up for eth mining. Building the miner took a couple updates compared to building ethminer. First, since stdatomic.h is missing from gcc 4.8.4, you need to use gcc 5 or 6. Second, jansson needs to be installed. On Ubuntu the required package is libjansson-dev. The default makefile uses a debug build with no optimization, so I modified the makefile to use O3 and LTO "OPT = -O3 -flto". I've shared the compiled binary on my google drive.
To mine with all the GPUs on your system, you'll have to edit the xmr.conf file and add to the "devices" list. The "index" is the card number from the output of "aticonfig --lsa". Although the miner supports setting GPU clock rates and fan speeds, I prefer to use my aticonfig scripts instead. It is also necessary to modify "rawintensity" and "worksize" for optimal performance. The xmr.conf included in the tgz file has the settings that I found work best for a R9 380 card clocked at 1050/1500. For a R7 370 card, I found a rawintensity setting of 640 worked best, giving about 400 hashes per second.
Although Monero was more profitable to mine than ethereum for a few days, the difficulty increase associated with more miners has evened it out. Dwarfpool has a XMR calculator that seems accurate. The pool I used was monerohash.com, and instead of running the monero client, I created an account online using mymonero.com.
Sunday, August 21, 2016
For a couple months, I've been intending to do a blog post on mining with Ubuntu. Now that I've been able do make a static build of Genoil's ethminer, that process has become much easier. Since I have no Nvidia GPUs, this post will only cover how to mine with AMD GPUs like the R7 and R9 series.
The first step is to download a 64-bit Ubuntu 14.04 desktop release. I use the desktop distribution since it includes X11, although it is possible to use Ubuntu server and then install the X11 packages separately. I recommend installing Ubuntu without any GPU cards installed (use your motherboard's iGPU), in order to confirm the base system is working OK. Follow the installation instructions, and at step 7, choose "Log in automatically". This will make it easier to have your rig start mining automatically after reboot.
After the initial reboot, I recommend installing ssh server. It can be installed from the shell (terminal) with: "sudo apt-get install openssh-server -y". Ubuntu uses mDNS, so if you chose 'rig1' as the computer name during the installation, you can ssh to 'rig1.local' from other computers on your LAN.
Shutdown the computer and install the first GPU card, and plug your monitor into the GPU card instead of the iGPU video port. Most motherboards will default to using the GPU card when it is installed, and if not, there should be a BIOS setup option to choose between them. If you do not even see a boot screen, try plugging the card directly into the motherboard instead of using a riser. Also double-check your card's PCI-e power connections.
Once you are successfully booting into the Ubuntu desktop, edit /etc/init/gpu-manager.conf to keep gpu manager from modifying /etc/X11/xorg.conf. Then install the AMD fglrx video drivers: "sudo apt-get install fglrx -y". If the fglrx drivers installed successfully, running "sudo aticonfig --lsa" will show your installed card. Next, to set up your xorg.conf file, run "sudo rm /etc/X11/xorg.conf" and "sudo aticonfig --initial --adapter=all".
After rebooting, if the computer does not boot into the X11 desktop, ssh into the computer and verify that /etc/modprobe.d/fglrx-core.conf was created when the fglrx driver was installed. This keeps Ubuntu from loading the open-source radeon drivers, which will conflict with the proprietary fglrx drivers. For additional debugging, look at the /var/log/Xorg.0.log file.
Continue with installing the rest of your cards one at a time. Re-initialize your xorg.conf each time, by executing "sudo rm /etc/X11/xorg.conf" and "sudo aticonfig --initial --adapter=all". Reboot one more time, and then exeucte, "aticonfig --odgc --adapter=all". This will display all the cards and their core/memory clocks. If you are connecting remotely via ssh, you need to run, "export DISPLAY=:0" or you will get the "X needs to be running..." error. You can use aticonfig to change the clock speeds on your card. For example, "aticonfig --od-enable --adapter=2 --odsc 820,1500" will set card #2 to 820Mhz core and 1500Mhz memory (a good speed for most R9 380 cards). To simplify setting clock speeds on different cards, I created a script which reads a list of card types and clock rates from a clocks.txt file.
Once your cards are installed and configured, you can use my ethminer build:
tar xzf ethminer-1.1.9nr-OCL.tgz
Once you've confirmed that ethminer is working, you can edit the mine.sh script to use your own mining pool account. If you want your rig to start mining automatically on boot-up, edit your .bashrc and add "cd ethminer-nr" and "./mine.sh" to the end of the file.
Sunday, July 31, 2016
In my last post about mining ethereum, I explained why I preferred Genoil's fork of the Ethereum Foundation's ethminer. After that post, I started having stability problems with one of the newer releases of Genoil's miner. I suspected the problem was likely deadlocks with mutexes that had been added to the code. They had been added to reduce the chance of the miner submitting stale or invalid shares, but in this case the solution was worse than the problem, since there is no harm in submitting a small number of invalid shares to a pool. After taking some time to review the code and discuss my ideas with the author, I decided to make some improvements. The result is ethminer-nr.
A description of some of the changes can be found on the issues tracker for Genoil's miner, since I expect most of my changes to be merged upstream. The first thing I did was remove the mutexes. This does open the possibility of a rare race condition that could cause an invalid share submit when one thread processes a share from a GPU while another thread processes a new job from the pool. On Linux the threads can be serialized using the taskset command to pin the process to a single CPU. On a multi-CPU system, use "taskset 1 ./ethminer ..." to pin the process to the first CPU.
As described in the issues tracker, I added per-GPU reporting of hash rate. I also reduced the stats output to accepted (A) and rejected (R), including stales, since I have never seen a pool submit fail, and only some pools will report a rejected share. The more compact output helps the stats still fit on a single line, even with hashrate reporting from multiple GPUs:
m 13:28:46|ethminer 15099 24326 15099 =54525Khs A807+6:R0+0
To help detect when a pool connection has failed, instead of trying to manage timeouts in the code, I decided to rely on the TCP stack. The first thing I did was enable TCP keepalives on the stratum connection to the pool. If the pool server is alive but just didn't have any new jobs for a while, the socket connection will remain open. If the network connection to the pool fails, there will be no keepalive response and the socket will be closed. Since the default timeouts are rather long, I reduced them to make network failure detection faster:
sudo sysctl -w net.ipv4.tcp_keepalive_time=30
sudo sysctl -w net.ipv4.tcp_keepalive_intvl=5
sudo sysctl -w net.ipv4.tcp_keepalive_intvl=3
I wasn't certain if packets sent to the server will reset the keepalive timer, even if there is no response (even an ACK) from the server. Therefore I also reduced the default TCP retransmission count to 5, so the pool connection will close after a packet is sent (i.e. share submit) 5 times without an acknowledgement.
sudo sysctl -w net.ipv4.tcp_retries2=5
I was also able to make a stand-alone linux binary. Until now the Linux builds had made extensive use of shared libraries, so the binary could not be used without first installing several shared library dependencies like boost and json. I had to do some of the build manually, so to make your own static linked binary you'll have to wait a few days for some updates to the cmake build scripts. If you want to try it now anyway, you can add "-DETH_STATIC=1" to the cmake command line.
As for future improvements, since I've started learning OpenCL, I'm hoping to optimize the ethminer OpenCL kernel to improve hashing performance. Look for something in late August or early September.