[lmyllari]

The kernel has a db of devices (vid:pid) that each driver maps to. Sometimes new devices come along that can still use the driver but their vid:pid aren't in the database. Thr kernel won't automatically load the driver but it can still be loaded manually. This may be possible yo fix in modeprobe.conf.

The kernel seems to find the device (based on the PNP id NTN0530?) and tries to load the right driver (that's why you see "nuvoton-cir 00:08: IR PNP Port not valid!" in boot messages). I looked in drivers/pnp/pnpacpi and I think the problem is the ACPI data - _STA returns 0x6 and the kernel thinks the device is not enabled and doesn't allocate it resources. 0x6 looks suspicious as http://www.acpi.info/DOWNLOADS/ACPIspec10b.pdf (section 6.3.5) says "If bit 0 is cleared, then bit 1 must also be cleared (i.e., a device that is not present cannot be enabled)."

I've opened a question in the Intel support community, maybe somebody can clarify there.