Announcement

Collapse
No announcement yet.

After almost 2 years of use, GUI doesnt show anymore on screen.

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

    After almost 2 years of use, GUI doesnt show anymore on screen.

    Hello

    so I have a HP 17-BY0320NG Laptop (i3 7020U with Intel HD 620 and a Radeon 520 for CPU and GPU) and it ran 18.04 without any issues since about August 2018.
    now a few days or weeks ago, I rebooted my Laptop and dont get any Gui on any physically connected screen be it the Laptop screen or via HDMI.

    I can do commands on tty2 or whatever it was called (ctrl+alt+f2), and apparently Google Chrome remote which also opens to a virtual Display can open Plasma just fine.

    when using nomodeset or recovery and continue booting from there i can get to the login screen but after clicking the login button I get other problems and I dont get to Plasma.

    is there anything I can do?

    Thanks and regards.

    #2
    Boot from an earlier kernel. See if it helps.

    Comment


      #3
      currently there seem to be 3 options in grub.
      4.15.0-1093-oem
      4.15.0-1091-oem
      4.15.0-112-generic

      none seem to work.

      is there a list of when which version came for 18.04 and can I just try to also install another next to it.

      Comment


        #4
        What sort of customization have been done> an OEM kernel is not a normal one for Kubuntu.
        The OEM kernel you have was updated in the last half of July, but as your original stock kernel does not seem to work, I am guessing it may not be related to the kernel. There have not been any significant updates to Plasma iirc, either.
        If you had the usual HWE stack, you would have the 5.4 kernel, and some other distinct versions to try out.

        Can you tell us of any modifications, external upgrades you have done toy your Kubuntu install?

        By no GUI, do you mean nothing at all, no mouse cursor or anything? No login screen?

        If you can do the ctrl-alt-f2, can you log in the the terminal, and run the command startx to try and start plasma, and record any error messages you may see.

        Comment


          #5
          oem kernel is probably because drivers I guess, never looked too much at the version names but when I installed with secure boot back then it already asked me in the installer to do MOK setup so I guess it already did stuff.

          with the help if the people on Telegram I got quite a bit farther.
          after axing amdgpu-pro

          originally there was just a blinking textcursor or success messages if I push a button during the kubuntu screen.

          startx resulted in segfaults and stuff.

          now I get to the login screen but as soon as I try to login to my main profile I get a freeze in the GUI where nothing really does anything except the mouse which still moves (and I can get into tty2 or a secondary profile).

          Comment


            #6
            Originally posted by My1xT View Post
            oem kernel is probably because drivers I guess, never looked too much at the version names but when I installed with secure boot back then it already asked me in the installer to do MOK setup so I guess it already did stuff.
            mok has nothing to do with installing a non standard kernel or drivers, so it will be something different. But as it seems to be happening on the stock kernel I doubt it is kernel specific anyway.


            startx resulted in segfaults and stuff.
            These 'segfaults and stuff' are the very useful bits of info we kinda sorta need to maybe see what is happening.



            Sent from my LM-V600 using Tapatalk

            Comment


              #7
              Originally posted by claydoh View Post
              mok has nothing to do with installing a non standard kernel or drivers, so it will be something different. But as it seems to be happening on the stock kernel I doubt it is kernel specific anyway.
              it doesnt?

              I mean wasnt the entire point of a MOK to make non-standard (and therefore non-signed kernels and kernel drivers boot with secure boot (especially considering this option literally only pops up in the installer when you select to install third party drivers and stuff?
              These 'segfaults and stuff' are the very useful bits of info we kinda sorta need to maybe see what is happening.
              I doubt it's THAT useful now anymore as that was the past state, which was kinda resolved and I now have a different issue (last line of the Post)
              Selfquote:
              now I get to the login screen but as soon as I try to login to my main profile I get a freeze in the GUI where nothing really does anything except the mouse which still moves (and I can get into tty2 or a secondary profile).

              Comment

              Working...
              X