Windows 8.1 RTM AMD Notebook drivers with hybrid support on Windows Update


Recommended Posts

I get the permanent black screen as well if I am upgrading from any other driverset. I was actually on 8.1, with an old set, tried to upgrade and had to do a full reinstall since my system restore points failed to work.

Link to comment
Share on other sites

Just tried the Windows Update driver on an HP Tm2. Permanent black screen.

 

So Mike, don't release the drivers for 1G Intel, 

 

Seketh. Have you tried changing your FeatureTestControl values to FFFF or something else? This usually solves the issue.

Link to comment
Share on other sites

I installed AMD 13.10 beta which support Windows 8.1 but in order to make it work there's a catch.

When you want to operate AMD, Intel needs to be on too. So it actually creates two "Displays"

One utilizing AMD, and the other Utilizing Intel. The trick is after logging in to change the default "Extend to Display 2" to only show to Display 1.

 

post-272706-0-78689000-1378759955.png

Link to comment
Share on other sites

I installed AMD 13.10 beta which support Windows 8.1 but in order to make it work there's a catch.

When you want to operate AMD, Intel needs to be on too. So it actually creates two "Displays"

One utilizing AMD, and the other Utilizing Intel. The trick is after logging in to change the default "Extend to Display 2" to only show to Display 1.

 

 

Well done dude! This has been a major cluster f*** for me. When I went into the Windows Resolutions settings it made me rage. Not because I saw 2 displays (usually only one) .. but because I saw 5 on my laptop.

Link to comment
Share on other sites

In extending mode Windows 8.1 does something weird, which I have seen in Surface.

It dedicates one Display ( Metro ) to one card, and the other Display (Desktop) to the other card.

When one wants to utilize only Intel, things are easy. Just disable AMD, or use only one display (it will use Intel)

When one wants to utilize AMD well you enable both cards, keep Intel on (because else it freaks out), and disable the monitor.

Kinda ****ed up, but the switchable graphics button on CCC is not always working seamlessly.

 

This way I'm updated to the maximum using official drivers from AMD, and Intel's from Microsoft.

Link to comment
Share on other sites

In extending mode Windows 8.1 does something weird, which I have seen in Surface.

It dedicates one Display ( Metro ) to one card, and the other Display (Desktop) to the other card.

When one wants to utilize only Intel, things are easy. Just disable AMD, or use only one display (it will use Intel)

When one wants to utilize AMD well you enable both cards, keep Intel on (because else it freaks out), and disable the monitor.

Kinda ****ed up, but the switchable graphics button on CCC is not always working seamlessly.

 

This way I'm updated to the maximum using official drivers from AMD, and Intel's from Microsoft.

 

I am still trying to find out of this is going to be the official way for switchable graphics under 8.1. Chances are very slim, since the button at times doesn't work and both cards stay active when on Intel which shouldn't be the case in normal circumstances like you mentioned.

 

But until some OEMs release a new Switchable graphics set for older gens we will not know how it works properly for 8.1.

 

My limited theory at the moment is that there will be no normal way to support 5xxxm and 6xxxm gen cards for 8.1 with one simple driver package (and I hope that I am wrong).

 

To me it seems like 7xxxm and 8xxxm have official Enduro support (which MS tried to replicate for the older gens), meaning that you can install Intel and AMD separately either way.

 

Simply put. AMD & OEMs dumped us like they did a long time ago and it will take another long while until we have stable drivers that work fully under Win 8.1.

Link to comment
Share on other sites

I have an Intel HD3000/7690m combo.

 

OEMs treat us like a red-headed stepchild too and AMD reference drivers don't work.

 

Really, installing Intel and AMD separately also doesn't really work either.

Link to comment
Share on other sites

I have an Intel HD3000/7690m combo.

 

OEMs treat us like a red-headed stepchild too and AMD reference drivers don't work.

 

Really, installing Intel and AMD separately also doesn't really work either.

 

Are you sure that the Enduro way doesn't work for you? Install Intel first on a clean environment. (the latest version)

 

And then after a restart install Mobility Catalyst drivers. Restart again for switchable menu.

Link to comment
Share on other sites

Are you sure that the Enduro way doesn't work for you? Install Intel first on a clean environment. (the latest version)

 

And then after a restart install Mobility Catalyst drivers. Restart again for switchable menu.

Yeah.  Mind you, I've not tried it in the last year, but I fought tooth and nail to try and get it working for Windows 8 when it first hit MSDN.  I would always end up with blue screens when switching, or black screens.  I did try updating my Catalyst drivers to the latest per an update prompt from the CCC software about a month ago, and it caused everything to implode.

 

IIRC, according to AMD, the only ones really supported by the reference drivers are the third gen Enduros (Ivy Bridge) and up.  From what I understand, those have no issue installing Intel and AMD separately.

Link to comment
Share on other sites

Well I can't complain now much.

I can use both cards in any way I want, it just needs few more clicks than simple switch button, which works about half the time.

Link to comment
Share on other sites

Of course, my card reads 7690m, but is a rebranded 6770m.

 

 

I do wonder if it has more to do with the fact that you are on sandybridge and not on ivy. What about Leshcats drivers? Have they given you any results?

Link to comment
Share on other sites

I do wonder if it has more to do with the fact that you are on sandybridge and not on ivy. What about Leshcats drivers? Have they given you any results?

They did when I last tried them.

 

I had the FTC issues with brightness, but other than that, they worked.

 

I stopped using Leshcat after HP delivered some Windows 8 drivers.  Which work in 8.1...sorta.

 

So I am going to be back to experimenting soon.

Link to comment
Share on other sites

They did when I last tried them.

 

I had the FTC issues with brightness, but other than that, they worked.

 

I stopped using Leshcat after HP delivered some Windows 8 drivers.  Which work in 8.1...sorta.

 

So I am going to be back to experimenting soon.

 

The inf in the Leshcat drivers was partly based on the new HP drivers. Obviously with 8.1 this is another ball game now and the same drivers might not be compatible anymore. Windows 8.1 uses a completely different installation method and I am sure that many people are wondering if HP or anyone will release an updated set.

 

I do have to mention that 8.1 does have backwards compatibility for Windows 8 drivers. So you could get lucky!

Link to comment
Share on other sites

The inf in the Leshcat drivers was partly based on the new HP drivers. Obviously with 8.1 this is another ball game now and the same drivers might not be compatible anymore. Windows 8.1 uses a completely different installation method and I am sure that many people are wondering if HP or anyone will release an updated set.

 

I do have to mention that 8.1 does have backwards compatibility for Windows 8 drivers. So you could get lucky!

They do work, but in some applications I get blurry text in 8.1.  I found a workaround, but I rather have a real fix.

Link to comment
Share on other sites

They do work, but in some applications I get blurry text in 8.1.  I found a workaround, but I rather have a real fix.

 

It could simply be one registry line that needs changing. It could be that this registry line is specific to your card and was not changed in the Leshcat driver because other models might not share it. This obviously relates back to the inf file. This is a large leap of faith on my behalf thinking that this is what causes the blurry text since I don't know the exact issue.

 

Either way .. if you knew what line is responsible for it then you could check what is missing and ask Leshcat to include it.

Link to comment
Share on other sites

It could simply be one registry line that needs changing. It could be that this registry line is specific to your card and was not changed in the Leshcat driver because other models might not share it. This obviously relates back to the inf file. This is a large leap of faith on my behalf thinking that this is what causes the blurry text since I don't know the exact issue.

 

Either way .. if you knew what line is responsible for it then you could check what is missing and ask Leshcat to include it.

I mean, the HP driver works.  I haven't tried Leshcat's drivers lately.  I am waiting for the upgrade 8.1 package...because I am lazy and don't want to reinstall all my stuff.

Link to comment
Share on other sites

This topic is now closed to further replies.