On a cursory look, you don't seem to compile apparmor - not that it would matter for my current issue. Number of modules I compile is very less as opposed to your config file. So there are many permutations to consider for me. I will try to post my config file some place safe.
It must be something in my set up that is different. I am now curious to know.
On a side note, you also have CONFIG_INTEL_IOMMU=y (which was fix for i915 issue for my MBP). This community helped me get past that issue during 5.7.x
I might go silent for a while to compare changes.
]]>So what is the issue?: Today, I realized that all my prior compiled kernels (till 0731) boot properly, except today's. Today's compiled kernel gave me kernel panic during boot saying root file system is not found and essentially kernel bailed on me.
Analysis: I noticed that I had not changed my config file or any compilation settings in a while now. Only difference was I had new sources. Reflog shows me that there is a new change coming in post 5.8 kernel that is about zstd support in initramfs (or something like that). I tried changing kernel config, without any success. So I restored my original setup (which is that git package I refered to earlier) and tried changing my mkinitcpio config to see if that helped. After reading a bit more I realized that there was a mention in the past about dracut vs mkinitcpio https://lists.archlinux.org/pipermail/a … 29570.html. So I won't be filing a bug report for mkinitcpio for now.
Fix for my issue today: I ended up keeping my already compiled kernel for 0803 and installing dracut per archwiki. The same kernel, when initramfs is changed (generated from mkinitcpio vs dracut), is booting smoothly.
FAQ:
1. Issue related to i915 in short is that since 5.7.x it appears we need to use intel_iommu=yes or something similar kernel parameter. In absence of this, stock archlinux kernel won't allow me to boot into graphical mode. Known issue. Thanks to awesome people here who dug deeper and identified the fix for 5.7.x kernel for arch.
2. I can't use linux-clear-bin kernel because I have been using apparmor and apparently this kernel doesn't come with apparmor precompiled (or the way it is right now, my apparmor doesn't work). So I will be required to compile my own custom kernel anyways.
3. Why do I compile my kernel these days? .. Earlier it was required to diagnose that i915 issue, then for apparmor for linux-clear-bin. Now I use it simply to keep learning and observing new kernel features to help me with my day job.
4. Why am I posting? I hope my trial and errors might help someone. I also hope I will get some ideas based on responses this post, which will be interesting to try. At last but not the least, I wanted to thank maintainers of dracut and all awesome people here