This is a facepalm moment. This is your incorrect assumption:
And you came to this assumption because you use similar OC settings for the two algos.
You can use the same OCs because the algos are similar, but you misunderstood this to mean the algos are similar because you can use the same OCs.
Ofcourse, you think OCs that are different by a few 100 Mhz resulting in a few percentage points difference in hashrate consitutes a large difference, so it makes sense that you are nitpicking.
It is clear we cannot learn from each other, so let’s stop trying.
In hiveOS, with nvidia driver 465.31, I can get it to stable at 102MH. I can’t get it any higher. HDMI dummy plug does not help. I did not test riser set up. I installed it on a pcie-x16 ribbon.
sorry about posting in 3 replies. I am a new user and can only post 1 image/reply
Hi,
Is someone tryied to change BIOS form v2 to v1? I thing that prices goes down that is why I didn’t buy 3060 yer. Maybe someone tried this experiment. IMO it will be the simplest way to unblock the card.
Hello all, this is my first post. We jointly came to the result in Ergo mining, as per the attached image. The hashrate has not been limited for two days since finding this setting.
Note the relative clock setting. When we set main clock absolute value, the limiter (or some other mechanism) kicks in and reduces the hashrate to 60 odd MH quickly.
EDIT we use regular x1 riser and no dummy monitor plug, the HDMI & displayport sockets are empty.
Good hash but… 122w opposed to 88w for 107.5 MH/s that’s a lot of power for 34w for 7 MH/s not sure that’s worth it - depends on efficiency goals perhaps
True. However we shared because it is weird. Why relative clock value works different than absolute clock value. We were thinking that it may be connected with core boost. Miner would set fixed clock, gamer would prefer the boost. Just a thought.
Will post results when I improve but in all honesty leaving as ‘stock’ or moving it to another algo
LHR V2 will hopefully be cheaper on the market… the V1 LHR’s may demand a premium - time will tell - Searching for older 3060’s to avoid this personally
Guys, don’t get in the trip of LHR limiting the Autolykos algo. This is the wrong way to go. Even nvidia says that the new LHR mechanism affects only Ethash.
I have a 3060 non-LHR and ERGO mining has been quite an adventure in finding the optimal settings. I would too get the odd drop to 60-70MH/s, even with my v1 non-LHR 3060.
The Autolykos algo is quite different than what we are all used to (Ethash), so it needs some more experiments to find the best settings that make the card respond best and give the most MH/s.
Keep fiddling with it! I am sure you can reach 120MH/s (depending on silicon lottery ofc).
Also, don’t be afraid to go above 2700 mem. Autolykos allows higher mem clocks, you can do 2800 easily!
What happens on 2800Mhz clock is the miner starts and shows indeed 119.5MH, but then in 30sec. or so it drops to 62-75MH. You say it is present in the former version, so there seems to be no limiter for Autolykos 2. Other algos apart from Ethash are unaffected.
