You are here

Firewire major problem with brand new system.

For anything relating to music-making on Windows computers, with lots of FAQs. Moderated by Martin Walker.

Re: Firewire major problem with brand new system.

Postby Pete Kaine » Wed Jan 08, 2020 1:40 pm

hardminder wrote:I plugged the PCIe Firewire card
https://www.siig.com/products/it-produc ... -pcie.html
to my new one. There the fun began...

No display, the lights on my Saffire are on, so the power is travelling, the fans on the GPU are on but no display. When I disconnect the firewire card, I get a display. Everything works fine.

I read online that this specific SIIG card has compatibility issues with a lot of other devices/boards, so I went to buy another one, another brand. Found that one on Amazon.

https://www.amazon.ca/gp/product/B07C8Z ... UTF8&psc=1

I'm feeling too lazy to trawl through the whole thread, but this should be the answer.

Your original card was based around the XIO2200 chipset which whilst recommended for the longest time, it was replaced about a decade ago by TI and this was before W7 came out, let alone W10.

Microsoft removed support for the XIO2200 chip in W10 a while back and the advice is to find a card with a XIO2213A or XIO2213B varient, which will also be a 3 port card.

The card you bought to test recently seems to be based around the ViA controller and I'm not overly surprised that didn't work, compatability there for audio handling has always been patchy.
User avatar
Pete Kaine
Frequent Poster (Level2)
Posts: 3135
Joined: Thu Jul 10, 2003 12:00 am
Location: Manchester
Kit to fuel your G.A.S - https://www.scan.co.uk/shop/pro-audio

Re: Firewire major problem with brand new system.

Postby hardminder » Sun Jan 12, 2020 10:55 pm

Pete Kaine wrote:
hardminder wrote:I plugged the PCIe Firewire card
https://www.siig.com/products/it-produc ... -pcie.html
to my new one. There the fun began...

No display, the lights on my Saffire are on, so the power is travelling, the fans on the GPU are on but no display. When I disconnect the firewire card, I get a display. Everything works fine.

I read online that this specific SIIG card has compatibility issues with a lot of other devices/boards, so I went to buy another one, another brand. Found that one on Amazon.

https://www.amazon.ca/gp/product/B07C8Z ... UTF8&psc=1

Your original card was based around the XIO2200 chipset which whilst recommended for the longest time, it was replaced about a decade ago by TI and this was before W7 came out, let alone W10.

Microsoft removed support for the XIO2200 chip in W10 a while back and the advice is to find a card with a XIO2213A or XIO2213B varient, which will also be a 3 port card.

I just bought that card. I didn't see your post before ordering it :
https://www.vantecusa.com/products_deta ... ards#tab-2

The chipset is listed as XIO1223B. I see it with my own eyes "XIO1223BZAY". I get the exact same result as I did with my first card : no display on my monitors, no way to tell if the system boots completely. When I unplug the card, everything runs normally.

I purchased a second hand Scarlett 18i6 for 60$ for the moment. My suggestion for anyone with a new W10 system and a Firewire interface would be not to lose your time with it. Get yourself a USB interface. I tried 4 different PCIe firewire cards, including one with the advised chipset, with no sucess.

Thanks to anyone who tried helping but I think firewire interfaces will soon be a thing of the past, sadly, mine was still in perfect working condition.
hardminder
Poster
Posts: 39
Joined: Thu Nov 07, 2019 8:22 am
OS : Windows 10 Pro 64x
Mobo : Asus Prime X-570P
CPU : AMD Ryzen 7 3800-X
GPU : Not relevant!
Memory : 2x16gb DDR4 RAM
Storage : 2x1tb M.2
PSU : EVGA 500BQ
Cubase 10 Pro

Re: Firewire major problem with brand new system.

Postby Martin Walker » Sun Jan 12, 2020 11:18 pm

hardminder wrote:My suggestion for anyone with a new W10 system and a Firewire interface would be not to lose your time with it. Get yourself a USB interface. I tried 4 different PCIe firewire cards, including one with the advised chipset, with no sucess.

Thanks to anyone who tried helping but I think firewire interfaces will soon be a thing of the past, sadly, mine was still in perfect working condition.

I tend to go along with this advice - to my mind Firewire has long been a source of PC compatibility problems due to Firewire card chipsets, and when I recently bought a new interface I opted for USB.

There may be question marks about USB low latency performance with some audio interfaces, but I bypassed these issues by choosing an RME interface, since their drivers are renowned for their performance.


Martin
User avatar
Martin Walker
Moderator
Posts: 15195
Joined: Wed Jan 13, 2010 9:44 am
Location: Cornwall, UK

Re: Firewire major problem with brand new system.

Postby OneWorld » Mon Jan 13, 2020 4:45 pm

Martin Walker wrote:
hardminder wrote:My suggestion for anyone with a new W10 system and a Firewire interface would be not to lose your time with it. Get yourself a USB interface. I tried 4 different PCIe firewire cards, including one with the advised chipset, with no sucess.

Thanks to anyone who tried helping but I think firewire interfaces will soon be a thing of the past, sadly, mine was still in perfect working condition.

I tend to go along with this advice - to my mind Firewire has long been a source of PC compatibility problems due to Firewire card chipsets, and when I recently bought a new interface I opted for USB.

There may be question marks about USB low latency performance with some audio interfaces, but I bypassed these issues by choosing an RME interface, since their drivers are renowned for their performance.


Martin

I still have a Firewire setup and that remains working even after the latest Win10 update. My firewire card is a Sonnet Technologies Allegro FW800-E PCIe-to-FireWire 800 TI XIO2213 and it works with a Focusrite Liquid 56

However, I sort of get the feeling that Firewire days are numbered. Next interface purchace will be USB3 (if there are any USB3 interfaces about). That said, I also bought into MLAN (dodged a bullet there!) and now of course there is Thunderbolt - when will manufacturers settle on one standard like they did with MIDI, and as far as I know, ethernet can be used which is ubiquitous and can handle sustained transfer of large amounts of data? - doesn't Dante do that?
OneWorld
Frequent Poster (Level2)
Posts: 2719
Joined: Tue Apr 07, 2009 12:00 am

Re: Firewire major problem with brand new system.

Postby tboydva » Wed Feb 26, 2020 11:59 am

Hi all - going to chime in here. I have a Focusrite Saffire Pro 40. Personally, I've had great success with firewire over the years (DV, scanners, audio interfaces). While USB was buggy and slow and latency-prone, my m-audio (can't recall the model) always worked like a charm. Anyway, I upgraded - maybe in December - to the latest Win10 (greater than 1809). I too now have problems. I've tried two separate firewire cards - both with the TI chipset. Works OK after a reboot but eventually, the communication will cease between the card and device (audio interface or scanner). On occasion, the system will lock up bad - then it turns black with the fans maxed out until shut down manually. No core dump. I wasn't aware that Focusrite warned about upgrading past 1809. Now I have to determine if I "go back." From my reading around the web, this seems to be a windows issue - not hardware. My hardware worked fine on 1809, then I wiped and reinstalled 1903 and firewire started acting buggy... Really sucks!
tboydva
Posts: 1
Joined: Wed Feb 26, 2020 11:53 am

Re: Firewire major problem with brand new system.

Postby Martin Walker » Wed Feb 26, 2020 10:43 pm

Hi tboydva, and welcome to the SOS Forums! 8-)

Also, thanks for such a useful first post :thumbup:


Martin
User avatar
Martin Walker
Moderator
Posts: 15195
Joined: Wed Jan 13, 2010 9:44 am
Location: Cornwall, UK

Re: Firewire major problem with brand new system.

Postby Pete Kaine » Thu Feb 27, 2020 3:53 pm

So, in the meantime since the first post I've seen this myself and it's also why I pulled the Prime X570 from my specs over the last few weeks.

Some point between launch and now there has been a BIOS update that breaks Firewire support. If you roll back to the earlier ones, you should be able to find a BIOS that still works, although given the fixes rolled out recently, I'd be loathed to do so.

I escalated it, they said they'd look into it and I've pulled the hardware until they come back with an answer I'm happy with.

hardminder wrote:The chipset is listed as XIO1223B. I see it with my own eyes "XIO1223BZAY". I get the exact same result as I did with my first card : no display on my monitors, no way to tell if the system boots completely. When I unplug the card, everything runs normally.

Yes, sorry, it's a new fault specific to that mainboard range.

hardminder wrote:I purchased a second hand Scarlett 18i6 for 60$ for the moment. My suggestion for anyone with a new W10 system and a Firewire interface would be not to lose your time with it. Get yourself a USB interface. I tried 4 different PCIe firewire cards, including one with the advised chipset, with no sucess.

Ironically they tend to work fine over a Thunderbolt connection + converter. The question is if it is worth it to buy the AIC+Converter+cable for about £150 or just buy a new interface... I imagine for most it's the latter.
User avatar
Pete Kaine
Frequent Poster (Level2)
Posts: 3135
Joined: Thu Jul 10, 2003 12:00 am
Location: Manchester
Kit to fuel your G.A.S - https://www.scan.co.uk/shop/pro-audio

Re: Firewire major problem with brand new system.

Postby Dremix » Fri Mar 13, 2020 3:45 pm

Hi All,

Was reading this and I had the same problems with my Asus Prime x570-P motherboard.
I build my new PC and inserted all my drives and cards in it. On first boot only a black screen. Monitor got a signal but no Bios no nothing.

After removing some hardware I found out it was my PCI-Express Firewire card from DAWI-control. After pulling the card out al worked and system booted.

After reading some forums I came across a message on the Creative Soundblast forum on which a lot of people also had troubles with their Soundblaster cards with weird behaviour after the newest AMD Bios.

So what happened is that AMD turned on a 10-bit Tag Field, which is only available on PCI-e Gen4 devices. This results in compatibility issues with older Gen PCI-e cards like my firewire card.

So I went into my BIOS and searched for the 10-bit tag field and dissabled it. Also put the compatibility on Gen3 for the PCI-E slot I inserted my Firewirecard afterward and voila systems boot and Windows 10 even loaded the ' Texas Instruments 1394 OHCI Compliant Host Controller' driver in the device Manager.

Hooked up my TC Electronic Konnekt Live firewire soundcard and it is working.

Hope some others find this helpful.

Regards,

Andreas
Dremix
Posts: 2
Joined: Fri Mar 13, 2020 3:35 pm

Re: Firewire major problem with brand new system.

Postby Pete Kaine » Mon Mar 16, 2020 10:28 am

Dremix wrote:So what happened is that AMD turned on a 10-bit Tag Field, which is only available on PCI-e Gen4 devices. This results in compatibility issues with older Gen PCI-e cards like my firewire card.

Interesting find, I've got a few more cards I may need to try that on!
User avatar
Pete Kaine
Frequent Poster (Level2)
Posts: 3135
Joined: Thu Jul 10, 2003 12:00 am
Location: Manchester
Kit to fuel your G.A.S - https://www.scan.co.uk/shop/pro-audio

Re: Firewire major problem with brand new system.

Postby Dremix » Mon Mar 23, 2020 5:33 pm

Interesting find, I've got a few more cards I may need to try that on!

Let me know if you where succesful. This can help others who read this message and are having issues.
Dremix
Posts: 2
Joined: Fri Mar 13, 2020 3:35 pm

Previous