Glad to know you got the problem solved.  8^ )

It would be interesting (for future reference to others) if you would post whatever information you have (hardware, brand, source, etc.) as well as what is provided by dmesg, lspci, lsmod, etc.

Cheers,

A.

I read another link:
https://sgcdn.startech.com/005329/media … V2_QSG.pdf
and startech says to offer Linux Ubuntu.

The *.pdf also says this:

That link is to yet another *.pdf that says this:

There is no mention of Linux in what seems to be the *.pdf with "latest requirements" for this card/chipset.

The card selling at the site recommended by GNUser is the same one I made reference to.
If it turns out to be expensive, just shop around for any other PCIe card that has the same chipset.

ie: Texas Instruments XIO2213B controller

Cheers,

A.

Also, the FSF maintains the helpful h-node.org database. To see the firewire adapters in their database, go to duckduckgo.com and enter this search query: firewire site:h-node.org. If the "does it work with free software?" line says "yes" then the device will have universal GNU/Linux compatibility.

All available external/loadable kernel modules are listed in the file /lib/modules/<kernel_version>/modules.order. Another way to see which ones are available on your system is to list the .ko files. Something like this would work: find /lib/modules -name '*.ko'.

Built-in kernel modules (which are statically linked into the kernel image and are therefore always "loaded") are listed in the file /lib/modules/<kernel_version>/modules.builtin. These built-in modules are invisible to tools such as lsmod and modprobe.

Whether external or built-in, every kernel module that's currently in active use will have a corresponding directory under /sys/module/.

I'm on Devuan ASCII with a custom kernel and I didn't pay any attention to firewire during compilation. I have several firewire-related external modules available:

$ find /lib/modules -name '*.ko' | grep firewire
/lib/modules/4.16.2-gnu/kernel/drivers/firewire/firewire-ohci.ko
/lib/modules/4.16.2-gnu/kernel/drivers/firewire/nosy.ko
/lib/modules/4.16.2-gnu/kernel/drivers/firewire/firewire-net.ko
/lib/modules/4.16.2-gnu/kernel/drivers/firewire/firewire-core.ko
/lib/modules/4.16.2-gnu/kernel/drivers/firewire/firewire-sbp2.ko
/lib/modules/4.16.2-gnu/kernel/drivers/staging/fwserial/firewire-serial.ko
/lib/modules/4.16.2-gnu/kernel/drivers/media/firewire/firedtv.ko
/lib/modules/4.16.2-gnu/kernel/sound/firewire/digi00x/snd-firewire-digi00x.ko
/lib/modules/4.16.2-gnu/kernel/sound/firewire/motu/snd-firewire-motu.ko
/lib/modules/4.16.2-gnu/kernel/sound/firewire/fireface/snd-fireface.ko
/lib/modules/4.16.2-gnu/kernel/sound/firewire/bebob/snd-bebob.ko
/lib/modules/4.16.2-gnu/kernel/sound/firewire/snd-firewire-lib.ko
/lib/modules/4.16.2-gnu/kernel/sound/firewire/tascam/snd-firewire-tascam.ko
/lib/modules/4.16.2-gnu/kernel/sound/firewire/dice/snd-dice.ko
/lib/modules/4.16.2-gnu/kernel/sound/firewire/fireworks/snd-fireworks.ko
/lib/modules/4.16.2-gnu/kernel/sound/firewire/oxfw/snd-oxfw.ko
/lib/modules/4.16.2-gnu/kernel/sound/firewire/snd-isight.ko

I hope that helps troubleshoot your issue.

Windows is not Linux.  8-⁷
The Startech webpage for this card does not mention Linux support.

That said ...

The card uses the Texas Instruments Texas Intruments -TSB82AA2 chipset and Startech's vendorID is 14b0.

Looking up TSB82AA2+14b0 on the linux-hardware.org website, we get this.

----

Results for 'Texas Instruments', 'TSB82AA2', id='14B0-*', type='firewire controller', bus='PCI' (0)
No data

----

Given that it is a card you can probably replace for less than US$25, I suggest that you get one that has Linux support.
   
See this one with a different TI chipset.

There are probably a few others, you'll have to shop around.

Cheers,

A.

I tried with:

modprobe firewire-ohci

but with no result.

Device /dev/fw was not created.