Announcement

Collapse
No announcement yet.

Problems booting after upgrade to 22.04

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Problems booting after upgrade to 22.04

    Hello everybody,

    after upgrading to 22.04 my system won't boot as before. To be honest I have no idea what is going on in a linux system. Is there anybody still willing to try to help me?
    After pressing the on/off button the system displays:






    From other forum posts I learned, that I can use ctrl+alt+F2 to switch to a command line mode and at least interact with the system.








    I also read, that some users have problems with missing graphics drivers after upgrading. Just in case this might have to do with the problem I used the Windows partition of the PC to find out what graphics hardware the system uses:





    Does anyone understand what problem my system has? And what I could do to fix it? Thanks in advance!

    regards,
    Michel







    #2
    Boot the computer and switch to a tty again, then:

    1. You could show us the output of sudo systemctl get-default

    2. Probably you will have to (re)install the Nvidia drivers - an easy way to do so in *Ubuntu is:
    Code:
    ubuntu-drivers devices
    sudo ubuntu-drivers autoinstall
    reboot​
    The first of the three commands is for you to see which driver(s) will be automatically installed by the command in the next line.

    PS: If this does not work and if the culprit are the Nvidia drivers you may have to uninstall the "old" Nvidia drivers first
    (sudo apt-get remove --purge --autoremove nvidia*), especially if you did not install them from *Ubuntu's repositories but from an external source.

    PPS: This has nothing to do with your actual problem, but if you have just release-upgraded your system to 22.04 I recommend logging in to a tty after booting up and sudo rm -r $HOME/.cache/* to remove "stale" user caches and exit again.
    Last edited by Schwarzer Kater; Mar 25, 2023, 04:40 AM. Reason: typos & added PS and PPS :-)
    Debian KDE & LXQt • Kubuntu & Lubuntu • openSUSE KDE • Windows • macOS X
    Desktop: Lenovo ThinkCentre M75s • Laptop: Apple MacBook Pro 13" • and others

    get rid of Snap script (20.04 +)reinstall Snap for release-upgrade script (20.04 +)
    install traditional Firefox script (22.04 +)​ • install traditional Thunderbird script (24.04)

    Comment


      #3
      1:


      2:













      P.S:​
      Thsi didn't work, probably because I didn't know what the asterisk in your proposed command stands for and didn't replace it.







      ​PPS:





      ​​


      Last edited by Michel Frey; Mar 24, 2023, 11:36 PM. Reason: edit: half of my post was suddely gone

      Comment


        #4
        1. sudo systemctl get-default -> "graphical target" ist correct - so no need to set anything else

        2. ubuntu-drivers devices && sudo ubuntu-drivers autoinstall -> in your case ​the output says that the correct driver for your Nvidia card is "nvidia-driver-390" and you have already installed it before (probably before release-upgrading). The system "thinks" everything is installed correctly at present, but my assumption is that due to the release-upgrade to 22.04 some things have broken -> try the following step (3.) :

        3. sudo apt-get remove --purge --autoremove nvidia* -> I am very sorry, I forgot the "remove" in my reply before in haste and there has to be an asterisk directly behind "nvidia" (without space). The asterisk is a placeholder for any characters that may follow the characters before, in this case so that "anything that begins with nvidia" gets removed. After this try sudo ubuntu-drivers autoinstall like in step 2 again and reboot.

        4. sudo rm -r $HOME/.cache/* -> "$HOME" is a "replacement" for the path to your home directory (it is a shell environmental variable). In Linux it is very important to know that a word with upper case letters is not equal the same word in lower case letters, so don't type "$home".
        Btw: Unlike in Windows in Linux a file named HELLO ≠ hello ≠ Hello ≠ helLO - these are four different files. In Windows a file named HELLO = hello = Hello = helLO - this is the same file.
        But this step 4 is only optional and has nothing to do with your problem, as I wrote. So do it after everything else is working correctly as "icing on the cake" if you like.

        Good luck!
        Last edited by Schwarzer Kater; Mar 26, 2023, 09:06 AM. Reason: typos
        Debian KDE & LXQt • Kubuntu & Lubuntu • openSUSE KDE • Windows • macOS X
        Desktop: Lenovo ThinkCentre M75s • Laptop: Apple MacBook Pro 13" • and others

        get rid of Snap script (20.04 +)reinstall Snap for release-upgrade script (20.04 +)
        install traditional Firefox script (22.04 +)​ • install traditional Thunderbird script (24.04)

        Comment


          #5
          Welcome to KubuntuForums, Michel Frey !!
          Everyone is a novice, some in one thing and some in other things, and there are no "dumb questions" on this forum.
          "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
          – John F. Kennedy, February 26, 1962.

          Comment


            #6
            Code:
            sudo apt-get remove --purge --autoremove nvidia*
            sudo ubuntu-drivers autoinstall
            reboot
            I had to do this myself in Kubuntu 22.04 today… (the second time within 6 months)!

            Before - due to the combination "update for the 5.19 hwe kernel" and "Nvidia drivers 525.89.02 kept back (because these were "phased")" at the same time - my computer did not start the GUI when I rebooted after the kernel update.
            Kernel 5.19.0-38-generic does not seem to work with the older nvidia-driver-525 (525.85.05) - at least with my hardware.

            I had to additionally sudo apt install libnvidia-common-525 as this last 525.89.02 package was still kept back afterwards (but this also could have someting to do with that I was lazy and used sudo apt purge nvidia* instead of sudo apt-get remove --purge --autoremove nvidia*).
            Now everything is working as it should.

            My next graphics card will be AMD again for sure!
            Last edited by Schwarzer Kater; Mar 31, 2023, 02:00 AM. Reason: added some information
            Debian KDE & LXQt • Kubuntu & Lubuntu • openSUSE KDE • Windows • macOS X
            Desktop: Lenovo ThinkCentre M75s • Laptop: Apple MacBook Pro 13" • and others

            get rid of Snap script (20.04 +)reinstall Snap for release-upgrade script (20.04 +)
            install traditional Firefox script (22.04 +)​ • install traditional Thunderbird script (24.04)

            Comment


              #7
              I did
              Code:
              sudo apt-get remove --purge --autoremove nvidia*
              sudo ubuntu-drivers autoinstall
              reboot​
              But the system still doesn't open the GUI after booting. So I tried
              Code:
              sudo apt install libnvidia-common-525​
              although I don't know if this is suitable for my hardware. In the mysterious output that was displayed after the autoremove-command I noticed some lines included numbers like 513 and 515. However, this command seems to have failed for some reason:




              Now the display after booting is



              I assume, that the information regarding remmina is not so important and can be fixed later, as soon as the GUI is back. But the GUI isn't back.

              greetings,
              Michel


              Comment


                #8
                I am sorry to hear that the GUI is still not back.

                But don't just install libnvidia-common-525 for your system!!!

                Nobody suggested you should do so.
                This is completely unsuitable because your graphics card should use the Nvidia 390 driver series (as you can read from the output of ubuntu-drivers devices).

                So better sudo apt remove libnvidia-common-525​ and sudo apt install libnvidia-common-390 - if libnvidia-common-525​ did get installed at all as it seems your internet connection to the *Ubuntu servers did not work.

                Please ask here or "google" for it if you don't understand what a Linux shell command means or does before using it - for your system's sake.

                That said one can guess from what you wrote ("…was displayed after the autoremove-command I noticed some lines included numbers like 513 and 515") that at least parts of the wrong Nvidia driver version had been installed before (probably from an external source/PPA?).

                PS: At this state I would try something like this:
                https://www.kubuntuforums.net/forum/...383#post669383
                P​PS: Do you have any important user data in your Kubuntu installation?
                If not the easiest and fastest way now could be to just wipe the partition and do a fresh installation with the most recent Kubuntu 22.04 ISO (takes about 5-10 minutes in my case).
                And to 1. update your system with Discover and 2. reboot and 3. sudo ubuntu-drivers autoinstall && reboot afterwards…
                Last edited by Schwarzer Kater; Mar 30, 2023, 02:29 AM. Reason: added PS & PPS
                Debian KDE & LXQt • Kubuntu & Lubuntu • openSUSE KDE • Windows • macOS X
                Desktop: Lenovo ThinkCentre M75s • Laptop: Apple MacBook Pro 13" • and others

                get rid of Snap script (20.04 +)reinstall Snap for release-upgrade script (20.04 +)
                install traditional Firefox script (22.04 +)​ • install traditional Thunderbird script (24.04)

                Comment


                  #9
                  I understand. Sorry, I will stick to your recommendations now.
                  After sudo apt remove libnvidia-common-525​ and sudo apt install libnvidia-common-390​ the output was:




                  ​Would you recommend to follow this instruction to try
                  Code:
                  apt --fix-broken install
                  ?

                  I'm unsure what the recommendation of your PS is. To somehow try to perform the upgrade again? Is that what is described in your link and what commands like
                  Code:
                  apt full-upgrade
                  do?

                  Thank you very much for your continued support!

                  Comment


                    #10
                    Maybe OP should remove nvidia drivers altogether, initially at least. Let us try to reach to a working desktop with nouveau drivers first.
                    Last edited by arsivci; Mar 30, 2023, 02:30 AM. Reason: spelling.

                    Comment


                      #11
                      Originally posted by Michel Frey View Post
                      […]
                      ​Would you recommend to follow this instruction to try
                      Code:
                      apt --fix-broken install
                      […]
                      Yes.
                      And did you read my PPS?

                      And the suggestion of arsivci is also a solid one if the sudo apt --fix-broken install above (do a reboot afterwards) did not work.

                      PS: I guess arsivci meant to just leave out the sudo ubuntu-drivers autoinstall part from the posts above (to not install the Nvidia drivers - perhaps you will have to install nouveau drivers additionally afterwards if they are not in your system, but let's see first), which would mean:
                      sudo apt-get remove --purge --autoremove nvidia*
                      reboot​

                      Try it if the sudo apt --fix-broken install and reboot did not get the GUI back before.
                      Last edited by Schwarzer Kater; Mar 30, 2023, 04:26 PM. Reason: added PS
                      Debian KDE & LXQt • Kubuntu & Lubuntu • openSUSE KDE • Windows • macOS X
                      Desktop: Lenovo ThinkCentre M75s • Laptop: Apple MacBook Pro 13" • and others

                      get rid of Snap script (20.04 +)reinstall Snap for release-upgrade script (20.04 +)
                      install traditional Firefox script (22.04 +)​ • install traditional Thunderbird script (24.04)

                      Comment


                        #12
                        Well, sudo apt --fix-broken install and reboot didn't help, leaving out the sudo ubuntu-drivers autoinstall​ neither. As far as I understand I could still try to install nouveau drivers manually to fix my broken installation or set up the partition from scratch. To answer your question: I have no valuable data on the partition. So probably you are right, it might be the easiest way to wipe the partition and install 22.04. Would you mind guiding me through the procedure? Of course I can google how 22.04 is installed, but not how I have to prepare the partition before in oder to make sure no remains of the broken installation are left. Thank you so much.

                        Comment


                          #13
                          Originally posted by Michel Frey View Post
                          […] Would you mind guiding me through the procedure? Of course I can google how 22.04 is installed, but not how I have to prepare the partition before in oder to make sure no remains of the broken installation are left. Thank you so much.
                          If you wouldn't mind waiting until next Wednesday (I don't want to sound rude, but before this I won't have the time for an individual step-by-step guidance regarding your individual computer setup, sorry…). In the meantime you could post your drive and partition scheme and firmware type (UEFI or "legacy" BIOS) - and possibly a screenshot of the situation you have trouble with - here for starters.

                          But there are plenty of threads in this forum about Kubuntu installations if you want to try it sooner (it is really no rocket science and you already seem to have done it successfully before).
                          Last edited by Schwarzer Kater; Apr 01, 2023, 10:43 AM.
                          Debian KDE & LXQt • Kubuntu & Lubuntu • openSUSE KDE • Windows • macOS X
                          Desktop: Lenovo ThinkCentre M75s • Laptop: Apple MacBook Pro 13" • and others

                          get rid of Snap script (20.04 +)reinstall Snap for release-upgrade script (20.04 +)
                          install traditional Firefox script (22.04 +)​ • install traditional Thunderbird script (24.04)

                          Comment


                            #14
                            Originally posted by Michel Frey View Post
                            .... I have no valuable data on the partition. So probably you are right, it might be the easiest way to wipe the partition and install 22.04. Would you mind guiding me through the procedure? Of course I can google how 22.04 is installed, but not how I have to prepare the partition before in oder to make sure no remains of the broken installation are left. Thank you so much.
                            Installing 22.04 from a freshly made AND checksum verified LiveUSB stick will take about 30 minutes. During the install process you will be given two methods for formatting your storage device (HD or SSD). One way is to let the install program choose your entire disk. The second way is to choose the manual formatting procedure. My advice is to choose the automatic procedure. The install program will devote the entire drive to Kubuntu using EXT4, create the necessary swap partition and also create the ESI boot partition, taking care of everything after you enter your timezone, name and password.
                            It will take about 15 minutes, depending on how fast your computer and HD are.

                            My experience doing upgrades to the next LTS has had mixed results. Since installing Kubuntu is so fast and easy, as you know from installing the previous release, I choose to store my important data on external storage and to do a clean install. This is made easy because I use the BTRFS as my filesystem, but that's a topic for another discussion. The chosen Nvidia driver will still be the 390, probably the last release of the Nvidia driver that works for the model of your GPU. On a previous computer was an Nvidia GT 650M, which also required the 390 driver. It ran well!

                            I'm sure you'll have no problem downloading the latest stable 22.04 ISO file, verifying its checksum, burning it to a USB stick and booting from it.



                            "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                            – John F. Kennedy, February 26, 1962.

                            Comment


                              #15
                              My plan is to follow this instruction https://www.ubuntubuzz.com/2022/07/h...sk-method.html
                              It's probably what I want (leave the existing windows partition unchanged, install Kubuntu to the partition where currently the broken one is installed). Because I already have this dual boot installation I assume, I already have an EFI partition and a swap partition. Does that mean, I can skip Steps 5A and 5B from the instruction? What about Step 5D, do I also have to skip that because I already have a boot loader?

                              Comment

                              Working...
                              X