If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#16
|
|||
|
|||
USB Controller list in Device Manager
Big E wrote:
We’re getting into an area where I don’t know the nuts and bolts, but with logic and your help, I’m learning. If it has screws, plugs and knobs, I’m all over it otherwise. I’m not a big fan of hot fixes either for similar reasons. I looked at the USBMan website info but I didn’t try anything there yet as none of the PCI slots seem to be working correctly at this point so the problem seems bigger than the SiS 7001. Everest recognizes both the onboard SiS USB and the NEC USB card for what they are as far as I can tell though I’m far from being an expert. The video card (Gigabyte GeForce FX 5200) shows up correctly as well. The audio card (Echo Mia) is another story altogether as Microsoft would have no data for that one. It shows up as Multimedia Controller [NoDB]. I’ll try a reinstall on that one later. As far as the CPU chip goes, I’m guessing that the folks who assembled the mobo only had 3.4GHz chips on hand. The board is designed to run at 2.8GHz, 800MHz FSB with a Prescott chip, hence the discrepancy. Clock info from CPU-Z and Everest as follows: Per CPU-Z CPU core speed 2806.5 Mhz Multiplier 14.0 Bus Speed 200.5 MHz Rated FSB 801.8 MHz Per Everest: CPU Clock: floats around 2804.65 to 2808.13 MHz Multiplier: 14.0 FSB: 200.33 to 200.58 MHz Memory bus same as FSB Seems to me not too far off the mark. The Award BIOS date is 12/28/04 and the version number matches the last one released by Foxconn though their website says it was released in 2007. Go figure. I’m reluctant to use a third party update - I’ve seen those royally hose up a machine. BIOS SuperSpeed set at 200 MHz (allowable range 200 – 232). On the Frequency/Voltage Control page, items listed are as follows: Auto Detect DIMM/PCI Clk: Enabled Spread Spectrum: Disabled CPU DRAM Frequency: SPD I haven’t found anything that specifically states at what speed the PCI bus is running. AGP must be OK, otherwise I probably wouldn’t be able to see what I’m typing. The installed memory is currently now 2GB PC-3200 400 MHz; was 1GB 400 MHz when I started this thread. What’s next? Thanks. OK. I hadn't considered the possibility of a mismatch between the Vcore regulator capabilities and the processor's power class. I'm having trouble remembering the right technical language now, but basically the BIOS checks the conditions, finds say an 04B processor, realizes the Vcore is only designed for 04A, and can select the fallback value for the multiplier. So instead of x17, it is using x14. This is also why 2.8GHz processors have no fallback option, because they're already at x14 multiplier. (Prescott PRB=0 and PRB=1 bit, indicates power requirements) http://download.intel.com/design/Pen...s/30056103.pdf If it was a Prescott, the geometry would be listed as 90nm instead of 0.13u. When Prescotts came out, they had a pin definition changed on the bottom of them, which detected whether the motherboard was "Prescott Ready". The processor itself, would refuse to start, if the pin was in the wrong state. Thus, for many people, there isn't any fallback case to consider, because it won't run at all. I don't know what happens, if you bust off, or insulate the pin as appropriate, to override the behavior. (The pin on the bottom of the chip, is a different issue than the PRB enumeration from an internal processor register.) In checking the info from Foxconn, it does say the motherboard supports Prescott. But it doesn't say anything about power class. And looking at the motherboard picture in the manual, the board has a two phase regulator ??? So that would explain Foxconn throttling back on the multiplier. Kinda a pointless design feature - if you support Prescott, why go for a gutless Vcore ? Prescott was the king of power consumption, and should have a decent regulator. (This may, in fact, be the first motherboard I've run into, that made that kind of design decision. Intel provided for this possibility, but I cannot say I've seen many motherboards using the feature.) So that provides a partial explanation of the frequency, and based on your info that the input clock is 200MHz, there is no reason to suspect the PCI or AGP clock. I just figured someone had messed around, to get it to run at 2.8GHz. (200/6 = 33Mhz, 200 is a canonical frequency, and dividers would be set properly for it.) The "Multimedia Controller [NoDB]" is coming from Everest and its own internal database. Which is perfectly normal. I have hardware here which cannot be identified. What I like Everest for, is giving the DeviceID, so I can look up the hardware myself. The official PCI registry is not available to the public, so instead we have to rely on the publicly maintained list of DeviceIDs. (Either that, or buy a current copy of Everest from Lavalys :-) ) Leftmost column is VEN, next is DEV, and the third level is SUBSYS. http://pciids.sourceforge.net/v2.2/pci.ids You can verify the DeviceID and other numbers, do map to the product (if it is in that file). And the most important part, is that the VEN/DEV/SUBSYS appears in the INF file of the driver installer for the product. There has to be a match, for it to work. The purpose of looking in Everest, is to check that the DeviceID type information, agrees with the INF file of the installer you're using. I'm guessing at this point, that the hardware is fine, and something is going on with drivers. There is an example here, of a place where corruption can occur. "XP asks for drivers" http://www.uwe-sieber.de/usbtrouble_e.html First link involves "driver.cab", the second "the data is invalid" (a registry settings issue). http://groups.google.ca/group/micros...f?dmode=source I'm not suggesting that you run off and try any of those! Those are just examples of corruptions that can occur in Windows, and either screw up the installation of hardware, or result in requests to install drivers again. I'm thinking it is a software problem, but I don't recognize the symptom of finding "extra" unrecognized entries in Device Manager. Paul |
Thread Tools | |
Display Modes | |
|
|