Hello,
I get
Linux Teucidide 5.7.6-201.fc32.x86_64 #1 SMP Mon Jun 29 15:15:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
while it is a machine kernel-5.18.10-200.fc36.x86_64
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 | | Room# D114A ===========================================================================
On 7/9/22 03:30, Patrick Dupre wrote:
Hello,
I get
Linux Teucidide 5.7.6-201.fc32.x86_64 #1 SMP Mon Jun 29 15:15:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
while it is a machine kernel-5.18.10-200.fc36.x86_64
Hi Patrick,
It is normal to have more than one kernel installed. uname is giving you the one you are currently running.
$ rpm -qa kernel kernel-5.17.11-200.fc35.x86_64 kernel-5.18.8-100.fc35.x86_64 kernel-5.18.7-200.fc36.x86_64
It is a bit odd that you have a fc32 one. Did you jump from fx32 to fc36?
-T
Subject: Re: uname -a
On 7/9/22 03:30, Patrick Dupre wrote:
Hello,
I get
Linux Teucidide 5.7.6-201.fc32.x86_64 #1 SMP Mon Jun 29 15:15:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
while it is a machine kernel-5.18.10-200.fc36.x86_64
Hi Patrick,
It is normal to have more than one kernel installed. uname is giving you the one you are currently running.
$ rpm -qa kernel kernel-5.17.11-200.fc35.x86_64 kernel-5.18.8-100.fc35.x86_64 kernel-5.18.7-200.fc36.x86_64
It is a bit odd that you have a fc32 one. Did you jump from fx32 to fc36?
I jumped form fc32 to fc34, and to fc36
rpm -qa kernel kernel-5.12.9-300.fc34.x86_64 kernel-5.17.12-100.fc34.x86_64 kernel-5.18.10-200.fc36.x86_64
-T _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
I jumped form fc32 to fc34, and to fc36
You may also want to have a look at, https://bugzilla.redhat.com/show_bug.cgi?id=2071034
-Joe
On 7/9/22 04:02, Patrick Dupre wrote:
I jumped form fc32 to fc34, and to fc36
rpm -qa kernel kernel-5.12.9-300.fc34.x86_64 kernel-5.17.12-100.fc34.x86_64
Hi Patrick,
When you boot, just as the OS is about to start and grub asks you what kernel to run, press your down arrow key to stop the count down and write us back what the default kernel grub wanted to run is.
-T
Hello every body,
I still have this issue,
I select (from grub) to boot on
menuentry 'Fedora Linux 36 (Workstation Edition) (on /dev/sda6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-0-rescue-03f1745f56634738ac83375619d247ec--a5b809ae-61c2-4d67-b0f3-109e99faad39' { insmod part_gpt insmod ext2 set root='hd0,gpt6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 a5b809ae-61c2-4d67-b0f3-109e99faad39 else search --no-floppy --fs-uuid --set=root a5b809ae-61c2-4d67-b0f3-109e99faad39 fi linux /boot/vmlinuz-0-rescue-03f1745f56634738ac83375619d247ec root=/dev/sda6 initrd /boot/initramfs-0-rescue-03f1745f56634738ac83375619d247ec.img }
Which is not the first OS of the list (which is fc34, still the default OS)
It really loads fc36 on /sda6
and I get:
uname -a Linux localhost.localdomain 5.17.12-100.fc34.x86_64 #1 SMP PREEMPT Mon May 30 17:47:02 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Note the date!
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 | | Room# D114A ===========================================================================
Sent: Sunday, July 10, 2022 at 6:11 AM From: "ToddAndMargo via users" users@lists.fedoraproject.org To: users@lists.fedoraproject.org Cc: "ToddAndMargo" ToddAndMargo@zoho.com Subject: Re: uname -a
On 7/9/22 04:02, Patrick Dupre wrote:
I jumped form fc32 to fc34, and to fc36
rpm -qa kernel kernel-5.12.9-300.fc34.x86_64 kernel-5.17.12-100.fc34.x86_64
Hi Patrick,
When you boot, just as the OS is about to start and grub asks you what kernel to run, press your down arrow key to stop the count down and write us back what the default kernel grub wanted to run is.
-T _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Wed, Jul 27, 2022 at 8:21 AM Patrick Dupre pdupre@gmx.com wrote:
[...] menuentry 'Fedora Linux 36 (Workstation Edition) (on /dev/sda6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-0-rescue-03f1745f56634738ac83375619d247ec--a5b809ae-61c2-4d67-b0f3-109e99faad39' {
Note that the text t display says "Fedora Linux 36", but then the vmlinuz appears to be a "rescue" vmlinuz.
insmod part_gpt insmod ext2 set root='hd0,gpt6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 a5b809ae-61c2-4d67-b0f3-109e99faad39 else search --no-floppy --fs-uuid --set=root a5b809ae-61c2-4d67-b0f3-109e99faad39 fi linux /boot/vmlinuz-0-rescue-03f1745f56634738ac83375619d247ec root=/dev/sda6 initrd /boot/initramfs-0-rescue-03f1745f56634738ac83375619d247ec.img
Again - note that the vmlinuz and initramfs are claiming to be "rescue".
}[...] It really loads fc36 on /sda6
It loads the *files* from sda6 as it has been instructed to do, assuming hd0,gpt6 maps to sda6.
[...] uname -a Linux localhost.localdomain 5.17.12-100.fc34.x86_64 #1 SMP PREEMPT Mon May 30 17:47:02 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
So it *really* loads the 5.17.12-100 kernel from Fedora 34 - not fc36.
I'm hardly a grub expert, but it looks to me like your boot entry has been modified in a manner to cause confusion - either the menu text for the rescue kernel has been modified, or somehow you have a rescue kernel attached to the "normal" Fedora 36 menu entry.
OK, I see your point, Actually, I should boot on the 4th item! How can I manage this order?
menuentry 'Fedora Linux 36 (Workstation Edition) (on /dev/sda6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.18.13-200.fc36.x86_64--a5b809ae-61c2-4d67-b0f3-109e99faad39' { insmod part_gpt insmod ext2 set root='hd0,gpt6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 a5b809ae-61c2-4d67-b0f3-109e99faad39 else search --no-floppy --fs-uuid --set=root a5b809ae-61c2-4d67-b0f3-109e99faad39 fi linux /boot/vmlinuz-5.18.13-200.fc36.x86_64 root=/dev/sda6 initrd /boot/initramfs-5.18.13-200.fc36.x86_64.img }
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 | | Room# D114A ===========================================================================
Sent: Wednesday, July 27, 2022 at 3:59 PM From: "Go Canes" letsgonhlcanes0@gmail.com To: "Community support for Fedora users" users@lists.fedoraproject.org Subject: Re: uname -a
On Wed, Jul 27, 2022 at 8:21 AM Patrick Dupre pdupre@gmx.com wrote:
[...] menuentry 'Fedora Linux 36 (Workstation Edition) (on /dev/sda6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-0-rescue-03f1745f56634738ac83375619d247ec--a5b809ae-61c2-4d67-b0f3-109e99faad39' {
Note that the text t display says "Fedora Linux 36", but then the vmlinuz appears to be a "rescue" vmlinuz.
insmod part_gpt insmod ext2 set root='hd0,gpt6' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 a5b809ae-61c2-4d67-b0f3-109e99faad39 else search --no-floppy --fs-uuid --set=root a5b809ae-61c2-4d67-b0f3-109e99faad39 fi linux /boot/vmlinuz-0-rescue-03f1745f56634738ac83375619d247ec root=/dev/sda6 initrd /boot/initramfs-0-rescue-03f1745f56634738ac83375619d247ec.imgAgain - note that the vmlinuz and initramfs are claiming to be "rescue".
}[...] It really loads fc36 on /sda6
It loads the *files* from sda6 as it has been instructed to do, assuming hd0,gpt6 maps to sda6.
[...] uname -a Linux localhost.localdomain 5.17.12-100.fc34.x86_64 #1 SMP PREEMPT Mon May 30 17:47:02 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
So it *really* loads the 5.17.12-100 kernel from Fedora 34 - not fc36.
I'm hardly a grub expert, but it looks to me like your boot entry has been modified in a manner to cause confusion - either the menu text for the rescue kernel has been modified, or somehow you have a rescue kernel attached to the "normal" Fedora 36 menu entry. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Jul 9, 2022, at 06:31, Patrick Dupre pdupre@gmx.com wrote:
Hello,
I get
Linux Teucidide 5.7.6-201.fc32.x86_64 #1 SMP Mon Jun 29 15:15:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
while it is a machine kernel-5.18.10-200.fc36.x86_64
I suspect you’ve got an extra /boot partition or directory someplace that GRUB2 is booting from, instead of the kernels owned by the current OS.
-- Jonathan Billings
Hello,
I get
Linux Teucidide 5.7.6-201.fc32.x86_64 #1 SMP Mon Jun 29 15:15:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
while it is a machine kernel-5.18.10-200.fc36.x86_64
I suspect you’ve got an extra /boot partition or directory someplace that GRUB2 is booting from, instead of the kernels owned by the current OS.
Yes,it is a multiboot
df Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 3963204 0 3963204 0% /dev tmpfs 4007996 0 4007996 0% /dev/shm tmpfs 4007996 10008 3997988 1% /run /dev/sdc3 23129256 13244128 8687172 61% / tmpfs 4007996 48 4007948 1% /tmp /dev/sdc2 435228 258272 149974 64% /boot tmpfs 801596 64 801532 1% /run/user/1000
Is the issue with /dev/sdc2 ?
-- Jonathan Billings _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Jul 9, 2022, at 08:23, Patrick Dupre pdupre@gmx.com wrote:
Yes,it is a multiboot
df Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 3963204 0 3963204 0% /dev tmpfs 4007996 0 4007996 0% /dev/shm tmpfs 4007996 10008 3997988 1% /run /dev/sdc3 23129256 13244128 8687172 61% / tmpfs 4007996 48 4007948 1% /tmp /dev/sdc2 435228 258272 149974 64% /boot tmpfs 801596 64 801532 1% /run/user/1000
Is the issue with /dev/sdc2 ?
I suspect that your mounted /boot partition has the kernels you are installing, but the kernel you are booting are on another partition that isn’t mounted. Since this isn’t UEFI, you will want to check where the bootloader is coming from, it might be one of the other OSs, which have a different grub.cfg.
Subject: Re: uname -a
On Jul 9, 2022, at 08:23, Patrick Dupre pdupre@gmx.com wrote:
Yes,it is a multiboot
df Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 3963204 0 3963204 0% /dev tmpfs 4007996 0 4007996 0% /dev/shm tmpfs 4007996 10008 3997988 1% /run /dev/sdc3 23129256 13244128 8687172 61% / tmpfs 4007996 48 4007948 1% /tmp /dev/sdc2 435228 258272 149974 64% /boot tmpfs 801596 64 801532 1% /run/user/1000
Is the issue with /dev/sdc2 ?
I suspect that your mounted /boot partition has the kernels you are installing, but the kernel you are booting are on another partition that isn’t mounted. Since this isn’t UEFI, you will want to check where the bootloader is coming from, it might be one of the other OSs, which have a different grub.cfg.
I guess that you are correct. Can I fix it?
-- Jonathan Billings _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 7/9/22 09:10, Patrick Dupre wrote:
Subject: Re: uname -a
On Jul 9, 2022, at 08:23, Patrick Dupre pdupre@gmx.com wrote:
Yes,it is a multiboot
df Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 3963204 0 3963204 0% /dev tmpfs 4007996 0 4007996 0% /dev/shm tmpfs 4007996 10008 3997988 1% /run /dev/sdc3 23129256 13244128 8687172 61% / tmpfs 4007996 48 4007948 1% /tmp /dev/sdc2 435228 258272 149974 64% /boot tmpfs 801596 64 801532 1% /run/user/1000
Is the issue with /dev/sdc2 ?
I suspect that your mounted /boot partition has the kernels you are installing, but the kernel you are booting are on another partition that isn’t mounted. Since this isn’t UEFI, you will want to check where the bootloader is coming from, it might be one of the other OSs, which have a different grub.cfg.
I guess that you are correct. Can I fix it?
Check the /boot entry in /etc/fstab for the correct partition ID (label, uuid as used). Check the *.conf entries in /boot/loader/entries for the partition ID's. Save /etc/grub2.cfg to a .bak and rerun "grub2-mkconfig -o /boot/grub2/grub.cfg" compare the new one with the old.