When installing PCI network interface cards (NICs), where should you check to verify available IRQ assignments and resource allocation?

Introduction / Context:
PCI devices typically rely on Plug and Play (PnP) mechanisms for resource allocation (IRQs, I/O ranges, memory windows). Understanding where these resources are configured or viewed is essential for troubleshooting hardware conflicts.

Given Data / Assumptions:

• Hardware: PCI NICs (modern, jumperless).
• Goal: Check IRQ availability and current assignments.
• Legacy files like CONFIG.SYS are not used for PCI resource assignment.

Concept / Approach:
PnP BIOS/UEFI and the operating system enumerate PCI devices and assign resources automatically. The motherboard BIOS (or UEFI) setup often displays or influences resource assignment, supports enabling/disabling slots, and handles legacy IRQ reservations. PCI cards do not use physical DIP switches or jumpers for IRQs.

Step-by-Step Solution:
Identify that PCI resource allocation is automatic via BIOS/OS.Recognize that legacy methods (DIP/jumpers) applied to ISA cards, not PCI NICs.Use the motherboard BIOS (and OS device manager) to view/alter resource configurations.

Verification / Alternative check:
Operating systems (e.g., Windows Device Manager, lspci in Linux) display assigned resources, while BIOS/UEFI provides slot settings and legacy IRQ reservations—confirming BIOS as the hardware-level reference point.

Why Other Options Are Wrong:

• Dip switches / Jumper settings: Typical for ISA/older devices; not for PCI IRQs.
• CONFIG.SYS: DOS-era driver loading; does not assign PCI IRQs.
• None of the above: Incorrect—BIOS is correct.

Common Pitfalls:
Assuming manual jumper configuration for PCI or editing startup files to change PCI resources—these do not apply.

Final Answer:
Motherboard BIOS