Monday, November 8th 2010
Radeon HD 6970 Launch May Face Delays
Originally slated for a November 22 launch, AMD's next-generation enthusiast-grade GPU, the Radeon HD 6970 may face some launch delays, according to industry sources. Apparently the company is yet to finalize a launch driver and BIOS for the HD 6970, and that could push back launch by a little. Meanwhile, a Zol.com.cn contributor let out some juicy pictures of the HD 6970 reference design accelerator.
Sources:
Expreview, Zol.com.cn
88 Comments on Radeon HD 6970 Launch May Face Delays
I would not believe these false reports about being late, pure FUD! :banghead:
All things beyond their control. If one piece of software for playing DVD's causes a fast switch issue and thus the large cursor, is it ATI's fault, or the software?
I enabled things like geometry instacing, a few different patterns of AA, AF and the ability to force DXVA and WMV hardware accleration. It has gotten me a couple times of video hangs due to codec problems, but once I sorted them it works great.
Take the average user that tries to enable it with a incompatible codec or one known to cause issue and they will cry like a little bitch about how horrible ATI is with their drivers.
Issues I have are currently.
Even with a custom BIOS the fast switch hang and video corruption still occurs with the codecs i have to use with my HG20 camcorder. I can't blame ATI for Pixelas shitty software though.
Occasional hang and green flash video. Voltage, GPU speed, memory speed, multi-monitor, Windows 7 and Vista. No difference, so I tend to blame Adobe for flash, as silverlight with hardware acceleration on Netflix is flawless.
--------------------------------------------------------------------------
www.bit-tech.net/hardware/graphics/2006/04/07/transparency_adaptive_aa_explained/2
For ATI cards the ability to use reg hacks to enable things that are no officially supported has been around for a long time.
"It's also possible to get Adaptive AA working on any GPU that is newer than Radeon 9700 via a registry hack. This is not officially supported by ATI, and performance implications are quite large. However, if you're interested in giving it a try for yourself, please read our news story covering the topic."
Nvidia does some things differently, however I have used alot of third party tools on their cards to enable features.
I know what the problem is, exactly, with the cursor. It will basically NEVER be fixed on 5-series cards, 100% for sure...it's been 13 months now!
It occurred on my new 5870 but as soon as I flashed my custom BIOS on it it has never happened sense.
If we could find WHY it happens, or WHEN it happens. Is it a scaling issue, does changing to a different pointer fix it?
Likewise, a bios will not fix it. I am running the most recent bios from AMD.
I have tried both reference and non-reference cards.
In fact I remember the 5870 product page on the official AMD/ATI website at the time, had a disclaimer at the time to the effect of;
*driver support for 5800 series cards sheduled for 2010
It's not software, it's the display output of the 5-series cards that causes the issue. 6-series cards have DP1.2, to fix the problem, but it only works with either the multistream boxes, or daisy-chained monitors. Without either of those, even the 6-series cards ahve the problem, as the DP and DVI outputs have different timings and protocols.
To eliminate the corruption, you must use the same type of output for all monitors, however, as it stands today, this is not possible, as the hardware is not on the market, and will not be, until next year.
And with that said, Eyefinity isn't even Beta...it's more like "alpha"...bare functionality, but broken as hell.
didn't expect it to be much larger, even despite being stuck on 40nm it doesn't seem like the core is goign to get that much larger and 256-bit mem says they don't have to add too many chips onthe board either.
But i accept that it is an old issue that can be very annoying for some people but if it is a hardware limitation thus unfixable why does ati keep adding "fixed corrupt cursor" to the driver fixes list?
You, bear, will be able to switch to a multi-stream box, when they come out, because you have 6-series, and this will eliminate the problem. So all is not lost for you. 5-series owners, unfortunately, do not have this option. I bought 5-series cards specifically for Eyefinity, so yeah, it's a sore point for me.
It's doesn't happen on the DP monitor for me, most often, either...it's on the DVI monitors that the cursor shows up corrupt most often. But give it some time, and you'll see it on the DP monitor as well.
Would you not need 2 x 8 pins to crash over 300W?
And even if i'm right? i'm sure it's not that straight forward...
But i admit if i was using display port monitors i would grab the box so i had the ability to add more monitors.
See page 7:
www.amd.com/us/Documents/AMD_Radeon_Display_Technologies_WP.pdf
"I accidentally . the driver"
When AMD is apparently months ahead of the competition to release these products (5000/6000) I would think taking a month extra to pound out driver conflicts before launch would be a good thing.. NOPE 10.10y hotfix is on the way.
Except the TH2G only does max 1680x1050 per screen, when using 3. AMD's solution supports HD res, plus 3D, etc.
That is why the GTX470 pulling 232w can make do with two 6-pin connectors or the HD5970 pulling 304w needs a 6-pin and an 8-pin. At least that is the way I've always understood it.
I didnt read this entire thread, but aside from driver/bios issues, I thought yields were single digits from TSMC on these things (if true, anyone want to bet that dope charlie doesnt report this?!!).
www.techeye.net/chips/amds-cayman-christmas-card-delayed-say-taiwanese-sources