I'm getting an error when starting lolminer ver1.01 on RX 470 8gb cards
Active: false (Unsupported device or driver version.)
+---------------------------------------------------------+
| _ _ __ __ _ _ ___ _ |
| | | ___ | | \/ (_)_ __ ___ _ __ / | / _ \/ | |
| | |/ _ \| | |\/| | | '_ \ / _ \ '__| | || | | | | |
| | | (_) | | | | | | | | | __/ | | || |_| | | |
| |_|\___/|_|_| |_|_|_| |_|\___|_| |_(_)___/|_| |
| |
| This software is for mining |
| Equihash 144/5, 192/7, 210/9 |
| BeamHash I (EquihashR 150/5/0) |
| BeamHash II (EquihashR 150/5/3) |
| BeamHash III |
| ZelHash (EquihashR 125/4/0) |
| CuckarooD 29 |
| CuckarooM 29 |
| Cuckaroo 30 CTX |
| Cuckatoo 31/32 |
| |
| |
| Made by Lolliedieb, June 2020 |
+---------------------------------------------------------+
Setup Miner...
Size:
Device 0:
Name: Radeon (TM) RX 470 Graphics
Address: 33:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8138 MByte free)
Active: false (Unsupported device or driver version.)
Device 1:
Name: Radeon (TM) RX 470 Graphics
Address: 37:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8138 MByte free)
Active: false (Unsupported device or driver version.)
Device 2:
Name: Radeon (TM) RX 470 Graphics
Address: 39:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8138 MByte free)
Active: false (Unsupported device or driver version.)
Device 3:
Name: Radeon (TM) RX 470 Graphics
Address: 40:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8138 MByte free)
Active: false (Unsupported device or driver version.)
Device 4:
Name: Radeon (TM) RX 470 Graphics
Address: 41:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8138 MByte free)
Active: false (Unsupported device or driver version.)
Connecting to pool...
Connected to beam.2miners.com:5353 (TLS enabled)
TLS Handshake success
Authorized worker: 2b7a39e73d27****************d15eeefc05.470
New job received: 231030 Difficulty 4096
Start Mining...
All devices deselected or failed compatiblity check. Closing lolMiner
Press any key to continue . . .
You need new driver. Not that oldest one... |
|
|
|
We're pleased to release Bminer 16.2.2. * Improve the performance of Ethereum mining on AMD GPUs. * Retire ZEC miner. * Improve stability of the Cuckatoo32 miner. * Support automatic transition to BeamHashIII. * Improve compatibility with Windows. Please see https://www.bminer.me/releases/ for more details. Happy mining. What about bfc? It didn't work. Error: "Indefined but requested solver: bfc" even if launch .bat file from miner archive without changes. And it's possible to mine eth on nicehash? If yes, how? I'm always recieve connection error. Tried ethash, ethstratum solvers. |
|
|
|
On eth nicehash always get error: Pool connection was close due to an error. Other miners works normal... P.S. Looks like problem is in drivers. AMD released new unofficial driver with support for the public preview for members of the Microsoft® Windows Insider Program that enables DirectX® 12 compatible GPU-acceleration within the Windows® Subsystem for Linux (WSL) for DirectML machine learning training workflows. There is the info: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-wsl-supportReinstalled 20.5.1. and miner works fine. I didn't know that TR miner depends on drivers... It 1st time happend for me... |
|
|
|
Phoenix, AMD released new unofficial driver with support for the public preview for members of the Microsoft® Windows Insider Program that enables DirectX® 12 compatible GPU-acceleration within the Windows® Subsystem for Linux (WSL) for DirectML machine learning training workflows. There is the info: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-wsl-supportMiner didn't support OpenCL from it. Can you add support for this driver?
|
|
|
|
|
Tried bfc. Used mine_bfc.bat
Changed wallet and pool.
After launching miner gives error - bfc solver not found.
|
|
|
|
I guess the miner feature to increase ethash support on 4GB GPUs is not working with the old Blockchain drivers (22.19.659.1)?
I honestly don’t know, haven’t tested. The reason is that you need newer drivers anyway to maximize the epoch for 4GBs, they have an overall lower memory footprint. I believe something like >= 19.11.3 is enough, but not 100% sure where they reduced the initial vram used. Phoenix maded some research about AMD drivers. Here his conslusions: After extensive testing of AMD Windows drivers for the last two years or so, we identified two broad groups of drivers: - Good drivers. These are versions from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.4.2 (inclusive). These will allow you to mine until DAG epoch 372-373 and won't need restart of PhoenixMiner on each DAG epoch change.
- Not so good drivers. These are versions 18.1.1 to 18.10.1 (inclusive), and from 19.8.1 to 19.12.1 (inclusive). This will allow you to mine until DAG epoch 365-366 and will require restart of PhoenixMiner on each DAG epoch change (for these drivers this will be preformed automatically unless you have added -dagrestart 0 command-line option to explicitly disable the auto-restart).
- Drivers older than 18.1.1 were not tested for 4 GB DAG operation.
It can be useful for 4Gb cards owners. |
|
|
|
Hi phoenix!!! AMD added new drivers a linux 20.20 and Windows !!!
Yes. In another driver "masterstroke" the new Windows driver is also version 20.5.1 like the last one, despite that it was released in June and should be 20.6.1 instead. Let us repeat: do not upgrade to drivers that are newer than the version of PhoenixMiner you are using. So, do not upgrade to the new 20.5.1 (the one from June 10) or the 20.20 Linux drivers yet. I decided to test "new" AMD drivers 20.5.1 (10 june). PM5.0e determined drivers as 20.5.1. No errors at launch... Speed normal - not less, not more... Continue testing... |
|
|
|
So many rejected shares on 5.0x verisions... About 1-1.2% overall rejected shares (not stales or incorrect) on my RX 580 8Gb rigs...
Could you please tell us on which pools? This is normal on nicehash, as it doesn't accept stale shares and they count as rejected shares, and it seems that recently nicehash started changing the jobs more often, leading to more rejected shares. Yes, it's on nicehash. Is there some way to correct show these stale shares? |
|
|
|
|
So many rejected shares on 5.0x verisions... About 1-1.2% overall rejected shares (not stales or incorrect) on my RX 580 8Gb rigs...
|
|
|
|
Miner didn't support new AMD 20.5.1 driver.
We are testing with the new driver and will release 5.0c soon that will support it. So far it seems that it behaves as the "good" drivers - i.e. allows mining until DAG epoch 373 on 4 GB cards. Thanks for info! Will waiting update. |
|
|
|
PhoenixMiner 5.0 AMD driver 20.4.1 RX5700(XT) works fine
I tell you more - With WHQL 20.4.2 version PM also works fine. But 20.5.1 - not. |
|
|
|
|
Miner didn't support new AMD 20.5.1 driver.
|
|
|
|
Finally! Support for new drivers. Thank you! |
|
|
|
|
Hi, kerney666!
No questions about fees. But can you add in your miner info about devfee mining when it goes? At least start mining devfee and stop.
|
|
|
|
|
I didn't understand, why all start to mine kawpow. It uses more power. Eth algo gives more profit.
|
|
|
|
i see much people using long command i feel i'm wrong i only using , PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -wal 0x4a3a28f53371a8c1b2e66955687711938716722c.TestQ -proto 3 this code only . 7 gpu's 199.500 mh/z using msi afterburner do i need to add something like boost AMD GPU's ? because claymore -xrboost . what about PhoenixMiner ? PhoenixMiner didn't have something like CM -rxboost. It's need to use AMD Memory Tweak tool for increasing REF parameter of each card. i'm using msi afterburner isn't enough ? isn't afterburner Memory Tweak tool ? No. https://bitcointalk.org/index.php?topic=5123724.0This tool can set REF parameter. This is what CM make by its -rxboost parameter. Except CM and this tool no other tools can make it. |
|
|
|
i see much people using long command i feel i'm wrong i only using , PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -wal 0x4a3a28f53371a8c1b2e66955687711938716722c.TestQ -proto 3 this code only . 7 gpu's 199.500 mh/z using msi afterburner do i need to add something like boost AMD GPU's ? because claymore -xrboost . what about PhoenixMiner ? PhoenixMiner didn't have something like CM -rxboost. It's need to use AMD Memory Tweak tool for increasing REF parameter of each card. |
|
|
|
Hi Phoenix,
Im from ClayMore´s miner and want to test the phoenix miner. Smiley
In CM i got 52 MH/s for an vega 64. (155 W on SW miner) and probably 200 from wall.
Here in my tests , using auto-tune or manual or intensity 15 i only got 44 mh/S , if increase intensity to 400 i got 32mh/S
I tested several kernels too, could be my amd drivers : Radeon-Software-Adrenalin-2019-19.5.2 ?
Its a Strange behavior.
Any ideia where should i look?
Thanks
Most probably you are using some options to change the timings and refresh rates of the VRAM, which aren't supported on PhoenixMiner. For similar things, you may use a third-party tool like AMD Memory Tweak tool: https://github.com/Eliovp/amdmemorytweak (note: we are not affiliated with the author(s) of this tool in any way) Hi, Thanks for response, Hmm the problem should be that in CM i use -strap command and the miner change the timings on the fly, right ? In PhoenixMiner should i use the thrid-party to get the same hashes right? or you have some command similiar to -strap for that? Thanks From PM readme file: "-mt <n> VRAM timings (AMD under Windows only): 0 - default VBIOS values; 1 - faster timings; 2 - fastest timings. The default is 0. This is useful for mining with AMD cards without modding the VBIOS. " Thats not analog of CM -straps parameter. This settings appears in AMD Radeon Settings starting from 19.x.x drivers. It can give increase in speed with stock vbios. |
|
|
|
Hi Phoenix!
There is a bug in PM4.9c + 20.2.2 drivers (Win). -mclock doesnt work for polaris cards with Samsung memory onboard (probably when use RX5700 as a main card and other cards are Polaris)
And a feature request: to give an apportunity to switch -tt memory or chip temterature dependent (very useful feature for Navi cards where memory is much hotter then chip and a goal is to control memory temperature)
Thanks in advance! Nice to see you back again!
-mclock stoped to work on polaris a long time ago. I didn't remember in what drivers it worked... 18.3.4 and 18.6.1 It's a long time ago... Two years passed. |
|
|
|
Hi Phoenix!
There is a bug in PM4.9c + 20.2.2 drivers (Win). -mclock doesnt work for polaris cards with Samsung memory onboard (probably when use RX5700 as a main card and other cards are Polaris)
And a feature request: to give an apportunity to switch -tt memory or chip temterature dependent (very useful feature for Navi cards where memory is much hotter then chip and a goal is to control memory temperature)
Thanks in advance! Nice to see you back again!
-mclock stoped to work on polaris a long time ago. I didn't remember in what drivers it worked... |
|
|
|
|
Show Posts
