Trying out the new NovaCustom laptop at work today
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
make oldconfig doesn't look at anything beyond the .config file in the kernel source code directory, which is something you have complete control over as you're the one that would put it there. A problem with defconfig is that it applies the default settings which, as you can see, aren't always useful. Some editing is needed. olddefcofig is a combination of oldconfig and defconfig in that it's like running oldconfig but it selects the default answers for new config symbols. Maybe that's what you want. Or maybe there's some new feature or thing you want, like the new Xe thing, and maybe the kernel's default is that this new feature or thing isn't turned on by default; that's the case for a lot of stuff. In that case going with the default wouldn't give you want you want.
OK, I see, you are right then, 'make oldconfig' is what I need then for now. Thanks for the info, very useful.
One other question - do you run 'make mrproper' or 'make clean' prior to compiling? I see these recommended in some how-to's, but I'm thinking the deblobbing process might have already taken care of this cleanup, as the deblob script has a lot of cleaning steps, but I'm not sure.
EDIT - it's kind of an odd question, but I've seen different views on cleaning the source. For example, Linux From Scratch recommends always running 'make mrproper' prior to compiling based on the Linux kernel team's recommendation - saying that you can never trust a kernel tree to be really clean once you un-tar it. However, others are recommending to run 'make clean' or 'make mrproper' if you are re-compiling over a compiled source that you already compiled previously to delete previously generated files. I'm assuming the Linux-libre source actually IS clean once you un-tar it.
My kernel automation script does both with make clean mrproper (you can combine!) :) The goal of Linux-libre is making minimal changes compared to upstream so Linux-libre should be just as clean as Linux in this regard.
>"My kernel automation script"
Is this available to review? I don't see it in your git repo, or not anything obviously named 'kernel-automation.sh' or anything like that. I'm just interested in seeing your steps and learning from them where possible.
It's not one program but a bunch for different purposes. The repository called kernel-tools.git exists and lets you build a cross-compiling toolchain for kernel compiling for all of the different architectures I support and for making the metapackages for things like freesh-archive-keyring. The one that does the setup for new kernel versions isn't in there. I'd want to do some cleaning before adding it.
We're up to the 6.9.3 kernel now, and just cruising along. I like it when things just work.
I don't think I've felt as comfortable as this with a kernel since 4.19, which I was using up to last year, so about 5 years total with one kernel version. One more year together and we would have been considered a common law marriage in the state of Texas.
I'm running the DWM minimal window manager today and my total memory used at startup is 177mb. Makes me sooooo happy. I'm like a child in a candy store when I can get my used memory below 200mb.