Skip to content

Instantly share code, notes, and snippets.

@kekneus373
Created January 12, 2026 15:22
Show Gist options
  • Select an option

  • Save kekneus373/3254fd972c1e5487178791e30cd4d57a to your computer and use it in GitHub Desktop.

Select an option

Save kekneus373/3254fd972c1e5487178791e30cd4d57a to your computer and use it in GitHub Desktop.
[FIX] ACPI resource conflict during boot

ACPI Resource Conflict

The message "ACPI: OSL: Resource conflict; ACPI support missing from driver?" indicates a conflict between system resources claimed by the ACPI (Advanced Configuration and Power Interface) subsystem and those accessed by a legacy driver, such as hardware monitoring drivers like nct6775 or it87 This typically occurs when an ACPI OperationRegion (OpRegion) and a driver's I/O port range overlap, leading to potential instability or erratic system behavior

The root cause is often a misconfiguration or outdated firmware, particularly in the BIOS, where ACPI settings may not properly coordinate with hardware drivers While the warning suggests that the driver may lack ACPI support, the issue is frequently resolved by adjusting kernel parameters rather than modifying the driver itself

A common solution is to use the kernel parameter acpi_enforce_resources=no, which disables ACPI's enforcement of resource reservations, allowing legacy drivers to access conflicting I/O ports without restriction This has been reported to resolve conflicts with the nct6775 and it87 drivers Alternatively, acpi_enforce_resources=lax can be used, though it may not resolve the issue in all cases

Other troubleshooting steps include updating the system's firmware (BIOS) to ensure proper ACPI implementation, checking BIOS settings related to ACPI and AHCI, and ensuring the system is fully updated Disabling ACPI entirely (acpi=off) can resolve conflicts but may disable essential power management features and cause issues with hardware like GPUs Therefore, adjusting acpi_enforce_resources is generally preferred over disabling ACPI entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment