AMD Special Edition Driver: Catalyst Omega

[Jamzer]

Installed on Windows 7 just fine and fixed my CCC issue. It's late, will try Linux tomorrow.

Hitman, what was the nature of your CCC prob on Win 7? 64 or 32 bit? How new or old is/are your card(s)? 'FirePro' by any chance?

 

[Hitman928]

Hitman, what was the nature of your CCC prob on Win 7? 64 or 32 bit? How new or old is/are your card(s)? 'FirePro' by any chance?

Not a firepro, it's my linux box that has a win7 (64 bit) partition. It has a 6870 in it, so decently old at this point but that's all I need for that box. The CCC problem was only on the latest beta drivers before the omega drivers where the drivers were working fine but CCC would crash any time I tried to change any settings.

 

[CaptainKangaroo]

Hi all, first post.

First off my specs are Q6600@3GHz, GA-P35-DS3R, Sapphire Radeon 6870 1GB, 4GB DDR2@800MHz, Samsung 840 120GB, Seagate Barracuda 500GB, LG 24" IPS 24EA53, LG 32" 1080p LEDTV. Win 7 64. I'm currently on the 14-4 drivers without issue.

At the end of November I updated my ATI HD 6870 drivers from 14-4 to 14-9 on Win 7 64. I know, they were out nearly two months but I usually don't bother updating for a while to avoid bugs, and seeing as my card is old I figured I wouldn't gain much performance anyway. The Catalyst Control Center would crash after selecting different options on 14-9 and trying to exit. Reverted back to 14-4 and it's was working fine. I didn't bother booting up a game to see if the 14-9 driver is stable in game.

Again, I updated to the Omega drivers tonight (14-12). This time Catalyst Control Center seemed more stable and only had the border at the top go blank until I restarted it. I fired up Elite Dangerous and all seemed well, though I didn't play extensively today. Then I sat back to watch a film on my extended desktop secondary monitor which is a TV. I turned off my primary monitor using the switch on the monitor and when I did so the signal to the TV disconnected and reconnected making the standard noise Win 7 does when you disconnect and then reconnect a device. This happened every time I turned my desktop monitor off, no matter if it was the primary or secondary display, nor if it was extended or duplicate.

As you may imagine I often use either monitor interchangeably so I could not stand for this extremely annoying behavior. I've gone back to the somewhat flawless 14-4 and, as before, everything is fine. I can now turn my monitor off without causing any unusual behavior from my TV. I would seriously consider getting an Nvidia card next time I'm on the market, as I would go nuts if I was forced to tolerate dysfunctional updates from AMD to get the best performance out of a new card in games.

Hope AMD can fix this issue and restore my faith after a less than stellar recent performance.

Thanks for reading.

 

[eagle101]

Tnk u testing it right now on my MSI R9 290X lighting edition.

14.12 AMD Catalyst Omega, desprado is this the driver you have?
i'm using it works very well for me on my 290x msi lightning

 

[eagle101]

14.12 omega took the little problems away, I thought I had possible a Bad 290x Msi Lightning
Thank God for the Omega Driver

 

[MaxDepth]

Well...that sucked. I have the MSI R7950.

I went from 13.4 drivers to this new suite. I installed everything and then...
- HTML5 and Flash video (streaming) flakes out and stutters.
- A ton of crapware with the raptr (gaming evolved). You should see how deep it embed itself into the Windows Registry (even after uninstalling it).

Rolled back to 13.4. Call me when it gets fixed.

Uhm, no thanks.

 

[Red Hawk]

If you choose "custom" instead of "express", you can opt out of installing Raptr/Gaming Evolved.

 

[Black Octagon]

Never install Raptr

 

[Plimogz]

^ Pretty much.

 

[tweakboy]

These were good with my old X800 xt . gb

 

[MaxDepth]

Yup. Although at the time of installation I did not research "gaming evolved," if I had I would have seen the raptr association.

That''l learn me...

Never install Raptr

 

[RadiclDreamer]

Does this have anything to do with the guy that used to run omegadrivers.net? Or just a coincidence in naming?

 

[shoulder]

I have a fairly old but still modern ATI video card. I haven't been in the game for a while and I just found out about the AMD takeover. I received warnings that my card didn't have DirectX 11 when I tried to run metal gear solid and when I attempted to render some 3d objects in adobe after effects, I was told that I would need to enable open GL on my video card. so I went to open up my ATI control center, I noticed that, I didn't have one. I didn't have any icons anywhere either. so for three days I searched and googled around looking for the correct software that would allow me to access my card functions and I finally decided to find some real people to answer my questions. what I'm working with: System Information
------------------
Time of this report: 2/3/2015, 17:36:19
Machine name: +++++++
Operating System: Windows 8.1 64-bit (6.3, Build 9600) (9600.winblue_r3.140827-1500)
Language: English (Regional Setting: English)
System Manufacturer: MSI
System Model: MS-7589
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz (4 CPUs), ~3.1GHz
Memory: 4096MB RAM
Available OS Memory: 4024MB RAM
Page File: 3703MB used, 1279MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.03.9600.16384 64bit Unicode Display Devices
---------------
Card name: ATI Radeon HD 4600 Series (Microsoft Corporation - WDDM v1.1)
Manufacturer: Advanced Micro Devices, Inc.
Chip type:
DAC type: Internal DAC(400MHz)
Device Type: Full Device
Device Key: Enum\PCI\VEN_1002&DEV_9490&SUBSYS_E1011092&REV_00
Display Memory: 2809 MB
Dedicated Memory: 1017 MB
Shared Memory: 1792 MB
Current Mode: 1360 x 768 (32 bit) (60Hz) what brought me here:
<error><msg>Package Manager Install Package Failure!</msg></error></monetreport> I need to configure my video card stings and there are no downloads anywhere that possess a working control center. I believe this is a casualty of the amd takeover. am I the only guy whos been left in the dust by this?

 

[Hitman928]

You should post a new topic in the computer help forum rather than adding to this long and old thread. As a quick answer, your video card only supports up to DX10. I'm not familiar with the game or software in question so you'll need to get other people's input there.

 

[DrMrLordX]

Sorry to thread necro, but Warsam, us Linux users may have an issue on our hands.

Catalyst Omega 14.12 + Linux kernel 3.19 (stable) =

Error! Bad return status for module build on kernel: 3.19.0-031900-generic (x86_64)

Ooops. The contents of make.log:

doing Makefile based build for kernel 2.6.x and higher
rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
make -C /lib/modules/3.19.0-031900-generic/build SUBDIRS=/var/lib/dkms/fglrx-core/14.501/build/2.6.x modules
make[1]: Entering directory '/usr/src/linux-headers-3.19.0-031900-generic'
  CC [M]  /var/lib/dkms/fglrx-core/14.501/build/2.6.x/firegl_public.o
/var/lib/dkms/fglrx-core/14.501/build/2.6.x/firegl_public.c: In function ‘kasSetExecutionLevel’:
/var/lib/dkms/fglrx-core/14.501/build/2.6.x/firegl_public.c:4819:5: error: implicit declaration of function ‘__get_cpu_var’ [-Werror=implicit-function-declaration]
     orig_level = __get_cpu_var(kasExecutionLevel);
     ^
/var/lib/dkms/fglrx-core/14.501/build/2.6.x/firegl_public.c:4820:38: error: lvalue required as left operand of assignment
     __get_cpu_var(kasExecutionLevel) = level;
                                      ^
/var/lib/dkms/fglrx-core/14.501/build/2.6.x/firegl_public.c: At top level:
/var/lib/dkms/fglrx-core/14.501/build/2.6.x/firegl_public.c:6396:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function]
 static int KCL_fpu_save_init(struct task_struct *tsk)
            ^
cc1: some warnings being treated as errors
scripts/Makefile.build:257: recipe for target '/var/lib/dkms/fglrx-core/14.501/build/2.6.x/firegl_public.o' failed
make[2]: *** [/var/lib/dkms/fglrx-core/14.501/build/2.6.x/firegl_public.o] Error 1
Makefile:1382: recipe for target '_module_/var/lib/dkms/fglrx-core/14.501/build/2.6.x' failed
make[1]: *** [_module_/var/lib/dkms/fglrx-core/14.501/build/2.6.x] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-3.19.0-031900-generic'
Makefile:88: recipe for target 'kmod_build' failed
make: *** [kmod_build] Error 2
build failed with return value 2

Please pass that along to the right people. I see no other indicators of this being an issue for anyone else (yet), but then it may be that Catalyst Omega 14.12 users under Linux aren't trying the new kernel just yet.

Anyone here have any confirmed instance of 14.12 working with kernel 3.19?

 

[Sequences]

Isn't the kernel much newer than the driver? What makes you think that it would be compatible out of the box? Maybe wait for the next driver release, or use the open source ones.

http://www.phoronix.com/scan.php?page=article&item=linux_319_radeon&num=1

 

[Hitman928]

Yeah, I don't think you can expect a driver to automatically support a new kernel. It'd kind of be like upgrading to Win 8 from Win 7 and expecting the driver to just work. The changes necessary shouldn't be as big as that, but I still wouldn't expect support on a brand new kernel when the drivers are a few months old now. This is just the reality of linux if you're always wanting to be on the latest kernel.

 

[DrMrLordX]

I tried it anyway, and if I have to, I'll roll back to the old kernel until AMD has a chance to issue a fix or a new release or something. fglrx was the only thing on my system that caused problems under 3.19, and in theory, it should have worked. Practice was quite different.

So let me be a guinea pig for others. It ain't workin just now.

Personally, I was looking forward to 3.19 since it was supposed to offer broader support for HSA in the mainline kernel (obviating the need to grab a kfd kernel from github). Perhaps the use of fglrx obviates the need for a kfd kernel? The 3.19 upgrade notes all indicated broader support for HSA using the default Radium/Gallium drivers . . .

edit: not to nitpick, but a metric ton of old Win7-era drivers did work in Win8. I've even gotten several Win7 drivers to work in Win10. But that's Windows. Linux is its own ball o' wax.

 

[james1701]

Funny thing, the last two weeks, I started having issues with the monitors not waking up. After a while, it would blue screen to a video tdr failure.

I have never had an issue with monitors not waking until now.

 

[DrMrLordX]

That's odd. Have you eliminated the possibility that it's a hardware failure issue?

That is, can you replicate it under 14.9 or something?

 

[james1701]

That is my next stop.

 

[turboGeeek]

greetings

im having a problem with this driver and even starting to wonder if it's driver related issue. Got a new card, a 290x lightning. Upon testing i keep getting whole system reset about 15 mins in gameplay. Anyone has this issue? Before u wonder my power supply is less than a year old 750w Coolermaster PSU. I have uninstalled all my previous nvidia drivers.

 

[DownTheSky]

Whole system reset w/o any errors => PSU overcharge protection kicks in.

 

[turboGeeek]

Whole system reset w/o any errors => PSU overcharge protection kicks in.

so i need more than 750w then? That's strange, i mean the card is not overclocked yet it's running stock

 

[Sunaiac]

You do not need more than 750W.
That's what I use for an O/C i7 980 and an O/C 290X with more than 200W margin (Antec TruPower 750 from 2010).
Either you have a multi-rail PSU with badly allocated rails (try changing the PCI plugs used, or your PSU has a default.

Or the problem is something else.