[OE-core] How to upgrade the kernel
Muhlenkamp, Lewis
lewis.muhlenkamp at stryker.com
Mon Dec 16 18:37:06 UTC 2019
Hello,
I am still fairly new to Yocto and Openembedded. I've built a custom distribution and have a few images. I'm now in the process of trying to determine how to upgrade from one version to another.
I created an image using Yocto 2.6. When I install it, it installs the following kernel RPMs:
### Start "rpm -qa | grep kernel | grep -v kernel-module" output ###
kernel-4.14.110+git0+bc35d5bd22_f93147df5d-r0.corei7_64_intel_common
kernel-image-4.14.110-intel-pk-standard-4.14.110+git0+bc35d5bd22_f93147df5d-r0.corei7_64_intel_common
kernel-4.14.110-intel-pk-standard-4.14.110+git0+bc35d5bd22_f93147df5d-r0.corei7_64_intel_common
kernel-image-bzimage-4.14.110-intel-pk-standard-4.14.110+git0+bc35d5bd22_f93147df5d-r0.corei7_64_intel_common
### End "rpm -qa | grep kernel | grep -v kernel-module" output ###
I built a newer image using Yocto 3.0. In the RPM repo I have the following kernel RPMs:
### Start "ls -1 /var/opt/repos/os | grep kernel | grep -v kernel-module" output ###
kernel-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm
kernel-4.19.73-intel-pk-standard-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm
kernel-dev-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm
kernel-image-4.19.73-intel-pk-standard-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm
kernel-image-bzimage-4.19.73-intel-pk-standard-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm
kernel-vmlinux-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common.rpm
systemd-kernel-install-243+0+efb536d0cb-r0.corei7_64.rpm
### End "ls -1 /var/opt/repos/os | grep kernel | grep -v kernel-module" output ###
When I try to do "dnf upgrade" I get the following error messages:
### Start excerpt from "dnf upgrade" command ###
Last metadata expiration check: 0:40:06 ago on Mon Dec 16 17:43:31 2019.
Dependencies resolved.
================================================================================
Package
Arch Version Repository
Size
================================================================================
Upgrading:
kernel
corei7_64_intel_common 4.19.73+git0+a7cb57afb9_ca05e9cd64-r0 OS_Repo 5.6 k
kernel-4.19.73-intel-pk-standard
corei7_64_intel_common 4.19.73+git0+a7cb57afb9_ca05e9cd64-r0 OS_Repo 16 k
kernel-image-4.19.73-intel-pk-standard
corei7_64_intel_common 4.19.73+git0+a7cb57afb9_ca05e9cd64-r0 OS_Repo 5.8 k
kernel-image-bzimage-4.19.73-intel-pk-standard
corei7_64_intel_common 4.19.73+git0+a7cb57afb9_ca05e9cd64-r0 OS_Repo 7.8 M
Transaction Summary
================================================================================
Install 1297 Packages
Upgrade 666 Packages
Skip 5 Packages
Total size: 232 M
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction check error:
file /boot/bzImage from install of kernel-image-bzimage-4.19.73-intel-pk-standard-4.19.73+git0+a7cb57afb9_ca05e9cd64-r0.corei7_64_intel_common conflicts with file from package kernel-image-bzimage-4.14.110-intel-pk-standard-4.14.110+git0+bc35d5bd22_f93147df5d-r0.corei7_64_intel_common
Error Summary
-------------
### End excerpt from "dnf upgrade" command ###
I also tried running "dnf upgrade --best --allowerasing", but got the same results.
Can I upgrade a system using the dnf command? If so, how? If not, what do I need to do to allow the system to be upgraded using the dnf command?
Thank you
Lewis Muhlenkamp
Follow this link to read our Privacy Statement<https://www.stryker.com/content/stryker/gb/en/legal/global-policy-statement.html/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20191216/9396cd64/attachment.html>
More information about the Openembedded-core
mailing list