It is important to note immediately that it is not just the video that has been disrupted. The modules/drivers were not permitted to load because of version-matching restraints.
Update
This can be caused by having an error in /etc/fstab in the /boot mount for those who keep boot on a separate partition (usually EFI main boards). If during an update this partition is not mounted, the modules could (likely would) get upgraded while the kernel, which resides in /boot, would not. dkms
normally prevents kernel-module mismatches.
I did indeed have kernel + module mismatch that led to the error message
ERROR: '/lib/modules/4.4.5-1-ARCH' is not a valid kernel module directory
mentioned in the question.
To fix it, I needed to boot from an Arch USB Stick and mount the OS and BOOT partitions to /mnt and /mnt/boot, respectively. I had to change root over to the machine arch-chroot /mnt /bin/bash
and update my kernel manually (and forcefully).
pacman -Sy linux --force
This brought my system's kernel up to date with the modules (4.4.5-1-ARCH) such that they match (as they absolutely should!)
As to why there was a kernel + module mismatch, I don't know. I am hoping [dkms][1]
will prevent this in the future. In my case, the modules weren't built when the new kernel was installed, rather, the modules were updated when the kernel was not.
Dynamic Kernel Module Support (DKMS) is a program/framework that enables generating Linux kernel modules whose sources generally reside outside the kernel source tree. The concept is to have DKMS modules automatically rebuilt when a new kernel is installed.
*Lerhaupt, Gary (September 1, 2003). "Kernel Korner - Exploring Dynamic Kernel Module Support (DKMS)". Linux Journal. Retrieved March 12, 2016.
Your hardware is too new sort of speak.
The bugs you are seeing are harmless and may persist for some time.
You could try upgrading your BIOS, that is utmost priority.
Then, you could try installing intel-microcode
non-free package.
See if these two options work for you first.
Today, I have assembled a computer with the very same CPU and seeing the same bugs. On just another motherboard.
Update 2018-Dec-1
The error on my Dell laptop with very recent UEFI BIOS update is still persistent as per log:
Dec 01 06:27:07 dell-7577 kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210)
Dec 01 06:27:07 dell-7577 kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
Dec 01 06:27:07 dell-7577 kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_OEMBD) while loading table (20170831/tbxfload-228)
Dec 01 06:27:07 dell-7577 kernel: ACPI Error: 1 table load failures, 13 successful (20170831/tbxfload-246)
Best Answer
I found this guide. I was able to boot turning off ACPI by adding the
acpi=off
flag in grub.Then I followed the guide above and was able to boot without
acpi=off
:If using sysdemd with rc.local disabled:
Edit
Add to rc.local
There were still a few of the ACPI error messages, but they did not affect booting.