The subject line expresses a recurring issue that I’ve had with upgrading Leap 15.3 . . . yesterday after a “large” or “medium” depending on how you look at it of approx. “1007” packages to upgrade, this morning on cold boot, rather than grub loading and showing the only linux system to choose from . . . instead it booted to a plain vanilla display . . . .
Last time this happened I had to get my SG2 disk out to boot the system and then either run the Yast bootloader, or likely the #grub2-mkconfig xxxxxxxxxxx command to repair grub . . . .
IMHO something in Leap 15.3 is not able to include grub2 in its upgrade. leaving the system . . . not bootable to the GUI . . . ???
That’s all the “useful information” that I could glean from looking at a blank white screen . . . no time then and today to mess with it. Two days back I booted the computer “normally” and ran a zypper . . . machine is “regularly” updated via zypper, showed the 1000 packages to upgrade. Ran it. Next day machine fails to boot the GUI.
Problem has happened before, which is why I’m posting about it now.
I’ll run the suggested command when I get a moment . . . likely tomorrow . . . .
This is a UEFI branded grub. The last time this happened SG2 puled the rabbit up out of the hole . . . likely if I could get to grub and go back a notch on kernel it would boot . . . but, I’m late for a very important date . . . .
You do not specify what command of zypper you use (just saying that you use zypper is not very specific :().
But when one does a zypper patch or zypper up om a regularly base in a :eap system on a decent frequency (say once a week), one should be very suspicious about the number of 1000 updates. I would have broken this off and checked what this is all about. E.g. checking my repo list, searching and even asking in the forums.
I have been using “dup -l” even in 15.3 because it was “beta” or “alpha” when I installed it . . . . I see now that there is a 15.4 available as “beta” . . . . I didn’t think too much about “1000” packages because over in TW where I spend most of my time on my desktop 1000 packages every few days seems to be the “new normal” . . . . Hindsight is much better than foresight, etc.
That machine is '09 MacBookPro with Nvidia card . . . but I’m running either nouveau or default . . . not using proprietary . . . too many problems going that way. Pretty sure that bootloader is not been updated with what is likely a new kernel . . . . I’m away from that machine so I can’t run any checks on it til . . . later.
Please understand that Leap and Tumbleweed are different.
Tumblweed snapshots are in fact new distribution versions and should be installed with zypper dup.
Leap provides patches when needed (security and recommended), To be installed by zypper ptach (or zypper up when you also want newer versions on non-standrad repos like Packman).
During the α and β tests of a Leap you have to use also zypper dup, but once it is released, you do a last zypper dup and after that normal life with zypper patch/up starts.
And yes, this as we say: filling up the pit after the calf has fallen in it.
Cool. I am aware that Leap & TW are “different” . . . but, I’m not checking in with the Blog to see when products are transitioning from when dup is OK to when it isn’t . . . . My question would be why doesn’t zypper have some “error” notification, since it notices typos and other stuff . . . to suggest running “up” or whatever . . . ??? : - )))))
Previously when this happened, no I could not get to a TTY . . . only could use the SG2 disk to boot the system . . . .
Hi
To be honest, I’ve never seen that sort of update package numbers, I suspect a 1-click repo, or maybe a dup used… but something really borked your system… Boot from the install media in rescue mode and manually mount the file system and check the os-release file.
Fire-spitting dragon would be helpful . . . . No, just a message saying “dup no longer required, please run ‘up’” . . . after the beta has been released . . . . My issue is that I run a few multi–boot machines, so the “care and feeding” of disparate OS’s is like a vocation . . . .
Don’t know about 1-click repo . . . but yes I did run dup . . . didn’t see that 15.4 was available until I posted here on the forum and selected my system . . . . I will have time to mess with it tomorrow or so . . . .
I’ve posted here a number of times, if the system is upgraded using zypper, why does zypper “bork” it’s own system???
The reasons I know seem to be different interpretations of the same basic problem:
repos enabled in Leap that should not be there at all
not auditing enabled repos after having used 1-click as an installation method
inappropriate selection of a 1-click installation
followed by zypper dup used instead of zypper up or zypper patch. Another might be a bad answer to zypper’s offered choices how to proceed in the event of conflict.
And you can’t not blame zypper for borking a system. You can only blame the one that types the commands. Like all of Unix/Linux, the system does what you type, not what you hoped for.
OK . . . back in the Leap edition . . . as before, using the SG2 disk was required to boot the system and I picked the newest kernel listed and the GUI booted up!!
I ran a zypper up and it showed 8 packages to upgrade . . . which I ran . . . . While I was there I ran the #grub2-mkconfig xxxxx command and then I went to Yast and I was rifling around in stuff, looked in repos and in a highly embarrassing moment realized that the system installed is “15.4 Beta”!!!
So, as far as being “correct” to run dup -l I believe I am “vindicated” . . . but in listing the thread as “15.3” . . . mea culpa . . . . I lose track of what’s what, etc.
Alrighty, the saga continues, on reboot after the grub2-mkconfig command, back into the white screen. Shut it down and selected “EFI boot” disk and a grub TTY loads and gives error “failed to set MOKlist” ??? something like that. I had to again boot the SG2 disk and selected the 5.14.21 xxxxx 10 default kernel and the GUI boots up fine.
I just ran the Yast Bootloader . . . but I’m not anticipating that what I believe is some kind of a “grub” communication problem will be fixed.
I lose track of what’s what, etc.