VMMaker not seeing driver

[dth930]

I'm trying to get a new install working on Win10.  I have an AMD Radeon 6670 card and am using Emudriver & tools 2.0 beta 15. 

I've installed the emudriver and rebooted.  When I go into it now, it correctly shows AMD Radeon 6670 and gives me the Uninstall option.  In Device Manager I see AMD Radeon 6670 also.  I have not installed any other drivers for the GPU (besides whatever Windows may have installed automatically).  However, when I go into VMMaker it tells me "No compatible driver found".  It only lists DISPLAY1 - Microsoft basic display driver.

I don't have any options for EDID emulation in the settings.  (though I should given the card I'm using)

I can go through the setup and generate modes for my display (a WG 25K7401, set as a K7000) but after it's done the option to Install Modes isn't enabled.

Am I missing a step somewhere?  Do I need to install any AMD drivers?
 - Dave

[dth930]

I should mention that I'm using the beta 15 release with Adrenalin 18.5.1.  I tried uninstalling and then installing using beta 15 with Adrenalin 16.2.1 but when I try that Emudriver doesn't find my card at all.

I started with a clean Windows 10 Pro install, so there are no legacy drivers around.
 - Dave

[Calamity]

The correct version for your card is 16.2.1. Maybe your card's pci id is not listed as compatible (post it here just in case). Have you tried a forced installation from the hardware manager?

[dth930]

These are IDs that are being reported:

PCI\VEN_1002&DEV_6758&SUBSYS_0B0E1028&REV_00
PCI\VEN_1002&DEV_6758&SUBSYS_0B0E1028
PCI\VEN_1002&DEV_6758&CC_030000
PCI\VEN_1002&DEV_6758&CC_0300

When I try to force the driver to update to Emudriver from device manager I get a notice that Windows confirmed that the best driver for my hardware is already installed.  The closest I see in the included driver pack is the 6570, but that's definitely not what I have.

It's weird that 18.5 sees it but 16.2 doesn't.  Is it possible that the mistaken installation of 18.5 left some remnants that's causing 16.2 not to see it?
 - Dave

[Calamity]

16.2.1 definitely has that ID included. But there are 2 versions of the package, make sure you got the one for non-GCN cards, use this link.

[dth930]

That was the problem.  When I was initially downloading the versions weren't clear from the filenames, but it makes sense now.

Thanks.
 - Dave