From: nospam@needed.invalid   
      
   On 5/26/2024 7:46 PM, philo wrote:   
   > On 5/25/24 6:40 PM, philo wrote:   
   >> Thanks for all the help on getting my Brother printer setup on my Ubuntu   
   22.04 machine.   
   >> As mentioned, I had to do a custom setup.   
   >> I upgraded an old installation to 24.04 and when I went to install the   
   printer...I'll be darned , the Brother recommended setup worked fine...but now   
   I have another problem   
   >>   
   >>   
   >> The drive I had used as a backup upgraded fine to 24.04 but I had to   
   upgrade from 22.04 to 23.10 first.   
   >>   
   >> My problem was that when I did that with my most recent drive,   
   >> the upgrade failed as it got to the end. The machine did boot to 23.10 but   
   there are broken dependencies which I cannot resolve as the Internet was lost   
   in the process.   
   >>   
   >>   
   >> I need to know how to proceed from here.   
   >>   
   >> I can download the 23.10 and burn the .iso to USB stick   
   >> but how to I add it as  source to software & updates?   
   >>   
   >> I can't fix dependencies without pointing the repair process somewhere   
   other than on-line   
   >>   
   >> The option for external source says to insert CD or DVD   
   >>   
   >> The ISO is too large. Their dialog is obsolete.   
   >>   
   >> Synaptic does have an option to add packages but where would I point that   
   within the ISO   
   >>   
   >>   
   >>   
   >> Even though I do have one working installation, I do want to get the other   
   one going as a backup without a complete fresh install   
   >>   
   >>   
   >> Thanks   
   >>   
   >   
   >   
   >   
   > Backed all my data up one more time, than thanks to Clonezilla, cloned my   
   good installation onto the drive that had the failed upgrade.   
   >   
   > Whew. Now I can put the drive away knowing I have a backup installation.   
   >   
   > While that was going on, I decided to upgrade my Mint 20.3 to version 21   
   >   
   > LOL, as it got to the end, the upgrade failed.   
   > The system booted by had problems>   
   >   
   > One nice thing about Mint at least is it took a nice snapshot and I was able   
   to roll everything back.   
   >   
   > Now I put a not on the machine NOT to upgrade the Mint install.   
      
   I think I see a pattern emerging here.   
      
   *******   
      
   Just for the record, when the new kernel tips over,   
   you select an alternate kernel from the GRUB menu.   
   Or at least, that is what worked in previous years.   
      
   Maybe your machine likes 5.15 but does not like 6.x .   
      
   During the installation, there may be an option to clean up   
   or not. And not cleaning up, may leave more options. During   
   software updates, I like to leave the machine littered with   
   old kernels, just for fun.   
      
   It's too bad there wasn't an "advisor" you could run,   
   which would notify you that one or more items on the   
   machine is going to cause problems. Windows has an advisor,   
   but when installing an OS, it did not recognize the graphics   
   were too crusty, and it wasted time for nothing by getting   
   part way through an upgrade and then rolling back. And because   
   it did not print any info on the screen, I had to "guess"   
   it was the graphics that did it. Sticking in my HD6450   
   graphics card, allowed that upgrade to go ahead. You have to   
   keep a lot of hardware history in your head, at times like this.   
      
   Even when there are log files, there is no guarantee you'll   
   catch the line that offers a hint. I guess this is all part of   
   the fun.   
      
   Part of the reason for wanting to fix busted upgrades, is   
   to develop your own set of rules for "pre-conditions for Upgrade".   
   For example, if my /tmp was mounted as a TMPFS, that is verboten.   
   Before Upgrade, I have to put /tmp back on / , "like Linus wants it" :-)   
   You also have a gander at your .ppa collection, and remove some   
   of those. On a virtual machine, you might do a "remove" on the   
   "virtual machine additions" -- things work better without it.   
      
   You have the option, of moving a disk drive to a more capable   
   machine, doing the Upgrade there, then moving the disk drive   
   back to Mr.Crusty for a test boot. It can still bomb, but then   
   you may have gathered evidence the thing actually works on   
   your "good" machine.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)