[QUOTE=nomead;507922]Is it configuration fuses on the die, microcode update, driver limitation, or what? And of course... could it be hacked afterwards :smile:[/QUOTE]

Probably the former, possibly based on "binning".

[QUOTE=M344587487;507915]I was expecting £700 but it's £650 in the UK. Tried to buy one but my bank decided I was trying to steal from myself and now they're out of stock so that's nice.[/QUOTE]

Scan just got some more on their site from £684. Too late in day for next day delivery, and I'm out Saturday so might as well see if cheaper at other sites as more stock appears.

Anyone got one yet? I'll probably pick one up eventually but as I refuse to pre-order it could be a while.

[QUOTE=M344587487;508890]Anyone got one yet? I'll probably pick one up eventually but as I refuse to pre-order it could be a while.[/QUOTE]

Despite AMD's promise to have an decent stock of these at launch time, they have been impossible to get in North America. There is only 1 retailer in our continent, Newegg.
I have submitted the "notify me via email" request for every one, but by the time I see the email and get to Newegg, they are long gone.
I have noticed they are available in the UK.

Some may say this portends good things for AMD's bottom line and competitiveness vs Nvidia, or maybe they just are having bad yields. If their rarity continues, we'll know the answer.

The three UK retailers I use for hardware are scan, ebuyer and overclockers. Scan are out of stock, ebuyer has two cards at £700, overclockers has 5 at £750 and 8 at £800. Scan and overclockers are taking pre-orders at £650. Aside from Powercolor only having a 2 year warranty to everyone else's 3 the only difference between models is the brand sticker they put on the fans, which makes the fishing retailers are doing with overpriced models all the more blatant.


As far as I can tell the cards are just ok for gaming, nothing to tempt anyone but an AMD fan away from nvidia but they are really compelling for certain compute. I wouldn't be surprised if demand from compute customers can suck up all of the supply for a while.

I've changed my tactics so I get a text when I get an email from newegg so I can respond quicker to their getting more stock.
It's truly bizarre to see the newegg page for Radeon VII that has 7 identical boards from 7 different companies at the exact same price
[url]https://www.newegg.com/Product/ProductList.aspx?Submit=ENE&IsNodeId=1&N=100007709%20601328427[/url]

GPUOWL Incompatible with new adrenaline 19.x.x driver
 

Considering that GPUOWL simply refuses to run on my vega 64 for the newest adrenaline drivers, I suspect it won't run either on Radeon VII. Just gotta wait until GPUOWL runs properly on the newest drivers or AMD fix their OpenCL stuff in their new 19.x.x drivers, then the card's full potential and stability can be tested.

Also, I reckon that Radeon VII is more like an early access product for now. I have seen a Reddit post claiming the base plate of the heatsink is slightly concave, with washer mod and sanding the baseplate flat down with relatively fine sandpaper reduced the temperature by about 40C (see [url]https://www.reddit.com/r/Amd/comments/arrxt2/radeon_vii_how_to_drop_40c_on_your_stock_cooler/[/url] ), hopefully later AIB models can have a perfectly flat base plate and alleviate the issue.

[QUOTE=xx005fs;508966]Considering that GPUOWL simply refuses to run on my vega 64 for the newest adrenaline drivers, I suspect it won't run either on Radeon VII. Just gotta wait until GPUOWL runs properly on the newest drivers or AMD fix their OpenCL stuff in their new 19.x.x drivers, then the card's full potential and stability can be tested.

Also, I reckon that Radeon VII is more like an early access product for now. I have seen a Reddit post claiming the base plate of the heatsink is slightly concave, with washer mod and sanding the baseplate flat down with relatively fine sandpaper reduced the temperature by about 40C (see [url]https://www.reddit.com/r/Amd/comments/arrxt2/radeon_vii_how_to_drop_40c_on_your_stock_cooler/[/url] ), hopefully later AIB models can have a perfectly flat base plate and alleviate the issue.[/QUOTE]

Are you running windoze or linux ? What version of gpuowl ?
I am running windoze 10 with Adrenalin 2019 19.1.1 drivers; gpuowl v5.0
My board is a Frontier vega. This is the first time I have tried 2019 drivers and I did notice one little thing different:
Since the frontier board is gpu device #0, I would usually just enter 'gpuowl -fft +3' but
on this setup the opencl puked ( I can't recall the error ).
Adding the '-d 0' made it work.

Many reviewers have commented that they thought the Radeon VII launch was rushed by about 1 or 2 months. The main complaint was the driver looked 'rough': lots of hiccups and crashes.

[QUOTE=tServo;508993]Many reviewers have commented that they thought the Radeon VII launch was rushed by about 1 or 2 months. The main complaint was the driver looked 'rough': lots of hiccups and crashes.[/QUOTE]
Marketing probably determined the launch date, ready or not. Radeon 7, 7 nm, Vega 2, whatever ... 7.2.2019 :smile: Now rumours say that 7nm Ryzen chips (and perhaps some Navi products) will be launched in the summer. And again, 7.7.2019 seems to be a recurring date in these rumours.

[QUOTE=tServo;508993]Are you running windoze or linux ? What version of gpuowl ?
I am running windoze 10 with Adrenalin 2019 19.1.1 drivers; gpuowl v5.0
My board is a Frontier vega. This is the first time I have tried 2019 drivers and I did notice one little thing different:
Since the frontier board is gpu device #0, I would usually just enter 'gpuowl -fft +3' but
on this setup the opencl puked ( I can't recall the error ).
Adding the '-d 0' made it work.

Many reviewers have commented that they thought the Radeon VII launch was rushed by about 1 or 2 months. The main complaint was the driver looked 'rough': lots of hiccups and crashes.[/QUOTE]

yes i am using windoze. I am getting the same error even though I am giving it the device number and ocl still breaks, albeit im using gpuowl 3.8

[QUOTE=xx005fs;508997]yes i am using windoze. I am getting the same error even though I am giving it the device number and ocl still breaks, albeit im using gpuowl 3.8[/QUOTE]

Using a more recent version of gpuowl might be worth a shot. It's pretty easy enough to do.
I would try 5.0 first then either 6.0 or 6.2 if 5.0 pukes.

You may also want to see if AMD has posted new drivers. I think they have updated them at least twice.