PoP!_os distro rollback

[BigBadBeef]

It's been a while since I've had to ask for advice on this website, so here it goes

I'm using PoP!_os, which is nothing but trouble recently. I updated via terminal and it started Kernel Panic-ing 10 minutes after boot every time. I booted into the previous kernel, and as expected, no problems.

Now, before proceeding, I need to clean this mess up. I already know how to boot into an old kernel, I also know how to make this boot permanent by editing the .efi file. However I wish to completely roll back the update it has performed on the kernel and shove it back on the corn cob from whence it came LOL. I also know it involves removing the newest kernel.

However before doing that, I wish consult with you on the cleanup procedure. I want to do this right so that it doesn't leave anything behind associated with that last update that would cause problems down the line. So how could I best approach getting rid of that last kernel update?

 

[CaffeineAddict]

Even if you succeed at rollback IDK how do you plan to hide updating the kernel again?
I'd personally look at replacing the whole distro, that is, deal with the uprooting the weeds instead of just cutting it only for it to grow again.

 

[BigBadBeef]

Well, I skip that particular kernel version!

But yeah, I am leaning toward moving to bazzite, but I first need to research just how much is it locked down to see if it is acceptable for my needs.

 

[KGIII]

I'd use a different distro (for reasons that I can elaborate on), but my next option would be to just keep using the older kernel until the next kernel comes along. When that kernel arrives, you can see if it's working properly. If not, then we can start looking for other solutions.

 

[CaffeineAddict]

I can't help with details about rollback, it should be as simple as removing the package with package manager that installed the kernel, kernel is just a package like any other, when removed the old one becomes active.
When removed the package manager should update initramfs to use previous kernel.

to see if it is acceptable

It's never acceptable for any update to not work, it's like knowing there is a security fix or something important that your system is lagging behind but you can't use it, not acceptable.

 

[BigBadBeef]

I'd use a different distro (for reasons that I can elaborate on)

No need, I already know what you're gonna say. Damned System76, they're making me leave after so many years...

I can't help with details about rollback, it should be as simple as removing the package with package manager that installed the kernel, kernel is just a package like any other, when removed the old one becomes active.

So no manual tweak of efi files would be needed?

 

[CaffeineAddict]

So no manual tweak of efi files would be needed?

This would be very unusual requirement and expectation from users to do.
What I said is how it works on Debian, you can remove the kernel with package manger but watch the output, make sure the output says something about updating initramfs, initramfs needs to be updated to boot into previous kernel.

You can also manually run sudo update-initramfs once kernel package is removed to be sure.

 

[BigBadBeef]

Right, thanks. But I'm gonna make some backups first. I don't trust PoP anymore.

 

[CaffeineAddict]

Right, thanks. But I'm gonna make some backups first.

Yes do, btw. the package manager should also run update-grub if not you can manually run it with sudo update-grub once the kernel is removed.

 

[osprey]

I wish to completely roll back the update it has performed on the kernel and shove it back on the corn cob from whence it came LOL.

The info one needs for rolling back would be in the /var/log/apt/history.log which records the info on each upgrade and installation. The latest apt command (which may not yet be in popOS) has history-rollback capability. See here: https://www.linux.org/threads/using-apt-history-commands.65306/.

It might be laborious to roll back from meticulous work with the history.log files, but it may not need to be done. The apps which have been upgraded in a latest update may not be dependent on the problematical kernel, so wouldn't really need to be removed. After all, lots of apps get upgraded on the same kernels. Just things to think about I guess.

 

[BigBadBeef]

Actually yes, It's just the problematic kernel I want to get rid of.

 

[BigBadBeef]

Additional use of my computer has revealed that the problem is considerably more pervasive than the simple matter of a bad kernel update. I won't go too far into detail, but suffice it to say that Wine, Proton, video playback and internet browsing are all severely affected. The window manager is also misbehaving, not letting me resize windows, maximize, minimize or move them half the time.

Time to distro hop for the first time after years of using Linux LOL!