I guess an entire channel trying to explain things to you didn't do the trick, then?

1. (For maybe the 76th time already, too) Hiveon Pool has 0% fees. The 3% you keep (so fondly) mentioning is completely optional. And it is set in place for PAID CUSTOMERS that rather opt for automatic payments instead of constantly having to top up their Hive OS account funds. The optional 3% instead of 3$ for each worker, can be enabled/disabled in your farm's Billing tab. Goes without saying that it only applies once enabled (so it won't account for any outstanding negative balances) and only for workers actually mining on Hiveon (so you can't pay for workers mining on other pools with it).

We have a TON of articles, Billing FAQs, Payment FAQs, etcetc. That are VERY clear on this. So perhaps it would be best you check and actually READ them before going into your baseless little rants again.
Pricing Page: https://hiveos.farm/pricing
Billing FAQ: https://forum.hiveos.farm/t/billing/
Hive OS Billing updates: https://[Suspicious link removed]/37u1745
Payment FAQ: https://[Suspicious link removed]/3AkAJWT

2. You're obviously a little dated with your information as we've been distributing 100% MEV rewards since the London Fork.

3. To summarize;

* Hiveon has 0% pool fees (unless you manually opt for the 3% as explained above).
* Hiveon covers transaction costs.
* Hiveon distributes 100% MEV rewards to miners(was 90% before the London Fork).

And I wholeheartedly suggest you inform yourself on how pools actually work. If you're going to attempt to do comparisons, you should at least try to do them evenly split (preferably from the same worker), at the exact same time, for an extensive amount of time (we're not talking mere days here).

On average, there's little to no difference in profits when it comes to the largest pools. You're talking about constant and derivative variables which shift any and each way consistently. Today pool X has the upper hand, tomorrow pool Y, the day after, pool Z overall the differences are negligible long-term.

So my general advice is to stick to where you are whether it's hiveon or any other pool. These constant debates on what and where the profitability is at its highest is a load of biased bullshit half the time, and the other half based on ridiculous measurements and stats that are as accurate as pulling them from thin air would be.

If there was one single pool that had the highest profitability out there - consistently too, everyone would be (obviously) mining on it.

Uhm, you do realize the latest stable image (available since July 16th) comes with Nvidia drivers: v460.84, right?
Widely tested drivers are opt for for good reason and it has nothing to do with "pure laziness".

my band? my comments? I'm only pointing out the obvious fact (check the coding) that your file wasn't used. And as you very well know it was immediately deleted after you posted it. We took your suggestion and applied it in our own way as we do with literally hundreds of suggestions from our users on a daily basis. So I'm not sure what or why you're implying here. Should we demand credit for using our original motd and modifying it? No. You want to modify it as you see fit, do so. We don't expect a cookie for it. So - again, how about you get off your high horse, tone down the self-entitlement here and in our chats, and just give people respect in order to receive it - as any normal human being should?

I wasn't aware you're the only one being on the planet that is able to do any coding. What you sent wasn't used and was immediately deleted from the channel. So how about you get off your high horse and check the coding first before claiming anything.

Looks like its affecting GPU on PCI Bus 01:00

https://i.imgur.com/mD3aNTT.png

This generally points to bad risers/cables or bad BIOS, but since you claim it works on Windows (even if Windows doesn't always pick up on same errors), I'd start by ensuring your motherboard BIOS is set accordingly fist.

Reset BIOS to factory defaults and ensure only the following changes are made;

Set PCIe Link Speed to GEN2
Disable Internal Graphics
Enable Above 4G Decoding
CSM Support: Disabled for new images / Enabled for older images
Set storage device with hive partition as first in boot priority
(Optional) Restore AC Power Loss (Power On)

You can use amdmemtweak tool which is embedded in hiveos to set the timings you want. Do note that if your cards are modded, there's really little to no point as this wouldn't do a whole lot for them.

Both c29/c31 are designed for 8GB GPUs. There are miners that support c29 on 4gb cards, but this is a classic space/time trade off. Meaning, hashrate just doesn't make it worthwhile to begin with.
I suggest you do a little more research online and perhaps find an algo/coin better suited for your cards.

Please send us an email (bee@hiveos.farm) with your worker link (URL to your rig's dashboard) and we'll take a look for you.

No adequate Linux drivers yet.

How are you mining XZC with Gminer when it doesn't support MTP?
Your error suggests issues with connectivity to the pool, which makes sense when looking at your second screenshot. You need to specify stratum+tcp:// in front of the pool address.
I also suggest using either T-Rex miner or Cryptodredge, both of which are far better miners than CCMiner and its forks.

What was the latest version you used that was still working for these GPUs? I suggest you stick to that one for the time being.
We will review any changes made that could have affected them, but do note that these GPUs are not supported to begin with (and never were).
The fact they work, to any extent, is to be taken as a given, not as an absolute.

https://hiveos.farm/features <-- To see a list of supported hardware (bottom of the page)

Which "old version" are you referring to, specifically?
Did you flash the new image? Or just ran the update via the dashboard?

Which BIOS version? Cause we've tested this on 60+ boards and all show the same issue. The issue was seen on even lower (builds 0.5-xx)

We don't recommend the ASUS B250 ME because as it stands, there are currently known issues with high LA caused by these boards on BIOS vers. 120x and up.
We're still waiting for official word from ASUS on the matter but this seems to affect AMD beyond a certain number of cards on these boards.
Any version prior to 120x seem to be working fine.

As for your specific issue, check what the LA is at because it sounds to me like the rig is tilting. If that's the case, you're most likely affected by the same issue.

A workaround is to power-cycle the rig(instead of shutting down or restarting, note that this is to be done EVERY time) or connect fewer cards (some board take up to 5, some take up to 6).

Also, ensure that your BIOS settings are set correctly:

Advanced\PCH Configuration\PCI Express Configuration -> PCIe Speed -> Gen 2
Advanced\System Agent (SA) Configuration\PEG Port Configuration -> PCIEX16_1 Link Speed -> Gen 2

This is a known issue with these boards. We're currently awaiting feedback from ASUS on the matter, but, we think it may be related to BIOS version. Anything above vers. 120x has this issue.
Boards with 1001 up to 1010 don't seem to be affected.

Thing is, you won't be able to rollback since they've ME locked it.

Please check your BIOS version and report back so I can send as much data to their guys testing this.

Thanks!

I personally think Nicehash should be avoided like the plague. A brief look at their dodgy history alone and the number of users and issues they still ignore should already tell you all you need to know about them. People tend to use Nicehash either due to ignorance(not negatively put but in terms of how and what to mine) or due to convenience with the auto conversion to BTC.
Mining the actual coin yourself, although arguably more time consuming, grants you the power to trade it on YOUR terms. Which, if done correctly, will always be more profitable.

Now, in terms of its mining service and servers, although they constantly claim there are no issues, this is quite easily proven by pointing your miners to (literally) any other pool. A certain magic happens where you no longer experience the same amount of rejects, invalids or connection dropouts.

It could be that this particular card just needs more juice to get things done.
I've come across cards that no matter what you throw at them, they won't function below/above a certain number, while others can/will.

That's the silicon lottery. You can have the exact same cards, from the same brand, same memory manufacturer, and they can still be vastly different in terms of performance.

That being said, you could try checking the card's BIOS to make sure there are no weird settings set. You could try a different riser. Easy to do is just grab this card and swap places with GPU0, for instance. see if the problem moves with card or stays with the riser. Basically, the general troubleshooting.

I honestly don't get why you'd want to go through all these loops and hoops, for 0 advantage and twice the hassle.

If you like Awesome Miner, just install windows and run their app. I don't see the point, nor benefit, in running hive on your rigs without using any of the features that make it such a great OS and platform to begin with.

The entire point of hive is to deploy, monitor and manage your rigs from a single web-based dashboard.

You basically want to ditch that to use a, IMHO inferior, monitoring tool that doesn't support half of hive's features or miners.

Yes, in most cases just running the is enough, but the above steps ensure chances of things going wrong are kept to an absolute minimum. Especially in cases where individuals come from older builds.

Cuda 9.2 and up are now the default on most miners.
You'll need at least 396.54, which is recommended on 0.6-01 (and above).

Start a Hive Shell session
Run the following commands;


Note that logs should be turned back off after this procedure if you're running hive off a USB stick

Once you reboot start a Hive Shell session again.
Run the following;


The installation could take up to around 10 minutes on SSD (depending on your internet connection speed) and takes longer on USB stick.
Reboot the machine again once done.

On some systems, OC and FAN settings may fail after a driver upgrade. This can easily be fixed.

Start a Hive Shell session
Run the following;


All should be working again.

Let me know how it goes!