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.
Best regards, Mischa Baars.
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 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?
Regards,
Hans
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.
Regards,
Hans
Best regards,
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
On Mon, 2020-03-02 at 13:23 +0100, Hans de Goede wrote:
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.
Gentlemen,
I've just installed A grubby, everything is working again.
Thanks for the help, Mischa.
Regards,
Hans _______________________________________________ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On Mon, Mar 2, 2020 at 5:23 AM Hans de Goede hdegoede@redhat.com wrote:
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.
It's not on Fedora-Workstation-Live-x86_64-32-20200226.n.0.iso
I guess at one time something had it listed as a dependency and dragged it in?
Grubby is in group 'standard', and 'standard' is in environment 'developer-workstation-environment'. But 'standard' is not in 'workstation-product-environment'.
I have no idea what developer-workstation-environment is.
workstation-product group also does not have grubby in it
And wow now I really want to take up a drinking habit. I think it's explicit that workstation-product-environment does not want the standard group brought into it for some reason, and has its own list of packages to be added. And that's where grubby would get inserted.
https://pagure.io/fedora-comps/blob/master/f/comps-f32.xml.in https://pagure.io/fedora-comps/blob/master/f/comps-f33.xml.in
Hello Hans and Chris,
On 3/2/20 8:46 PM, Chris Murphy wrote:
On Mon, Mar 2, 2020 at 5:23 AM Hans de Goede hdegoede@redhat.com wrote:
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.
It's not on Fedora-Workstation-Live-x86_64-32-20200226.n.0.iso
You are correct. I tested with a Server minimal install and it was there so I (wrongly) assumed that it would be installed for Workstation as well.
This is my fault, because the grubby package used to be in core and someone moved it to arm-tools due extlinux not having BLS support and still needing the old grubby tool.
But I mentioned that only the grubby-deprecated package was needed for armv7 and that grubby should be in a group that's included by all products/spins.
And was suggested standard as the correct group, but as Chris mentioned this is not pulled by workstation-product-environment.
I wonder how we didn't find this bug before...
I guess at one time something had it listed as a dependency and dragged it in?
Grubby is in group 'standard', and 'standard' is in environment
Right, that's why it gets pulled in for Server installs:
server-product-environment -> standard -> grubby
'developer-workstation-environment'. But 'standard' is not in 'workstation-product-environment'.
I have no idea what developer-workstation-environment is.
workstation-product group also does not have grubby in it
And wow now I really want to take up a drinking habit. I think it's explicit that workstation-product-environment does not want the standard group brought into it for some reason, and has its own list of packages to be added. And that's where grubby would get inserted.
If some products/spins don't want the standard group to be brought into then I think that grubby should be moved to the core group again. I've proposed the following pull-request for fedora-comps:
https://pagure.io/fedora-comps/pull-request/463
Best regards,
On Sun, 01 Mar 2020 18:06:43 +0100 "Michael J. Baars" mjbaars1977.fedora-kernel@cyberfiber.eu wrote:
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.
I successfully have built and installed custom kernels for both 5.5 and 5.6 in F31. However, I use an older method with the src.rpm, https://fedoraproject.org/wiki/Building_a_custom_kernel/Source_RPM instead of any of the currently recommended methods, and install from rpms. I am unfamiliar with the method you are using, so cannot offer any help. However, it does sound like a bug that anything would be looking for lilo in F31. I think the currently recommended methods (mock? fedpkg?) automatically install any needed dependencies from the repositories, so if it is a dependency error, they would correct that. What does the output say? I usually use something like > output.save 2> error.save on the commands when I have problems, set verbose in the spec file, and then examine the saved output to see what caused the error. A dependency problem will usually show up before the actual error in the output e.g. in your case it might warn of not finding something it is looking for before it defaults to lilo.
On Sun, 2020-03-01 at 12:05 -0700, stan wrote:
On Sun, 01 Mar 2020 18:06:43 +0100 "Michael J. Baars" mjbaars1977.fedora-kernel@cyberfiber.eu wrote:
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.
I successfully have built and installed custom kernels for both 5.5 and 5.6 in F31. However, I use an older method with the src.rpm, https://fedoraproject.org/wiki/Building_a_custom_kernel/Source_RPM instead of any of the currently recommended methods, and install from rpms. I am unfamiliar with the method you are using, so cannot offer any help. However, it does sound like a bug that anything would be looking for lilo in F31. I think the currently recommended methods (mock? fedpkg?) automatically install any needed dependencies from the repositories, so if it is a dependency error, they would correct that. What does the output say? I usually use something like > output.save 2> error.save on the commands when I have problems, set verbose in the spec file, and then examine the saved output to see what caused the error. A dependency problem will usually show up before the actual error in the output e.g. in your case it might warn of not finding something it is looking for before it defaults to lilo.
Hi Stan,
Use this method when you need to build kernels with personalized kernel configuration settings.
Regards, Mischa.
kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On Mon, 02 Mar 2020 15:21:00 +0100 "Michael J. Baars" mjbaars1977.fedora-kernel@cyberfiber.eu wrote:
Hi Stan,
Use this method when you need to build kernels with personalized kernel configuration settings.
Thanks, but I already do that, that's why I started building a custom kernel. I use a config file tuned to the hardware I run (make localconfig?). I used to also patch the kernel, but I'm taking a break from that, as the kernel seems to be working OK for me without the patch, and it needs to be regularly maintained with the constant changes.
It's pretty straightforward to customize the kernel config, using the config file from the previous kernel in /boot and make oldconfig, and then make menuconfig, after the sources are unpacked. Then I just move the config to SOURCES/kernel-local, and rpmbuild uses it when building the rpms. I like that the custom kernels are known and managed by the package manager.
I think that your method probably builds a vanilla kernel, one without the Fedora kernel patches. But, as I said, I am unfamiliar with that method, so there is probably a way to apply the Fedora kernel patches that way too.
One of the joys of linux, the many different ways to accomplish the same task.
kernel@lists.fedoraproject.org
-
Chris Murphy -
Hans de Goede -
Javier Martinez Canillas -
Michael J. Baars -
stan