Quantcast
Channel: Intel Communities : Discussion List - Chipsets
Viewing all articles
Browse latest Browse all 3841

Surface Pro (2) performance problems when iRST drivers are used

$
0
0

Hi,

 

I have been doing deployments of Windos 8.1 RTM with Microsoft Surface Pro 1 and 2 tablets.

What I've noticed is that when the iRST (hdc / iahcic) drivers are used in WinPE, and subsequently during offline injection or pre-staging, the tablets start to behave ultra slow! It's not workable anymore, and all actions take forever to complete.

 

I've tested and reproduced this behavior with:

iaAHCIC version 12.8.0.1016

iaAHCIC version 12.9.0.1001

 

Solution

When I only apply the LxLpAHCI driver (version 9.4.0.1021) as supplied in the latest Jan 2014 Surface Pro 2 driver pack, all works properly.

 

 

Only, I'd like to utilize a generic driver set of Mass Storage drivers without having to discriminate between hardware model, IMHO a pnp id should be leading to which driver get applied... which now does not work as both drivers iaAHCIC and LxLpAHCI use the same pnp id (PCI\VEN_8086&DEV_9C03) detection in their inf file.

 

For driver injection and pre-staging this is doable to distinct between hardware models and apply the proper driver.

However, for WinPE (5.0) this will become quite a bit harder when wanting to utilize a generic WinPE for multiple models, thus having to inject the iaAHCIC driver, post Win8.1 RTM hardware models, to be injected in WinPE 5.0.

 

A quick peek in getting to see the difference in operation between these drivers is that:

iaAHCIC uses MSISupported (= 1)

LxLpAHCI utilizes Windows native driver mshdc which has MSISupported off (= 0)

 

Or, could it be power management problems that are causing this behavior in the iaAHCIC drivers?

 

Is this a bug, or do I really have to mind even my WinPE 5.0 to be more loading drivers dynamically (using script) based on hardware model?


Viewing all articles
Browse latest Browse all 3841

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>