General discussion

Locked

IRQ Conflicts

By bapease ·
Recently I enabled the USB port on my computer (IBM Aptiva, Win 9. In order to do so I disabled by NIC card (Kingston Ether PCI 10/100), enabled the USB, rebooted then re-enabled the NIC card. I had previously been advised that the USB would require IRQ 14 which was then being used by the NIC. Since then on every other boot I loose the network because the NIC card is not assigned an IRQ. When the net work is available the NIC gets IRQ 3, IRQ 4 becomes com 3 or 5; IRQ 7 & 10 are AT&T Win Modem. When the network is not available IRQ 3 is COM2, IRQ 4 & 10 are AT&T Win Modem. Or if I disable the AT&T Win Modem, something else gets assigned to IRQ 3 and the NIC is not assigned and IRQ. I would like to get the NIC to IRQ 10. Every time that I attempt to assign the settings for the NIC is reverts to settings in use by the Motherboard and I'm not sure how to set it for IRQ 10. Any suggestions?

This conversation is currently closed to new comments.

10 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

IRQ Conflicts

by TheChas In reply to IRQ Conflicts

First, if you do not use your COMM or Parallel ports, remove the devices from device manager, and disable them in BIOS settings.
Same for the secondary IDE controller.

Before exiting BIOS settings, set update ESCD (configuration) to enable.

This is to free-up any IRQs that are assigned, but that you are not using.

Next, look at the default IRQ that your motherboard uses for different slots.

You may need to move the modem and NIC to different slots in order to get the best IRQ configuration.

Don't just disable the modem or NIC.
Remove the NIC from device manager, and remove the modem from the modems section of control panel.

Finally, you may need to disable IRQ steering in order to force Windows to assign the IRQs in thebest manner.

This is from a Microsoft Knowledge Base article:

How to Disable PCI Bus IRQ Steering in Windows

The information in this article applies to:
Windows 98

SUMMARY
This article describes how to disable (PCI) bus interrupt request (IRQ) steering.

MORE INFORMATION
When PCI bus IRQ steering is enabled, Windows dynamically assigns or "steers" PCI bus IRQs to PCI devices. If there are IRQ conflicts between PCI devices, you may need to disable PCI bus IRQ steering to determine where the conflicts occur. To disable PCI bus IRQ steering, follow these steps:

Click Start, point to Settings, click Control Panel, and then double-click System.

Click the Device Manager tab.

Double-click the System Devices branch.

Double-click PCI Bus, and then click the IRQ Steering tab.

Click the Use IRQ Steering check box to clear it, click OK, and then click OK again.

When you are prompted to restart your computer, click Yes.

NOTE: If you click No instead ofYes when you are prompted to restart your computer, the changes do not take affect.

end part 1

Collapse -

IRQ Conflicts

by TheChas In reply to IRQ Conflicts

part 2

NOTE: You may also have to disable PCI bus IRQ steering in your computer's basic input/output system (BIOS). For information about how to do so, contact you BIOS manufacturer.

The following settings determine which routing tables Windows uses when programming IRQ steering:

Get IRQ table using ACPI BIOS:

When this check box is selected, the ACPI BIOS IRQ routing table is the first table Windows tries to use to program IRQ steering. If a PCI device is not working properly, click this check box to clear it.

Get IRQ table using MS Specification table:

When this check box is selected, the MS Specification routing table is the second table Windows tries to use to program IRQ steering.

Get IRQ table from Protected Mode PCIBIOS 2.1 call:

When this check box is selected, the Protected Mode PCIBIOS 2.1 routing table is the third table Windows tries to use to program IRQ steering.

Get IRQ table from Real Mode PCIBIOS 2.1 call:

When this check box is selected, the Real Mode PCIBIOS 2.1 routing table is the fourth table Windows tries to use to program IRQ steering.

NOTE: By default, the "Get IRQ table from Protected Mode PCIBIOS 2.1 call" check box is not selected. You should only click this check box to place a check mark if a PCI device is not working properly.

IRQ Holder For PCI Steering may appear under IRQ Routing Status even though PCI bus IRQ steering is disabled. This can occur if the IRQ settings are being read by your computer's BIOS. For information about modifying the BIOS, contact your BIOS manufacturer.

For additional information about PCI bus IRQ steering, please see the following article in the Microsoft Knowledge Base:
Q182604 Description of PCI Bus IRQ Steering

Chas

Collapse -

IRQ Conflicts

by bapease In reply to IRQ Conflicts

The question was auto-closed by TechRepublic

Collapse -

IRQ Conflicts

by Data Ninja In reply to IRQ Conflicts

As in answer #1, the very last item might be the best thing to do first.. In your BIOS, locate the item that says "OS is PNP compatible" or something similar. Change this from "No" to "Yes" so the OS can pick and choose IRQs. If it is already set to"Yes", the change it to "No" and see what happens. Depending on the BIOS, I've had similar problems but each time that PNP OS setting has had to be different, so I always try both settings.

Collapse -

IRQ Conflicts

by bapease In reply to IRQ Conflicts

The question was auto-closed by TechRepublic

Collapse -

IRQ Conflicts

by Hotshot3000 In reply to IRQ Conflicts

It might help to know what your other IRQ assignments are. Why would your NIC be assigned IRQ 14 in the first place? That IRQ is usually reserved for your IDE controller, and 15 is for a secondary IDE controller. If those have been reassigned, they could be playing havoc with your other devices. That may be part of why your system is playing musical IRQs.

<p>Is your WinModem being used for sound or voice capability? If not, the voice capability would be the first thing I would try to disable (and thereby free up an IRQ).

<P>If allowing IRQ steering (as mentioned by others) does not do the job, you can go into Device Manager and manually reserve certain resources for each device that needs it.

Collapse -

IRQ Conflicts

by bapease In reply to IRQ Conflicts

The question was auto-closed by TechRepublic

Collapse -

IRQ Conflicts

by Hotshot3000 In reply to IRQ Conflicts

It might help to know what your other IRQ assignments are. Why would your NIC be assigned IRQ 14 in the first place? That IRQ is usually reserved for your IDE controller, and 15 is for a secondary IDE controller. If those have been reassigned, they could be playing havoc with your other devices. That may be part of why your system is playing musical IRQs.

Is your WinModem being used for sound or voice capability? If not, the voice capability would be the first thing I would try to disable (and thereby free up an IRQ).

If allowing IRQ steering (as mentioned by others) does not do the job, you can go into Device Manager and manually reserve certain resources for each device that needs it.

Collapse -

IRQ Conflicts

by bapease In reply to IRQ Conflicts

The question was auto-closed by TechRepublic

Collapse -

IRQ Conflicts

by bapease In reply to IRQ Conflicts

This question was auto closed due to inactivity

Back to Desktop Forum
10 total posts (Page 1 of 1)  

Related Discussions

Related Forums