Johnny, Thank you for the reply and I will continue the top posting, at least for this thread. :) Based on your reply I am assuming the instructions posted on the CentOS wiki will be relevant for for 4.14.x? I did see the talk about the 4.14 kernel here. As for options I can definitely see why you would go with the Fedora defaults. I was compiling to obtain AppleTalk protocol support (not common) but I ended up using DKMS and that worked perfectly. Thank you for all of your work. Chris On 02/16/2018 10:31 AM, Johnny Hughes wrote: > I normally don't top post .. but since you did, I will to follow along > in this thread :) > > You might want to try the newer 4.14.17 kernel that we are currently > testing .. see this thread: > > https://lists.centos.org/pipermail/arm-dev/2018-February/003223.html > > If this kernel works, we will likely be upgrading to the 4.14.x LTS tree. > > There does seem to be some differences in some config options between > the 4.9.x and 4.14.x kernels (we took the default configs for each from > Fedora). If we need to turn on (or off) options in the 4.14.x config > file, please feed that back to us on this list. > > Thanks, > Johnny Hughes > > > On 02/07/2018 02:54 PM, Chris Szilagyi wrote: >> I finally ended up working around the problem by adding a copy statement >> in the kernel.spec file, just after it runs the scripts to generate the >> configs, to manually copy my working config file to the >> BUILD/kernel-*/linux-*/ folder. From there it looks like the scripts >> pick it up and then place it in to the BUILD/kernel-*/linux-*/configs/ >> folder. But initially I still am not sure where it tries to get them >> from initially. >> >> >> On 2018-02-07 09:46 AM, Chris Szilagyi wrote: >>> Hello: >>> I am following the CentOS instructions to compile a custom kernel for >>> ARM. I am following the instructions here: >>> https://wiki.centos.org/HowTos/Custom_Kernel. I do need my own config >>> which I have generated and copied to the directories as mentioned in >>> the instructions. >>> >>> I eventually get to the step and start the build with : rpmbuild -bb >>> --target=`uname -m` kernel.spec 2> build-err.log | tee build-out.log >>> >>> During the build, just after the "make -s mrproper", it tries to "cp >>> configs/kernel-4.9.75-armv7l.config", and gives the error "No such >>> file or directory". It seems that the BUILD/kernel-*/linux-*configs/ >>> directory is somehow being generated by some scripts, and the config I >>> need is not there. I can't seem to find out where it gets the config >>> files that it places in the configs folder. Can anybody shed some >>> light on this? >>> >>> I noticed that the running kernel is "armv7hl", and doing a "uname -m" >>> returns "armv7l" (missing the "h"). Not sure if this has anything to >>> do with it.