The failure comes at reboot. After passing my luks password authentication goes to black screen wit blinking white cursor top left corner with no way to enter user password to get access to the desk top.
I followed the info sent to me for the upgrade via email from support. Changing the repositories, using the sudo commands. I also updated the coreboot at their recommendation.
As of now, I want to remove what is being asked to remove in the terminal output and install the items listed as upgradable at the end of the output in the screenshot.
On the screencap is see sudo apt upgrade but for this I’d try (if it works) sudo apt-get dist-upgrade. Also there is the sudo apt full-upgrade [but I doubt it will help with distro - more with what’s kept back, for often good reason].
As always, they should give you list of upgradable stuff (if able) and option to accept or not.
Autoremove is just cleanup of files that are not needed anymore. You can do that afterwards too - the process may take care of it too.
One caveat to this is that the suggested commands usually work in a normal system but if I read right, you may have already done some less than successful upgrading (that blinking prompt) and I’m doubtful the upgrade commands will fix the system. Maybe, maybe not. Consider that you may have to move on from upgrading to doing a completely new install and just move some files from the old system (which may be more efficient and more complete than fixing several problems).
I used the sudo command for auto-remove and rebooted the L13.
After reboot I used the sudo commands for update and upgrade and it reported nothing to be upgradable…in other words the last 3 items in the screen capture I posted are gone.
My next step is to back up an image of what I have now and then try the upgrade again with the repository changes and sudo commands.
After changing the repos to byzantium when I perform the 3 sudo commands for update, upgrade without packages, and full upgrade is it necessary to reboot after each command output?
Also, in my last failed upgrading process I get a blue window for a yes/ no question for auto reboot in regrds acknowledgement of certain library installations…answering no would allow the computer to automatically do it…yes would have my acknowledge all…does it matter?
Also my last failed attempt indicated a failure to get/install some kind of library or file called “Perl”…???
This goes to area that I haven’t encountered. For the dist-upgrade, it should look for the newer repo, so there shouldn’t be any need to manually change that. If your system is up to date on your distro version, you should only need to use the dist-upgrade. Reboots are also prompted, so shouldn’t need to do those extra. Auto reboots should be fine (I’m not knowledgeable any need to go manual - probably just for some special needs and setups if you have those - I’d trust the system [although, backups are always a good idea regardless]). I have no idea what the perl might reference.
No, dist-upgrade does not let you upgrade from Amber to Byzantium. You can get the full explanation of dist-upgrade with man apt-get on your local system.
Whereas Ubuntu for example has it’s own command line tool do-release-upgrade to switch to newer versions, Debian has not. In the official manual it is told there to upgrade the current install with full-upgrade and then replace all occurencies of the current versions codename in etc/apt/sources.list. to the new codename and then do: