Pages: 1
You should probably write your full reasoning to Tom's Hardware then and see if you can prove them wrong or perhaps set them upon a followup to point out the Microsoft Driver issue. I would say you would be the underdog in this fight but good luck though.atlvolunteer wrote:
Well, first of all, the CPU has nothing to do with how much power USB devices draw. This is limited by two things: a) the USB controller, which is generally part of the chipset on the motherboard and b) the USB specification, which specifies how much power a USB 1.1 or 2 device can draw. So to link it to the "Core Duo" processors is ridiculous. As to the "Core Duo" chipset, I assume they are referring to the 945(GM or PM), or, actually, the ICH7M. I work for a BIOS vendor, and I haven't heard of any problems with ICH7 and USB power consumption. About the only thing I have ever heard about the USB controllers in Intel chipsets is that they sometimes provide too little power to some USB devices that try to use more power than the USB spec. allows. However, if this is true, then it is probably Intel's fault. They don't rely on Microsoft to write drivers for their chipset. They write their own.
Last edited by kilroy0097 (2006-02-01 00:06:04)
I don't understand. You recommended that "those more technically educated that care about that sort of thing to read it." I did, and posted an opinion based on my knowledge of the field. Do you disagree with the facts I present?kilroy0097 wrote:
You should probably write your full reasoning to Tom's Hardware then and see if you can prove them wrong or perhaps set them upon a followup to point out the Microsoft Driver issue. I would say you would be the underdog in this fight but good luck though.atlvolunteer wrote:
Well, first of all, the CPU has nothing to do with how much power USB devices draw. This is limited by two things: a) the USB controller, which is generally part of the chipset on the motherboard and b) the USB specification, which specifies how much power a USB 1.1 or 2 device can draw. So to link it to the "Core Duo" processors is ridiculous. As to the "Core Duo" chipset, I assume they are referring to the 945(GM or PM), or, actually, the ICH7M. I work for a BIOS vendor, and I haven't heard of any problems with ICH7 and USB power consumption. About the only thing I have ever heard about the USB controllers in Intel chipsets is that they sometimes provide too little power to some USB devices that try to use more power than the USB spec. allows. However, if this is true, then it is probably Intel's fault. They don't rely on Microsoft to write drivers for their chipset. They write their own.
Do you think he disagrees with the facts you present? I would say yes.atlvolunteer wrote:
I don't understand. You recommended that "those more technically educated that care about that sort of thing to read it." I did, and posted an opinion based on my knowledge of the field. Do you disagree with the facts I present?kilroy0097 wrote:
You should probably write your full reasoning to Tom's Hardware then and see if you can prove them wrong or perhaps set them upon a followup to point out the Microsoft Driver issue. I would say you would be the underdog in this fight but good luck though.atlvolunteer wrote:
Well, first of all, the CPU has nothing to do with how much power USB devices draw. This is limited by two things: a) the USB controller, which is generally part of the chipset on the motherboard and b) the USB specification, which specifies how much power a USB 1.1 or 2 device can draw. So to link it to the "Core Duo" processors is ridiculous. As to the "Core Duo" chipset, I assume they are referring to the 945(GM or PM), or, actually, the ICH7M. I work for a BIOS vendor, and I haven't heard of any problems with ICH7 and USB power consumption. About the only thing I have ever heard about the USB controllers in Intel chipsets is that they sometimes provide too little power to some USB devices that try to use more power than the USB spec. allows. However, if this is true, then it is probably Intel's fault. They don't rely on Microsoft to write drivers for their chipset. They write their own.
Yeah, I guess it seems obvious he does. I guess I should have been more clear. Specify which statements you disagree with, and I will attempt to provide more data on the subject.RandomZer0 wrote:
Do you think he disagrees with the facts you present? I would say yes.atlvolunteer wrote:
I don't understand. You recommended that "those more technically educated that care about that sort of thing to read it." I did, and posted an opinion based on my knowledge of the field. Do you disagree with the facts I present?kilroy0097 wrote:
You should probably write your full reasoning to Tom's Hardware then and see if you can prove them wrong or perhaps set them upon a followup to point out the Microsoft Driver issue. I would say you would be the underdog in this fight but good luck though.
Last edited by atlvolunteer (2006-02-01 09:46:48)
It also describes the issue documented in KB899179. The wierd thing is that I can't find any reference to this Knowledge base article on Microsoft's website. Also, it sounds to me like the issue as they describe it would be fairly common and could occur any time a USB2 device is connect to a system running WinXP SP2, regardless of the chipset. It is strange that it only occurs with this particular chipset/CPU combination.it has been known to be a "problem" at least since 12 July 2005
http://discussions.hardwarecentral.com/ … p?t=169408I am still wondering how much of a bug it is from MS. They say it is a SP2 issue, but I have not seen them test it with SP1. They did test it on the Dothan and Turion64 and neither of those had this problem. They point at this bug from MS, but it sounds like an issue with Intel's south bridge.
...
Of course it could be that it is tied to the southbridge, but it somehow related to the CPU and the Yonah is having problems with a specific sleep mode (there are something like 5-7 sleep/halt modes total and 2 cores to deal with). Yes there might be a software work-a-round, but it might have to change what power mode the CPU uses when a USB 2.0 device is hooked up, but that sounds like it will be an Intel driver patch to me. I just have a hard time blaming MS when it is only this platform that has an issue.
If the solution is as simple as adding a registry key, why hasn't anybody tested it yet? It would only take a minute to add the key...For now, we are told that the solution to the matter could be simple: a simple addition of a single key to the Windows System Registry. At the time of this writing, neither Microsoft, Intel, nor Tom's Hardware Guide has had the opportunity to attempt this suggested fix to our Napa system. The engineers of Tom's Hardware plan on testing a Napa notebook with modified Registry settings and we will publish our findings as soon as they are available.
Pages: 1