Mailing List Archive: [SOLVED] Kernel build failing on new install

[SOLVED] Kernel build failing on new install

Oct 13, 2020, 7:13 AM

Post #1 of 8 (854 views)

On Tue, Oct 13, 2020 at 09:08:33AM +0200, J. Roeleveld wrote
> On Tuesday, October 13, 2020 3:04:33 AM CEST Walter Dnes wrote:
> > I'm near the tail-end of an install, trying to build the kernel.
> > "make" gets an error as follows. Any ideas?
> >
> > (chroot) livecd /usr/src/linux # make
> > CALL scripts/checksyscalls.sh
> > CALL scripts/atomic/check-atomics.sh
> > DESCEND objtool
> > CHK include/generated/compile.h
> > CHK kernel/kheaders_data.tar.xz
> > GEN kernel/kheaders_data.tar.xz
> > make[1]: *** [kernel/Makefile:133: kernel/kheaders_data.tar.xz] Error 127
> > make: *** [Makefile:1729: kernel] Error 2
>
> Try disabling CONFIG_IKHEADERS in your kernel config.
> I have it disabled on my system.

Thanks. That fixed my problem. It seems that deleting stuff in "make
menuconfig" is 90% of the work in a kernel config. All etherenet
drivers are default enabled. What bugs me is that with every kernel
upgrade, "make oldconfig" shows a whole bunch of new ethernet drivers,
and they're all default enabled.

--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [SOLVED] Kernel build failing on new install [ In reply to ]

neil at digimed

Oct 13, 2020, 9:57 AM

Post #2 of 8 (854 views)

Permalink

On Tue, 13 Oct 2020 10:13:34 -0400, Walter Dnes wrote:

> > Try disabling CONFIG_IKHEADERS in your kernel config.
> > I have it disabled on my system.
>
> Thanks. That fixed my problem. It seems that deleting stuff in "make
> menuconfig" is 90% of the work in a kernel config. All etherenet
> drivers are default enabled. What bugs me is that with every kernel
> upgrade, "make oldconfig" shows a whole bunch of new ethernet drivers,
> and they're all default enabled.

AFAIR that option only enables the brand of card, the individual models
still have to be selected. But it is annoying when configuring a new
version of a working kernel.

--
Neil Bothwick

Nothing is illegal if one hundred businessmen decide to do it.

Re: [SOLVED] Kernel build failing on new install [ In reply to ]

peter at prh

Oct 13, 2020, 10:06 AM

Post #3 of 8 (854 views)

Permalink

On Tuesday, 13 October 2020 15:13:34 BST Walter Dnes wrote:

> It seems that deleting stuff in "make menuconfig" is 90% of the work in a
> kernel config. All etherenet drivers are default enabled. What bugs me is
> that with every kernel upgrade, "make oldconfig" shows a whole bunch of new
> ethernet drivers, and they're all default enabled.

You can avoid that by copying your .config file from the previous version.

--
Regards,
Peter.

Re: [SOLVED] Kernel build failing on new install [ In reply to ]

ash at suugaku

Oct 13, 2020, 10:12 AM

Post #4 of 8 (854 views)

Permalink

On Tue, Oct 13, 2020 at 06:06:51PM +0100, Peter Humphrey wrote:
> On Tuesday, 13 October 2020 15:13:34 BST Walter Dnes wrote:
>
> > It seems that deleting stuff in "make menuconfig" is 90% of the work in a
> > kernel config. All etherenet drivers are default enabled. What bugs me is
> > that with every kernel upgrade, "make oldconfig" shows a whole bunch of new
> > ethernet drivers, and they're all default enabled.
>
> You can avoid that by copying your .config file from the previous version.

Even then, running a `make syncconfig` on your old .config in a new kernel
sources directory will ask all the same questions regarding new features. Some
defaults are sensible, some are not.

--

Ashley Dixon
suugaku.co.uk

2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA

Re: [SOLVED] Kernel build failing on new install [ In reply to ]

grant.b.edwards at gmail

Oct 13, 2020, 6:28 PM

Post #5 of 8 (854 views)

Permalink

On 2020-10-13, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Tue, 13 Oct 2020 10:13:34 -0400, Walter Dnes wrote:
>
>> > Try disabling CONFIG_IKHEADERS in your kernel config.
>> > I have it disabled on my system.
>>
>> Thanks. That fixed my problem. It seems that deleting stuff in
>> "make menuconfig" is 90% of the work in a kernel config.

I can't even remember the last time I configured a kernel from
scratch. I always start with a .config file from an older version or
a different machine.

>> All etherenet drivers are default enabled. What bugs me is that
>> with every kernel upgrade, "make oldconfig" shows a whole bunch of
>> new ethernet drivers, and they're all default enabled.
>
> AFAIR that option only enables the brand of card, the individual models
> still have to be selected.

That's how it has always worked for me. By default it will _show_ you
new drivers, but they're disabled by default. If you're paying
attention, you can disable the a whole submenu full of
new-but-disabled drivers and save a bunch of time.

> But it is annoying when configuring a new version of a working kernel.

Yep.

--
Grant

Re: [SOLVED] Kernel build failing on new install [ In reply to ]

waltdnes at waltdnes

Oct 13, 2020, 10:09 PM

Post #6 of 8 (854 views)

Permalink

On Tue, Oct 13, 2020 at 06:06:51PM +0100, Peter Humphrey wrote
> On Tuesday, 13 October 2020 15:13:34 BST Walter Dnes wrote:
>
> > It seems that deleting stuff in "make menuconfig" is 90% of the work in a
> > kernel config. All etherenet drivers are default enabled. What bugs me is
> > that with every kernel upgrade, "make oldconfig" shows a whole bunch of new
> > ethernet drivers, and they're all default enabled.
>
> You can avoid that by copying your .config file from the previous version.

That's what "make oldconfig" is about. Copy over the previous kernel
.config and use that as a starting point. Any additional ethernet
drivers in the new kernel are defaulted to enabled.

--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [SOLVED] Kernel build failing on new install [ In reply to ]

neil at digimed

Oct 14, 2020, 12:57 AM

Post #7 of 8 (854 views)

Permalink

On Wed, 14 Oct 2020 01:09:44 -0400, Walter Dnes wrote:

> > You can avoid that by copying your .config file from the previous
> > version.
>
> That's what "make oldconfig" is about. Copy over the previous kernel
> .config and use that as a starting point. Any additional ethernet
> drivers in the new kernel are defaulted to enabled.

Are you sure of that? Or is it just that the submenus containing those new
drivers are enabled? I'm sure that's how it's always worked for me.

--
Neil Bothwick

What do you do when you see an endangered animal eating an endangered
plant?

Re: [SOLVED] Kernel build failing on new install [ In reply to ]

grant.b.edwards at gmail

Oct 14, 2020, 8:17 AM

Post #8 of 8 (854 views)

Permalink

On 2020-10-14, Walter Dnes <waltdnes@waltdnes.org> wrote:

> That's what "make oldconfig" is about. Copy over the previous kernel
> .config and use that as a starting point. Any additional ethernet
> drivers in the new kernel are defaulted to enabled.

I've been doing "make oldconfig" for almost 30 years. I've never seen
a new Ethernet driver enabled by default.

--
Grant

Mailing List Archive

Mailing List Archive

Attached Files: