Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Name: Trent M
When I bought a new IEEE 1394 (FireWire) PCI card a few months back, it worked right out of the box on my computer with a Gigabyte GA-7VM400AM motherboard, with no need to manually install drivers or anything.
2 days ago, after 5 years of trouble-free use since new, the BIOS corrupted on that motherboard, and it will no longer boot. I got another motherboard, a Gigabyte GA-7VKML, and it worked out of the box with the hard drive, RAM, and AGP video card, but not the FireWire card.
The "new" motherboard was made around the same time as the old one. The FireWire card worked fine on the old one, but on this one, it won't work. Device Manager tells me that the card cannot start up because it has a problem. (Code 10.)
The card is detected as a VIA OHCI Compliant IEEE 1394 Host Controller. It says that the driver is installed and the card is ready to go, except for this error.
Any ideas what could be wrong? I use the card almost constantly to transfer video from my MiniDV camcorder to the computer, and I would hate not being able to use it.
Thanks in advance,
-Trent"If at first you don't succeed, skydiving may not be for you."
-Our tour guide at Fenway Park in Boston, MA.
Shoot...the computer is NOT the Acer Extensa 501DX laptop. lol
"If at first you don't succeed, skydiving may not be for you."
-Our tour guide at Fenway Park in Boston, MA.
0 
Sometimes the solution is as simple as enabling the device in Devie manager.
You can also examine what drivers are installed for the device as they may not be the right ones.
0
The card is in fact enabled in the device manager. It's icon has a yellow "!". (Corresponding to the "cannot start" error.)
The drivers are the ones that Windows XP installed when I first got the card a few months back. They didn't change with the switch to the new mobo.
Thanks,
-Trent"If at first you don't succeed, skydiving may not be for you."
-Our tour guide at Fenway Park in Boston, MA.
0
I guess I didn't make myself clear. Go to Device manager and expand the catagory so the card name is showing. Then right click on the card and choose properties. Under the general tab there is a box with text in it. Currently your box may have a message indicating the device has some problem. Use the down arrow on the right of that message to choose "enable this device".
0
Yes, I know what you meant. In the list box it already says "Use this device (enable)", with the other option "Do not use this device (disable)".
Thanks,
-Trent"If at first you don't succeed, skydiving may not be for you."
-Our tour guide at Fenway Park in Boston, MA.
0
OK, then look at the driver to see if it is a generic MSoft driver or the one you were using previously. That is at the same screen as above.
0
"The drivers are the ones that Windows XP installed when I first got the card a few months back. They didn't change with the switch to the new mobo."
did you reinstall windows, after installing the new board??larry
0
After rereading the entire thread I think your problem may be an IRQ conflict. Go the device manager and highlight Computer and then select View> resources by Type> IRQ.
See if the card is sharing an IRQ with another high use device.
The simple solution to change the IRQ assignment for the Firewire card is to move it to an different slot. You motherboard manual may even have a list of the default IRQ for each slot. Generally the slot next to the video should be left empty if possible. Down near the bottom may produce better results.
Your BIOS options may also allow you to manually assign a particular IRQ to each slot.
0
It is the Generic MS driver, dated 2001. It's the same driver that was used for the other mobo.
No, I did not reinstall Windows. Suprisingly, the Windows on the hard drive booted and worked right out of the box with the new mobo.
The FireWire card doesn't appear in the list of devices sorted by IRQ. In the Resources tab of the card's Properties page, it says "This device isn't using any resources because it has a problem."
The card is in PCI slot #3, farthest away from the AGP slot. The BIOS does let me manually assign IRQ's to the 3 PCI slots, so i'll try that. According to the Device Manager, IRQs 2, 7, 10, 11, 12, 17, 19, and 20 (and maybe more, depending on how far up it goes) are not in use, so i'll see if the BIOS will let me assign one of those IRQs to PCI slot #3.
Trying another slot will mean having to punch out one of those shields, but I will do it if the IRQ changing doesn't work.
"If at first you don't succeed, skydiving may not be for you."
-Our tour guide at Fenway Park in Boston, MA.
0
You could try removing the listing for the card in Device Manager and rebooting. See if that allows Windows to configure the card.
Also, below is a link for VIA drivers for the chip on that card.
0
I have tried removing the card and rebooting. Windows successfully re-installs the card, then says it can't start the card due to a problem.
I will try the drivers after changing the IRQ for the card.
Thanks,
-Trent"If at first you don't succeed, skydiving may not be for you."
-Our tour guide at Fenway Park in Boston, MA.
0
I tried every available IRQ I could for PCI slot #3 - didn't make a difference.
I tried to download that driver before - both download links just take me to the MS home page.
OK, i'm going to try a different PCI slot...
Thanks,
-Trent"If at first you don't succeed, skydiving may not be for you."
-Our tour guide at Fenway Park in Boston, MA.
0
YAY! I moved the card to PCI slot #2, but then when I noticed in the POST that the USB controller and the FireWire card were both using IRQ 10, I went into the BIOS setup and changed the #2 PCI slot to IRQ 11. I booted, and the card works perfectly now!
Even though I set it to IRQ 11, Windows says that it is using IRQ 18. I don't know what that is about, but as long as it works, I guess I shouldn't worry!
Thank you, OtheHill, larryf215, and DAVEINCAPS!
-Trent"If at first you don't succeed, skydiving may not be for you."
-Our tour guide at Fenway Park in Boston, MA.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
