When I try to upgrade my system with zypper dup, everything goes smoothly until the system tries to install the kernel. Then the upgrade freezes just when the progress bar shows that the installation of the kernel is 100% complete.
I use the following command when I upgrade Tumbleweed.
sudo zypper dup --no-allow-vendor-change
I rebooted the system and tried to start all over in the hope that it would succeed the second time, but it froze at the exact same place.
My experience is that after the new kernel is installed (100% showing), there is a noticeable delay before anything else happens. That’s because a kernel update requires other changes, such as generating a new “initrd”. And those other changes can take a while.
No-allow-vendor-change was made default in /etc/zypp/zypp.conf somewhere between two & three years ago, so unless you are using a really old zypp.conf file, you don’t need to type it out.
I rebooted the system and tried to start all over in the hope that it would succeed the second time, but it froze at the exact same place.
Any ideas what I can do?[/QUOTE]Wait longer? How long did you wait?
I don’t let dup upgrade my kernel. I keep it locked, using a wildcard, so a new one only gets installed if and when I choose. When I install it manually (zypper in kernel-default), after the dup has completed all its post scripts, zypper asks about removing the lock. I say yes, but it does not remove it due to the wildcard in the lock, and proceeds with new kernel installation.
I waited approximately 20+ minutes, don’t remember precisely. I know from previous upgrades that the installation of a new kernel takes time because of the additional changes as you guys point out. But it never took this long.
Just now, I’m trying to upgrade a third time. This time it installed all the packages, strangely no kernel was installed. But the installation has yet again frozen. This time at the final stage with, where the prompt reads:
I don’t let dup upgrade my kernel. I keep it locked, using a wildcard, so a new one only gets installed if and when I choose. When I install it manually (zypper in kernel-default), after the dup has completed all its post scripts, zypper asks about removing the lock. I say yes, but it does not remove it due to the wildcard in the lock, and proceeds with new kernel installation.
I assume you do this as a cautionary step. How do I lock it with a wildcard?
I believe my problem is solved. But here’s the output that shows my repositories. If you find my setup troublesome, I’d be glad to know what you think I ought to do.
In part, but more an exercise of control. It’s a big download and space consumer. Unless I’m waiting on a particular fix or know something is fubar, I like to not fix what ain’t broke.
How do I lock it with a wildcard?
Examples:
zypper al kernel-defaul?
zypper al kerne?-de?ault
zypper al rnel-de
Technically the latter two each have two wildcards. The last is a bit expansive, might catch something unintended.
I see. I have a fast broadband access with an unlimited download plan. Since I also use snapper, I figure that I can always revert back to a previous kernel in case the kernel introduces some bugs.
Thanks for showing me how to lock it with wildcards!