Re: compiling and installing a custom kernel (5.5.7)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 3/2/20 12:16 PM, Javier Martinez Canillas wrote:
Hello Hans,

On 3/1/20 7:18 PM, Hans de Goede wrote:
Hi,

On 3/1/20 6:06 PM, Michael J. Baars wrote:
Hi,

Since I've upgraded to Fedora 31, I'm having trouble compiling and
installing custom kernels. This never happened with Fedora 30, so some
things must have changed that I'm unaware of.

'dnf info kernel-5.5.7' shows that the Fedora team is successful in
compiling and installing the new kernels where I'm not. Help would be
appreciated.

After downloading the most recent kernel from the kernel archives I run
this sequence of commands as usual:

make menuconfig O=../linux-5.5.7-build
make modules_install O=../linux-5.5.7-build
make install O=../linux-5.5.7-build

The first two commands run without error. The third one, it seems is
not looking for the grub bootloader, but for the lilo bootloader, and
exits with an error. This is only since I use Fedora 31.

What am I doing wrong??? Have I forgotten to install a dependency of
some sort?

Also, I found this link:
https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/
which seems a little outdated. It is not of any use to me in its
current state.

The kernel makefile expects grub installs to have an "installkernel"
command available. On Fedora this is part of grubby which in recent

That's correct.

Fedora releases is no longer installed by default.

"sudo dnf install grubby"

Should make the last step work.

Javier (added to the Cc) is there any chance we can move the installkernel
script into a package which is installed by default?


The old grubby tool is no longer installed by default and is part of the
grubby-deprecated package now. But the grubby package that contains the
installkernel script (and the grubby script that manages the snippets in
/boot/loader/entries) should still be installed by default.

At least for the Fedora 31 livecd grubby is not installed by default (I just
double checked) and AFAIK booting the livecd and then doing an install is
how most (or at least a lot) of our users install Fedora.

So if the new grubby is intended to be installed by default then we need
to make some changes to either comps or to the compose config files for
the Workstation livecd.

Regards,

Hans
_______________________________________________
kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [USB]     [Asterisk PBX]

  Powered by Linux