Fixing Missing Network Interface After Suspend on MX Linux 25 (igc Driver Reload Workaround)

Issue

After upgrading or running MX Linux 25(SysVinit), a network issue can occur where the system resumes from suspend and the ethernet interface is no longer available. In some cases, the interface disappears entirely and is reported as:

• “No such device”
• or is missing from ip link / ifconfig

This appears to be related to the igc driver not properly reinitializing after resume.

Environment

• MX Linux 25
• Kernel using igc Intel network driver
• Suspend / resume via system sleep states

Root cause (observed)

After resume, the igc kernel module may remain in a broken state. The device does not re-enumerate correctly, leaving the interface unavailable until the driver is reloaded.

Workaround

A simple suspend hook script can force the driver to reload after resume.

Create the following file: /etc/pm/sleep.d/99_igc_reload

case "$1" in
    resume|thaw)
        # Unload and reload the driver to fix the 'No such device' error
        /sbin/modprobe -r igc
        /bin/sleep 1
        /sbin/modprobe igc
        ;;
esac

chmod +x /etc/pm/sleep.d/99_igc_reload

How it works

• On resume or thaw events, the script runs automatically via pm-utils
• The igc kernel module is unloaded
• A short delay ensures cleanup
• The module is reloaded, reinitializing the network interface

Result

After applying this fix:

• Network interface reappears after suspend
• No manual restart of NetworkManager required
• System resumes cleanly

Notes

This is a workaround, not a root-cause fix. The underlying issue is likely in driver suspend/resume handling or kernel power management interaction with the igc module.