Hello,
I did an upgrade today from from FC37 to FC39 and all went well except that the kernel is NOT in grub.
All the apps are now FC39 but no option to boot with the FC39 kernel.
I tried to reinstall the kernel to see if it would be picked up by grub that that didn't work either.
RPM shows that the kernel is installed.
How do I progress from here?
Robin
On 11/11/23 19:48, Robin Laing wrote:
Hello,
I did an upgrade today from from FC37 to FC39 and all went well except that the kernel is NOT in grub.
All the apps are now FC39 but no option to boot with the FC39 kernel.
I tried to reinstall the kernel to see if it would be picked up by grub that that didn't work either.
RPM shows that the kernel is installed.
How do I progress from here?
sudo update-grub ?
On 11/11/2023 22.12, Mike Wright wrote:
On 11/11/23 19:48, Robin Laing wrote:
Hello,
I did an upgrade today from from FC37 to FC39 and all went well except that the kernel is NOT in grub.
All the apps are now FC39 but no option to boot with the FC39 kernel.
I tried to reinstall the kernel to see if it would be picked up by grub that that didn't work either.
RPM shows that the kernel is installed.
How do I progress from here?
sudo update-grub ? _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
I tried that and it didn't work.
I got help on the Fedora Discord and it was a strange issue related to previous upgrades.
I had a directory on my system pointing to the FC39 kernel.
-rwx------. 1 root root 35973272 Nov 11 19:24 /boot/efi/1a7fd46e52044d0b903f101cf47a634d/6.5.11-300.fc39.x86_64/initrd
The instructions I got were to remove that directory and run the command
rpm -q --scripts kernel-core | grep add
Which brought me to this script to run.
/bin/kernel-install add 6.5.11-300.fc39.x86_64 /lib/modules/6.5.11-300.fc39.x86_64/vmlinuz || exit $?
The FC39 kernel now shows up when I run grubby --info=ALL
From the help on Discord, the comment was:
The existence of the directory /boot/efi/1a7fd46e52044d0b903f101cf47a634d triggers the update to generate systemd-boot configuration. In previous version it did not always do that.
I have done what I have been instructed remotely and will try booting in the morning to see if it worked.
Will post an update.
Robin
https://www.shisaihua.com/fedora-39-upgraded-and-kernel-not-shown-in-grub-li...
to remove /boot/efi/xxxxxxxx folder works.
Robin Laing mesat@telusplanet.net 于2023年11月12日周日 16:46写道:
On 11/11/2023 22.12, Mike Wright wrote:
On 11/11/23 19:48, Robin Laing wrote:
Hello,
I did an upgrade today from from FC37 to FC39 and all went well except that the kernel is NOT in grub.
All the apps are now FC39 but no option to boot with the FC39 kernel.
I tried to reinstall the kernel to see if it would be picked up by grub that that didn't work either.
RPM shows that the kernel is installed.
How do I progress from here?
sudo update-grub ? _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
I tried that and it didn't work.
I got help on the Fedora Discord and it was a strange issue related to previous upgrades.
I had a directory on my system pointing to the FC39 kernel.
-rwx------. 1 root root 35973272 Nov 11 19:24 /boot/efi/1a7fd46e52044d0b903f101cf47a634d/6.5.11-300.fc39.x86_64/initrd
The instructions I got were to remove that directory and run the command
rpm -q --scripts kernel-core | grep addWhich brought me to this script to run.
/bin/kernel-install add 6.5.11-300.fc39.x86_64 /lib/modules/6.5.11-300.fc39.x86_64/vmlinuz || exit $?
The FC39 kernel now shows up when I run grubby --info=ALL
From the help on Discord, the comment was:
The existence of the directory /boot/efi/1a7fd46e52044d0b903f101cf47a634d triggers the update to generate systemd-boot configuration. In previous version it did not always do that.
I have done what I have been instructed remotely and will try booting in the morning to see if it worked.
Will post an update.
Robin _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
In my searches, didn't come across that thread. It was my first time on Discord.
I didn't have to re-install the kernel, just ran the script that Villy Kruse recommended.
------------- The exact command to do that you can find by running
rpm -q --scripts kernel-core | grep add
Example
/bin/kernel-install add 6.5.9-300.fc39.x86_64 /lib/modules/6.5.9-300.fc39.x86_64/vmlinuz || exit $? /bin/kernel-install add 6.5.10-300.fc39.x86_64 /lib/modules/6.5.10-300.fc39.x86_64/vmlinuz || exit $? /bin/kernel-install add 6.5.11-300.fc39.x86_64 /lib/modules/6.5.11-300.fc39.x86_64/vmlinuz || exit $?
Re-installing the latest kernel-core package would do the same thing except downloading it again from the repository. ----------------
Computer booted today and now works.
Robin
On 12/11/2023 05.59, Suse Shi wrote:
https://www.shisaihua.com/fedora-39-upgraded-and-kernel-not-shown-in-grub-li... https://www.shisaihua.com/fedora-39-upgraded-and-kernel-not-shown-in-grub-list/
to remove /boot/efi/xxxxxxxx folder works.
Robin Laing <mesat@telusplanet.net mailto:mesat@telusplanet.net> 于 2023年11月12日周日 16:46写道:
On 11/11/2023 22.12, Mike Wright wrote: > On 11/11/23 19:48, Robin Laing wrote: >> Hello, >> >> I did an upgrade today from from FC37 to FC39 and all went well except >> that the kernel is NOT in grub. >> >> All the apps are now FC39 but no option to boot with the FC39 kernel. >> >> I tried to reinstall the kernel to see if it would be picked up by >> grub that that didn't work either. >> >> RPM shows that the kernel is installed. >> >> How do I progress from here? > > sudo update-grub ? > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> > To unsubscribe send an email to users-leave@lists.fedoraproject.org <mailto:users-leave@lists.fedoraproject.org> > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ <https://docs.fedoraproject.org/en-US/project/code-of-conduct/> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines <https://fedoraproject.org/wiki/Mailing_list_guidelines> > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org <https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org> > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue <https://pagure.io/fedora-infrastructure/new_issue> I tried that and it didn't work. I got help on the Fedora Discord and it was a strange issue related to previous upgrades. I had a directory on my system pointing to the FC39 kernel. -rwx------. 1 root root 35973272 Nov 11 19:24 /boot/efi/1a7fd46e52044d0b903f101cf47a634d/6.5.11-300.fc39.x86_64/initrd The instructions I got were to remove that directory and run the command rpm -q --scripts kernel-core | grep add Which brought me to this script to run. /bin/kernel-install add 6.5.11-300.fc39.x86_64 /lib/modules/6.5.11-300.fc39.x86_64/vmlinuz || exit $? The FC39 kernel now shows up when I run grubby --info=ALL From the help on Discord, the comment was: The existence of the directory /boot/efi/1a7fd46e52044d0b903f101cf47a634d triggers the update to generate systemd-boot configuration. In previous version it did not always do that. I have done what I have been instructed remotely and will try booting in the morning to see if it worked. Will post an update. Robin _______________________________________________ users mailing list -- users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe send an email to users-leave@lists.fedoraproject.org <mailto:users-leave@lists.fedoraproject.org> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ <https://docs.fedoraproject.org/en-US/project/code-of-conduct/> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines <https://fedoraproject.org/wiki/Mailing_list_guidelines> List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org <https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue <https://pagure.io/fedora-infrastructure/new_issue>-- Regards, -suse
On 12 Nov 2023, at 21:51, Robin Laing mesat@telusplanet.net wrote:
It was my first time on Discord.
Its discuss not discord.
Barry
Okay.
My confusion.
Still my first time to use it.
On 12/11/2023 15.57, Barry wrote:
On 12 Nov 2023, at 21:51, Robin Laing mesat@telusplanet.net wrote:
It was my first time on Discord.
Its discuss not discord.
Barry
Okay.
My confusion.
Still my first time to use it.
I thought it was discuss on discord. Everything else seems to be going to Discord and my mind just thought the same thing. I am sorry.
Robin
On Sun, 2023-11-12 at 22:24 -0700, Robin Laing wrote:
Okay.
My confusion.
Still my first time to use it.
On 12/11/2023 15.57, Barry wrote:
On 12 Nov 2023, at 21:51, Robin Laing mesat@telusplanet.net wrote:
It was my first time on Discord.
Its discuss not discord.
Barry
Okay.
My confusion.
Still my first time to use it.
I thought it was discuss on discord. Everything else seems to be going to Discord and my mind just thought the same thing. I am sorry.
AFAIK it's Discourse, not Discuss (or Discord). I say this only because the official Evolution support has moved to that platform along with a lot of other Gnome stuff.
Suffice it to say that I detest it, but that's another topic.
poc
On 13 Nov 2023, at 11:01, Patrick O'Callaghan pocallaghan@gmail.com wrote:
AFAIK it's Discourse, not Discuss (or Discord). I say this only because the official Evolution support has moved to that platform along with a lot of other Gnome stuff.
You are right the software is Discourse (https://www.discourse.org/) and web sites often use discuss.<domain>.
Fedora uses discussion.fedoraproject.org http://discussion.fedoraproject.org/ KDE uses discuss.kde.org Python uses discuss.python.org http://discuss.python.org/
Personally I prefer discourse to email for its markup and editing capabilities.
Barry
On Mon, 2023-11-13 at 11:39 +0000, Barry Scott wrote:
On 13 Nov 2023, at 11:01, Patrick O'Callaghan pocallaghan@gmail.com wrote:
AFAIK it's Discourse, not Discuss (or Discord). I say this only because the official Evolution support has moved to that platform along with a lot of other Gnome stuff.
You are right the software is Discourse (https://www.discourse.org/) and web sites often use discuss.<domain>.
Fedora uses discussion.fedoraproject.org http://discussion.fedoraproject.org/ KDE uses discuss.kde.org Python uses discuss.python.org http://discuss.python.org/
Personally I prefer discourse to email for its markup and editing capabilities.
I dislike it because a) it requires a browser (I know you can interact with it via email, but that's genuinely terrible, and b) discussions disappear after a time rather than being permanently available.
I could go on, but I don't want to hijack this thread.
poc
On Mon, Nov 13, 2023 at 7:26 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Mon, 2023-11-13 at 11:39 +0000, Barry Scott wrote:
On 13 Nov 2023, at 11:01, Patrick O'Callaghan pocallaghan@gmail.com wrote:
AFAIK it's Discourse, not Discuss (or Discord). I say this only because the official Evolution support has moved to that platform along with a lot of other Gnome stuff.
You are right the software is Discourse (https://www.discourse.org/) and web sites often use discuss.<domain>.
Fedora uses discussion.fedoraproject.org http://discussion.fedoraproject.org/ KDE uses discuss.kde.org Python uses discuss.python.org http://discuss.python.org/
Personally I prefer discourse to email for its markup and editing capabilities.
I dislike it because a) it requires a browser (I know you can interact with it via email, but that's genuinely terrible, and b) discussions disappear after a time rather than being permanently available.
Yeah, things were a lot better with mailing lists. You did not have to join a social media site, you weren't the product, and search engines could index the messages and subsequently return them in search results. Nowadays it's difficult to find things.
I could go on, but I don't want to hijack this thread.
You can't put that genie back in the bottle :)
Jeff
On 13 Nov 2023, at 12:27, Patrick O'Callaghan pocallaghan@gmail.com wrote:
b) discussions disappear after a time rather than being permanently available.
I am not noticing any deletion of posts.
Barry
On Mon, 2023-11-13 at 21:06 +0000, Barry wrote:
On 13 Nov 2023, at 12:27, Patrick O'Callaghan pocallaghan@gmail.com wrote:
b) discussions disappear after a time rather than being permanently available.
I am not noticing any deletion of posts.
I've only used the Evolution forum, but there is an explicit statement under every thread:
This topic will close a month after the last reply.
I don't know if this is specific to Evolution, or to Gnome, or to Discourse, but I think it's indicative of an attitude that topics (by which they seem to mean threads) are only of transient relevance, something completely at odds with the goals of a support forum.
That's why a group of us set up a more traditional mailing list for Evolution when the existing one was shut down by Gnome. Those interested can find it at:
https://lists.osuosl.org/mailman/listinfo/evolution-users
poc
On 13 Nov 2023, at 22:54, Patrick O'Callaghan pocallaghan@gmail.com wrote:
This topic will close a month after the last reply.
That means closed to new replies, not that it is deleted.
Barry
On Tue, 2023-11-14 at 14:22 +0000, Barry wrote:
On 13 Nov 2023, at 22:54, Patrick O'Callaghan pocallaghan@gmail.com wrote:
This topic will close a month after the last reply.
That means closed to new replies, not that it is deleted.
Maybe, but it still means one can't answer an old question, which is sometimes useful, including if one wants to reply to one's own query with SOLVED.
poc
On 14 Nov 2023, at 16:17, Patrick O'Callaghan pocallaghan@gmail.com wrote:
Maybe, but it still means one can't answer an old question, which is sometimes useful, including if one wants to reply to one's own query with SOLVED.
That is a policy that the site chooses. With the Fedora discuss the infrastructure people are open to adapting policy over time to what serves the community well.
I don't think there is a close time for the discuss.fedoraproject.org topics, or its very large.
Some topics get locked to prevent further comment as a moderator action, but that is rare.
Barry
On Tue, 2023-11-14 at 16:44 +0000, Barry Scott wrote:
On 14 Nov 2023, at 16:17, Patrick O'Callaghan pocallaghan@gmail.com wrote:
Maybe, but it still means one can't answer an old question, which is sometimes useful, including if one wants to reply to one's own query with SOLVED.
That is a policy that the site chooses. With the Fedora discuss the infrastructure people are open to adapting policy over time to what serves the community well.
I don't think there is a close time for the discuss.fedoraproject.org topics, or its very large.
In the case of Gnome, the policy appears to be to regard month-old topics as closed, which IMO is mistaken. However I concede that this isn't necessarily a point against Discourse. The fact remains that it's hard to use effectively without a browser, which is my main objection, not to mention the social-media orientation of much of the interface.
Again, this is OT for the thread so I suggest we leave it there. If Fedora ever decides to close down this list because "there's a Discourse forum which fulfils the same function" (which is essentially what Gnome has done) we'll no doubt come back to it.
poc