Why black screen after Ubuntu installed? [duplicate]

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








up vote
0
down vote

favorite













This question already has an answer here:



  • My computer boots to a black screen, what options do I have to fix it?

    32 answers



I have just installed Ubuntu using ubuntu-16.04.4-desktop-amd64.iso. I had Endless OS on my lepton and I decided to overwrite it by Ubuntu.



Now, when I start my laptop, I first see "acer" logo, then, for a second I see a purple screen and then black screen.



What can I do to bring my new laptop back to the operational state?






system-installation







share|improve this question













marked as duplicate by karel, wjandrea, Panther, user117103, Fabby Apr 10 at 7:37


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.


















    up vote
    0
    down vote

    favorite













    This question already has an answer here:



    • My computer boots to a black screen, what options do I have to fix it?

      32 answers



    I have just installed Ubuntu using ubuntu-16.04.4-desktop-amd64.iso. I had Endless OS on my lepton and I decided to overwrite it by Ubuntu.



    Now, when I start my laptop, I first see "acer" logo, then, for a second I see a purple screen and then black screen.



    What can I do to bring my new laptop back to the operational state?






    system-installation







    share|improve this question













    marked as duplicate by karel, wjandrea, Panther, user117103, Fabby Apr 10 at 7:37


    This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite












      This question already has an answer here:



      • My computer boots to a black screen, what options do I have to fix it?

        32 answers



      I have just installed Ubuntu using ubuntu-16.04.4-desktop-amd64.iso. I had Endless OS on my lepton and I decided to overwrite it by Ubuntu.



      Now, when I start my laptop, I first see "acer" logo, then, for a second I see a purple screen and then black screen.



      What can I do to bring my new laptop back to the operational state?






      system-installation







      share|improve this question














      This question already has an answer here:



      • My computer boots to a black screen, what options do I have to fix it?

        32 answers



      I have just installed Ubuntu using ubuntu-16.04.4-desktop-amd64.iso. I had Endless OS on my lepton and I decided to overwrite it by Ubuntu.



      Now, when I start my laptop, I first see "acer" logo, then, for a second I see a purple screen and then black screen.



      What can I do to bring my new laptop back to the operational state?





      This question already has an answer here:



      • My computer boots to a black screen, what options do I have to fix it?

        32 answers






      system-installation




      system-installation






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 8 at 17:30









      Roman

      271147




      271147




      marked as duplicate by karel, wjandrea, Panther, user117103, Fabby Apr 10 at 7:37


      This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






      marked as duplicate by karel, wjandrea, Panther, user117103, Fabby Apr 10 at 7:37


      This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          There is a open bug that causes random hard CPU lockups (caused by intel-microcode), some during the boot process (which makes it difficult to troubleshoot). Try starting it with dis_ucode_ldr grub parameter.



          More in the bug report: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920






          share|improve this answer




















          • Can I avoid this bug by using other (for example older) version of Ubuntu?
            – Roman
            Apr 10 at 18:49










          • How can I start with dis_ucode_ldr grub parameter?
            – Roman
            Apr 10 at 18:50










          • @Roman: you can hold shift during boot time to get into grub menu. Then you can edit start parameters. More about it here: wiki.ubuntu.com/Kernel/KernelBootParameters
            – ant
            Apr 12 at 9:28


















          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote













          There is a open bug that causes random hard CPU lockups (caused by intel-microcode), some during the boot process (which makes it difficult to troubleshoot). Try starting it with dis_ucode_ldr grub parameter.



          More in the bug report: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920






          share|improve this answer




















          • Can I avoid this bug by using other (for example older) version of Ubuntu?
            – Roman
            Apr 10 at 18:49










          • How can I start with dis_ucode_ldr grub parameter?
            – Roman
            Apr 10 at 18:50










          • @Roman: you can hold shift during boot time to get into grub menu. Then you can edit start parameters. More about it here: wiki.ubuntu.com/Kernel/KernelBootParameters
            – ant
            Apr 12 at 9:28















          up vote
          1
          down vote













          There is a open bug that causes random hard CPU lockups (caused by intel-microcode), some during the boot process (which makes it difficult to troubleshoot). Try starting it with dis_ucode_ldr grub parameter.



          More in the bug report: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920






          share|improve this answer




















          • Can I avoid this bug by using other (for example older) version of Ubuntu?
            – Roman
            Apr 10 at 18:49










          • How can I start with dis_ucode_ldr grub parameter?
            – Roman
            Apr 10 at 18:50










          • @Roman: you can hold shift during boot time to get into grub menu. Then you can edit start parameters. More about it here: wiki.ubuntu.com/Kernel/KernelBootParameters
            – ant
            Apr 12 at 9:28













          up vote
          1
          down vote










          up vote
          1
          down vote









          There is a open bug that causes random hard CPU lockups (caused by intel-microcode), some during the boot process (which makes it difficult to troubleshoot). Try starting it with dis_ucode_ldr grub parameter.



          More in the bug report: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920






          share|improve this answer












          There is a open bug that causes random hard CPU lockups (caused by intel-microcode), some during the boot process (which makes it difficult to troubleshoot). Try starting it with dis_ucode_ldr grub parameter.



          More in the bug report: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 9 at 8:22









          ant

          565




          565











          • Can I avoid this bug by using other (for example older) version of Ubuntu?
            – Roman
            Apr 10 at 18:49










          • How can I start with dis_ucode_ldr grub parameter?
            – Roman
            Apr 10 at 18:50










          • @Roman: you can hold shift during boot time to get into grub menu. Then you can edit start parameters. More about it here: wiki.ubuntu.com/Kernel/KernelBootParameters
            – ant
            Apr 12 at 9:28

















          • Can I avoid this bug by using other (for example older) version of Ubuntu?
            – Roman
            Apr 10 at 18:49










          • How can I start with dis_ucode_ldr grub parameter?
            – Roman
            Apr 10 at 18:50










          • @Roman: you can hold shift during boot time to get into grub menu. Then you can edit start parameters. More about it here: wiki.ubuntu.com/Kernel/KernelBootParameters
            – ant
            Apr 12 at 9:28
















          Can I avoid this bug by using other (for example older) version of Ubuntu?
          – Roman
          Apr 10 at 18:49




          Can I avoid this bug by using other (for example older) version of Ubuntu?
          – Roman
          Apr 10 at 18:49












          How can I start with dis_ucode_ldr grub parameter?
          – Roman
          Apr 10 at 18:50




          How can I start with dis_ucode_ldr grub parameter?
          – Roman
          Apr 10 at 18:50












          @Roman: you can hold shift during boot time to get into grub menu. Then you can edit start parameters. More about it here: wiki.ubuntu.com/Kernel/KernelBootParameters
          – ant
          Apr 12 at 9:28





          @Roman: you can hold shift during boot time to get into grub menu. Then you can edit start parameters. More about it here: wiki.ubuntu.com/Kernel/KernelBootParameters
          – ant
          Apr 12 at 9:28



          -

          Popular posts from this blog

          GRUB: Fatal! inconsistent data read from (0x84) 0+xxxxxx

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite Can anybody help me with this messages at (before) grub starts booting? . . Fatal! inconsistent data read from (0x84) 0+xxxxxx . Fatal! inconsistent data read from (0x84) n+yyyyyy . (hd0,4) This is running in dual boot with windows 7. Both Windows and Ubuntu are running flawlessly, except for this "errors" list. boot grub2 share | improve this question edited Apr 8 at 12:59 Byte Commander 59.4k 26 159 267 asked Apr 8 at 12:56 Viciente 6 1 add a comment  |  up vote 1 down vote favorite Can anybody help me with this messages at (before) grub starts booting? . . Fatal! inconsistent data read from (0x84) 0+xxxxxx . Fatal! inconsistent data read from (0x84) n+yyyyyy . (hd0,4) This is running in dual boot with windows 7. Both Windows and Ubuntu are running flawlessly, except for this "errors" list. boot grub2 share | improve th...
          Read more

          Problem in reading from socket

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I have a spark streaming program, that reads data from a socket I have craeted using: nc -lk 9999 The program reads the data from socket and exclude the "Error" messages. When I write manually in socket, it works fine. I have created a python script that prints "Error" messages frequently. I will save the result in a file using: stdbuf -oL python my_script.py &>> my_file.txt and read the file from the socket: nc -lk 9999 | tail -f my_file.txt Every thing is ok, the socket will read data from file while the file is being updated on the background, But the problem is that my spark program doen't capture the "Error" messages. As a summary: when I write manually "Error" messages in socket, spark capture them, But it won't capture "Error" message generated by python script from socket. Actually the program doesn't work if I read file from socket in...
          Read more

          Do not install recommended packages of dependencies

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite Recommended packages of a package and recommended packages of it's dependencies are installed by default when installing a package (tested on Ubuntu 18.04 Beta). How to install recommended packages of a package, but skip recommended packages of it's dependencies by a single apt command? apt software-installation dependencies share | improve this question asked Apr 24 at 6:37 linuxbuild 191 6 2 The --(no-)install-recommends,suggests flags are set for the entire apt operation, so your best bet would be (a) either installing without recommends and then installing the recommends, or (b) parsing out the recommends and installing them explicitl. Both are covered in ... – muru Apr 24 at 6:49 3 Possible duplicate of How to --install-suggests on an already installed package? – muru Apr 24 at 6:49 2 (It m...
          Read more