TI Firewire Card Driver Issue

[petergoode]

I am not sure if this is the correct forum for this question, so please
accept my apologies in advance if I should have placed it in a different
category...

My question pertains to Windows XP Pro SP2 installation of drivers for my
Texas Instruments OHCI Compliant IEEE 1394 Host Controller (firewire card).

When I originally installed the card in the old XP Home SP2 system, it was
automatically installed with drivers contained in the OS, there was no
separate cd with drivers provided with the card.

I moved the card over to a new XP Pro SP2 system, and upon booting, the OS
asks to be directed to a disc or folder with the appropriate driver.

A web search led to identification of a file called GIC
220U-ALi-33s-1-4-7.zip which extracted to EHCI_147.exe, but when I run it, it
asks "Windows XP SP1 has USB 2.0 controller inbox driver. Do you want to
install ALi usb 2.0 controller driver?"

I have absolutely no idea what the implications might be if I run that.

If anyone can provide some guidance, it would be greatly appreciated...thanks!



Peter

 

[Paul]

I am not sure if this is the correct forum for this question, so please
accept my apologies in advance if I should have placed it in a different
category...

My question pertains to Windows XP Pro SP2 installation of drivers for my
Texas Instruments OHCI Compliant IEEE 1394 Host Controller (firewire card).

When I originally installed the card in the old XP Home SP2 system, it was
automatically installed with drivers contained in the OS, there was no
separate cd with drivers provided with the card.

I moved the card over to a new XP Pro SP2 system, and upon booting, the OS
asks to be directed to a disc or folder with the appropriate driver.

A web search led to identification of a file called GIC
220U-ALi-33s-1-4-7.zip which extracted to EHCI_147.exe, but when I run it, it
asks "Windows XP SP1 has USB 2.0 controller inbox driver. Do you want to
install ALi usb 2.0 controller driver?"

I have absolutely no idea what the implications might be if I run that.

If anyone can provide some guidance, it would be greatly appreciated...thanks!

Peter

Obviously, something isn't right.

You can start, by going to Device Manager. In WinXP, if you do
Properties on a Device, then use the Details tab, and look for
"Device Instance ID", you get a text string that looks like this.
This is for the USB2 controller on my motherboard.

PCI\VEN_1106&DEV_3104&SUBSYS_31041849&REV_90\3&267A616A&0&84

See if you can locate that string, and post it for feedback.
The VEN and DEV values are the most important.

The VEN and DEV values are informally maintained in this file,
if you want to look them up yourself. There are also utilities
that can assign a name to them, but at the moment, it is more
important to get the string, in case something funny is
going on.

http://pciids.sourceforge.net/pci.ids

A separate file is used to hold the identities of USB devices.
That file is also informally maintained.

The official registries keep the IDs secret. The informally
maintained files, may not contain all existing devices, so
the system is less than perfect.

Paul

 

[petergoode]

Thanks for trying to help with this.

Here is the string shown for the device id for the multimedia controller
(Firewire card):

PCI\VEN_1131&DEV_7146&SUBSYS_00031809&REV_01\5&F334E6&0&3008F0

Though I am moderately experienced with PC software, I am not as good on
hardware, and really have no idea what this means...but if it helps with the
troubleshooting, there it is!

Thanks again.

pg

 

[smlunatick]

I am not sure if this is the correct forum for this question, so please
accept my apologies in advance if I should have placed it in a different
category...

My question pertains to Windows XP Pro SP2 installation of drivers for my
Texas Instruments OHCI Compliant IEEE 1394 Host Controller (firewire card).

When I originally installed the card in the old XP Home SP2 system, it was
automatically installed with drivers contained in the OS, there was no
separate cd with drivers provided with the card.

I moved the card over to a new XP Pro SP2 system, and upon booting, the OS
asks to be directed to a disc or folder with the appropriate driver.

A web search led to identification of a file called GIC
220U-ALi-33s-1-4-7.zip which extracted to EHCI_147.exe, but when I run it, it
asks "Windows XP SP1 has USB 2.0 controller inbox driver.  Do you want to
install ALi usb 2.0 controller driver?"  

I have absolutely no idea what the implications might be if I run that.

If anyone can provide some guidance, it would be greatly appreciated...thanks!

Peter

This ALi download appears to be for an ALi based USB 2.0 controller
and you are looking for Firewire / iLink drivers. USB and Firewire
are two different technologies.

 

[Paul]

Thanks for trying to help with this.

Here is the string shown for the device id for the multimedia controller
(Firewire card):

PCI\VEN_1131&DEV_7146&SUBSYS_00031809&REV_01\5&F334E6&0&3008F0

Though I am moderately experienced with PC software, I am not as good on
hardware, and really have no idea what this means...but if it helps with the
troubleshooting, there it is!

Thanks again.

pg

According to pci.ids, that is a Philips SAA7146 ???

Using part of that string in a search, suggests
the card is a "DELL MOVIE STUDIO VIDEO DEVICE" ???

http://www.drivershq.com/Drivers/Devices/Dell-Emuzed-Movie-Studio-Driver/31002/20/Drivers.aspx

And then, we get closer still. Product is "Emuzed Atlantis",
with some rebranding along the way. There could be more
than one version of the card in existence.

http://www.lumanate.com/Downloads/Docs/Atlantis-I PCI Brief_112602.pdf

http://web.archive.org/web/20030207221125/http://www.emuzed.com/products_atla_pci.html

http://i1.ebayimg.com/08/i/000/f2/94/4ca8_1.JPG

http://support.dell.com/support/edocs/storage/Legacy/video/s51903/en/intro.htm

On the Dell site, I can find this "patch" DMSPHWPatch-A00.exe (says 1.39)

http://search.dell.com/results.aspx...ra=False&~srd=False&ipsys=False&advsrch=False

When I look inside that 7MB download, and look at one of the config
files with notepad, this is what I see.

SAA7146=PCI\VEN_1131&DEV_7146&SUBSYS_00031809&REV_01
PCIBridge=PCI\VEN_104C&DEV_AC28&SUBSYS_00000000&REV_01
1394Link=PCI\VEN_104C&DEV_8023&SUBSYS_00021809&REV_00
Audio=ZBUS\AUDIO

That means the card is a composite device. The card connects to the
PCI bus, with a PCI to PCI bridge. That isolates the PCI bus of
the PC, from the extended PCI bus travelling through the card.

SAA7146 Texas Instruments
Video TSB43AB22/A Firewire chip
| |
---+---------+--------+--- On-card PCI Bus
|
PCI Bridge
|
v
( Motherboard_PCI_Slot )

The VEN_104C&DEV_8023 of the 1394 Link, is your Firewire chip.

104c Texas Instruments
8023 TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)

It could be, that a PCI bridge driver might be needed, to make
the stuff on the other side of the bridge, visible to the system.
That might or might not already be in Windows.

The original CD that came with the card, is undoubtedly a source
of inspiration, as the drivers in there may hint at what is
needed to get the thing installed. I don't know what that
7MB "patch" above, does to the installation. I don't know
if it is a full driver package, or needs whatever was already
installed by the CD, to work. There is mention of a hardware
diagnostic, which is used to test that the contents of the
card are recognized.

Looking at one of the other files, it looks like the Atlantis
driver deals with SAA7146 video and audio, leaving it to default
systems drivers to handle PCIbridge and IEEE1394 Firewire.

This is much more than a simple Firewire card

I don't have any composite devices here, so cannot
provide any first hand experience with how they work,
as far as the contents of Device Manager and its display.

Paul