Jump to content

Recommended Posts

Posted

Got a really frustrating issue here  - some of our desktops all have AMD Radeon integrated graphics and are connected to Philips E Line touchscreens

 

The pause function doesn't work on the screens due to the annoying HDCP - which you can switch off in the Adrenalin control panel (this has worked in the past)

 

However every machine I try to install this on now it simply doesn't work. It installs OK and the drivers are updated, but if you try to open the adrenalin control panel it does nothing - no errors logged, nothing

 

I can't find a registry setting to disable hdcp either so I'm stuck with this turd of a package - unless anyone knows a workaround or how to get the thing to start! Tried the usual things I've found in a search but nothing has worked so far

Posted

is it making the expected changes in the registry? If not.. try applying those manually?

 

Log a support call with Philips - the big display vendors do work with AMD/NVIDIA/Microsoft etc.

Log a support call with your PC/Laptop vendor - again they will work with their supply chain so can escalate back to AMD.

 

Also do you need Adrenalin? We have AMD integrated graphics  and I'm not sure that we have it installed, and so far  don't have problems... but we have (in the past) had board firmware updated to deal with changing HDCP behaviours from later versions of windows/drivers so maybe there is another path?

Posted

I tried support with Philips who blamed the AMD driver, the PC vendor blamed Philips....etc

 

Eventually I found that using the Adrenalin control panel to disable hdcp worked...until now! I think I'll try and get a version that's a bit older and see if that still works

Posted
6 hours ago, Sheridan said:

I tried support with Philips who blamed the AMD driver,

Well one of you is a global manufacturer of displays that connect to AMD devices, and one of you is not. I know what my expectation would be here.

 

In other news I shall not be considering Philips  monitors or touchscreen displays in future.

Posted

Managed to fix it by rolling all the way back to V23 of the driver package (current is 25)

 

Seems to be a signal issue between the two devices. Not an issue with Intel GPUs and our AMD's don't have an issue with other screen makes - so only an issue with AMD and Philips!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...