Am 09.06.2024 um 20:09 schrieb Go Canes:
On Sun, Jun 9, 2024 at 7:47 AM Klaus-Peter Schrage via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
What I don't understand: What produced the entry "resume=UUID=8e895..."
in the file /etc/default/grub which was created on the install date, May
3rd?
Do you have a /etc/kernel/cmdline file? I was tripped-up recently
because that file existed and had data that was not correct for what I
was trying to do - an old kernel would boot, newer kernels would not.
Yes, I have. I includes the "resume=" parameter as well, and, according
to the time stamp, was created (like /etc /default/grub) at install
time. So Anaconda should have created it.
I try to sum up what I have learned from the diskussion in this thread:
Still on F39, I have rearranged my system with partitions scattered on
three drives (in another thread, I reported problems with grub that I
supposed to have aroused from that). At that time, I had an old and
small swap partition hanging around, which I hadn't used for years
(meaning that it wasn't listed in fstab). Now it is no longer present,
but a suppose it was at install time of F40.
I definitely did not include the old swap in the manual partition
scheme, but I guess that Anaconda found it and included it into the
files responsible for the resume kernel parameter. That was no problem
until recent kernels which, as Barry stated, require that resume= refers
to a physical partition.
Thanks to all who contributed!
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
