Reverting Back to Older Version of Unbuntu ?

zooba72 · 06-08-2017, 08:59 PM

Hey Everyone - I need some help with my xubuntu laptop. I must have had auto-updates enabled and the upgrade to 4.4.0-72 has caused some issues - my system now immediately panics on boot.

From the advanced boot menu, I can boot the previous version: 3.19.0-80-generic and it boots fine. How can I revert back ? I simply want this to boot the 3.19 version by default ... Can I edit the boot menu so that 3.19 loads by default or is there a way of downgrading to 3.19?

Thank you

zooba72 · 06-08-2017, 09:14 PM

ok - I thought I figured this out:

I edited /etc/default/grub
GRUB_DEFAULT = <number corresponding to the release you want>

Still choking at boot - I might have a different issue. I can definitely launch 3.19 from the advanced menu but it does seem to want to load by default.

syg00 · 06-08-2017, 09:31 PM

Been a long time since I used Ubuntu, but you need to run update-grub after modifying the defaults. Note also that this may be only a temporary fix, as the list may change after the next kernel ships. Or may not, depending on how Ubuntu handle the number of retained kernels in the boot list.
Like I said, too long ago.

zooba72 · 06-08-2017, 09:59 PM

Yes - I actually figured that out and got it to update but I selected the wrong boot option - now it goes to memtest by default. Is there any way I can get back to the menu to edit it again ??

syg00 · 06-08-2017, 10:09 PM

Just do as you did before, but get it right. You should still see the "Advanced" (sub-)menu option.

zooba72 · 06-08-2017, 10:15 PM

I don't have the menu option anymore - it boors directly to memtest. I have not let it finish yet, not sure if I'll have that option afterwards?

zooba72 · 06-08-2017, 11:11 PM

For those who find themselves in a similar situation where they screwed up the GRUB configuration and are boot directly to memtest - Hold down the SHIFT key immediately after boot, that will bring back the option to enter the advanced menu and boot a kernel.

syg00 · 06-08-2017, 11:49 PM

And if that doesn't work, try <Esc>.
If all else fails you can fix it from a live/install CD/USB/whatever.

Vanilla Lumina · 06-09-2017, 02:50 AM

I'd recommend backing up your files somewhere and then installing a fresh copy to avoid any issues with things breaking. ^^

RockDoctor · 06-09-2017, 07:31 AM

When a new kernel gives me problems (happens to me occasionally when running Fedora Rawhide or Ubuntu Next), here's what I do:

Boot into the old kernel
Use the package manager to remove the offending kernel

syg00 · 06-09-2017, 08:24 AM

I prefer to raise a bug - that's what development projects are for. The last time I had an issue with rawhide (4.11), the problem was resolved before I could. Mighty impressive the effort some of these people put in.