You are not logged in.
As I told you, I tried standard kernel that provided by arch repository.
Yeah, I read that - and it's meaningless.
You're supposed to apply the repo config to your custom kernel to isolate whether it's a config issue or some patch in your custom kernel spoils it…
I do not have any patches, just :
asp update linux
asp export linux
After I edit PKGBUILD I get rid of initramfs(but for some reasons it still triggers initramfs) and docs. After copy my config file to the linux folder, after updpkgsums, after makepkg -s. Thats all.
Last edited by ihitmani (2021-10-17 13:41:07)
Offline
What's the point of that? The compiler flags? Just use the repo config.
The diff is 12.5k lines… most notably a whole bunch of CONFIG_ACPI* options aren't set.
Online
What are the difference of 5.11 kernel and newer? I did not change CONFIG_ACPI, as I said it just stopped working on newer kernel. I have this config for more then a year. Also I did not change it for more then a year and it worked fine.
Offline
The compiler flags will not be used for the kernel build, only for building host tooling.
The custom kernel config contained CONFIG_MCORE2=y which will add -march=core2 to KBUILD_CFLAGS.
The config you are using as input is not the same as the config the kernel actual uses after it updates the options to be compatible with the kernel it is building.
Have you compared the config after it is updated for the 5.12 kernel to see what changed?
Offline
No, I haven't compare it
Offline