Log in

View Full Version : i have a problem with my network card and capture card why?


kurt476
1st December 2004, 16:47
Ok i don't know why this is but humm my capture card and network card are having conflict i think. When I disable the network card the capture seem to work fine after that.

Dose any budy know what i can do to fix this so i can run my network?

acrespo
1st December 2004, 19:45
I have the same problem. If I remove my NIC and activate my onboard NIC the problem is gone. The strange thing is both NICs is sharing IRQs with the same other device (USB 1.0/1.1).
I need my PCI NIC because it have offboard management of connections, but I can't do it function properly (I wrote my own thread about my problem today).

kurt476
2nd December 2004, 01:49
Yeah it seem like it has a conflick with the IRQ it is a strange thing with this. I wounder if there is a solution to our problem?
I need my NIC For tranfering files over my network i don't want to wast cd's if i can tranfer.

jcsston
11th December 2004, 08:31
When I ran under Windows 98 if my network card was not disabled my system would randomly freeze up after a while of capturing. I tried replacing the network card with a different brand without effect.
Since upgrading to Windows XP I haven't had the problem any more.

Sergei_Esenin
12th December 2004, 15:32
Ok i don't know why this is but humm my capture card and network card are having conflict i think. When I disable the network card the capture seem to work fine after that.

This is just a guess, but--you're probably running a VIA chipset, or maybe an nVidia chipset, right? You're almost certainly not running an Intel chipset. Most people don't realize that VIA especially, but to some smaller extent nVidia, have quirky PCI implementations in their motherboard chipsets. Even AMD had PCI implementation issues with their MP and MPX chipsets that caused conflicts or lowered performance with some PCI devices like video capture cards which require a constant share of bus bandwidth. I'm no Intel fanboy, but while their current CPUs underperform compared to AMD's, their core logic motherboard chipsets have reference PCI implementations that are far less prone to device conflicts.

These are generally chipset and BIOS level problems. If you haven't done so already, update your BIOS. The best way to resolve these issues if the BIOS update doesn't solve them is to change PCI latency settings--try raising and lowering them for one device or the other to see if both devices can now be used at once. You can also try adjusting the global PCI Delay Transaction setting. However, as with any BIOS adjustments, be sure to return them to defaults if they don't alleviate your problem.

Including onboard devices I've had 3 video capture cards, two NICs, and two soundcards in my system at once for years. As you can imagine, conflicts have arisen. On my VIA chipset motherboard I could never get every device to function at the same time, even after much BIOS-fu and many driver updates. When I upgraded to an nVidia chipset I could get everything to work except one NIC was very slow and one capture card would drop frames if viewing while capturing. When I upgraded to an Intel chipset platform, everything finally worked, even without BIOS black arts. It's really about the chipset and the quality of its PCI implementation, more than the devices on the PCI bus.

CPUs don't really matter. Individual PCI devices don't matter much. The single most important part of a PC is the motherboard's core logic chipset, which can either increase conflicts or solve them. Sadly, almost no one outside the IT profession knows this.

Arachnotron
12th December 2004, 15:33
Shuffeling your cards around in the pci slots untill you find a combination that works is the only thing you can do I am afraid.

Try to put the capture card in a pci slot that does not share a IRQ with any other device. Most MB manuals have a table about this.

A common combination is that the first PCI shares the IRQ with the AGP slot, the second with the fifth and the third with the sixth PCI. Unfortunately, this is by no means standard and it does not take IRQ's shared with on-board devices into consideration. Again, try the manual.

There are differences in how well devices handle shared IRQ's (officially it should not be a problem at all, but hey...)

SCSI cards and RAID controllers handle it badly
Capture cards also often have problems;
NIC, USB and soundcards mostly are ok with it.

[edit] so if you find you have unshared PCI slots, use those for your "trouble devices". If two PCI slots do share an IRQ, use those for sound, NIC, USB cards etc.

jggimi
12th December 2004, 15:56
Don't forget, VIA based motherboards need additional drivers (called Hyperion 4-in-1) for proper operation, which are frequently updated. www.viatech.com

jcbiv
13th December 2004, 20:56
Ive seen this alot in the past. I know Intel chipsets are not immune since the first time I encountered the unfriendly IRQ sharing problem was with this old dual PIII machine with sound + secondary video card.
I would usually see it with video card/NICs though.

I have never seen it in any Win2K or XP machines.