[SOLVED] Fedora 37 after upgrade from 36 - change kernel version problem
FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Fedora 37 after upgrade from 36 - change kernel version problem
I run the Aarch64 version on an M1 MacMini under UTM/QEMU.
After upgrade to Fedora 37 I got different kernel Versions.
How I could change to the last kernel 6.0.12-300.fc37?
cat /proc/version
Linux version 5.18.17-200.fc36.aarch64 (mockbuild@buildvm-a64-05.iad2.fedoraproject.org) (gcc (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1), GNU ld version 2.37-27.fc36) #1 SMP PREEMPT_DYNAMIC Thu Aug 11 13:58:26 UTC 2022
How did you upgrade? The normal result of a Fedora 36 to 37 upgrade is installation and use of the latest F37 kernel. Are vmlinuz-6.0.*-30?.fc37 present in /boot/ along with 5.18.17-200.fc36? Are stanzas in your bootloader for 6.0.* kernels present? I don't use aarch64, so don't know what bootloader it uses or how it is configured there. But, I have found it is possible for F37 kernel installation to fail to put everything traditionally required into /boot/. When that happens, I copy vmlinuz from /usr/lib/modules/<version>/ to /boot/, rename it to include the applicable version string, then create a bootloader stanza for it manually, before it becomes usable. Alternatively, a boot stanza can be created that loads vmlinuz directly from the applicable /usr/lib/modules/ directory.
Please do not post screenshots for directory listings or other command output. Use a terminal and ls -gG, redirecting command output to a file first if it will help you, then copy and paste the command or file content here using code tags. Your first screenshot doesn't list any kernels. So, we still don't know if /boot/ contains any kernels.
Now I downloaded the new Fedora-Workstation-Live-aarch64-37-1.7.iso and install a new VM.
With this and after updates after installing the newest kernel works.
I think something went wrong with the upgrade from ver 36 to ver 37
I deleted the old VM. I still had a backup of this older VM via the Mac TimeMachine backup.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.