HDMI support broken in newer ATI drivers

[siliconaudio]

Yes, I actually have tried it. Most recently with Catalyst 10.1 (which was used to make the attached screenshot), but I didn't have CCC on the machine that I used to respond at the time. And the quote was from someone who was running the 9.12 Hotfix at the time.

Sorry Whurlston, that was me being an arrogant fool because I was so frustrated. I apologise.

I have done some more research on this and it turns out that only people with Panasonic TVs are seeing this. So, you won't see this problem if you're not using a Panasonic.

See THIS THREAD for details...

[whurlston]

No problem. I'm just glad you didn't see my first response (I was having a bad day myself).

Try this: Open regedit and browse to

Code:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\

Search "Values" for "4670". It should take you to a key like

Code:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000

You may have additional number keys like "0001" depending on the monitors/ports you have connected.

There will be a value in that key that is named "DAL6 DFPI4[resolution]", for me it's "DALR6 DFPI 41920x1080x0x59" since I'm running 1920x1080x59. This will be a binary value. Change the very first non 00 (I think it's 80 or 08) to 00. Edits are inserted so just type 00 then delete the unwanted value. This will be the same as setting Overscan to 0 in CCC.

If you have any trouble, just export the 0000 key and zip and post it. I can find and change the value for you.

[siliconaudio]

Hey Whurlston, thanks for the tip. As it happens, I had been digging around in

Code:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{GUID}\0000

but wasn't sure what value I needed to change.

The GUID is specific to the video card, but otherwise has the same structure as the key you referenced. It turns out that editing the "DALR6 DFPI 31920x1080x0x50" value (We're on PAL here, so 50 Hz) is exactly what I needed to do, but interestingly, the values weren't there under the CLASS key.

Anyway, you were right on the money in regard to the value. I changed the first non-zero value from 08 to 00 and that corrected the under-scan.

So, I owe you a debt of gratitude, because I can now watch TV without the big ugly black boarder - so, THANK YOU Next time you're in New Zealand, I'll buy you a beer.

AMD still need to fix this, but this gets me going in the mean time.

[whurlston]

Mine was probably under the class key because I'm using the inbox Windows 7 drivers on my 4670 at the moment (no CCC so I had to adjust the registry). I found that setting when I tried a beta driver and could not get CCC to run. Glad you got it sorted. I'll take you up on that beer (well maybe a shot) if I ever make it to NZ.

[MonoksideC]

I'm really glad that I found this thread. I've been pulling my hair out over this as well - at least now I know that it's an issue with Panasonic TVs in general.

I tried the registry fix, but it isn't working for me. Every time I change the values from 08 to 00 under that key, they just change back to 08 after I reboot and the problem is still there.

[MonoksideC]

I uninstalled CCC completely and now the settings stick. Kinda weird.

Thanks for finding this out and sharing the info!

[siliconaudio]

What OS are you running MonoksideC? The setting is sticking for me. I have CCC on Windows XP SP3.

The ATI/AMD CCC and drivers seem to be in a constant state of flux. Features/performance can go down the toilet from one driver to the next. I Don't think I'll ever go down the ATI/AMD route again. I never had these issues when I ran nVidia cards. I'm sick of the grief.

[siliconaudio]

Good news, this problem is now completely resolved in CCC/Driver pack 10.2

[dexter69]

Hi There - apologies for the nooby question

After a full week of searching I stumbled on this thread, so I really hope I can get an answer lol

Anyway - running 4200HD with ccc 10.1 (i think) on W7...

Last week, the laptop suddenly refused to detect my LG hd tv, no matter what I tried, it just point blank refuses to see it - it's weird though, it "thinks" that its a standard VGA in the Windows Display Props, however CCC thinks that a CRT is installed, again however, the card correctly picks up the TV when I connect using DVI...

It's starting to really irk me now - I think there was a raft of updates applied to the PC last week, but not entirely sure, leastways, it [I]was/I] working prior to last week, now it's not...

Hope someone can help !

[whurlston]

From a command prompt (administrative command prompt if you have UAC enabled):

1. Type "set devmgr_show_nonpresent_devices" and press enter.
   
2. Type "devmgmt.msc" and press enter.
   
3. Select "View"->"Show hidden devices".
   
4. Expand "Monitors".
   
5. Delete all installed monitors.
   
6. Unplug the cable to your TV.
   
7. Wait 5-10 seconds and then plug it in again.
   

If this doesn't work, we can try something else.