Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

3rd Party Driver for IEEE 1394 bus controllers will not install


  • Please log in to reply
7 replies to this topic

#1 jhp016s

jhp016s

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:32 AM

Posted 22 October 2016 - 07:18 PM

I am trying to install the "firepro" driver to be able to use a pointgrey camera on my computer. I am trying to install it by clicking on it in the devices tree>right clicking>choose update driver>browse my computer for software>use disk>browse

Then I am getting the driver from the Pointgrey folder. When I click next it tells me "the folder doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows 32 bit systems.

According to pointgrey I do have the 32 bit version of their software installed. They remoted in and tried a bunch of things but couldn't figure it out. In the end they said I needed to get a Firewire PCIe card that had a LSI chipset instead of a VIA chipset. Does this sound right? Why would this make a difference in installing a driver. 

I am running Windows 7, 64 bit

 

I have also tried to install the 64 bit firepro driver and I get the same error except it says make sure the folder contains a driver to work with windows 64 bit systems

 

I have opened up the .inf file and when I read through it, it does list LSI and TI chipsets in the file.  Is it possible that this is the reason its not letting me install, seems weird.

Any help would be appreciated before I go buy this PCIe card.



Thanks



BC AdBot (Login to Remove)

 


#2 JohnC_21

JohnC_21

  • Members
  • 23,970 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:32 AM

Posted 22 October 2016 - 07:26 PM

Right click the IEEE device in Device Manager. Select Properties and under the Details tab select Hardware Ids in the dropdown box. Copy and Paste the first line into your next post. 

 

Is the Vendor and Device ID along with the Subsys number in the the 64bit inf file?


Edited by JohnC_21, 22 October 2016 - 07:27 PM.


#3 jhp016s

jhp016s
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:32 AM

Posted 22 October 2016 - 07:50 PM

PCI\VEN_1106&DEV_3044&SUBSYS_30441106&REV_80
 
I didn't see anything labeled subsys.
 
I also didn't see anything for Vendor
 
 
 
THis is what I found for device id's:
 
[Manufacturer]
%MfgName% = PGR1394b_Mfg,NTamd64
 
[PGR1394b_Mfg]
; DisplayName               Section           DeviceId
 
%PGR1394b_DeviceDesc1%=PGR1394b_DDI, PCI\VEN_104C&DEV_8019
%PGR1394b_DeviceDesc1%=PGR1394b_DDI, PCI\VEN_104C&DEV_8020
%PGR1394b_DeviceDesc1%=PGR1394b_DDI, PCI\VEN_104C&DEV_8023
%PGR1394b_DeviceDesc1%=PGR1394b_DDI, PCI\VEN_104C&DEV_8024
%PGR1394b_DeviceDesc1%=PGR1394b_DDI, PCI\VEN_104C&DEV_8029
%PGR1394b_DeviceDesc1%=PGR1394b_DDI, PCI\VEN_104C&DEV_8032
%PGR1394b_DeviceDesc1%=PGR1394b_DDI, PCI\VEN_104C&DEV_803A
%PGR1394b_DeviceDesc1%=PGR1394b_DDI, PCI\VEN_104C&DEV_8235
%PGR1394b_DeviceDesc2%=PGR1394b_DDI, PCI\VEN_104C&DEV_8025
%PGR1394b_DeviceDesc2%=PGR1394b_DDI, PCI\VEN_104C&DEV_823F
%PGR1394b_DeviceDesc4%=PGR1394b_DDI, PCI\VEN_11C0&DEV_5901
%PGR1394b_DeviceDesc4%=PGR1394b_DDI, PCI\VEN_11C1&DEV_5901
%PGR1394b_DeviceDesc5%=PGR1394b_DDI, PCI\VEN_11C1&DEV_5811
 
THis is the part where I saw the chipset requirements:
 
;--------- Strings Section ---------------------------------------------------
 
[Strings]
Provider = "Point Grey Research"
MfgName = "Point Grey Research"
PGR1394b_DeviceDesc1 = "Texas Instruments OHCI Compliant IEEE 1394a Host Controller"
PGR1394b_DeviceDesc2 = "Texas Instruments OHCI Compliant IEEE 1394b Host Controller"
PGR1394b_DeviceDesc4 = "LSI (Agere) OHCI Compliant IEEE 1394b Host Controller"
PGR1394b_DeviceDesc5 = "LSI (Agere) OHCI Compliant IEEE 1394a Host Controller"
PGR1394b_DeviceDesc7 = "PGR1394 Device"
 
DeviceClassName="Point Grey Bus Host Controllers"
PGR1394b_SvcDesc = "Point Grey Bus Host Controllers"
DiskId1 = "PGR1394b Device Installation Disk #1"
 
 


#4 JohnC_21

JohnC_21

  • Members
  • 23,970 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:32 AM

Posted 22 October 2016 - 09:54 PM

That chipset is a 

 

0x3044 VIA Fire II 1394a OHCI Link Layer Ctrlr1 0x1106  

 

So far I have only found 32bit drivers for this chipset. I will have to do a little more searching to see if 64bit is available.

 

If you select Update Driver in Device Manager does it find it over the internet or is it available under optional updates in Windows Update?

 

Per this video, see if swapping the legacy driver for 1394 works.


Edited by JohnC_21, 22 October 2016 - 10:04 PM.


#5 jhp016s

jhp016s
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:32 AM

Posted 22 October 2016 - 11:14 PM

It will update over the Internet. I am also able to install all 4 drivers available in device manager, Windows and Windows legacy, as well the two VIA drivers signed and unsigned. The problem is that with all of these drivers, third party applications are unable to recognize the cameras even though the computer lists them as working. Pointgrey is basically saying I need their driver installed (FirePro driver) for third party apps to use the cams but it keeps denying the install saying folder doesn't contain a compatible file, make sure their is a 32 bit driver or 64 bit driver (I have tried both options from point grey).

#6 Platypus

Platypus

  • Moderator
  • 14,657 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Australia
  • Local time:09:32 PM

Posted 23 October 2016 - 06:43 AM

I believe Point Grey are correct, and their virtual device driver will only interface with TI or Agere Firewire chips, as indicated by the installer manifest. It's a fairly well known issue with Firewire, long standing advice for compatibility has been to avoid VIA and use TI if possible. My own first experience building a system incorporating Firewire into a Pentium 1 PC followed that path - a (cheaper) VIA board wouldn't work with some things, got one with a TI chip, no problems ever.

Top 5 things that never get done:

1.


#7 jhp016s

jhp016s
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:32 AM

Posted 23 October 2016 - 11:53 AM

Thanks everybody for the input on trying to get me going.  Do you all think this card will suffice it says it has a TI chipset:

 

https://www.amazon.com/Combo-Firewire-PCI-Express-Controller-Chipset/dp/B01E55O9KM/ref=sr_1_7?ie=UTF8&qid=1477241250&sr=8-7&keywords=ti+firewire+controller



#8 Platypus

Platypus

  • Moderator
  • 14,657 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Australia
  • Local time:09:32 PM

Posted 23 October 2016 - 05:06 PM

As far as we can tell from the info given, looks like it should suit the purpose.

Top 5 things that never get done:

1.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users