|
Unrelated issue. I've got 3 rigs with 1060 3GB cards mining BEAM using GMiner. Since the Equihash 150.5 algo requires just shy of 3GB of VRAM, I'm running those rigs on HIVEOS for now.
I'm monitoring then from AM as External miners by looking at port 42010. This works fine except the earnings are not showing up. When I right click and "Define coin for pool", I select BEAM. However, nothing is showing and if I go back to "Define coin for poo"l again, it has reverted back to BTC.
Also, on these External miners, when I click on the Pools tab, it shows the Grin29 pool my managed miners are connected to, not the BEAM pool these miners are actually mining on. On my Managed miners, I can of course select the pool each rig is mining on, but for External rigs, this is not possible. I do see the GPUs and hash rates as AM is picking that up from the GMiner API.
I don't know if something changes, but I seem to recall AM being able to show earnings for External miners in the past.
|
|
|
|
|
Perfect. That did the trick. Thanks!
|
|
|
|
It is pretty easy to install. Just go here and download the latest image: https://hiveos.farm/installThen download and use HDD Raw Copy Tool to burn the image to USB or SSD from a windows computer. Then you boot the rig from that image and it will ask you for a RidID and password, which you will be assigned when you create you first worker/rig after establishing an account by going here: https://the.hiveos.farm/register/Once that is done, you need to create a wallet, which is the BEAM address you want to mine to. Next you create a flightsheet, where you specify the coin (BEAN), the wallet (the BEAM address you just created above), and the miner (GMiner). When setting up the miner, you need to pick 150_5 for the algorithm, %WAL%.%WORKER_NAME% for the template, and there pool url, port and password, and you're done. |
|
|
|
|
I would recommend HIVE as opposed to Win 7. I had a 7x EVGA 1060 3GB in win 7 and could not get it stable. Switched to HIVE and it has been rock solid with core +100, mem +500 and power at 70%.
I dusted off 2 other 1060 3GB based rigs and brought them online as well on BEAM, also on HIVE. These 2 rigs both have 8 GPUs in them. All 3 rigs are very stable.
|
|
|
|
I assume you only have one single Host for this Linux miner defined in the Options dialog, Managed Hosts section. This host must have the "Linux" checkbox active and there shouldn't be any other hosts in the list connecting to the same computer. Can you verify this?
Yes, I only have a single host defined for this specific miner. I did have a windows hosts defined previously that I deleted and replaced with the nvOC based one. But this was also the case for the first rig that I converted from Windows to nvOC. One note on this is that I had to restart AM before it would "pick up" the first rig that I switched from windows to nvOC. And yes, I do have the "Linux" checkbox checked. Can you also review the Awesome Miner application log file for any error message about this connection problem?
How do I access this log? Also, will setting GPU clocks, power levels and fan control be a future option for the Linux remote agent? btw, I really like the recently added native control of these with the windows version. So much simpler than having to use the Afterburner remote agent. One thing I found is that I had to re-create my GPU Clocking Profiles as the old ones did not include the temp target values. |
|
|
|
|
What is the default API port for gminer?
I'm trying to monitor my rigs from Awesome Miner and if I try to add an extra config argument of "--api 14001", when I restart the miner, I get a log error message of "api cannot be added twice".
So does HIVE add an API port "behind the scene" or something like that?
|
|
|
|
question:
Mining Beam - gminer v1.31 supports 3Gb nvidia cards (such as 1060) on windows, or not?
It does, but only under Windows 7. |
|
|
|
It's already built-in in AM, it adds automatically -> --api 4028
Just to be clear, my mining rig is running HIVEOS. I'm monitoring my rigs from AM running on the Windows machine. My config that launches gminer on a HIVE controlled rig looks as follows: === /hive/miners/gminer/1.31/gminer.conf =================================================
--algo 150_5 --server beam.usa.nicehash.com --port 3370 --user 3CvNvHBWkEQohrkMAnUaJznPFsq8LKpPha.miner009 --pass x
=== /hive/miners/gminer/1.31/gminer.conf =================================================
Note how --api 4028 is missing. If I go into the gminer config and add the extra parameter --api 4028, gminer fails to launch. When I look in the log, it tells me --api cannot be specified more than once. On the AM side of things, I have tried adding an external miner both with and without the port being specified. Either way, AM cannot see the rig. So it is almost as if HIVE adds an api port on its own, but I don't know what port it is. Other miners use standard ports, like Claymore is 3333 I think it was. Back when I was mining ETH, specifying that port when setting the external miner in AM worked like a charm. |
|
|
|
|
What is the syntax for the --api parameter?
None of these seem to work:
--api 43001
--api 0.0.0.0:43001
--api 192.168.1.25:43001
I'm trying to configure a remote monitor port so that I can monitor my HIVEOS rigs from Awesome Miner instead of from the HIVEOS cloud dashboard.
|
|
|
|
Is there a trick to get BEAM working on a 1060 3GB card? I'm running Windows 7 64-bit SP1. Here's what Awesome Miner diagnostics tells me: Initialize diagnostics (20)
Starting Diagnostics. Awesome Miner Remote Agent version: 6.1.12
OS: Microsoft Windows 7 Professional Service Pack 1 64-bit
nVidia driver version: 418.81
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: GMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: GMiner, IsProfitMiner: False)
====================================================================================================
C:\Users\peter\AppData\Roaming\AwesomeMinerService\gminer_1_31_minimal_windows64_1\miner.exe -a 150_5 -s beam.usa.nicehash.com -n 3370 -u 3CvNvHBWkEQohrkMAnUaJznPFsq8LKpPha.miner011 -p x --pers auto -w 0 --api 4028
====================================================================================================
Mining Engine Process started, PID: 3536
> No device found
====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration or crashing software
Diagnostics completed
I have 3 rigs with 23 1060 3G cards between them (almost all EVGA GTX 1060 SC 03G-P4-6162-KR). I'd love to bring them out of retirement and mine me some BEAM with them. My test setup is a Asus Z270-A mobo, Celeron 3930 CPU, 4GM RAM, 16384MB of Virtual Memory and just a single 1060 to start. EDIT: I was testing with a monitor connected to the Internal graphics and that is what caused the issue. Once I switched to PEG, it started working. I guess unlike Windows 10, Windows 7 does not allow mining with the internal GPU enabled in BIOS and acting as the primary display... |
|
|
|
I've been playing around with the Linux remote agent. My first rig came up and started working right away, but I'm having issues with my 2nd rig. When I look at the remote agent log, I see a bunch of these: Feb 08 15:25:37 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: IntelliBreeze.IntelliCom.Exceptions.ProtocolException: Too large Header/Content length
Feb 08 15:25:37 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:25:37 PM.696 [010] [S]Setting callback channel
Feb 08 15:25:37 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:25:37 PM.699 [010] [S]IntelliServer::AddChannel - Client: 10.0.1.212:2524, Channel: 32 connected
Feb 08 15:25:37 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:25:37 PM.700 [010] [E]ChannelHandler::ReadAsync - Channel: 32 failed
After a while it changes to: Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.739 [064] [E]ChannelHandler::CommandAsync - Channel: 669, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.739 [064] [E]ChannelHandler::CommandAsync - Channel: 481, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.739 [064] [E]ChannelHandler::CommandAsync - Channel: 357, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.739 [064] [E]ChannelHandler::CommandAsync - Channel: 292, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.739 [028] [E]ChannelHandler::CommandAsync - Channel: 356, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.744 [028] [E]ChannelHandler::CommandAsync - Channel: 223, CommunicationError
Feb 08 15:55:41 miner008 AwesomeMiner.RemoteAgent.Linux[4337]: 2/8/19 3:55:41 PM.744 [062] [E]ChannelHandler::CommandAsync - Channel: 224, CommunicationError
So in AM, the miner shows up as "Service offline", but when I go to Managed Hosts and click "Test connection", I get the following message: Successfully connected to Awesome Miner Remote Agent/Service 6.1.11 I uninstalled and reinstalled the remote agent, but I still have the issue. I'm running nvOC 19.30 (Ubuntu 18.04), btw. I like this distro since it is all setup for mining out of the box and has a bash file where I set the GPU clocks and power. If there's another distro that provides basics I need, I'm not opposed to give that a go. What Linux distro do you guys use with AM? EDIT: Did a clean install of Ubuntu 18.04 LTS Server and after getting it all setup with the latest drivers, etc, I installed the remote agent. Getting the exact same errors as on the nvOC distro. |
|
|
|
This is a good site to get an idea about what your solar production is: https://pvwatts.nrel.gov/pvwatts.phpYou enter your address and the size in watts of your system, and it will calculate for your lat/long and weather conditions. You can play around with different tilt and azimuth value to see how it impacts overall production. I live in central Virginia and here are my numbers for my 34,720 Watt system: (80 x 260W panels + 48x 290W panels) Month Solar Radiation AC Energy Value
( kWh / m2 / day ) ( kWh ) ( $ )
January 3.81 3,257,432 395,648
February 4.75 3,652,182 443,594
March 5.10 4,236,092 514,516
April 5.66 4,372,219 531,050
May 5.77 4,518,811 548,855
June 5.90 4,356,810 529,178
July 5.95 4,495,470 546,020
August 5.84 4,374,852 531,370
September 5.38 3,955,102 480,387
October 4.70 3,764,586 457,247
November 4.20 3,330,549 404,528
December 3.61 3,089,051 375,196
Annual 5.06 47,403,156 5,757,589
So for the year, I average 130 kWh per day for my location and my climate. My rate is $0.12146 year around 24/7, with taxes and fees. Since I have a net metering arrangement with the power company, anytime I produce more than I consume, it goes back into the grid and I'm credited 100% and can then pull out out at night when I'm not producing anything. If I consistently produce more than I consume, I start building up a "bank" of kWh with the poco. So in my case, it really doesn't matter when I run my miners. But for off-grid applications and those without net metering agreements, the method h311m4n came up with is very slick! |
|
|
|
Is it on a grid-tie inverter? Solar powered rig would be ideal to have setup but would need to have mains to follow for dips and night use. I need to look at this as its best option long term.
Yep, grid tied with net metering. With net metering, any excess that I produce goes back into the grid and I'm credited the kWh 1:1. So in essence, the power company is buying back the kWh I produce at the exact same rate that I pay them. In my area, the cost per kWh is constant 24 hours a day year around. Cool. What country are you in? I am in the UK and they call it the feed in tariff (FIT) although I think they are scrapping it very soon so no option to sell back to them (boo hiss). I'm in the US (Virginia specifically). They no longer do net metering because the state no longer mandates it. Fortunately I'm grandfathered in according to the POCO solar guy that I worked with when getting it all up and running initially. |
|
|
|
With net metering, any excess that I produce goes back into the grid and I'm credited the kWh 1:1. So in essence, the power company is buying back the kWh I produce at the exact same rate that I pay them.
As long as you don't produce MORE power than you use over the course of a billing period. That is actually ok too. What happens in that case, is that I start building up a "bank" of kWh with the power company. I had built up a bank of about 7,000 kWh before I started getting into mining. That bank was wiped out within 2 billing periods, lol. |
|
|
|
Is it on a grid-tie inverter? Solar powered rig would be ideal to have setup but would need to have mains to follow for dips and night use. I need to look at this as its best option long term.
Yep, grid tied with net metering. With net metering, any excess that I produce goes back into the grid and I'm credited the kWh 1:1. So in essence, the power company is buying back the kWh I produce at the exact same rate that I pay them. In my area, the cost per kWh is constant 24 hours a day year around. |
|
|
|
|
Yeah, I'm the sucker that bought most of those cards, lol.
Very fair deal at the time and they all made back a decent amount before things went South. I'm sitting on 150k of RVN and nearly 100 ZEN (also have misc other holdings including BTC). Of course neither is worth much atm, but I'm still optimistic that the tides will turn at some point in the future.
If the sun ever comes back out and my 35kw Solar array starts producing again, I'll start turning my rigs back on, at least during the daytime, when my solar production far exceeds my consumption.
|
|
|
|
|
I too am heating my house with some of my GPU rigs (the majority have been shut down for a while now), but it is getting to the point where I'm thinking about switching over to heating with my efficient (20 SEER) heat pump instead and shutting down these remaining rigs as well...
Solar production has been very low lately as well since it has been cloudy or raining 90% of the time over the last several months. Plus the sun is low on the horizon anyway this time of year.
I guess the thing to do is sit tight, be patient, and ride this out over the next 6-18 months or however long it will take.
Speaking of waiting this out, does difficulty typically remain relatively constant at times like this? I guess the answer depends on how much hash power drops out I suppose.
|
|
|
|
Thanks for the update. So when you use the GPU ID mapping and set GPU 3 to have lower clock speed, this doesn't take effect? When using MSI Afterburner UI directly, it works fine?
It's possible to verify the clocking operations that Awesome Miner send to MSI Afterburner Remote Server. Via the Awesome Miner Remote Agent log file (toolbar: Tools -> Log File -> Remote Agent) you can search for "Executing GPU clocking command" and see what numbers Awesome Miner is using. This could be good to get an understanding of where it goes wrong.
Clocking for Remote Agent on Linux will be supported in the future. The idea is to also add support for overdriventool and nvidiainspector on Windows.
Correct, it doesn't appear to work using GPU ID either. I tried disabling MSI Afterburner Remote Server for this particular rig by renaming the folder containing the executable, but that caused the rig to become unresponsive after a few minutes of mining. What's the best way to disable Remote Server Agent on a specific miner for testing purposes? I take a look at the log fine. Great news about clocking for Linux agent and nvidiainspector support! |
|
|
|
If you use the GPU name Awesome Miner must be able to get the names from MSI Afterburner, but in your case you only get "GPU 0" and so on without the name. Can you please try to apply the updated fix for MSI Afterburner Remote Server, listed at the bottom of this page? https://support.awesomeminer.com/support/solutions/articles/35000086015-gpu-overclockingI know a few other users that were able to resolve the GPU name problem by applying the updated DLL-file. Thanks Patrik. That took care of the issue with the GPU names not showing up properly. However, Afterburner Remote Server reports all 7 cards as being identical as follows: GPU 0: GeForce GTX 1080Ti GPU 1: GeForce GTX 1080Ti GPU 2: GeForce GTX 1080Ti GPU 3: GeForce GTX 1080Ti GPU 4: GeForce GTX 1080Ti GPU 5: GeForce GTX 1080Ti GPU 6: GeForce GTX 1080Ti And while that is technically true, GPU 3 is very different in that is an EVGA FTW3 Hybrid as opposed to just an EVGA SC2, so it has different PL and Core boost requirements. I use wish Afterburner would allow you to set specific PL and Core clocks like how it is typically done under Linux. Speaking of which, will GPU clock profiles be supported in the Linux Remote Agent at some point? |
|
|
|
I'm running all my rigs as Managed Profit Miners. Most of my rigs contain identical GPUs, but I do have a few that are mixed, and I'm having a hard time getting different clock profiles to work consistently with them I have my Profit Profiles and Groups already setup, and they are as follows: Profit Profiles GTX 1050Ti GTX 1060 3GB GTX 1070 GTX 1070Ti GTX 1080 GTX 1080Ti Profit Profile Groups (these are my mixed rigs other than one that is a mix of air and water 1080Tis discussed below) 1x 1050Ti 1x 1070Ti 2x 1070 x1 1080Ti 1x 1070 1x 1080 For Profit Profiles, I figured it would not be necessary to distinguish between Air and Water Cooled GPUs. Agreed? For GPU Clocking Profiles on the other hand, I have created different profiles for Air vs. Water cooled GPUs since they require different settings. So I have the following: GTX 1050Ti ETH GTX 1050Ti Standard GTX 1060 3GB ETH GTX 1060 3GB Standard GTX 1070 ETH GTX 1070 Standard GTX 1070 Hybrid ETH GTX 1070 Hybrid Standard GTX 1070Ti ETH GTX 1070Ti Standard GXT 1080 Hybrid ETH GTX 1080 Hybrid Standard GTX 1080Ti ETH GTX 1080Ti Standard GTX 1080Ti Hybrid ETH GTX 1080Ti Hybrid Standard So I have this one rig with a mix of 1080Ti's that are air cooled and one that is a hybrid. The GPUs are as follows according to AM: GPU0 EVGA 1080Ti SC2 GPU1 EVGA 1080Ti SC2 GPU2 EVGA 1080Ti SC2 GPU3 EVGA 1080Ti FTW3 Hybrid GPU4 EVGA 1080Ti SC2 GPU5 EVGA 1080Ti SC2 GPU6 EVGA 1080Ti SC2 I created a Clocking profile group with 6x 1080Ti Standard profiles and 1x 1080Ti Hybrid Standard. I arranged the GPUs in the profile to match what is shown in the table above by simply entering 0 - 6 for each GPU. But apparently I'm doing something wrong since all 7 GPUs share the same clock and power settings and after a short while the miner software is restarted by AM since the FTW3 hybrid keeps falling over because the clocks are too high given the much factory OC of the FTW3 card compared to the SC2's. When I look at this mining rig in the GPU tab, I can clearly see that the clock on the FTW3 is about 80 MHz higher than the other 6 and it also uses about 40 more Watts. When I click GPU settings/settings via Awesome Miner and MSI Afterburner... I can confirm that all 7 GPUs share the exact same power and clock settings, which is why the FTW3 runs higher than the rest. When I click the Profile drop down, the Clocking Profile Group I created is not in the list to choose from. So how do I associate a Clocking profile group to a particular miner? Do I have to create a Profit Profile specifically to this mining rig instead of using the regular GXT 1080Ti Profit Profile that I use for all my 1080Ti Air cooled only rigs? That appears to be the only way I can then select this "custom" 1080Ti Profit Profile, from within which I can then select the Clocking Profile Group I created for individual algos. EDIT: So I went ahead and created a Profit Profile called GTX 1080Ti Mix and within it, I selected my Clocking profile group with 6x 1080Ti and 1x 1080Ti hybrid. I then went to this miner and changed the miner properties to point to the new Profit profile I created. I restarted the miner, but it is still showing all 7 GPUs at 80% and +120 Core. EDIT2: I changed to match on GPU Name instead of ID. Still didn't work. Here are some pic of my config: https://ibb.co/jo0hYAhttps://ibb.co/mLh1RVhttps://ibb.co/iUQufqhttps://ibb.co/nJyrRVhttps://ibb.co/igBNYANote that in the last screenshot above, where I'm showing the "Settings via Awesome Miner and MSI Afterburner", all that is showing GPU 0:, GPU 1:, etc. The actual name you can see in the window behind, do not carry through to the Afterburner window. Could that be the issue? If so, how do I get the GPU names I assigned to show up there? Thanks! |
|
|
|
|
Show Posts
