Created attachment 406740 [details] module loading problem on initramfs stage and some acpi warnings... once booted, it prints(in 0.5s for the module error): starting version 218 ctx=0x7f1628fe82e0 path=/lib/modules/4.0.5-gentoo/kernel/drivers/misc/mei/mei.ko.xz error=No such file or directory ctx=0x7f1628fe82e0 path=/lib/modules/4.0.5-gentoo/kernel/drivers/net/wireless/ath/ath9k/ath9k_common.ko.xz error=No such file or directory ctx=0x7f1628fe82e0 path=/lib/modules/4.0.5-gentoo/kernel/drivers/net/wireless/ath/ath9k/ath9k_common.ko.xz error=No such file or directory ctx=0x7f1628fe82e0 path=/lib/modules/4.0.5-gentoo/kernel/drivers/net/mii.ko.xz error=No such file or directory ctx=0x7f1628fe82e0 path=/lib/modules/4.0.5-gentoo/kernel/drivers/mfd/mfd-core.ko.xz error=No such file or directory ctx=0x7f1628fe82e0 path=/lib/modules/4.0.5-gentoo/kernel/drivers/platform/x86/asus-wmi.ko.xz error=No such file or directory ctx=0x7f1628fe82e0 path=/lib/modules/4.0.5-gentoo/kernel/net/bluetooth/bluetooth.ko.xz error=No such file or directory ctx=0x7f1628fe82e0 path=/lib/modules/4.0.5-gentoo/kernel/deivers/media/v4l2-core/videobuf2-vmalloc.ko.xz error=No such file or directory [ 14.699830] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000 000400-0x000000000000047F (\PMIO) (20150204/utaddress-254) [ 14.699872] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 14.699879] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000 000500-0x0000000000000549 (\SBGP) (20150204/utaddress-254) [ 14.699898] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000 000500-0x0000000000000563 (\GPIO) (20150204/utaddress-254) [ 14.699917] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 14.699920] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000 000500-0x0000000000000549 (\SBGP) (20150204/utaddress-254) [ 14.699938] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000 000500-0x0000000000000563 (\GPIO) (20150204/utaddress-254) [ 14.699959] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 14.699961] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000549 (\SBGP) (20150204/utaddress-254) [ 14.699979] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150204/utaddress-254) [ 14.699997] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 14.699999] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 14.733738] ACPI Warning: SystemIO range 0x000000000000E000-0x000000000000E01F conflicts with OpRegion 0x000000000000E000-0x000000000000E00F (\_SB_.PCI0.SBUS.SMBI) (20150204/utaddress-254) while, when I entered in the system ,these modules are already loaded, and nothing seems to be wrong, though I'm not sure enough. as I see, the error occurs once it boot, and no related message about the module-loading error left in dmseg, it should be still in the initramfs stage, could it be the in-initramfs module depend on and initiatively load these modules? If so, how can I get to know which module should be included in initramfs? and about the following acpi warning，there should have nothing to do with genkernel， but I have been troubled for days， if possible，could anyone please give me some suggestions? longing for explanations and solutions，thanks very much!
Created attachment 406742 [details] my kernel configuration file
confirmed,this should be a bug of either kernel or genkernel-next. While, when I compiled these related module to be in-kernel, these errors went away. as to the acpi warning, I dont't know, what changes have I made, they disappered in the bootup message, but still stays in dmesg.
If you can attach a screenshot (or just a photo) of the boot screen where these messages appear, it may help us determine where the failure happens.
(In reply to Ben Kohler from comment #3) > If you can attach a screenshot (or just a photo) of the boot screen where > these messages appear, it may help us determine where the failure happens. sorry it has been years ago, and I have forgot the details
