Ah, sorry, I missed that when you replied earlier. If it still doesn’t work, then I don’t know what the problem would be.
You said you were still seeing that “missing resume=” error? One way you might confirm that the kernel parameters were set the way you think they were set would be to run cat /proc/cmdline. That should show the actual parameters that were used to boot the current system.
Her’s what I get - looks like there’s no ‘resume=’ there ~ wonder why…
firebat@fedora:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.19.9-200.fc43.x86_64 root=/dev/sda8
I think you said earlier that you were dual booting this system and using another OS’s bootloader? If so, your configuration changes would need to be made in that other bootloader’s configuration. Configuring one bootloader to manage multiple operating systems is somewhat non-trivial, but it can be done.
the ubuntu grub ‘bootloader’ already has a resume= for ubuntu… doesn’t seem possible to make two entries for resume=…
Like I said, it is somewhat non-trivial, but you can add additional menu entries to GRUB that will target other operating systems on other partitions or disks.
There is another user who is attempting that with another GRUB bootloader (in his case, one that was installed by CatchyOS) here:
He said he accomplished it by adding a 40_custom file with a custom menu entry definition.
I also use a lone bootloader to load multiple opertating systems, but I do it with systemd boot, which is a completely different boot loader that works in a completely different way and it only works on UEFI systems.
I know it can be done, but I haven’t done anything like that with GRUB for ages and about all I can do is point you to the documentation.
If you want, you could try collaborating with that other user who is working on this same problem.
Good luck. 
Sure :D, I can help… I don’t know much about Linux yet… But I’ve been experimenting a lot with the boot process because I’ve been switching between distros all the time, hahaha… So I have some experience, although there are still things I don’t understand, so I can’t vouch for my configuration methods.
Plus, I rely heavily on AI agents… They’re usually very helpful.
But I’m willing to help with what I know so far.
Could you tell me what the main problem is, or what you’re trying to achieve?
Do you want to configure your computer’s boot loader so that the operating systems start up without any problems?
Hi Jose:
Thanks for offering to help. I didn’t mean to bring you in directly. Let Jaimie ask if she gets stuck. Otherwise, she can probably figure it out.
It’s okay—if I can help others, that’s enough for me, honestly.
Where to start… I’m running Ubuntu 24.04lts on sda5 (ext4), Win7 on sda2 (NTFS) and sda1 (hidden), sda3 is just a storage drive used by linux/microsoft (NTFS), sda4 is extended, sda6 is future whatever (ext4), and sda7 is fedora /boot (ext4), sda8 is fedora / (ext4).
Using Ubuntu’s grub for bootloader, but its os-prober can’t see btrfs, so everything is ext4 or NTFS.
Older Gateway laptop w/4GbRAM Core2 64bit. Don’t see anything in bios on EFI, and my TMP 1.2 is off. No seure boot option there either. My Ubuntu and Win7 both hibernate/restore and standby/resume w/o issues. Everything individually (ea partition) backed up using G4L (Ghost for Linux) lzop image on usb drives.
You can read all the info above on what has been looked at, run, etc. so far - not even sure if fedora 43 actually requires EFI to get hibernate to work and that may be the make or break issue. Suggestions are that my ubuntu grub needs editing to get hibernate resume= seen, but it already has a resume= in it for ubuntu’s hibernation… and it may be the EFI is the part messing up fedora hibernation - I can run sudo systemctl hibernate and get:
as an error message and it doesn’t even try to hibernate. Different from my Win10 on another laptop that will hibernate but not restore - just reboots when you try to restore. Been using info from these three sources:
https://fedoramagazine.org/hibernation-in-fedora-36-workstation/
https://linuxconfig.org/how-to-restore-hibernation-on-fedora-35
https://askubuntu.com/questions/1358417/how-could-i-enable-hibernation-on-a-dell-inspiron-5548-running-ubuntu-focal/1358453#1358453
Got any ideas?
I see… Basically, your legacy BIOS isn’t compatible with hibernation. In current versions, you shouldn’t disable TPM—whether it’s enabled or disabled doesn’t affect hibernation—but you should disable Secure Boot because that might be why hibernation isn’t working. This is also often disabled in specific cases with some computers when dual or triple booting isn’t working properly. Hmm, let me look into this a little more… but I saw somewhere that you might also need to change something in etc/default/grub, though I’m not entirely sure… Anyway, I have a question… Hibernation is similar to the suspend function, except that hibernation shuts down all the hardware and saves what was being done to the swap file, right? If not, I’ll be wasting my time looking into this, hahahaha 
By the way… Could you tell me the specific model of your gateway? That would make it easier to find a solution.
@polsena205 She’s been through most of the hibernation configuration. I think the only bit she is missing is the details of how to create that 40_custom config file for GRUB so that it will boot Fedora Linux.
Ugh… Now I have a little more context… and I really don’t know how to help… But generally, when another system’s boot menu doesn’t appear or another system takes over the boot process, I usually modify the file etc/default/grub and then run os-prober, or I mount the other system where the system is running and run os-prober… but… in Fedora, I don’t know how to do it.
OK. I thought you had said you had managed to get a “foreign” bootloader to load Fedora Linux, so if I misunderstood, that was my mistake. I’m sure there are other places where she can find the answer.
Thanks.
Ubuntu has this app called Grub Customizer:
this legacy bios lets Ubuntu 24.04lts hibernate/restore, and windoz 7 as well, and they both suspend/resume… also, the bios has nothing special except the TPM ~ nothing on it on EFI/UEFI, nothing indicating anything about any Secure Boot.
As far as the TPM 1.2, unless on when installing the OS, turning it on afterwards helps nothing according to Ubuntu’s diagnostics.
Those resume= and resume_offset= parameters need to be on that line that starts with linux .... In your screenshot, those are not there.
If the TMP chip is enabled, Fedora Linux will use it for faster random number generation. There are a few things that might be a little faster if the TPM chip is enabled (e.g. the system might boot a little faster), but Fedora Linux does not require it.
apples and oranges - the parameters ARE there in the fedora grub as I state… the screenshot is ubuntu’s grub customizer of the ubuntu grub fedora boot section, which of course does not have the parameters - but I think they should be there instead of just in the fedora grub (where it does no good since we’re booting ubuntu grub…)
Here’s this on security check:
…and its report:
Device Security Report
======================
Report details
Date generated: 2026-04-10 09:11:19
fwupd version: 2.0.20
System details
Hardware model: Gateway E-475M
Processor: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz
OS: Fedora Linux 43 (Workstation Edition)
Security level: HSI:0! (v2.0.20)
HSI-1 Tests
UEFI Bootservice Variables: Pass (Locked)
TPM v2.0: ! Fail (Not Found)
Firmware BIOS Region: ! Fail (Not Locked)
Firmware Write Protection Lock: ! Fail (Not Enabled)
Platform Debugging: Pass (Not Supported)
UEFI Secure Boot: ! Fail (Not Enabled)
Firmware Write Protection: Pass (Not Enabled)
HSI-2 Tests
Intel BootGuard: ! Fail (Not Supported)
IOMMU Protection: ! Fail (Not Found)
Platform Debugging: Pass (Not Supported)
HSI-3 Tests
Pre-boot DMA Protection: ! Fail (Not Valid)
Suspend To RAM: ! Fail (Enabled)
Control-flow Enforcement Technology: ! Fail (Not Supported)
Suspend To Idle: ! Fail (Not Enabled)
HSI-4 Tests
Encrypted RAM: ! Fail (Not Supported)
Supervisor Mode Access Prevention: ! Fail (Not Supported)
Runtime Tests
Firmware Updater Verification: Pass (Not Tainted)
Linux Swap: ! Fail (Not Encrypted)
Linux Kernel Lockdown: ! Fail (Not Enabled)
Linux Kernel Verification: Pass (Not Tainted)
Host security events
2026-03-28 12:01:22 Linux Swap ! Fail (Encrypted → Not Encrypted)
For information on the contents of this report, see https://fwupd.github.io/hsi.html
not that concerned on any security as no online banking, etc. is done on this system (Win10 w/ESET Internet Seurity on another laptop is used for secure stuff) and it is never taken anywhere…
ubuntu’s grub customizer has this on the edit screen for ubuntu:
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 fde5b459-7c69-45f7-bfec-070de23cf8d2
else
search --no-floppy --fs-uuid --set=root fde5b459-7c69-45f7-bfec-070de23cf8d2
fi
echo 'Loading Linux 6.8.0-85-generic ...'
linux /boot/vmlinuz-6.8.0-85-generic root=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 ro quiet splash resume=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 resume_offset=1914880 $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.8.0-85-generic
which has the ubuntu hibernate resume= and offset= stuff… probably just need to copy the stuff from fedora grub to the ubuntu grub on fedora boot to look similar?