Leap 15.5 not reviving from suspend? No Packman in the repos?

English Applications
#21

Let me just answer your question about the latest stable Leap.

So 15.4 is the stable release.

1 Like
#22

@hui

Well, in my humble opinion I just run a system as the system maintains itself, I’m not trying to get under the hood with stuff and then when it blows up I look around for help with it. However the installer sets up the system and zypper maintains it, etc.

So, very clearly our experiences as they say, “vary” . . . perhaps because I’m running linux on a Mac, or I’ve been running TW since '13 and I can observe “neutrally” the way the system was maintained such that the number of breakages in routine maintenance has increased, exponentially over the numerous years of playing with linux, going back to '07 . . . ???

PS: I know Leap 15.5 is alpha/beta, but compared to TW it is considered “stable.” I get the “you shouldn’t be using TW if you don’t know what you are doing, you should be using Leap because it is ‘stable.’” As of late TW is more stable than 15.5 . . . .

#23

I made the complete opposite experience over the last 25 years since im using linux: linux got way more robust, maintenance friendly, “newbie” friendly, easier to maintain, less prone to break…overall it doesn’t take much knowledge or effort to use a stable linux distro nowadays.
But if you like to learn something new everyday, don’t fear a terminal, are able to use mailing lists and bugzilla, are able to do basic research and troubleshooting, you may (and propably should) use a rolling release or developement version.

Sorry that makes no sense. Nobody claimed that an alpha version is stable. Alpha is alpha is alpha and never reaches the stability of a rolling release like Tumbleweed.
GPS2010 gave you already the hint: The last STABLE Leap release is Leap 15.4.
Leap 15.5 is a testing release…so definitely not stable in any way.

#24

et al:

Posted to bug report:

[QUOTE]@Takashi:

So I managed to get the suggested kernel packages installed and suspended the machine. 10 mins later I attempted to revive from suspend, the display did power up and show the GUI, but as before, GUI was “frozen” and I could not use the mouse. So, in that sense the newer kernel is “worse” than the older one, where I could at least mouse around, but clicking on stuff failed to respond–here I couldn’t mouse.

I rebooted and used grub menu to select the previous kernel and it booted to TTY “emergency” mode with error, “unable to open display.” [/QUOTE]

@hui

You should be “happy” to hear that I did use cli to install the three packages, I was hoping that it would install all three with one command, but it didn’t, and rather than installing from within “cd Downloads” it appeared to re-download the packages and then report “no sign in key” which I “ignored.”

So far the newer kernel packages have not appeared to improve the issues with “non-revival from suspend.”

#25

Please include a link to the bug report so that others can follow it directly if desired.

#26

link was already provided in this thread, looks like #7

#27

Ok, I see it is progressing there. :+1:

#28

Just found another bug report I filed on Leap 15.5 GUI freezing back in Nov '22 . . . may or may not relate, doesn’t exactly seem to show a solution . . . but possibly relating to the “XFCE” DE, which would be the same?

https://bugzilla.suse.com/show_bug.cgi?id=1205452

#29

Seems like maybe the Gecko Plasma install has zyppered its way out of the “failure to revive” problem . . . ???

#30

For those interested . . . the dev on the bug report suggested moving the kernel up a notch to 5.14 xxxx, but that didn’t address the issue.

However, going to the Backports 6.1.12 xxxx option has seemed to bring revival from suspend back into play. http://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/x86_64/

I’ll monitor it for a bit before marking this thread as solved.

1 Like
#31

Looks like the bug report dev isn’t posting back on how to select the cutting edge kernel so that it gets loaded by grub?? I thought that running “update-bootloader” would select the newest kernel, but zypper installed 5.14 and grub seems to be defaulting to that kernel?? The 5.14 kernel does not revive from suspend, but the 6.1.12 option does . . . which I have to use ext usb drive SuperGrub2 to select the 6.1.12 option for Leap.

Is there any way to get grub to pick up the newer kernel, or, nope Leap won’t let that happen???

#32

Do you not see it offered in the “Advanced options…” grub menu?

1 Like
#33

Thanks for the reply . . . in many of my installs the “advanced options” shows a number of lines, all saying the same thing, so nothing to distinguish the kernels. I just rebooted and in Leap 15.5 all of the lines say something like “Leap 15.5 alpha /dev/sda8” . . . so going from the ext usb SG2 listing of a couple of 5.14 options and then the 6.1.12 I clicked down to the 5th line and yes, on reboot uname -r is showing the 6.1.12 kernel!!

So, that does work, but does add an extra step beyond the regular top listing for Leap and click go and it’s booting the newest kernel . . . ??? A bit pressed for time right now, but I’m pretty sure if I rebooted and just clicked regular Leap option it would go back to 5.14 as it did earlier today . . . .

#34

In Yast->Bootloader->Bootloader Options-> Standard Boot you can chose the default boot entry. Change it to the kernel 6 series and everything should work.

1 Like
#35

OK, thanks for providing that information . . . I just checked it, but in Leap it shows “grub is not configured” because in this multi-boot machine it is my TW install that handles grub . . . .

I believe that TW is running the 6.1xxx kernels these days, but I’ll have to get back over to TW to see what YaSt will show me about my options . . . ???

#36

This is in important information that this is a multiboot machine. In such cases it is recommended to set up proper chainloading. If you don’t set up chainloading, you always have to update grub of the “other OS” if you get a new kernel in the actual running OS or you will get the phenomen what you actual see: you always boot old kernels…

#37

mentioned in post #4 “I boot a different distro each day, same machine.”

But, OK, “proper chainloading”??? Not sure what that is, but I only go “one way” on the grub menu through the week, and if there have been any kernel upgrades on any of the systems that week I run a fresh “update-bootloader” in TW to “realign” grub with latest kernels. In this recent incident I think I ran it 3 or 4 times to try to get it to find the newest kernel for 15.5 . . . so far doesn’t seem to have moved it up to the “top hit.”

#38

As posted previously:

[QUOTE]Looks like the bug report dev isn’t posting back on how to select the cutting edge kernel so that it gets loaded by grub?? I thought that running “update-bootloader” would select the newest kernel, but zypper installed 5.14 and grub seems to be defaulting to that kernel?? The 5.14 kernel does not revive from suspend, but the 6.1.12 option does . . . which I have to use ext usb drive SuperGrub2 to select the 6.1.12 option for Leap.

Is there any way to get grub to pick up the newer kernel, or, nope Leap won’t let that happen??? [/QUOTE]

Just tried to run a zypper in Leap and got the same “problem” as before with “6.1.12” but reverting back to 5.14 fails to revive from suspend . . . unable to upgrade the system, etc.

Problem: problem with the installed kernel-default-6.1.12-lp154.2.1.g373f017.x86_64
 Solution 1: Following actions will be done:
  install kernel-default-5.14.21-150500.40.1.x86_64 from vendor SUSE LLC <https://www.suse.com/>
    replacing kernel-default-6.1.12-lp154.2.1.g373f017.x86_64 from vendor obs://build.opensuse.org/Kernel
  deinstallation of kernel-default-6.1.12-lp154.2.1.g373f017.x86_64
 Solution 2: keep obsolete kernel-default-5.14.21-150500.37.3.x86_64
#39

I’m not sure why you are having a problem. You have not provided enough information to diagnose.

I booted up my Leap 15.5 system.
I configured the repo

http://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/

I then installed the kernel from there. I rebooted, and it booted into the new kernel:

% uname -a
Linux twleap 6.2.0-lp154.5.g89e2785-default #1 SMP PREEMPT_DYNAMIC Mon Feb 20 06:22:59 UTC 2023 (89e2785) x86_64 x86_64 x86_64 GNU/Linux

I haven’t run into any problems with that.

#40

I’m not sure why I’m having the problem either and the bug report dev didn’t offer any explanation on it either, other than to have me install the 6.1.12 kernel.

He didn’t give me the hint to “configure the repo” to fit the new kernel, so that is helpful advice.

I had the same problem over in a Gecko rolling install, and there I got the same 6.2 kernel, installed it, rebooted and it selected the new kernel . . . but it did not fix the non-revival from suspend problem the way it has worked in Leap . . . . So the merry-go-round of problems continues . . . .

I’ll try to add the new repo into Leap when I get back to it, thanks kindly.