Boot freezes just after loading graphics on Ubuntu 18.10 and Fedora 29

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I wish I could offer more info than this, both distros use Gnome, both fail at exactly the same moment in boot process.
Background changes, mouse icon is shown and then everything freezes.



Both distros work when running from live-usb. Problem asserts itself when booting from hdd. I've tried repartitioning.. I am using /boot/efi



Will try to repartition again, as it makes sense that could somehow be the issue.



EDIT (last few lines of boot.log):



[[0;32m OK [0m] Started WPA supplicant.
[[0;32m OK [0m] Started Hostname Service.
[[0;32m OK [0m] Started Modem Manager.
[[0;32m OK [0m] Started Raise network interfaces.
[[0;32m OK [0m] Started Dispatcher daemon for systemd-networkd.
[[0;32m OK [0m] Started Network Manager.
[[0;32m OK [0m] Reached target Network.
Starting OpenVPN service...
Starting Permit User Sessions...
Starting Network Manager Wait Online...
Starting Network Manager Script Dispatcher Service...
[[0;32m OK [0m] Started Permit User Sessions.
Starting GNOME Display Manager...
Starting Hold until boot process finishes up...
[[0;32m OK [0m] Started Disk Manager.
[[0;32m OK [0m] Started OpenVPN service.
[[0;32m OK [0m] Started Network Manager Script Dispatcher Service.
[[0;32m OK [0m] Started Snappy daemon.
Starting Wait until snapd is fully seeded...


EDIT: I found this answers which helped a lot. However in my case problem doesn't seem to be in the display manager, i've tried gdm gdx and lightdm and all have same issue.



It seems that the problem is likely with the GPU, I've purged nvidia drivers (no effect) and am reinstalling them ATM. If this doesn't work I will try to enforce usage of intel gpu (if that's possible)










share|improve this question









New contributor




poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 1




    It seems like a video driver error. Look at logs.
    – Ipor Sircer
    yesterday






  • 1




    from what I can find online, it seems that this is some kind of kernel issue that's caused by insufficient randomness of the system which can be resolved by moving the mouse and pressing keys. However, in my case mouse doesn't work and keys produce no results. I'm gonna try with 18.04 and see what happens.
    – poppycockears
    yesterday















up vote
1
down vote

favorite












I wish I could offer more info than this, both distros use Gnome, both fail at exactly the same moment in boot process.
Background changes, mouse icon is shown and then everything freezes.



Both distros work when running from live-usb. Problem asserts itself when booting from hdd. I've tried repartitioning.. I am using /boot/efi



Will try to repartition again, as it makes sense that could somehow be the issue.



EDIT (last few lines of boot.log):



[[0;32m OK [0m] Started WPA supplicant.
[[0;32m OK [0m] Started Hostname Service.
[[0;32m OK [0m] Started Modem Manager.
[[0;32m OK [0m] Started Raise network interfaces.
[[0;32m OK [0m] Started Dispatcher daemon for systemd-networkd.
[[0;32m OK [0m] Started Network Manager.
[[0;32m OK [0m] Reached target Network.
Starting OpenVPN service...
Starting Permit User Sessions...
Starting Network Manager Wait Online...
Starting Network Manager Script Dispatcher Service...
[[0;32m OK [0m] Started Permit User Sessions.
Starting GNOME Display Manager...
Starting Hold until boot process finishes up...
[[0;32m OK [0m] Started Disk Manager.
[[0;32m OK [0m] Started OpenVPN service.
[[0;32m OK [0m] Started Network Manager Script Dispatcher Service.
[[0;32m OK [0m] Started Snappy daemon.
Starting Wait until snapd is fully seeded...


EDIT: I found this answers which helped a lot. However in my case problem doesn't seem to be in the display manager, i've tried gdm gdx and lightdm and all have same issue.



It seems that the problem is likely with the GPU, I've purged nvidia drivers (no effect) and am reinstalling them ATM. If this doesn't work I will try to enforce usage of intel gpu (if that's possible)










share|improve this question









New contributor




poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 1




    It seems like a video driver error. Look at logs.
    – Ipor Sircer
    yesterday






  • 1




    from what I can find online, it seems that this is some kind of kernel issue that's caused by insufficient randomness of the system which can be resolved by moving the mouse and pressing keys. However, in my case mouse doesn't work and keys produce no results. I'm gonna try with 18.04 and see what happens.
    – poppycockears
    yesterday













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I wish I could offer more info than this, both distros use Gnome, both fail at exactly the same moment in boot process.
Background changes, mouse icon is shown and then everything freezes.



Both distros work when running from live-usb. Problem asserts itself when booting from hdd. I've tried repartitioning.. I am using /boot/efi



Will try to repartition again, as it makes sense that could somehow be the issue.



EDIT (last few lines of boot.log):



[[0;32m OK [0m] Started WPA supplicant.
[[0;32m OK [0m] Started Hostname Service.
[[0;32m OK [0m] Started Modem Manager.
[[0;32m OK [0m] Started Raise network interfaces.
[[0;32m OK [0m] Started Dispatcher daemon for systemd-networkd.
[[0;32m OK [0m] Started Network Manager.
[[0;32m OK [0m] Reached target Network.
Starting OpenVPN service...
Starting Permit User Sessions...
Starting Network Manager Wait Online...
Starting Network Manager Script Dispatcher Service...
[[0;32m OK [0m] Started Permit User Sessions.
Starting GNOME Display Manager...
Starting Hold until boot process finishes up...
[[0;32m OK [0m] Started Disk Manager.
[[0;32m OK [0m] Started OpenVPN service.
[[0;32m OK [0m] Started Network Manager Script Dispatcher Service.
[[0;32m OK [0m] Started Snappy daemon.
Starting Wait until snapd is fully seeded...


EDIT: I found this answers which helped a lot. However in my case problem doesn't seem to be in the display manager, i've tried gdm gdx and lightdm and all have same issue.



It seems that the problem is likely with the GPU, I've purged nvidia drivers (no effect) and am reinstalling them ATM. If this doesn't work I will try to enforce usage of intel gpu (if that's possible)










share|improve this question









New contributor




poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I wish I could offer more info than this, both distros use Gnome, both fail at exactly the same moment in boot process.
Background changes, mouse icon is shown and then everything freezes.



Both distros work when running from live-usb. Problem asserts itself when booting from hdd. I've tried repartitioning.. I am using /boot/efi



Will try to repartition again, as it makes sense that could somehow be the issue.



EDIT (last few lines of boot.log):



[[0;32m OK [0m] Started WPA supplicant.
[[0;32m OK [0m] Started Hostname Service.
[[0;32m OK [0m] Started Modem Manager.
[[0;32m OK [0m] Started Raise network interfaces.
[[0;32m OK [0m] Started Dispatcher daemon for systemd-networkd.
[[0;32m OK [0m] Started Network Manager.
[[0;32m OK [0m] Reached target Network.
Starting OpenVPN service...
Starting Permit User Sessions...
Starting Network Manager Wait Online...
Starting Network Manager Script Dispatcher Service...
[[0;32m OK [0m] Started Permit User Sessions.
Starting GNOME Display Manager...
Starting Hold until boot process finishes up...
[[0;32m OK [0m] Started Disk Manager.
[[0;32m OK [0m] Started OpenVPN service.
[[0;32m OK [0m] Started Network Manager Script Dispatcher Service.
[[0;32m OK [0m] Started Snappy daemon.
Starting Wait until snapd is fully seeded...


EDIT: I found this answers which helped a lot. However in my case problem doesn't seem to be in the display manager, i've tried gdm gdx and lightdm and all have same issue.



It seems that the problem is likely with the GPU, I've purged nvidia drivers (no effect) and am reinstalling them ATM. If this doesn't work I will try to enforce usage of intel gpu (if that's possible)







ubuntu fedora boot






share|improve this question









New contributor




poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 5 hours ago





















New contributor




poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked yesterday









poppycockears

164




164




New contributor




poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.







  • 1




    It seems like a video driver error. Look at logs.
    – Ipor Sircer
    yesterday






  • 1




    from what I can find online, it seems that this is some kind of kernel issue that's caused by insufficient randomness of the system which can be resolved by moving the mouse and pressing keys. However, in my case mouse doesn't work and keys produce no results. I'm gonna try with 18.04 and see what happens.
    – poppycockears
    yesterday













  • 1




    It seems like a video driver error. Look at logs.
    – Ipor Sircer
    yesterday






  • 1




    from what I can find online, it seems that this is some kind of kernel issue that's caused by insufficient randomness of the system which can be resolved by moving the mouse and pressing keys. However, in my case mouse doesn't work and keys produce no results. I'm gonna try with 18.04 and see what happens.
    – poppycockears
    yesterday








1




1




It seems like a video driver error. Look at logs.
– Ipor Sircer
yesterday




It seems like a video driver error. Look at logs.
– Ipor Sircer
yesterday




1




1




from what I can find online, it seems that this is some kind of kernel issue that's caused by insufficient randomness of the system which can be resolved by moving the mouse and pressing keys. However, in my case mouse doesn't work and keys produce no results. I'm gonna try with 18.04 and see what happens.
– poppycockears
yesterday





from what I can find online, it seems that this is some kind of kernel issue that's caused by insufficient randomness of the system which can be resolved by moving the mouse and pressing keys. However, in my case mouse doesn't work and keys produce no results. I'm gonna try with 18.04 and see what happens.
– poppycockears
yesterday











2 Answers
2






active

oldest

votes

















up vote
1
down vote













I had same issue in RHEL 7.6 with gdm 3.28 after X authorization. I think this is gdm bug.



  1. Open second console: Ctrl+Alt+F2



  2. Run htop, find X process and send SIGTERM to it.




    • F4 type gdm - to find X process


    • F9 => SIGTERM


  3. X Window will autoreload and from the second try gdm will work properly.



  4. Optional: you may want to add these lines to /etc/gdm/custom.conf to avoid login screen:



    AutomaticLogin=username
    AutomaticLoginEnable=True






share|improve this answer


















  • 1




    Sorry, this doesn't seem to work. I did manage to get terminal running but couldn't find X. Did system update: no effect. I will try LTS and see what happens
    – poppycockears
    yesterday






  • 1




    Updated answer..
    – Drakonoved
    yesterday

















up vote
1
down vote













If somebody runs into the same problem:



I've logged in using ubuntu recovery mode, resumed to fully booted state. Using ubuntu additional drivers installed proprietary Nvidia drivers, now everything works!



I've also switched display manager to light-dm but this likely had no impact.






share|improve this answer








New contributor




poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );






    poppycockears is a new contributor. Be nice, and check out our Code of Conduct.









     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481686%2fboot-freezes-just-after-loading-graphics-on-ubuntu-18-10-and-fedora-29%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    1
    down vote













    I had same issue in RHEL 7.6 with gdm 3.28 after X authorization. I think this is gdm bug.



    1. Open second console: Ctrl+Alt+F2



    2. Run htop, find X process and send SIGTERM to it.




      • F4 type gdm - to find X process


      • F9 => SIGTERM


    3. X Window will autoreload and from the second try gdm will work properly.



    4. Optional: you may want to add these lines to /etc/gdm/custom.conf to avoid login screen:



      AutomaticLogin=username
      AutomaticLoginEnable=True






    share|improve this answer


















    • 1




      Sorry, this doesn't seem to work. I did manage to get terminal running but couldn't find X. Did system update: no effect. I will try LTS and see what happens
      – poppycockears
      yesterday






    • 1




      Updated answer..
      – Drakonoved
      yesterday














    up vote
    1
    down vote













    I had same issue in RHEL 7.6 with gdm 3.28 after X authorization. I think this is gdm bug.



    1. Open second console: Ctrl+Alt+F2



    2. Run htop, find X process and send SIGTERM to it.




      • F4 type gdm - to find X process


      • F9 => SIGTERM


    3. X Window will autoreload and from the second try gdm will work properly.



    4. Optional: you may want to add these lines to /etc/gdm/custom.conf to avoid login screen:



      AutomaticLogin=username
      AutomaticLoginEnable=True






    share|improve this answer


















    • 1




      Sorry, this doesn't seem to work. I did manage to get terminal running but couldn't find X. Did system update: no effect. I will try LTS and see what happens
      – poppycockears
      yesterday






    • 1




      Updated answer..
      – Drakonoved
      yesterday












    up vote
    1
    down vote










    up vote
    1
    down vote









    I had same issue in RHEL 7.6 with gdm 3.28 after X authorization. I think this is gdm bug.



    1. Open second console: Ctrl+Alt+F2



    2. Run htop, find X process and send SIGTERM to it.




      • F4 type gdm - to find X process


      • F9 => SIGTERM


    3. X Window will autoreload and from the second try gdm will work properly.



    4. Optional: you may want to add these lines to /etc/gdm/custom.conf to avoid login screen:



      AutomaticLogin=username
      AutomaticLoginEnable=True






    share|improve this answer














    I had same issue in RHEL 7.6 with gdm 3.28 after X authorization. I think this is gdm bug.



    1. Open second console: Ctrl+Alt+F2



    2. Run htop, find X process and send SIGTERM to it.




      • F4 type gdm - to find X process


      • F9 => SIGTERM


    3. X Window will autoreload and from the second try gdm will work properly.



    4. Optional: you may want to add these lines to /etc/gdm/custom.conf to avoid login screen:



      AutomaticLogin=username
      AutomaticLoginEnable=True







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited yesterday

























    answered yesterday









    Drakonoved

    7031518




    7031518







    • 1




      Sorry, this doesn't seem to work. I did manage to get terminal running but couldn't find X. Did system update: no effect. I will try LTS and see what happens
      – poppycockears
      yesterday






    • 1




      Updated answer..
      – Drakonoved
      yesterday












    • 1




      Sorry, this doesn't seem to work. I did manage to get terminal running but couldn't find X. Did system update: no effect. I will try LTS and see what happens
      – poppycockears
      yesterday






    • 1




      Updated answer..
      – Drakonoved
      yesterday







    1




    1




    Sorry, this doesn't seem to work. I did manage to get terminal running but couldn't find X. Did system update: no effect. I will try LTS and see what happens
    – poppycockears
    yesterday




    Sorry, this doesn't seem to work. I did manage to get terminal running but couldn't find X. Did system update: no effect. I will try LTS and see what happens
    – poppycockears
    yesterday




    1




    1




    Updated answer..
    – Drakonoved
    yesterday




    Updated answer..
    – Drakonoved
    yesterday












    up vote
    1
    down vote













    If somebody runs into the same problem:



    I've logged in using ubuntu recovery mode, resumed to fully booted state. Using ubuntu additional drivers installed proprietary Nvidia drivers, now everything works!



    I've also switched display manager to light-dm but this likely had no impact.






    share|improve this answer








    New contributor




    poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.





















      up vote
      1
      down vote













      If somebody runs into the same problem:



      I've logged in using ubuntu recovery mode, resumed to fully booted state. Using ubuntu additional drivers installed proprietary Nvidia drivers, now everything works!



      I've also switched display manager to light-dm but this likely had no impact.






      share|improve this answer








      New contributor




      poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.



















        up vote
        1
        down vote










        up vote
        1
        down vote









        If somebody runs into the same problem:



        I've logged in using ubuntu recovery mode, resumed to fully booted state. Using ubuntu additional drivers installed proprietary Nvidia drivers, now everything works!



        I've also switched display manager to light-dm but this likely had no impact.






        share|improve this answer








        New contributor




        poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        If somebody runs into the same problem:



        I've logged in using ubuntu recovery mode, resumed to fully booted state. Using ubuntu additional drivers installed proprietary Nvidia drivers, now everything works!



        I've also switched display manager to light-dm but this likely had no impact.







        share|improve this answer








        New contributor




        poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 5 hours ago









        poppycockears

        164




        164




        New contributor




        poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        poppycockears is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.




















            poppycockears is a new contributor. Be nice, and check out our Code of Conduct.









             

            draft saved


            draft discarded


















            poppycockears is a new contributor. Be nice, and check out our Code of Conduct.












            poppycockears is a new contributor. Be nice, and check out our Code of Conduct.











            poppycockears is a new contributor. Be nice, and check out our Code of Conduct.













             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481686%2fboot-freezes-just-after-loading-graphics-on-ubuntu-18-10-and-fedora-29%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown






            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?