In the sleek, power-managed world of a modern computer, the Advanced Configuration and Power Interface (ACPI) is the unseen orchestra conductor. It choreographs the sleep states, the fan speeds, the CPU throttling—a silent ballet of energy efficiency. But buried within the ACPI namespace of certain embedded and industrial motherboards lies a peculiar device: ACPI0004 (often with a specific HID of NSC6001). To the casual user, it’s an anonymous driver entry. To the hardware archaeologist, it is a ghost in the machine—a deliberate, fascinating bridge connecting the 64-bit, multi-core present to the 8-bit, 4.77 MHz dawn of the IBM PC.
The NSC6001 is not a CPU, a GPU, or a storage controller. It is the ACPI identifier for a legacy ISA bus controller, typically manufactured by National Semiconductor. But to call it just a "bus controller" is like calling a Rosetta Stone just a "tablet." Its primary function is to conjure the spirit of the original Industry Standard Architecture (ISA) bus—the primitive, 16-bit expansion bus of the 1984 IBM PC/AT—onto a motherboard that physically possesses no such slots.
The Problem: Anachronistic Hardware
Consider the challenge facing an industrial motherboard designer in the 2010s. The customer needs a modern x86 processor (say, an Intel Atom or AMD Embedded) running Windows or Linux. But they also need to control a legacy data acquisition card, a CNC machine interface, or an industrial robot arm—all of which speak only the timing and signaling language of ISA. These devices expect to be addressed directly via memory-mapped I/O and direct hardware interrupts (IRQs 3-7, 9-12). Modern chipsets, however, have long since replaced the ISA bus with the Low Pin Count (LPC) bus and, more recently, eSPI.
Enter the NSC6001. It sits as a logical device on the LPC bus, acting as a hardware translator. From one side, it speaks LPC to the modern chipset; from the other, it generates the correct -MEMR, -MEMW, -IOR, -IOW strobe signals and handles the complex, non-multiplexed address lines of a true ISA bus. The NSC6001 device in the ACPI namespace is the software declaration of this translation layer.
Why is this "Interesting"? The Politics of Plug and Play
The true intrigue of the NSC6001 lies not in its hardware specs, but in its interface with the operating system. ACPI is fundamentally a power management standard. Yet here it is, being used to declare a legacy, non-enumerable bus.
Modern buses (PCI, USB) are self-discoverable. You ask a PCI device, "Who are you?" and it replies with its Vendor and Device ID. ISA devices, being prehistoric, do not. Operating systems have relied on a cumbersome crutch since the mid-1990s: Plug and Play ISA (PNPISA). To work, each legacy card needed a separate, flaky configuration ROM.
The NSC6001 offers a more elegant, centralized solution. Instead of relying on the legacy card’s primitive configuration, the motherboard’s firmware (UEFI/BIOS) hard-codes the reality into the ACPI DSDT (Differentiated System Description Table). The ACPI device node for NSC6001 contains specific _CRS (Current Resource Settings) methods that tell the OS: "The legacy sound card is at I/O port 0x220, IRQ 5. The industrial I/O card is at memory 0xD0000, IRQ 10."
The OS driver for NSC6001 reads this ACPI table, and then dynamically creates the non-ACPI legacy device objects (like ISAPNP or direct platform devices) in the kernel. The NSC6001 is thus a meta-device—a device whose sole purpose is to fabricate other devices out of static information stored in firmware.
The Modern Resurrection: Coreboot and Linux acpi nsc6001
Because the NSC6001 is a relic (National Semiconductor was absorbed by Texas Instruments years ago), you won't find it on a standard retail PC. Its kingdom is the embedded world (PC/104 stacks, industrial single-board computers). However, it has found a strange second life in the open-source firmware community, particularly Coreboot.
For hobbyists and engineers building a vintage-inspired system (like a modern 486- or Pentium-class system on a new board), the Coreboot source code contains explicit drivers for nsc_pc87360-series super I/O chips, of which the NSC6001 logic is a part. Writing a Coreboot payload that initializes an NSC6001 means writing a small piece of code that sets up those legacy memory windows and IRQ routes before the OS even boots. When Linux boots and sees the ACPI0004 (NSC6001) device, its pc87360 driver matches, reads the pre-initialized state, and simply continues the handshake.
Conclusion: The Importance of Invisible Bridges
The ACPI NSC6001 is a testament to the layered complexity of modern computing. It is a deliberate software fossil, a translation layer that allows a twenty-first-century operating system to perform its most cherished trick: seamless power management and device enumeration on a platform that was never designed for it.
Every time a legacy ISA device appears as a fully functional node in the /sys filesystem of a modern Linux kernel, or receives a DMA channel allocated by Windows 10, the NSC6001 has done its job. It is a quiet, uncelebrated mediator that asks for no fanfare, only a correct entry in the DSDT. In an industry obsessed with obsolescence, the NSC6001 stands as a defiant monument to backwards compatibility—proof that the ghost of the IBM PC/AT still haunts the silicon of today, and that sometimes, the most interesting hardware is the hardware you are not supposed to know exists.
The ACPI NSC6001 is a specific hardware ID often encountered by users during a fresh installation of Windows or while browsing the Device Manager. Usually appearing as an "Unknown Device," this identifier points toward a specialized hardware component that requires a specific driver to communicate with the operating system. Understanding the ACPI NSC6001
ACPI stands for Advanced Configuration and Power Interface. It is an industry specification that allows the operating system to control hardware power management. The "NSC" prefix generally refers to National Semiconductor, a manufacturer known for producing Super I/O chips and other low-level motherboard controllers.
When you see "ACPI\NSC6001" in your hardware IDs, your computer is essentially saying it has found a piece of hardware—likely an Infrared (IR) port or a specialized power management controller—but it doesn't have the software instructions (drivers) to run it. Common Hardware Associated with NSC6001
In the vast majority of cases, the NSC6001 ID is associated with:
Fast Infrared (FIR) Controllers: Many older laptops and certain desktop motherboards included infrared sensors for data transfer or remote control functionality. The Ghost in the Machine: Unearthing the ACPI
Super I/O Chips: These chips manage low-bandwidth devices like serial ports, parallel ports, and system fans.
Trusted Platform Modules (TPM): In rarer instances on specific legacy workstation boards, this ID has been linked to early security chip implementations. Why Does it Show as an Unknown Device?
Modern operating systems like Windows 10 and Windows 11 often lack "in-box" drivers for legacy infrared components. Because infrared technology has largely been replaced by Bluetooth and Wi-Fi, Microsoft no longer includes these drivers by default. Consequently, the system recognizes the presence of the chip via the ACPI table but cannot initialize it. How to Identify and Fix the Missing Driver
If you are looking to clear the yellow exclamation mark in your Device Manager, follow these steps:
Check Device PropertiesRight-click the "Unknown Device" in Device Manager. Select Properties, go to the Details tab, and choose Hardware Ids from the dropdown menu. If it says ACPI\NSC6001, you have confirmed the hardware identity.
Manufacturer Support PagesSearch the support website of your laptop or motherboard manufacturer (such as HP, Dell, or Lenovo). Look for "Infrared," "Communication," or "Chipset" drivers. Even if the driver is listed for an older version of Windows (like Windows 7), it will often work on newer systems if installed in Compatibility Mode.
Manual Driver UpdateSometimes, the driver is already on your system but not assigned. You can try selecting "Update Driver" > "Browse my computer for drivers" > "Let me pick from a list." Look for "Infrared devices" and see if a National Semiconductor driver is available in the Windows driver store. Should You Disable It?
If you do not use infrared features—which most modern users do not—there is no harm in leaving the device as "Unknown" or right-clicking it and selecting "Disable." Disabling the device will remove the error icon and prevent the OS from attempting to find a driver, which can slightly speed up boot times on older hardware. Conclusion
The ACPI NSC6001 is a legacy hardware identifier primarily tied to National Semiconductor infrared modules. While it rarely impacts system performance if left uninstalled, a quick trip to your manufacturer's legacy driver archive can usually resolve the "Unknown Device" listing for those who prefer a clean Device Manager.
There is no official "NSC6001 guide" from Microsoft or Intel, but this guide consolidates technical details, drivers, and troubleshooting for this specific ACPI hardware ID. Outdated: Written for Windows 98/2000/XP
A quick Google search for "ACPI NSC6001 driver" will lead you to sketchy driver download sites offering nsc6001.sys or acpi_nsc6001.inf. Be extremely cautious.
Many of these files are:
If you still want to try, here is the legitimate (theoretical) source. Do not download from third-party sites.
If the device doesn't appear normally, it may be hidden.
cmd as Administrator.set devmgr_show_nonpresent_devices=1start devmgmt.mscThe ACPI NSC6001 error is not a hardware failure. It is a software configuration problem rooted in Windows' Plug and Play driver database.
Modern Windows (10/11) may refuse to install unsigned legacy drivers. You will need to:
Disable driver signature enforcement (temporarily):
bcdedit /set testsigning on (adds "Test Mode" watermark).Manually install the driver:
.inf and .sys from the OEM package..inf.Watchdog configuration (if driver supports it):
wdt.exe enable 60)."The driver \Driver\WUDFRd failed to load for device ACPI\NSC6001."
This occurs when Windows Update tries to assign a modern driver (like Windows User-Mode Driver Framework) to a legacy device that isn't compatible.
The system may take 2-3 minutes to shut down because Windows waits for the NSC6001 device to report a successful power transition. Eventually, it times out.