We found a problem when we tried to use the FireWire port on our computers that were running Windows 7, Windows 8 and 8.1 and Windows 10. We were trying to import video into Sony Vegas and Adobe Premiere, and we quickly found out that we couldn’t import video into the computer via the FireWire port. We never had this problem with Windows XP. At first we thought this was a compatibility problem between Windows 7, Windows 8/8.1, Windows 10 and Sony Vegas and Adobe Premiere, but we quickly ruled that out when another program also had problems using the Firewire port. The problem was with the Windows 10, 7, Windows 8 and 8.1 FireWire driver (a.k.a. The 1394 Driver) and the fix was a simple one.
- Via Vt6307 Fire Iim Ieee 1394 Host Controller Drivers Online
- Driver Via Vt6307 Fire Iim Ieee 1394 Host Controller
- Via Vt6307 Fire Iim Ieee 1394 Host Controller Drivers License
For Windows 7, just use the Legacy driver. Just follow the instructions below. If you are on Windows 10, or 8 or 8.1 you will need to download the Legacy driver from Microsoft. Just skip down to the section marked The Fix for Windows 8 and 8.1 and Windows 10. The Fix for Windows 7 Note: The fix for Windows 8 and 8.1 are further down below and are different than Windows 7.
For Windows 7 simply replace the new 1394 driver with the Legacy driver that comes with Windows 7. Below is the step by step instructions on how to install the Legacy driver so you won‘t have any problems either: Click Start Then click on Control Panel Click on Device Manager Note: If you don’t see Device Manager listed, click on View By: Category on the top right side of the Control Panel Window. Then Click on Large Icons you should now have a list of items in the Control Panel and click on Device Manager.
Under the Device Manager, look down the list for IEEE 1394 Bus Host Controllers and Double Click on it. It should display something like - 1394 OHCI Compliant Host Controller Note: If it has the word (Legacy) behind it, you are already setup and you can just exit out.
Type Information; ID: 3044: Chip Number: VT6306/VT6307/VT6308: Chip Description: VIA Fire II 1394a OHCI Link Layer Ctrlr1: Notes: No drivers needed after win 7. VIA VT6308 Fire IIM IEEE1394 Host Controller (PHY: VIA VT6307). The VIA Fire IIM VT6308P/S is a single-chip, low power 2-port IEEE 1394 host The VIA VT6308P/S has VIA and OHCI software driver support built into all.
Next, double click on the 1394 OHCI Compliant Host Controller A window will popup saying 1394 OHCI Compliant Host Controller Properties Click on the Driver Tab Then look down in the widow and click on Update Driver Then select - Browse my computer for driver software Next select - Let me pick from a list of device drivers on my computer It will bring up a list of drivers. Click on 1394 OHCI Compliant Host Controller (Legacy) NOTE: It is important that you select the one with (Legacy) after it, just like shown above. Then click Next Once it installs the 1394 OHCI Compliant Host Controller (Legacy), it will say Windows has successfully updated your driver software. Click on the Close button and exit out of all of the other windows. Then Reboot your computer.
You will now be able to import video via the FireWire port on your computer. If you are still having a problem importing video after you have switched the FireWire driver to Legacy, then the problem may be with the FireWire port. This is a common problem.
The FireWire port will work with an external driver, but it won't let you import video from your video camera. Most people report this problem with Dell computer, but it does happen with other brands, even brand new computers.
This problem is usually with the FireWire port that is built into the motherboard. The fix is simple: 1.
Install a FireWire card into one of the open slots in the computer 2. Using the instructions above, set the drive to Legacy. Reboot the computer. Then connect the FireWire cable from the video camera, into the new FireWire port that you just added. This fixes the problem 99% of the time.
FireWire cards are not the expensive, they run from $10 and up, depending on any extra features the card may have. NOTE: We have noticed that when Microsoft has issued certain updates, it can cause Windows 7 to switch back to use the original 1394 OHCI Compliant Host Controller driver. If you notice the FireWire device is transferring slowly or not working, then just repeat the above steps and reinstall the Legacy driver. The Fix for Windows 8 and 8.1 and for Windows 10 In Windows 8 and 8.1, plus Windows 10, Microsoft left out the Legacy driver. Just go to and download the Legacy driver.
Then follow the installing directions on that same support page. If you are running Windows 10, you will need to use the Windows 8 / 8.1 Legacy driver. So follow the same steps as Windows 8 / 8.1. Then Reboot your computer. You will now be able to import video via the FireWire port on your computer. If you are still having a problem importing video after you have switched the FireWire driver to Legacy, then the problem may be with the FireWire port. This is a common problem.
The FireWire port will work with an external driver, but it won't let you import video from your video camera. Most people report this problem with Dell computer, but it does happen with other brands, even brand new computers. This problem is usually with the FireWire port that is built into the motherboard. The fix is simple: 1. Install a FireWire card into one of the open slots in the computer 2. Using the instructions above, set the drive to Legacy. Reboot the computer.
Then connect the FireWire cable from the video camera, into the new FireWire port that you just added. Note: I received an email from Mike Tilka and he was having a problem getting the FireWire port working on his Dell XPS 8100 and on an Gateway computer with the drivers from above. He said he needed to get the driver from this link for his computers: If you have a Dell or a Gateway computer and the above fix doesn't work for you, then you might want to try the above link.
This fixes the problem 99% of the time. FireWire cards are not the expensive, they run from $10 and up, depending on any extra features the card may have. NOTE: We have noticed that when Microsoft has issued certain updates, it can cause Windows 10, Windows 8 and Windows 8.1 to switch back to use the original 1394 OHCI Compliant Host Controller driver. If you notice the FireWire device is transferring slowly or not working, then just repeat the above steps and reinstall the Legacy driver. About Us Since 1993, when Studio 1 Productions opened, we have been serving videographers, filmmakers and photographers.
Whether you are home user, hobbyist, prosumer or professional, we are here to help you. Studio 1 Productions, is owned and run by honest and experienced videographers.
Via Vt6307 Fire Iim Ieee 1394 Host Controller Drivers Online
This is why so many people have come to rely on us for dependable and knowledgeable answers and products. All of the products we offer are products we use ourselves in our video productions.
This gives us a better knowledge of the products over other companies.
Via Vt6307 Fire Iim Ieee 1394 Host Controller Drivers
On Mar 10 lagunax wrote: root@.:/home/producer# lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09). 01:00.0 PCI bridge: ASMedia Technology Inc.
ASM1083/1085 PCIe to PCI Bridge (rev 01) 02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 Fire II(M) IEEE 1394 OHCI Controller (rev 80).
02:00.0 FireWire (IEEE 1394) 0c00: VIA Technologies, Inc. VT6306/7/8 Fire II(M) IEEE 1394 OHCI Controller 1106:3044 (rev 80) (prog-if 10 OHCI). root@.:/home/producer# dmesg grep fire 0.535278 firewireohci 0000:02:00.0: enabling device (0080 - 0083) 0.598118 firewireohci 0000:02:00.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x11 root@.:/home/producer# dmesg grep 1394 root@.:/home/producer# As far as I know, the PCI identifiers 1106:3044 (rev 80) belong to VIA VT6308. I have VT6306 and VT6315, and had a VT6307 for a while, but no VT6308; but I am quite sure that the VT6308 is very similar internally to VT6307, and that other Linux users have working VT6308s.
Your dmesg starts like it should, but then at least one important line does not follow. On Mar 10 lagunax wrote: root@.:/home/producer# lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09). 01:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 01) 02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc.
Via Vt6307 Fire Iim Ieee 1394 Host Controller Drivers Download
Driver Via Vt6307 Fire Iim Ieee 1394 Host Controller
Via Vt6307 Fire Iim Ieee 1394 Host Controller Drivers License
VT6306/7/8 Fire II(M) IEEE 1394 OHCI Controller (rev 80). 02:00.0 FireWire (IEEE 1394) 0c00: VIA Technologies, Inc. VT6306/7/8 Fire II(M) IEEE 1394 OHCI Controller 1106:3044 (rev 80) (prog-if 10 OHCI). root@.:/home/producer# dmesg grep fire 0.535278 firewireohci 0000:02:00.0: enabling device (0080 - 0083) 0.598118 firewireohci 0000:02:00.0: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x11 root@.:/home/producer# dmesg grep 1394 root@.:/home/producer# As far as I know, the PCI identifiers 1106:3044 (rev 80) belong to VIA VT6308. I have VT6306 and VT6315, and had a VT6307 for a while, but no VT6308; but I am quite sure that the VT6308 is very similar internally to VT6307, and that other Linux users have working VT6308s. Your dmesg starts like it should, but then at least one important line does not follow.