1 |
On Fri, Nov 11, 2022 at 1:25 AM Dale <rdalek1967@×××××.com> wrote: |
2 |
> |
3 |
> Is there some major change that causes copying .config file from 5.14 to |
4 |
> 5.18 or higher to break? |
5 |
|
6 |
So, I just upgraded to 5.15 recently and tend to stick to LTS kernels, |
7 |
precisely to minimize this sort of thing. |
8 |
|
9 |
My guess is that you missed something in make oldconfig, but obviously |
10 |
without exact errors that could be completely wrong. |
11 |
|
12 |
I can't speak to 6.0 specifically, but one thing that I've found is a |
13 |
gotcha is when they consolidate config items under higher level ones. |
14 |
So they'll take what used to be 50 questions, and turn it into 1 |
15 |
question with 50 questions underneath it. The 1 question shows up as |
16 |
a new config item, and if you don't appreciate what it does and answer |
17 |
no to it, then you'll disable every item underneath it. |
18 |
|
19 |
Basically, don't assume that any new question is a new feature, and if |
20 |
you say no you'll still have all the pre-existing features. It could |
21 |
be a virtual question and answering no turns off a whole bunch of |
22 |
things that you had previously said yes to. You need to review |
23 |
oldconfig questions pretty carefully. You could try defaulting the |
24 |
answers but even then the defaults aren't always reasonable. They |
25 |
don't just turn on things you don't need. For example, by default |
26 |
linux turns off CGROUP support, and almost everything uses that today. |
27 |
That was just the first thing I checked, and I bet there are a million |
28 |
other gotchas like that. |
29 |
|
30 |
-- |
31 |
Rich |