locked
Driver question -PCI Simple Communications Controller

    Question

  • Low priority.

    After installing the software I went back through my driver install CD to get things working.  Everything is OK except something called PCI Simple Communications Controller.  It doesn't appear to be affecting anything adversely, but I can't find any info on it online.  All the threads I have Googled have pointed back to Microsoft's Update pages, which I do not yet want to tempt just yet.  I don't have any expansion cards.  My board is a DQ965GF.  Any suggestions?

    Monday, April 16, 2007 2:13 PM

Answers

  •     Hi, I have found the solution.  If you go in device manager, click on the pci simple communications controller, go in property and then go in details.  You will see a code like per example PCI/VEN_8086&DEV_27D8&SUBSYS...

    The VEN code means vendor and the DEV code means device: in my case the vendor is 8086 and the device is 27D8.

        Once you have the two codes, go to www.pcidatabse.com.  Enter the two codes and you should get the name of your

    hardware.  From there you can search for a driver download for your hardware.

        In my case the pci simple communications controller was a Microsoft UAA Bus HD audio.  I also had another pci

    device that didn't work properly, using the same method I found out that my pci device was an HSF PCI internal modem with code number CX11252-11.  I had a hard time downloading one of the drivers, after 6 or 7 times the download started so be patient if you have the same hardware

    .

        NOTE: to access the device manager, go in control panel, then performance and maintenance, system, hardware and finally device manager.

     

        Good luck.

    Thursday, December 27, 2007 4:14 PM
  • The 32 Bit drivers for XP Pro should work, just fine. 

     

    http://downloadfinder.intel.com/scripts-df-external/filter_results.aspx?strTypes=all&ProductID=2372&OSFullName=Windows*+XP+Professional&lang=eng&strOSs=44&submit=Go%21

     

    This is most likely the built-in Gigabit Ethernet Controller, or an added PCI modem.

    Monday, April 16, 2007 3:45 PM

All replies

  • Well, that board is part of Intel's desktop line. Unfortunately I don't see any Windows Server 2003 drivers for it on Intel's web site, which is likely to be the reason you're seeing that error. That's how Device Manager presents an unrecognized serial device, which could be any number of things. There's no easy way to tell except by checking Device Manager carefully to see if any of the expected MB devices are missing.
    Monday, April 16, 2007 3:05 PM
    Moderator
  • The 32 Bit drivers for XP Pro should work, just fine. 

     

    http://downloadfinder.intel.com/scripts-df-external/filter_results.aspx?strTypes=all&ProductID=2372&OSFullName=Windows*+XP+Professional&lang=eng&strOSs=44&submit=Go%21

     

    This is most likely the built-in Gigabit Ethernet Controller, or an added PCI modem.

    Monday, April 16, 2007 3:45 PM
  • I had a simular situation following the installation of WHS on a system I built to house it. My situation was the Gigabit Ethernet Controller needed a driver that Windows Server 2003 did not provide during setup. After I ran the driver and utilities CD from my mb, it installed the needed driver(s) and WHS properly connected to the router and therefor the Internet, automatically connected to automatic updates and downloaded and installed them. The server is great, I love it!

     

    Seree

     

    p.s. I am having difficulty with the font size here. Normal is extremely small, and large is extremely large. lol Sorry if this is too small, but my only other option is huge! ;-) 

    Monday, April 16, 2007 5:01 PM
  • i have got the same problem, and i still cant solve it!!!

     

    i have try all the latest drivers version on the intel website.... did you manage to fix it??

    Friday, June 22, 2007 8:49 AM
  • My solution to get the HECI driver to load was hack the inf file. I'm waiting for my RAID array to initialize right now so I can't reboot for a couple of hours but I'll see if it worked on next reboot, if it did my temp monitoring will be working. I built my new server last night and sure enough I noticed that Intel Desktop Utilities worked but no temp monitoring.

    To get the HECI driver to install I did the following: unpack the HECI driver files, open the HECI.inf in Notepad, under the Manufacturer and Models Section I removed the one line under [Intel.NTx86.5.2] and replaced it with the content from [Intel.NTx86.5.1]

    As soon as I pointed to the HECI folder it loaded, of course asking if I wanted to load this driver or not.
    Saturday, September 01, 2007 4:05 PM
  • After the reboot, all temps are monitored, just like it was when I tested the board in XP so this is a solution that works
    Sunday, September 02, 2007 2:23 PM
  • Awesome trick, worked like a charm...
    Thursday, October 25, 2007 8:32 PM
  • Usually a PCI Simple Communications Controller is an added PCI modem, but Doug is right in that it can be a serial device - after skimming through the drivers link for your board I noticed this:

     

    AMT: Intel® Active Management Technology Serial Over LAN (SOL) Driver  AMT: Intel® Active Management Technology Serial Over LAN (SOL) Driver 

     

    If you do not happen to also have a modem installed in the machine this may be the what you need.

    Thursday, October 25, 2007 9:14 PM
  • I had the same problem, took the modem out and googled the manufacturer.

    Downloaded and installed the drivers and the simple communications controller error went away.

    Hope this helps.

     

    Lawrence

     

    Friday, November 30, 2007 8:21 PM
  •     Hi, I have found the solution.  If you go in device manager, click on the pci simple communications controller, go in property and then go in details.  You will see a code like per example PCI/VEN_8086&DEV_27D8&SUBSYS...

    The VEN code means vendor and the DEV code means device: in my case the vendor is 8086 and the device is 27D8.

        Once you have the two codes, go to www.pcidatabse.com.  Enter the two codes and you should get the name of your

    hardware.  From there you can search for a driver download for your hardware.

        In my case the pci simple communications controller was a Microsoft UAA Bus HD audio.  I also had another pci

    device that didn't work properly, using the same method I found out that my pci device was an HSF PCI internal modem with code number CX11252-11.  I had a hard time downloading one of the drivers, after 6 or 7 times the download started so be patient if you have the same hardware

    .

        NOTE: to access the device manager, go in control panel, then performance and maintenance, system, hardware and finally device manager.

     

        Good luck.

    Thursday, December 27, 2007 4:14 PM
  • Sorry guys I had a typo for the pci database.  The link is www.pcidatabase.com. sorry

    Thursday, December 27, 2007 4:50 PM
  • Thank you very much! 

    This solved my problem in a heartbeat.  In my case, the problematic devices were related to drivers I had chosen not to download (from Intel's MB support site) because I didn't think I needed Intel's Management Engine Interface or Intel's Serial Over Lan.  Your instructions and www.pcidatabase.com enabled me to ID the devices and identify the additional drivers that I needed to download and install.


    Sunday, February 17, 2008 2:55 AM
  • Awesome!  Thanks for such helpful information!  This is a nice trick to know for the future too!

    Saturday, March 01, 2008 4:51 PM
  • hi doug

     i downloaded that and it said the my intel atm was disabled.   do you have any idea why or how to enable it

    Thursday, March 27, 2008 10:56 PM
  • hi marc

     ok i downloaded the intel active management technology and everything downloaded ok until the end  it said that the ATM is disabled.   do you know how to enable it??

    Friday, March 28, 2008 1:32 PM
  •  

    Great website, but my device is not found.

     

    29C4

     

    Any suggestions for what to try next?

     

    Thanks,

     

     

    Monday, April 14, 2008 2:39 PM
  • This thread might give you some clues, with an Intel board on W3K.

    Firefox 3 Beta 5 is having problems with the link facility here so copy and paste the URL.

    http://episteme.arstechnica.com/eve/forums/a/tpc/f/77909774/m/258002567831



    Monday, April 14, 2008 3:00 PM
  • I had the same issue with my Intell 33tl. Intels site said to install IMEI package. This fixed the device manager issue with PCI Comm Device.

    Hope this helps.

    Steve

     

    Friday, June 27, 2008 11:27 PM
  • Hi Zeusman,

     

    Thanks for an excellent tip. In my case it was the Intel Active Client Manager HECI Device for the DC7800CMT. It shows up as an unknown device: PCI Simple Communications Controller - PCI\VEN_8086&DEV_29B4. If people are having the same issue the Hyperlink is attached to the device name (HECI).

     

    Thanks.

    Monday, June 30, 2008 9:19 AM
  • Hi Sassym20,

     

    I had the same issue on the HP DC7800CMT, it was reporting it was disabled.

     

    In device manager there were two unknown devices:

     

    PCI Simple Communications Controller - Intel Active Client Manager HECI Device

    PCI – Unknown Device - Intel AMT LMS_SOL for AMT 3.xx

     

    Once both of these were installed the status changed to enabled and an icon will be present next to the clock.

    Monday, June 30, 2008 9:27 AM
  • I have a slightly different problem.  I put a pci modem in the computer and the computer is calling it a "simple pci communication controller".  I have a driver for the modem but when updating the driver for the "simple pci communication controller, it doesn't recognize it as valid.  If I try to install the modem manually without plug and play it says I don't have a modem connected to the pc.  Any help would be great. 

     

    Friday, July 11, 2008 7:12 PM
  • cwkellerjr,

    What hardware are you trying to install this modem on? If this is in your server, then don't forget that the drivers should be Server 2003 compatible, if possible.

     

    Colin


     

    Friday, July 11, 2008 7:32 PM
  • It's just a PC with XP.

     

    Friday, July 11, 2008 7:44 PM
  • OK,

    Have you tried installing without plug and play, then, go to the Hardware page of My Computer - System Properties and select Device Manager . From here, 'right-click' the offending item and choose Update Driver. This should allow you to select 'update from the web'; try that first, see if it can find a driver, if not, then go through the process but select 'no not this time', that way, you will be offered the choice of installing your driver from your own location.

     

    Colin

    Friday, July 11, 2008 7:54 PM
  • Unfortunately, this is a computer for my mother who only has dial-up access to the internet.  (Hence the modem.)  I got the driver myself and put it on a flash drive.  When I update the PCI Simple Communications Controller driver and point it to the .inf file it says it didn't find anything.  I then tried to add a modem myself.  When it looks for a device connected to the computer it only finds the PCI Simple Communications Controller and says there is no modem connected to the PC.  I have installed the driver anyway but that does no good since the PC doesn't see a modem.

     

    I have tried to just find a driver for the PCI Simple Communications Controller but haven't had any luck.

     

    I will try anything.

     

    Chad

    Friday, July 11, 2008 9:02 PM
  • Chad, it's possible that you have the wrong driver, or that it's not a modem. Microsoft has a knowledgebase article about how to identify the PCI Simple Communications Controller device you're having problems with.
    Saturday, July 12, 2008 3:20 AM
    Moderator
  • As far as the Management Engine driver is concerned, you may have better luck if you use something like Universal Extractor to extract files out of the installer. It's a regular InstallShield installer that archives the files using the same MSZIP scheme as Microsoft CAB archives. Edit heci\heci.inf, remove the Intel.NTx86.5.2 section (the one that says NT 5.2 aka Windows Server 2003 isn't supported in the comment), and rename the Intel.NTx86.5.1 section to Intel.NTx86.5.2. Then start up Device Manager, right click on the appropriate driverless entry, click Update Driver, tell it you want to specify where to find the driver, tell it you'll choose the driver to install, hit the Browse button and navigate to the directory containing heci.inf. Windows should be able to find the driver. It'll complain about it not being signed or verified for the device, but it'll install. Good luck.
    Thursday, July 31, 2008 3:40 AM
  • Hi Zeusman,

    I have the similar problem but on the link, it show 10 different links, where do I go and enter the codes?

    Thanks,

     

    Mani

    Saturday, May 30, 2009 1:06 AM