[SOLVED] Need to configure resume partition after upgrading to kernel 6.1.31

litelinux · 06-02-2023, 03:11 PM

Hello,

Just making sure if someone is having the same issue. I'm using grub2 as the bootloader, and before upgrading to kernel 6.1.31, I just need to run grub-mkconfig -o /boot/grub/grub.cfg after a kernel upgrade, and the resume partition and whatnot would be properly set up. After upgrading to kernel 6.1.31 though, I have to explicitly set the "resume" kernel command-line option in /etc/default/grub, then run grub-mkconfig again for things to be properly set up. Was there something that changed between kernels 6.1.21 and 6.1.31 that made this mandatory? I have no issue with editing /etc/default/grub, just asking.

Cheers,
ltlnx

LuckyCyborg · 06-02-2023, 03:23 PM

Quote:

Originally Posted by litelinux

Hello,

Just making sure if someone is having the same issue. I'm using grub2 as the bootloader, and before upgrading to kernel 6.1.31, I just need to run grub-mkconfig -o /boot/grub/grub.cfg after a kernel upgrade, and the resume partition and whatnot would be properly set up. After upgrading to kernel 6.1.31 though, I have to explicitly set the "resume" kernel command-line option in /etc/default/grub, then run grub-mkconfig again for things to be properly set up. Was there something that changed between kernels 6.1.21 and 6.1.31 that made this mandatory? I have no issue with editing /etc/default/grub, just asking.

Cheers,
ltlnx

It was already (and always) mandatory in the form of "resume=<device or UUID>" kernel parameter.

It's strange for me that your system accepted it without being literally specified...

Maybe you have relied on some "undocumented feature" , aka benign bug?

litelinux · 06-03-2023, 05:32 AM

Quote:

Originally Posted by LuckyCyborg

It was already (and always) mandatory in the form of "resume=<device or UUID>" kernel parameter.

It's strange for me that your system accepted it without being literally specified...

Maybe you have relied on some "undocumented feature" , aka benign bug?

I found out that I applied the "resume=" some months ago in the /etc/default/grub config file, but slackpkg replaced it after this update. No wonder it didn't apply. Gotta be more careful next time.

Cheers,
ltlnx

marav · 06-03-2023, 06:16 AM

Quote:

Originally Posted by litelinux

I found out that I applied the "resume=" some months ago in the /etc/default/grub config file, but slackpkg replaced it after this update. No wonder it didn't apply. Gotta be more careful next time.

Cheers,
ltlnx

slackpkg new-config (always) let you decide if you want to overwrite the file or not
according to the slackbuild & doinst.sh

Code:

...
# Install default options file:
mkdir -p $PKG/etc/default
cat $CWD/etc.default.grub > $PKG/etc/default/grub.new

Code:

...
# Process config files in etc/grub.d/:
for file in etc/grub.d/*.new ; do
  config $file
done
config etc/default/grub.new