Quote:
Originally Posted by joshmel
wow, super sorry i posted my thoughts... i wont make that mistake again here. But to answer your rhetorical: Ive seen AMD post similar things on their own forums. Basically a "no problems with our drivers, everything works fine, must be you", only to have a fix show up 3 - 6 months later. It would be easy to see them doing so here, leaving the issues up to "user error". Regardless, I understand this is all non issue for you with your obvious technical expertise, what with being able to run catalyst 10.9 with an nvidia card, but for the rest of us non programmer types, it is kind of annoying to no be able to use a piece of hardware.
|
Funny. I don't recall saying that I'm using a NVIDIA card with Catalyst 10.9. I'm glad you recognize my technical expertise though.
Quote:
Originally Posted by Wim
Hi All
OK - I'll try and explain where we are with this issue.
We have reproduced the BSOD with 10.8 CCC and will have a fix in our release of v5.5, which should be around the end of the month.
We've not found any problems on 10.9 yet, but this could only occur on certain setups. Please note, that we do not support ATI Crossfire configurations today so problems could be found if you're using crossfire and move to v10.9.
Can anyone report problems with v10.9 and not using Crossfire configurations? If so and you post your system details.
Thanks
Wim
|
Thanks for posting about this Wim. I'm glad DisplayLink's experience with Catalyst 10.9 and DisplayLink 5.5 beta support what I've been posting about here.