Hello there,
Mining with Linux.
I want to thank you for making the best miner for ETH mining with 4GB gpus at this moment.
None of the other miners can mine epoch 382 with full hashrate, only lolminer can do it without a sweat.
So, what I did was, instead od 4072 or 4076 for mem allocating argument, I put 4080, since it is the size of current DAG and my 4GB gpu says it have 4090 capacity and 4071 of that free.
Next thing I did was to put keepfree 5 argument, I don’t know if that was a must.
So my 4GB RX470s all work in “memory saving mode” and I am getting full hashrate speed.
There it is.
In short, I am using 4080 for memory allocation and keepfree 5.
Your miner is the only one doing that.
Thank you for letting us squeeze the last atom of full hashrate from our 4GB AMD gpus!
Keep up the good work man

Compute mode on?

Please,
Can you implement an option for minimal rig speed and restart if that speed is lower?
I am using lolminer through SMOS and several times now I found it to be working with 0 H/s.
Nicehash is mixing ETH and ETC and due to that miner just won’t keep working normally.
Sometimes it’s one graphic cards, sometimes it’s few, sometimes it’s all cards affected.
They have 0 H/s but miner keeps working and both SMOS and Nicehash showing rigs online but with 0 H/s.
I appreciate all you did with the miner, for me it’s the best option homestly. I wan’t to keep using it.
Please, put minimal speed option in miner, so it could restart if speed is lower than minimal.
Thank you in advance

What about that OhMyGodETHPill for 1080 and 1080Ti?
It came with Nicehash software like forever...
Did you try it for 1070s?

Same here with R9 380X
It says Lolminer supports R9 380, but I couldn’t do it.
Any solution?

Hi there,
Need a little help.
I read lolminer would support R9 380s, so I tried some of my R9 380X but without success.
Miner would load, recognize the cards but after that it would say cards are not supportet, waited those 10s and shut down.
I was trying them for mining BEAM.
On ETH it was saying some other error, it doesn’t matter, because I can use R9 380X for ETH
with other miners like PhoenixMiner but since they are just waste of electricity I won’t.

So...please, can you help me,

Does lolminer support R9 380X 4GB at all and if it does, for what algo?
I really would like to use them for BEAM if they could be used at all.

Thank you in advance

With Claymore, since you have Polaris cards, not only -rxboost 30, but -strap 1 or -strap 2 also. (-strap will boost way much more than -rxboost) ...think these are Windows ONLY...maybe I'm wrong
I still use Claymore for injecting straps into my RX470s while using Phoenix for actual mining.
Just start Claymore with -rxboost 30 and -strap 2, disable all cards, minimize it and then run Phoenix.
*found that while I was doing some other work with Claymore in background minimized and then I saw other people do it also with Phoenix
Sadly for me, Claymore won't work with latest drivers, so now I use it on just one rig with 18.12.1.1 driver.
With 20.8.1 Claymore just crashes for me.
It only works for Polaris cards, I think. For other cards AmdMemTweak is doing same job, but one have to know to use it...
I still haven't found right parameters for my RX470s with Hynix memory, don't have enough knowledge and time...some day, maybe, some other cards... 

For 4GB cards -rvram -1 should solve the problem, they wrote about it in text you just quoted...
Try update driver to latest from given list (20.7.1 or 20.8.1)...or higher, maybe.
One of my two 6 x RX470 4B rigs is working great just with 18.2.1.1, the other with the exact same cards wouldn't hash properly until I tried all and finally updated driver all to 20.7.1  (20.8.1).
I avoid Nicehash with 4GB cards because they mix ETH and ETC...making mess with that switching and giving me way less profit.
Lolminer have that "zombie mode" which still have to be developed, gonna try it later because PM works just fine for me.
Update driver to 20.7.1 or 20.8.1 or higher, it should solve your problem with RX480 4GB...DAG 373 is last my RX470s can handle under Win10.

Try T-rex miner?
Maybe it's the GPU architecture

I had almost the same problem (my last card wasn't mining full hash instead of your first) and I was crying like a baby here 
ONLY solution I found was to update driver to 20.7.1 or 20.8.1
Problem with those drivers is Claymore won't work if you use Claymore for injecting straps...well it's not a problem, it's just something I can't use any more to get max hash rate from my 4 GB cards.
Also, another problem even when I solved this issue was, Team Red Miner not recognizing compute mode turned ON and patching registry...
After that, I was back to "last card not working" issue.
So, update to last driver, no more Claymore for injecting straps and no TRM because it just messes up everything. (for me)
I tried all drivers from list Phoenix gave (18.12.1.1 to 20.8.1), whole week without normal sleep, trying everything 
If you know how to use AMD Mem Tweak you can inject straps from there...I was getting whole 10Mh/s from Claymore on my 6x rx470s rig, so it's not a small gain.
Also, try not to mine on Nicehash with 4GB GPUs because they very often switch from ETH to ETC...switching from ETH to ETC and back to ETH makes you loose a tons of time for Phoenix to get back to normal hashrate - really annoying 
Phoenix sometimes can skip whole ETC DAG Nicehash mess, with "not enough memory for DAG" and restart miner back to ETH...but that's if you're lucky and your Phoenix goes on "lucky restart miner" streak 
Everything I wrote is something I experienced, not saying it will happen to you.
At the same time, second rig with exact same 6x rx470s rig from the same batch, same custom vbios, is working like a charm on 18.12.1.1 driver, so I guess my Gigabyte H110 mobo is the source of all my problems - only thing I couldn't check because it's a long drive, so I suspect it
Hope you'll get all your cards back to full work mode only with driver update 

I have 6 x rx 470 gb custom vbios rig, gigabyte h110 mobo, win10, msi afterburner...etc
Last card in the rig just won’t go over 2.9kH/s whatever I try.
Tried with 4 cards, 5 cards, always the same. Last card in that rig drops down with hash.
No more ideas   
I tried TRM, same issue...
Here is what is happening:
I clean install (DDU) new driver (20.4.2 or whatever), then I patch with new patcher, start miner as admin to switch on compute mode, and while it’s running like that without compute mode all 6 cards work normally but with less hash rate, which is expectable.
AS SOON as I turn compute mode on (with and without restarting the rig), that last card in rig goes down to 2.9kH/s with the rest cards working full 31.5 MH/s.
Whenever I clean DDU reinstall driver and turn compute mode on, that last card drops down with hash.
So every time I turn compute mode on, the last card just won’t go over 2.9kH/s avg.
I tried with and without msi afterburner, all kind of commands (clkernel, clf, altinit...)

At the same time, the other rig with the exactly same 6x rx 470 gb cards, same custom vbios, different mobo/cpu, is working great with 18.12.1.1 driver.
Did anyone have this problem with last card not working and solved it? Can it be that Gigabyte mobo is the problem?
Please help, anyone, throw in few fresh or not so fresh ideas, I didn’t have proper sleep last three days ...
Thank you

I have a problem with last card not working over 3.5kH/s.
Upgraded driver from 18.12.1.1 to 20.4.2, last card still not working.
I was trying all kind of commands in test bat file, suddenly out of nowhere, in middle of
typing next command combo, all 6 cards started working great.
I was so exausted and happy, just deleted that test bat file and left it like that.
Thought “prolem solved”, but after 27ish hours last card dropped again to just 3.5kH/s at max.
Last 20 hours I was trying to get it back but no success.
The other rig I have same identical cards, same custom vbios, still working great on 18.12.1.1 driver.
Left it to run on 5 cards full and 6th on 2.9kH/s average...
Need ssome rest and some sleep.
Any idea, command line example, anything...would help.
Thank you

I have the same problem on one of my 6 card rigs.
Followed instructions from “4GB cards txt” and was trying variations in command values.
Suddenly the last card started working, I was so happy and I did the stupidest possible thing - deleted that
test bat file thinking...I really don’t know was I thinking.
Rig worked whole 27 hours, then it just switched back to last card not getting over 1 kH/s.
Last 20 hours I am trying to get it back to work but looks like I can’t get the same commands combo.
I’m out of ideas, left it to run like that...last card is getting up to 3.5kH rest are 31.5 MH/s   
Will try again tho, after I get some decent sleep 
If anyone have any ideas, all are welcome.
Thx

I have 4GB cards also.
Try Team Red Miner.
No problem with 374, works like it’s 360
I was very pleased to see that 
Phoenix sometimes gets through, sometimes gives me same hashrates as yours at 374.
TRM keeps working like it’s nothing.
But I saw someone saying it can crash after some time.
I didn’t use it more than 2-3 hours, and during that time everything was OK.
Some mandatory commands in command line but was working just fine.
I’m back at Phoenix but it’s good to have an alternative.
Or just switch to Linux.

I have rx 470 and 18.12.1.1 is proven to be best for me.
Maybe your clocks or/and voltage are a bit high?
Check those also, might not be the driver but the OC...or even -gt if you set it too brutal

Not only -rxboost, but you need to run -strap 1 command also.
Claymore can find which cards are you using and apply straps for them, if they are in the straps table.
For Polaris cards it’s really big gain.
My 6 x RX470 4GB rig goes from 177MH/s to 184.5-185MH/s depending on MEM clock (2000-2050)

You can use AmdMemTweak to actually read timings and all the settings from Claymore while Claymore is running.
After that, you can apply those settings through AmdMemTweak with a batch file.
No need for Claymore after that.
AmdMemTweak tool is working good and it’s easier to read and apply straps which are already tested (through Claymore), than testing and making your own. But with AmdMemTweak you can try sqeezing even little more hashrate just with changing those reads you got from Claymore.
It’s a little boring to read and then apply settings for all the cards, so many typing, but once you do it, you won’t be needing Claymore.
For boosting Phoenix I used to run Claymore with -rxboost 1, -strap 1, -wd 0 and -mport 0 commands.
Didn’t pause miner with “mark” but I stopped the cards with typing 0,1...5 to disable all 6 cards.
After that just minimized Claymore and run Phoenix.
All the straps were applied to Phoenix and I was getting same hashrates.

Now I use AmdMemTweak, idk why, maybe because of my OCD and not wanting to run two miners at the same time...

Both, Claymore and AmdMemTweak boost solutions are working fine, you can try any of those.
Also driver can make a small change. 18.12.1.1 is proven to work best for my rigs.
Maybe you’ll get better results with different driver.

So here I am again
Does anyone else have problems with driver 18.12.1.1 going only to DAG 364?
I was using all recommendations for mining with 4GB cards, but it looks like 18.12.1.1 is not good driver.
Maybe it should be in “not so good driver” part...
It’s strange, I thought it was all good, but I saw just now they won’t go further.
Gonna try 19.12.2, maybe it will go to 370...

If anyone is using RX 470 4GB and know which driver will go to DAG 372-3
please let me know.
It would save a lot of time if 19.12.2 don’t work either...

Thank you

I am using 4GB cards in Win 10 and it’s working fine with all recommended options - drivers, etc.
DAG 372-373 is the limit, also just like you said.
Mining on NiceHash, it’s best and easiest for me.
I tried using -dagrestart 1 option because miner would crash after some time.
It was doing fine, restarting miner on every DAG change, but just for one day.
Now -dagrestart 1 is not doing anything but miner doesn’t crash any more.
Miner restarts only when it gets DAG high for not enough vram to buffer DAG.
Then it gets back to first available DAG with occasional DAG 0 “recalculations”.
What do you recommend? Should I set -eres 0 and -dagrestart 1?
Or just one of those, or just leave it like this untill DAG gets to 370?
When is a good time to set -eres 0 (and -dagrestart 1) if it should be used at all? I gues it should, but when?
After I exploit Win10, I will switch to SimpleMineOS, it’s really great.
And after no more 4GB cards for ETH, I will switch to something else.
I don’t pay for electricity, so anything I mine is pure profitability for me...3 years, I returned my investment multiple times.
Thank you in advance

In Win10 it won’t load DAG since it says not enough memory, cards hanging, restart miner etc.
Simple -wd 0 stops Claymore from restarting.
I tried that and it’s working.
Actually I needed -rxboost from Claymore for another job for two cards from rig.
That’s how I found out about it.

It’s really working in Win10 with any other miner or aplication where you need higher mem speeds

Just tried that edit -> mark thing and it’s also working..