Bitcoin Forum
August 09, 2024, 05:39:16 PM *
News: Latest Bitcoin Core release: 27.1 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Mining (Altcoins) / Re: Any word on amd vega hash rates? on: November 05, 2017, 11:54:29 PM
Same. Anyone have any insight?

Make sure your running the batch file/devcon as an administrator. If that doesn't work, make sure you have the 64 bit version of devcon if you're running 64 bit windows, and the 32 bit version of devcon if you're running 32 bit windows.

Side note for people who might search this in the future:

The Asus Z270-A WILL NOT RUN 7 Vega. At least not without additional hardware. Its impossible to install the drivers, they'll crash every time no matter how you do it. 6 cards is doable, as long as they're placed in every slot EXCEPT PCIeX16_1. If a card is placed in the first x16 slot, then the drivers will crash while installing if you try to use more than 5 cards. Just a heads up for anyone who might be having this problem.

Edit: Running 7+ Vega on the Asus Z270-A is doable with a PCIe expander. Just make sure no cards are placed in the first x16 slot.
2  Alternate cryptocurrencies / Mining (Altcoins) / Re: Any word on amd vega hash rates? on: October 29, 2017, 07:01:25 AM
Hello!

I need a help with power table.

I set 850 mV for P0-P7 and 850 mV for P3 HBM memory.


But in GPU-Z Sensors - VDDC 1 V or more.

Why?

Because lowering voltages past a certain point in the power play table doesn't actually do anything. Use OverdriveNTool to apply the voltages. Also remember that memory voltage is actually core voltage floor, so make sure it's equal to or lower than your desired core voltage.
3  Alternate cryptocurrencies / Mining (Altcoins) / Re: Any word on amd vega hash rates? on: October 28, 2017, 10:47:35 AM
This is correct by you don't want to disable the iGPU on rigs that use it (like mine).
You can instead call
Code:
devcon.exe disable "PCI\VEN_1002&DEV_687F"
timeout /t 2
devcon.exe enable "PCI\VEN_1002&DEV_687F"
This is enable/disable ALL devices that match the prefix.

Just my 2p Smiley

Even better! I disable the iGPU on all of my systems, so I wasn't really thinking about that. Can anyone confirm whether the vendor defined identifier (DEV_687F) is the same for all the Vega variants (V56, V64, V64L)?
4  Alternate cryptocurrencies / Mining (Altcoins) / Re: Any word on amd vega hash rates? on: October 28, 2017, 05:57:00 AM

Thanks for your contribution Mythic - just tested with my Vega 64 and your solution works great. I've tweaked your automation a little further to disable and enable all Radeon cards in a rig at startup - see below for my contribution (note: this doesn't have code to execute xmr-stak-amd or overdriventool as those are straight forward commands and can be added to the end. If I have some time I might just add some parameters at the top for ease of editing and add some error handling to idiot proof the whole process):

Code:
@echo on
set currentdir=%cd%
cd C:\Program Files (x86)\Windows Kits\10\Tools\x64
devcon findall * | findstr Radeon > %currentdir%\radeoncards.txt
for /F "tokens=1 delims=:" %%a in (%currentdir%\radeoncards.txt) do (
devcon disable "@%%a"
timeout /t 15
devcon enable "@%%a"
timeout /t 15
)
del %currentdir%\radeoncards.txt
cd %currentdir%

After reading the documentation for devcon, I've found that you can actually just do

Code:
cd %~dp0
timeout /t 5
devcon.exe disable =Display
timeout /t 5
devcon.exe enable =Display

Where devcon.exe is placed in the same folder as the batch file. This ought to simplify things a bit.
5  Alternate cryptocurrencies / Mining (Altcoins) / Re: Mining with more than 4 Vegas and HBCC -> SOLUTION on: October 27, 2017, 07:21:05 PM
Here you can have the 4+ hbcc activation for free!

 If you won't pay for it:

https://bitcointalk.org/index.php?topic=2002025.msg23619746#msg23619746

 Cool
I wanted source code, didn't get it for "fair price", but this is very good. Thx.

PM me your fair price...


ROFL. I think we've already established that a fair price is $0.
6  Alternate cryptocurrencies / Mining (Altcoins) / Re: Any word on amd vega hash rates? on: October 27, 2017, 06:46:30 PM
Is OverdriveNTool working good? There has been reports, that changing values with it doesn't really do much (same as Wattmann). But I guess it has been updated and working fine since then?

OverdriveNTool is working fine for me, but I basically only use it to adjust voltages. I use the registry mod for GPU and MEM clocks.

I can run the batch file as admin manually, and it works great.

When I run it in my startup folder it doesn't run as admin and doesn't work.

How are you getting it to run on startup as admin?

Use the task scheduler to execute your batch file at startup. See here: https://superuser.com/a/929227
7  Alternate cryptocurrencies / Mining (Altcoins) / Re: Any word on amd vega hash rates? on: October 27, 2017, 04:27:36 PM
Ups...

But now "Disabled on reboot" and "Enabled on reboot"

Reboot, run the batch file again, and try mining.
8  Alternate cryptocurrencies / Mining (Altcoins) / Re: Any word on amd vega hash rates? on: October 27, 2017, 04:09:07 PM
I have a report "Disable failed"

Are you running the batch file as an administrator?
9  Alternate cryptocurrencies / Mining (Altcoins) / Re: Any word on amd vega hash rates? on: October 27, 2017, 01:53:11 PM
Question:  the command to launch OverdriveNTool -p0Vega0 -p1Vega1...  is that pulling up separately saved profiles for each Vega card and applying them, or something else?

That's exactly what it does. Every card can undervolt to varying degrees, so I have different profiles with different voltages for each card. From the OverdriveNTool documentation:

Code:
Command Line:
-p[gpu_id]"Name"
apply profile "Name" to GPU with id=[gpu_id], silently
10  Alternate cryptocurrencies / Mining (Altcoins) / Re: Any word on amd vega hash rates? on: October 27, 2017, 12:22:31 PM
thanks for sharing, i have found the same process when i look at the other hbcc-activate program yesterday !

No problem! Just to set the record straight, I didn't copy this from the other guy. I actually discovered this last Thursday, after spending days running through pretty much every other possibility (Linux, virtual machines, etc). Kind of weird how people tend to discover things at around the same time.
11  Alternate cryptocurrencies / Mining (Altcoins) / Re: Any word on amd vega hash rates? on: October 27, 2017, 12:13:30 PM
I hadn't originally planned on putting this out there, but some other asshole decided to charge a fee for this info. Fuck that guy. Here's a fix for reduced hashrate and a method for running 4+ Vega at full speed while mining XMR.

Basic Users:

1. Use the Blockchain drivers.
2. Open up your device manager.
3. Open up the "Display Adapters" dropdown.
4. Right click on one of your Vega's.
5. Disable it.
6. Wait a few seconds.
7. Right click on the Vega you just disabled.
8. Re-enable it.
9. Repeat steps 4-8 for the rest of your cards.
10. Enjoy mining at full speed with as many Vega as you damn well please. Probably.

Advanced Users:

The previously described process is a bit of a pain in the ass. Let's automate it.

New Procedure

1. Get your hands on the Windows Device Console (Devcon.exe). This will let you disable/enable devices from console.
2. Create a batch file in the same folder as devcon.exe with the following lines in it:
Code:
cd %~dp0
timeout /t 5
devcon.exe disable "PCI\VEN_1002&DEV_687F"
timeout /t 5
devcon.exe enable "PCI\VEN_1002&DEV_687F"
3. This will selectively disable/enable all the Vega cards you currently have in your system. Thanks to bytiges for noting that killing all the display adapters might not be a good idea for those using iGPU.
4. Run the batch file as an administrator at login, or whenever you lose hashrate on your cards. Enjoy never having to toggle the HBCC switch again.

Outdated Procedure

1. Get your hands on the Windows Device Console (Devcon.exe). This will let you disable/enable devices from console.
2. Run the command devcon.exe FindAll * to generate a list of all the currently attached devices and their hardware IDs.
3. Search your newly generated list for "Radeon RX Vega." You should find something like this:
Code:
PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&3AAC35E3&0&000000E7 : Radeon RX Vega
4. The part to the left of the colon is what you need. Shocking, I know. Put that thing into a batch file that looks something like this:
Code:
@echo on
cd C:\Users\Mythic\Desktop\Startup
timeout /t 5
devcon.exe disable PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&3AAC35E3&0&000000E7
timeout /t 15
devcon.exe enable PCI\VEN_1002&DEV_687F&SUBSYS_0B361002&REV_C3\6&3AAC35E3&0&000000E7
timeout /t 15
OverdriveNTool.exe -p0Vega0 -p1Vega1 -p2Vega2 -p3Vega3 -p4Vega4 -p5Vega5 -p6Vega6
timeout /t 10
cd C:\Users\Mythic\Desktop\xmr-stak-amd
xmr-stak-amd.exe
5. Run your batch file at startup as an administrator. Enjoy never having to toggle the HBCC switch again.

FAQ:

Q: So, Mythic, how exactly does this enable HBCC on cards 5-7?

A: It doesn't! HBCC Does nothing to improve your hashrate! Turns out the drivers are just shit and are bugged when Windows first boots up. Who would have guessed?

Q: But Mythic, does that mean I don't need 16 GB of ram to run my cards at full speed?

A: Correct! 4 GB of ram is completely sufficient!

Q: If I wanted to donate some pizza money to the broke ass college student that typed this up, how would I do so?

A: You ask the best questions! I doubt I'll get anything before more well known people/websites copy everything I just said (with no credit, obviously), but here are some addresses just in case.
          XMR: 42e8AWjcirkBDzCNnSjPxeGJeht71kFfWcoxxCWsxe8HZqP29NruDsxcvVSjbKw17AUDepopK7ZYCUn mRvcGS9kBT5XWhMQ
          ETH: 0x74Ed2CA095Dd3aE98D88d5ca1dDb77E752152938
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!