Why does switching to the tty give me a blank screen? The 2019 Stack Overflow Developer Survey Results Are InCTRL + ALT + F1 show nothingHow to switch between console mode and GUI in 17.10 in X.Org mode?When I press ALT+CTRL+F1 it takes me to a blank screenWhat is the difference between GRUB_CMDLINE_LINUX and GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grubHow can I get TTYs to work with NVIDIA drivers?How do I use Nvidia GTX 860M with 14.04?Can't view output in tty. (Ctrl+alt+f1 to f6 don't work, and display a black screen).Ctrl+Alt+F1 stopped working in 16.04.LTSTTY is not showing the login promptUbuntu 12.10 TTY console (Ctrl+Alt+F[1-6]) not workingWhy is a virtual terminal “virtual”, and what/why/where is the “real” terminal?How to change the screen resolution of the virtual console on an external VGA?Command-line / Virtual terminal issueCompletely black blank screen after bootXTerm working but not Terminal?How do you use the TTY (without X server) on one screen, and X on the other?Alt + F keys always switches to virtual terminal on Ubuntu 16.04.2Why can I not use the virtual consoles on Ubuntu 16.04?Cannot type into terminal - Ubuntu Server 16.04.1Ctrl+Alt+F-keys do not respond after having gone in the loginless virtual console

Does adding complexity mean a more secure cipher?

Ubuntu Server install with full GUI

How to support a colleague who finds meetings extremely tiring?

What to do when moving next to a bird sanctuary with a loosely-domesticated cat?

Likelihood that a superbug or lethal virus could come from a landfill

Are there any other methods to apply to solving simultaneous equations?

Geography at the pixel level

What do I do when my TA workload is more than expected?

Is an up-to-date browser secure on an out-of-date OS?

Can we generate random numbers using irrational numbers like π and e?

For what reasons would an animal species NOT cross a *horizontal* land bridge?

If climate change impact can be observed in nature, has that had any effect on rural, i.e. farming community, perception of the scientific consensus?

"as much details as you can remember"

Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?

Why doesn't UInt have a toDouble()?

Why not take a picture of a closer black hole?

Are spiders unable to hurt humans, especially very small spiders?

How can I add encounters in the Lost Mine of Phandelver campaign without giving PCs too much XP?

What do hard-Brexiteers want with respect to the Irish border?

How did passengers keep warm on sail ships?

Is Cinnamon a desktop environment or a window manager? (Or both?)

Why doesn't shell automatically fix "useless use of cat"?

How do PCB vias affect signal quality?

Is it ethical to upload a automatically generated paper to a non peer-reviewed site as part of a larger research?



Why does switching to the tty give me a blank screen?



The 2019 Stack Overflow Developer Survey Results Are InCTRL + ALT + F1 show nothingHow to switch between console mode and GUI in 17.10 in X.Org mode?When I press ALT+CTRL+F1 it takes me to a blank screenWhat is the difference between GRUB_CMDLINE_LINUX and GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grubHow can I get TTYs to work with NVIDIA drivers?How do I use Nvidia GTX 860M with 14.04?Can't view output in tty. (Ctrl+alt+f1 to f6 don't work, and display a black screen).Ctrl+Alt+F1 stopped working in 16.04.LTSTTY is not showing the login promptUbuntu 12.10 TTY console (Ctrl+Alt+F[1-6]) not workingWhy is a virtual terminal “virtual”, and what/why/where is the “real” terminal?How to change the screen resolution of the virtual console on an external VGA?Command-line / Virtual terminal issueCompletely black blank screen after bootXTerm working but not Terminal?How do you use the TTY (without X server) on one screen, and X on the other?Alt + F keys always switches to virtual terminal on Ubuntu 16.04.2Why can I not use the virtual consoles on Ubuntu 16.04?Cannot type into terminal - Ubuntu Server 16.04.1Ctrl+Alt+F-keys do not respond after having gone in the loginless virtual console



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








71















After booting to the GUI in 12.04, I attempt to move to the virtual terminal (or shell, or tty) via Ctrl-Alt-F1 (F1 through F6), and the screen remains blank. I have tried all 6 tty instances and the results are the same. Ctrl-alt-F7 brings me back to the GUI without a problem. Any thoughts?










share|improve this question
























  • This occurs often together with being unable to see Grub of the boot splash. Can you see those?

    – hexafraction
    Jul 11 '12 at 20:11

















71















After booting to the GUI in 12.04, I attempt to move to the virtual terminal (or shell, or tty) via Ctrl-Alt-F1 (F1 through F6), and the screen remains blank. I have tried all 6 tty instances and the results are the same. Ctrl-alt-F7 brings me back to the GUI without a problem. Any thoughts?










share|improve this question
























  • This occurs often together with being unable to see Grub of the boot splash. Can you see those?

    – hexafraction
    Jul 11 '12 at 20:11













71












71








71


35






After booting to the GUI in 12.04, I attempt to move to the virtual terminal (or shell, or tty) via Ctrl-Alt-F1 (F1 through F6), and the screen remains blank. I have tried all 6 tty instances and the results are the same. Ctrl-alt-F7 brings me back to the GUI without a problem. Any thoughts?










share|improve this question
















After booting to the GUI in 12.04, I attempt to move to the virtual terminal (or shell, or tty) via Ctrl-Alt-F1 (F1 through F6), and the screen remains blank. I have tried all 6 tty instances and the results are the same. Ctrl-alt-F7 brings me back to the GUI without a problem. Any thoughts?







command-line virtual-console






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 '17 at 11:17









muru

1




1










asked Jul 11 '12 at 19:47









SeanOSeanO

511178




511178












  • This occurs often together with being unable to see Grub of the boot splash. Can you see those?

    – hexafraction
    Jul 11 '12 at 20:11

















  • This occurs often together with being unable to see Grub of the boot splash. Can you see those?

    – hexafraction
    Jul 11 '12 at 20:11
















This occurs often together with being unable to see Grub of the boot splash. Can you see those?

– hexafraction
Jul 11 '12 at 20:11





This occurs often together with being unable to see Grub of the boot splash. Can you see those?

– hexafraction
Jul 11 '12 at 20:11










6 Answers
6






active

oldest

votes


















64














This is usually caused because the graphical text-mode resolution set at boot up is not compatible with your video card. The solution is to switch to true text-mode by configuring Grub appropriately:



  1. Open the terminal with Ctrl+Alt+T


  2. Paste the below, and enter your password when asked:



    sudo sed -i -e 's/#GRUB_TERMINAL/GRUB_TERMINAL/g' /etc/default/grub


  3. Then type sudo update-grub


  4. Reboot and the virtual terminals should now work.





share|improve this answer


















  • 1





    Unfortunately, this didn't help with my graphic-driver issues (I need the X server down to install proper drivers, but the lack of drivers prevents me from getting a working command-line with ctrl-alt-F1).

    – Jonathan Y.
    Feb 1 '15 at 20:34






  • 8





    CAREFUL, this thing has completely messed up my grub, I don't see a boot menu anymore. (Ubuntu 15.04)

    – Arty
    Oct 25 '15 at 3:21







  • 1





    @MinaMichael No. It changes #GRUB_TERMINAL to GRUB_TERMINAL. The slash ends the regular expression, and the g is the global-modifier that sais: replace ALL matches.

    – Philipp Zedler
    Jan 12 '16 at 11:23






  • 1





    Doesn't work on 14.0.4 for me

    – Zach Rattner
    May 17 '16 at 1:57






  • 2





    Grub file states # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console Why would disabling graphical terminal fix this issue? For Ubuntu 16.04

    – Sun Bear
    Mar 10 '17 at 17:56



















14














What fixed this for me was adding nomodeset to the GRUB_CMDLINE_LINUX_DEFAULT line in the /etc/default/grub file. Here's how:



  1. Type in terminal: gksu gedit /etc/default/grub



  2. Search for this line: GRUB_CMDLINE_LINUX_DEFAULT



    So for example if you have:



    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"


    change it to:



    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1 nomodeset"


  3. After you finish, update grub (sudo update-grub) and reboot (sudo reboot) for the changes to take effect.


Optional: You could add nomodeset vga=xxx (not just nomodeset), the xxx is a VESA screen code that best matches your screen resolution. Take a look at this.






share|improve this answer




















  • 2





    Worked for me. Be sure to read the last paragraph above, about running sudo update-grub to apply the changes.

    – Andy Thomas
    Mar 18 '16 at 20:44











  • Worked for me on 14.0.4

    – Zach Rattner
    May 17 '16 at 1:58






  • 1





    When I do this with 14.04 and some Hardware enabling stack whatever this works technically, but graphical desktop is not booted into nor does startx work. But the terminal is back.

    – hakre
    Sep 16 '16 at 16:10






  • 1





    For me On Ubuntu 16.04 this caused my HDMI-VGA monitor to completely stop working.

    – Padraic Cunningham
    Dec 22 '16 at 17:21











  • @PadraicCunningham you can undo it from tty. I hope it wasn't too much trouble

    – Mina Michael
    Dec 22 '16 at 20:49


















6














This is for newer version of Ubuntu:




  1. Edit the GRUB configuration file:



    sudo nano /etc/default/grub



  2. Locate the line



    #GRUB_GFXMODE=640x480


    change it to



    GRUB_GFXMODE=auto


    and save the file.




  3. Then update grub



    sudo update-grub






share|improve this answer

























  • On Ubuntu 14.04.5 I installed a program that caused a 4.x kernel to be installed. Previously I had a 3.x kernel. This answer is what fixed this issue of blank ttys for me on an Asus Zenbook UX303LN.

    – frederickjh
    Apr 17 '18 at 12:30


















1














Please take a look at my question at https://answers.launchpad.net/ubuntu/+question/643882, with regards to virtual terminal not functioning on Ubuntu 16.04 on Lenovo Thinkpad T400.



The solution i presented is geared towards user with Hybrid Graphics Card, in particular, AMD/ATI graphics card and Intel integrated graphics card. For me, disabling the intel graphics card and enabling the opensource ATI/AMD radeon module helps in my case.



If you are using a old Radeon graphics card like mine (Radeon HD 3450/3470), now you can switch between virtual terminal and graphical desktop with ease to troubleshoot potential issues.



If adding blacklist intel_graphics_card in /etc/modprobe.d/blacklist.conf and running



sudo depmod -a 


still doesn't work due to linux kernel or other dependencies, you are advised to add modprobe.blacklist=<module_name> to /etc/default/grub like the following example:



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M radeon.dpm=1 modprobe.blacklist=i915"





share|improve this answer
































    0














    You need to shut down the graphics driver after you Ctrl+Alt+F1 before you try to install the Nvidia driver



    As in sudo /etc/init.d/lightdm stop






    share|improve this answer




















    • 3





      "before you try to install the Nvidia driver" - I'm not sure what you mean by that. The question doesn't mention anything about Nvidia drivers.

      – wjandrea
      Oct 2 '17 at 18:20


















    0














    Here is what worked for me on Ubuntu 18.04 with 2560x1440 screen:



    • open grub configuration file in editor: sudo gedit /etc/default/grub


    • uncomment GFXMODE and set your exact resolution -> change#GRUB_GFXMODE toGRUB_GFXMODE=2560x1440


    • add line GRUB_GFXPAYLOAD_LINUX=keep


    • Add remove splash and add nosplash noplymouth nomodeset to your GRUB_CMDLINE_LINUX_DEFAULT. After cahnges mine looks like GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash noplymouth intel_idle.max_cstate=1 nomodeset"


    • save the file


    • update grub sudo update-grub


    • reboot


    • use Ctlr+Alt+F2 to switch immediately after boot






    share|improve this answer























      Your Answer








      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "89"
      ;
      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',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      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
      );



      );













      draft saved

      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f162535%2fwhy-does-switching-to-the-tty-give-me-a-blank-screen%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      6 Answers
      6






      active

      oldest

      votes








      6 Answers
      6






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      64














      This is usually caused because the graphical text-mode resolution set at boot up is not compatible with your video card. The solution is to switch to true text-mode by configuring Grub appropriately:



      1. Open the terminal with Ctrl+Alt+T


      2. Paste the below, and enter your password when asked:



        sudo sed -i -e 's/#GRUB_TERMINAL/GRUB_TERMINAL/g' /etc/default/grub


      3. Then type sudo update-grub


      4. Reboot and the virtual terminals should now work.





      share|improve this answer


















      • 1





        Unfortunately, this didn't help with my graphic-driver issues (I need the X server down to install proper drivers, but the lack of drivers prevents me from getting a working command-line with ctrl-alt-F1).

        – Jonathan Y.
        Feb 1 '15 at 20:34






      • 8





        CAREFUL, this thing has completely messed up my grub, I don't see a boot menu anymore. (Ubuntu 15.04)

        – Arty
        Oct 25 '15 at 3:21







      • 1





        @MinaMichael No. It changes #GRUB_TERMINAL to GRUB_TERMINAL. The slash ends the regular expression, and the g is the global-modifier that sais: replace ALL matches.

        – Philipp Zedler
        Jan 12 '16 at 11:23






      • 1





        Doesn't work on 14.0.4 for me

        – Zach Rattner
        May 17 '16 at 1:57






      • 2





        Grub file states # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console Why would disabling graphical terminal fix this issue? For Ubuntu 16.04

        – Sun Bear
        Mar 10 '17 at 17:56
















      64














      This is usually caused because the graphical text-mode resolution set at boot up is not compatible with your video card. The solution is to switch to true text-mode by configuring Grub appropriately:



      1. Open the terminal with Ctrl+Alt+T


      2. Paste the below, and enter your password when asked:



        sudo sed -i -e 's/#GRUB_TERMINAL/GRUB_TERMINAL/g' /etc/default/grub


      3. Then type sudo update-grub


      4. Reboot and the virtual terminals should now work.





      share|improve this answer


















      • 1





        Unfortunately, this didn't help with my graphic-driver issues (I need the X server down to install proper drivers, but the lack of drivers prevents me from getting a working command-line with ctrl-alt-F1).

        – Jonathan Y.
        Feb 1 '15 at 20:34






      • 8





        CAREFUL, this thing has completely messed up my grub, I don't see a boot menu anymore. (Ubuntu 15.04)

        – Arty
        Oct 25 '15 at 3:21







      • 1





        @MinaMichael No. It changes #GRUB_TERMINAL to GRUB_TERMINAL. The slash ends the regular expression, and the g is the global-modifier that sais: replace ALL matches.

        – Philipp Zedler
        Jan 12 '16 at 11:23






      • 1





        Doesn't work on 14.0.4 for me

        – Zach Rattner
        May 17 '16 at 1:57






      • 2





        Grub file states # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console Why would disabling graphical terminal fix this issue? For Ubuntu 16.04

        – Sun Bear
        Mar 10 '17 at 17:56














      64












      64








      64







      This is usually caused because the graphical text-mode resolution set at boot up is not compatible with your video card. The solution is to switch to true text-mode by configuring Grub appropriately:



      1. Open the terminal with Ctrl+Alt+T


      2. Paste the below, and enter your password when asked:



        sudo sed -i -e 's/#GRUB_TERMINAL/GRUB_TERMINAL/g' /etc/default/grub


      3. Then type sudo update-grub


      4. Reboot and the virtual terminals should now work.





      share|improve this answer













      This is usually caused because the graphical text-mode resolution set at boot up is not compatible with your video card. The solution is to switch to true text-mode by configuring Grub appropriately:



      1. Open the terminal with Ctrl+Alt+T


      2. Paste the below, and enter your password when asked:



        sudo sed -i -e 's/#GRUB_TERMINAL/GRUB_TERMINAL/g' /etc/default/grub


      3. Then type sudo update-grub


      4. Reboot and the virtual terminals should now work.






      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Jul 11 '12 at 22:56









      ishish

      117k32270295




      117k32270295







      • 1





        Unfortunately, this didn't help with my graphic-driver issues (I need the X server down to install proper drivers, but the lack of drivers prevents me from getting a working command-line with ctrl-alt-F1).

        – Jonathan Y.
        Feb 1 '15 at 20:34






      • 8





        CAREFUL, this thing has completely messed up my grub, I don't see a boot menu anymore. (Ubuntu 15.04)

        – Arty
        Oct 25 '15 at 3:21







      • 1





        @MinaMichael No. It changes #GRUB_TERMINAL to GRUB_TERMINAL. The slash ends the regular expression, and the g is the global-modifier that sais: replace ALL matches.

        – Philipp Zedler
        Jan 12 '16 at 11:23






      • 1





        Doesn't work on 14.0.4 for me

        – Zach Rattner
        May 17 '16 at 1:57






      • 2





        Grub file states # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console Why would disabling graphical terminal fix this issue? For Ubuntu 16.04

        – Sun Bear
        Mar 10 '17 at 17:56













      • 1





        Unfortunately, this didn't help with my graphic-driver issues (I need the X server down to install proper drivers, but the lack of drivers prevents me from getting a working command-line with ctrl-alt-F1).

        – Jonathan Y.
        Feb 1 '15 at 20:34






      • 8





        CAREFUL, this thing has completely messed up my grub, I don't see a boot menu anymore. (Ubuntu 15.04)

        – Arty
        Oct 25 '15 at 3:21







      • 1





        @MinaMichael No. It changes #GRUB_TERMINAL to GRUB_TERMINAL. The slash ends the regular expression, and the g is the global-modifier that sais: replace ALL matches.

        – Philipp Zedler
        Jan 12 '16 at 11:23






      • 1





        Doesn't work on 14.0.4 for me

        – Zach Rattner
        May 17 '16 at 1:57






      • 2





        Grub file states # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console Why would disabling graphical terminal fix this issue? For Ubuntu 16.04

        – Sun Bear
        Mar 10 '17 at 17:56








      1




      1





      Unfortunately, this didn't help with my graphic-driver issues (I need the X server down to install proper drivers, but the lack of drivers prevents me from getting a working command-line with ctrl-alt-F1).

      – Jonathan Y.
      Feb 1 '15 at 20:34





      Unfortunately, this didn't help with my graphic-driver issues (I need the X server down to install proper drivers, but the lack of drivers prevents me from getting a working command-line with ctrl-alt-F1).

      – Jonathan Y.
      Feb 1 '15 at 20:34




      8




      8





      CAREFUL, this thing has completely messed up my grub, I don't see a boot menu anymore. (Ubuntu 15.04)

      – Arty
      Oct 25 '15 at 3:21






      CAREFUL, this thing has completely messed up my grub, I don't see a boot menu anymore. (Ubuntu 15.04)

      – Arty
      Oct 25 '15 at 3:21





      1




      1





      @MinaMichael No. It changes #GRUB_TERMINAL to GRUB_TERMINAL. The slash ends the regular expression, and the g is the global-modifier that sais: replace ALL matches.

      – Philipp Zedler
      Jan 12 '16 at 11:23





      @MinaMichael No. It changes #GRUB_TERMINAL to GRUB_TERMINAL. The slash ends the regular expression, and the g is the global-modifier that sais: replace ALL matches.

      – Philipp Zedler
      Jan 12 '16 at 11:23




      1




      1





      Doesn't work on 14.0.4 for me

      – Zach Rattner
      May 17 '16 at 1:57





      Doesn't work on 14.0.4 for me

      – Zach Rattner
      May 17 '16 at 1:57




      2




      2





      Grub file states # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console Why would disabling graphical terminal fix this issue? For Ubuntu 16.04

      – Sun Bear
      Mar 10 '17 at 17:56






      Grub file states # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console Why would disabling graphical terminal fix this issue? For Ubuntu 16.04

      – Sun Bear
      Mar 10 '17 at 17:56














      14














      What fixed this for me was adding nomodeset to the GRUB_CMDLINE_LINUX_DEFAULT line in the /etc/default/grub file. Here's how:



      1. Type in terminal: gksu gedit /etc/default/grub



      2. Search for this line: GRUB_CMDLINE_LINUX_DEFAULT



        So for example if you have:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"


        change it to:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1 nomodeset"


      3. After you finish, update grub (sudo update-grub) and reboot (sudo reboot) for the changes to take effect.


      Optional: You could add nomodeset vga=xxx (not just nomodeset), the xxx is a VESA screen code that best matches your screen resolution. Take a look at this.






      share|improve this answer




















      • 2





        Worked for me. Be sure to read the last paragraph above, about running sudo update-grub to apply the changes.

        – Andy Thomas
        Mar 18 '16 at 20:44











      • Worked for me on 14.0.4

        – Zach Rattner
        May 17 '16 at 1:58






      • 1





        When I do this with 14.04 and some Hardware enabling stack whatever this works technically, but graphical desktop is not booted into nor does startx work. But the terminal is back.

        – hakre
        Sep 16 '16 at 16:10






      • 1





        For me On Ubuntu 16.04 this caused my HDMI-VGA monitor to completely stop working.

        – Padraic Cunningham
        Dec 22 '16 at 17:21











      • @PadraicCunningham you can undo it from tty. I hope it wasn't too much trouble

        – Mina Michael
        Dec 22 '16 at 20:49















      14














      What fixed this for me was adding nomodeset to the GRUB_CMDLINE_LINUX_DEFAULT line in the /etc/default/grub file. Here's how:



      1. Type in terminal: gksu gedit /etc/default/grub



      2. Search for this line: GRUB_CMDLINE_LINUX_DEFAULT



        So for example if you have:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"


        change it to:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1 nomodeset"


      3. After you finish, update grub (sudo update-grub) and reboot (sudo reboot) for the changes to take effect.


      Optional: You could add nomodeset vga=xxx (not just nomodeset), the xxx is a VESA screen code that best matches your screen resolution. Take a look at this.






      share|improve this answer




















      • 2





        Worked for me. Be sure to read the last paragraph above, about running sudo update-grub to apply the changes.

        – Andy Thomas
        Mar 18 '16 at 20:44











      • Worked for me on 14.0.4

        – Zach Rattner
        May 17 '16 at 1:58






      • 1





        When I do this with 14.04 and some Hardware enabling stack whatever this works technically, but graphical desktop is not booted into nor does startx work. But the terminal is back.

        – hakre
        Sep 16 '16 at 16:10






      • 1





        For me On Ubuntu 16.04 this caused my HDMI-VGA monitor to completely stop working.

        – Padraic Cunningham
        Dec 22 '16 at 17:21











      • @PadraicCunningham you can undo it from tty. I hope it wasn't too much trouble

        – Mina Michael
        Dec 22 '16 at 20:49













      14












      14








      14







      What fixed this for me was adding nomodeset to the GRUB_CMDLINE_LINUX_DEFAULT line in the /etc/default/grub file. Here's how:



      1. Type in terminal: gksu gedit /etc/default/grub



      2. Search for this line: GRUB_CMDLINE_LINUX_DEFAULT



        So for example if you have:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"


        change it to:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1 nomodeset"


      3. After you finish, update grub (sudo update-grub) and reboot (sudo reboot) for the changes to take effect.


      Optional: You could add nomodeset vga=xxx (not just nomodeset), the xxx is a VESA screen code that best matches your screen resolution. Take a look at this.






      share|improve this answer















      What fixed this for me was adding nomodeset to the GRUB_CMDLINE_LINUX_DEFAULT line in the /etc/default/grub file. Here's how:



      1. Type in terminal: gksu gedit /etc/default/grub



      2. Search for this line: GRUB_CMDLINE_LINUX_DEFAULT



        So for example if you have:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"


        change it to:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1 nomodeset"


      3. After you finish, update grub (sudo update-grub) and reboot (sudo reboot) for the changes to take effect.


      Optional: You could add nomodeset vga=xxx (not just nomodeset), the xxx is a VESA screen code that best matches your screen resolution. Take a look at this.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Aug 22 '17 at 19:53









      wjandrea

      9,56542765




      9,56542765










      answered Jan 18 '16 at 20:15









      Mina MichaelMina Michael

      4,2271860122




      4,2271860122







      • 2





        Worked for me. Be sure to read the last paragraph above, about running sudo update-grub to apply the changes.

        – Andy Thomas
        Mar 18 '16 at 20:44











      • Worked for me on 14.0.4

        – Zach Rattner
        May 17 '16 at 1:58






      • 1





        When I do this with 14.04 and some Hardware enabling stack whatever this works technically, but graphical desktop is not booted into nor does startx work. But the terminal is back.

        – hakre
        Sep 16 '16 at 16:10






      • 1





        For me On Ubuntu 16.04 this caused my HDMI-VGA monitor to completely stop working.

        – Padraic Cunningham
        Dec 22 '16 at 17:21











      • @PadraicCunningham you can undo it from tty. I hope it wasn't too much trouble

        – Mina Michael
        Dec 22 '16 at 20:49












      • 2





        Worked for me. Be sure to read the last paragraph above, about running sudo update-grub to apply the changes.

        – Andy Thomas
        Mar 18 '16 at 20:44











      • Worked for me on 14.0.4

        – Zach Rattner
        May 17 '16 at 1:58






      • 1





        When I do this with 14.04 and some Hardware enabling stack whatever this works technically, but graphical desktop is not booted into nor does startx work. But the terminal is back.

        – hakre
        Sep 16 '16 at 16:10






      • 1





        For me On Ubuntu 16.04 this caused my HDMI-VGA monitor to completely stop working.

        – Padraic Cunningham
        Dec 22 '16 at 17:21











      • @PadraicCunningham you can undo it from tty. I hope it wasn't too much trouble

        – Mina Michael
        Dec 22 '16 at 20:49







      2




      2





      Worked for me. Be sure to read the last paragraph above, about running sudo update-grub to apply the changes.

      – Andy Thomas
      Mar 18 '16 at 20:44





      Worked for me. Be sure to read the last paragraph above, about running sudo update-grub to apply the changes.

      – Andy Thomas
      Mar 18 '16 at 20:44













      Worked for me on 14.0.4

      – Zach Rattner
      May 17 '16 at 1:58





      Worked for me on 14.0.4

      – Zach Rattner
      May 17 '16 at 1:58




      1




      1





      When I do this with 14.04 and some Hardware enabling stack whatever this works technically, but graphical desktop is not booted into nor does startx work. But the terminal is back.

      – hakre
      Sep 16 '16 at 16:10





      When I do this with 14.04 and some Hardware enabling stack whatever this works technically, but graphical desktop is not booted into nor does startx work. But the terminal is back.

      – hakre
      Sep 16 '16 at 16:10




      1




      1





      For me On Ubuntu 16.04 this caused my HDMI-VGA monitor to completely stop working.

      – Padraic Cunningham
      Dec 22 '16 at 17:21





      For me On Ubuntu 16.04 this caused my HDMI-VGA monitor to completely stop working.

      – Padraic Cunningham
      Dec 22 '16 at 17:21













      @PadraicCunningham you can undo it from tty. I hope it wasn't too much trouble

      – Mina Michael
      Dec 22 '16 at 20:49





      @PadraicCunningham you can undo it from tty. I hope it wasn't too much trouble

      – Mina Michael
      Dec 22 '16 at 20:49











      6














      This is for newer version of Ubuntu:




      1. Edit the GRUB configuration file:



        sudo nano /etc/default/grub



      2. Locate the line



        #GRUB_GFXMODE=640x480


        change it to



        GRUB_GFXMODE=auto


        and save the file.




      3. Then update grub



        sudo update-grub






      share|improve this answer

























      • On Ubuntu 14.04.5 I installed a program that caused a 4.x kernel to be installed. Previously I had a 3.x kernel. This answer is what fixed this issue of blank ttys for me on an Asus Zenbook UX303LN.

        – frederickjh
        Apr 17 '18 at 12:30















      6














      This is for newer version of Ubuntu:




      1. Edit the GRUB configuration file:



        sudo nano /etc/default/grub



      2. Locate the line



        #GRUB_GFXMODE=640x480


        change it to



        GRUB_GFXMODE=auto


        and save the file.




      3. Then update grub



        sudo update-grub






      share|improve this answer

























      • On Ubuntu 14.04.5 I installed a program that caused a 4.x kernel to be installed. Previously I had a 3.x kernel. This answer is what fixed this issue of blank ttys for me on an Asus Zenbook UX303LN.

        – frederickjh
        Apr 17 '18 at 12:30













      6












      6








      6







      This is for newer version of Ubuntu:




      1. Edit the GRUB configuration file:



        sudo nano /etc/default/grub



      2. Locate the line



        #GRUB_GFXMODE=640x480


        change it to



        GRUB_GFXMODE=auto


        and save the file.




      3. Then update grub



        sudo update-grub






      share|improve this answer















      This is for newer version of Ubuntu:




      1. Edit the GRUB configuration file:



        sudo nano /etc/default/grub



      2. Locate the line



        #GRUB_GFXMODE=640x480


        change it to



        GRUB_GFXMODE=auto


        and save the file.




      3. Then update grub



        sudo update-grub







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Oct 2 '17 at 18:30









      wjandrea

      9,56542765




      9,56542765










      answered Sep 10 '17 at 18:01









      MichaelMichael

      7112




      7112












      • On Ubuntu 14.04.5 I installed a program that caused a 4.x kernel to be installed. Previously I had a 3.x kernel. This answer is what fixed this issue of blank ttys for me on an Asus Zenbook UX303LN.

        – frederickjh
        Apr 17 '18 at 12:30

















      • On Ubuntu 14.04.5 I installed a program that caused a 4.x kernel to be installed. Previously I had a 3.x kernel. This answer is what fixed this issue of blank ttys for me on an Asus Zenbook UX303LN.

        – frederickjh
        Apr 17 '18 at 12:30
















      On Ubuntu 14.04.5 I installed a program that caused a 4.x kernel to be installed. Previously I had a 3.x kernel. This answer is what fixed this issue of blank ttys for me on an Asus Zenbook UX303LN.

      – frederickjh
      Apr 17 '18 at 12:30





      On Ubuntu 14.04.5 I installed a program that caused a 4.x kernel to be installed. Previously I had a 3.x kernel. This answer is what fixed this issue of blank ttys for me on an Asus Zenbook UX303LN.

      – frederickjh
      Apr 17 '18 at 12:30











      1














      Please take a look at my question at https://answers.launchpad.net/ubuntu/+question/643882, with regards to virtual terminal not functioning on Ubuntu 16.04 on Lenovo Thinkpad T400.



      The solution i presented is geared towards user with Hybrid Graphics Card, in particular, AMD/ATI graphics card and Intel integrated graphics card. For me, disabling the intel graphics card and enabling the opensource ATI/AMD radeon module helps in my case.



      If you are using a old Radeon graphics card like mine (Radeon HD 3450/3470), now you can switch between virtual terminal and graphical desktop with ease to troubleshoot potential issues.



      If adding blacklist intel_graphics_card in /etc/modprobe.d/blacklist.conf and running



      sudo depmod -a 


      still doesn't work due to linux kernel or other dependencies, you are advised to add modprobe.blacklist=<module_name> to /etc/default/grub like the following example:



      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M radeon.dpm=1 modprobe.blacklist=i915"





      share|improve this answer





























        1














        Please take a look at my question at https://answers.launchpad.net/ubuntu/+question/643882, with regards to virtual terminal not functioning on Ubuntu 16.04 on Lenovo Thinkpad T400.



        The solution i presented is geared towards user with Hybrid Graphics Card, in particular, AMD/ATI graphics card and Intel integrated graphics card. For me, disabling the intel graphics card and enabling the opensource ATI/AMD radeon module helps in my case.



        If you are using a old Radeon graphics card like mine (Radeon HD 3450/3470), now you can switch between virtual terminal and graphical desktop with ease to troubleshoot potential issues.



        If adding blacklist intel_graphics_card in /etc/modprobe.d/blacklist.conf and running



        sudo depmod -a 


        still doesn't work due to linux kernel or other dependencies, you are advised to add modprobe.blacklist=<module_name> to /etc/default/grub like the following example:



        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M radeon.dpm=1 modprobe.blacklist=i915"





        share|improve this answer



























          1












          1








          1







          Please take a look at my question at https://answers.launchpad.net/ubuntu/+question/643882, with regards to virtual terminal not functioning on Ubuntu 16.04 on Lenovo Thinkpad T400.



          The solution i presented is geared towards user with Hybrid Graphics Card, in particular, AMD/ATI graphics card and Intel integrated graphics card. For me, disabling the intel graphics card and enabling the opensource ATI/AMD radeon module helps in my case.



          If you are using a old Radeon graphics card like mine (Radeon HD 3450/3470), now you can switch between virtual terminal and graphical desktop with ease to troubleshoot potential issues.



          If adding blacklist intel_graphics_card in /etc/modprobe.d/blacklist.conf and running



          sudo depmod -a 


          still doesn't work due to linux kernel or other dependencies, you are advised to add modprobe.blacklist=<module_name> to /etc/default/grub like the following example:



          GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M radeon.dpm=1 modprobe.blacklist=i915"





          share|improve this answer















          Please take a look at my question at https://answers.launchpad.net/ubuntu/+question/643882, with regards to virtual terminal not functioning on Ubuntu 16.04 on Lenovo Thinkpad T400.



          The solution i presented is geared towards user with Hybrid Graphics Card, in particular, AMD/ATI graphics card and Intel integrated graphics card. For me, disabling the intel graphics card and enabling the opensource ATI/AMD radeon module helps in my case.



          If you are using a old Radeon graphics card like mine (Radeon HD 3450/3470), now you can switch between virtual terminal and graphical desktop with ease to troubleshoot potential issues.



          If adding blacklist intel_graphics_card in /etc/modprobe.d/blacklist.conf and running



          sudo depmod -a 


          still doesn't work due to linux kernel or other dependencies, you are advised to add modprobe.blacklist=<module_name> to /etc/default/grub like the following example:



          GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M radeon.dpm=1 modprobe.blacklist=i915"






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jun 22 '17 at 3:50









          Sergiy Kolodyazhnyy

          75.1k9155327




          75.1k9155327










          answered Jun 19 '17 at 5:59









          Jiawan 탁가만 YovanJiawan 탁가만 Yovan

          114




          114





















              0














              You need to shut down the graphics driver after you Ctrl+Alt+F1 before you try to install the Nvidia driver



              As in sudo /etc/init.d/lightdm stop






              share|improve this answer




















              • 3





                "before you try to install the Nvidia driver" - I'm not sure what you mean by that. The question doesn't mention anything about Nvidia drivers.

                – wjandrea
                Oct 2 '17 at 18:20















              0














              You need to shut down the graphics driver after you Ctrl+Alt+F1 before you try to install the Nvidia driver



              As in sudo /etc/init.d/lightdm stop






              share|improve this answer




















              • 3





                "before you try to install the Nvidia driver" - I'm not sure what you mean by that. The question doesn't mention anything about Nvidia drivers.

                – wjandrea
                Oct 2 '17 at 18:20













              0












              0








              0







              You need to shut down the graphics driver after you Ctrl+Alt+F1 before you try to install the Nvidia driver



              As in sudo /etc/init.d/lightdm stop






              share|improve this answer















              You need to shut down the graphics driver after you Ctrl+Alt+F1 before you try to install the Nvidia driver



              As in sudo /etc/init.d/lightdm stop







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Jul 18 '16 at 7:10









              Kevin Bowen

              14.9k155971




              14.9k155971










              answered Feb 26 '15 at 0:25









              Pat HertelPat Hertel

              143




              143







              • 3





                "before you try to install the Nvidia driver" - I'm not sure what you mean by that. The question doesn't mention anything about Nvidia drivers.

                – wjandrea
                Oct 2 '17 at 18:20












              • 3





                "before you try to install the Nvidia driver" - I'm not sure what you mean by that. The question doesn't mention anything about Nvidia drivers.

                – wjandrea
                Oct 2 '17 at 18:20







              3




              3





              "before you try to install the Nvidia driver" - I'm not sure what you mean by that. The question doesn't mention anything about Nvidia drivers.

              – wjandrea
              Oct 2 '17 at 18:20





              "before you try to install the Nvidia driver" - I'm not sure what you mean by that. The question doesn't mention anything about Nvidia drivers.

              – wjandrea
              Oct 2 '17 at 18:20











              0














              Here is what worked for me on Ubuntu 18.04 with 2560x1440 screen:



              • open grub configuration file in editor: sudo gedit /etc/default/grub


              • uncomment GFXMODE and set your exact resolution -> change#GRUB_GFXMODE toGRUB_GFXMODE=2560x1440


              • add line GRUB_GFXPAYLOAD_LINUX=keep


              • Add remove splash and add nosplash noplymouth nomodeset to your GRUB_CMDLINE_LINUX_DEFAULT. After cahnges mine looks like GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash noplymouth intel_idle.max_cstate=1 nomodeset"


              • save the file


              • update grub sudo update-grub


              • reboot


              • use Ctlr+Alt+F2 to switch immediately after boot






              share|improve this answer



























                0














                Here is what worked for me on Ubuntu 18.04 with 2560x1440 screen:



                • open grub configuration file in editor: sudo gedit /etc/default/grub


                • uncomment GFXMODE and set your exact resolution -> change#GRUB_GFXMODE toGRUB_GFXMODE=2560x1440


                • add line GRUB_GFXPAYLOAD_LINUX=keep


                • Add remove splash and add nosplash noplymouth nomodeset to your GRUB_CMDLINE_LINUX_DEFAULT. After cahnges mine looks like GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash noplymouth intel_idle.max_cstate=1 nomodeset"


                • save the file


                • update grub sudo update-grub


                • reboot


                • use Ctlr+Alt+F2 to switch immediately after boot






                share|improve this answer

























                  0












                  0








                  0







                  Here is what worked for me on Ubuntu 18.04 with 2560x1440 screen:



                  • open grub configuration file in editor: sudo gedit /etc/default/grub


                  • uncomment GFXMODE and set your exact resolution -> change#GRUB_GFXMODE toGRUB_GFXMODE=2560x1440


                  • add line GRUB_GFXPAYLOAD_LINUX=keep


                  • Add remove splash and add nosplash noplymouth nomodeset to your GRUB_CMDLINE_LINUX_DEFAULT. After cahnges mine looks like GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash noplymouth intel_idle.max_cstate=1 nomodeset"


                  • save the file


                  • update grub sudo update-grub


                  • reboot


                  • use Ctlr+Alt+F2 to switch immediately after boot






                  share|improve this answer













                  Here is what worked for me on Ubuntu 18.04 with 2560x1440 screen:



                  • open grub configuration file in editor: sudo gedit /etc/default/grub


                  • uncomment GFXMODE and set your exact resolution -> change#GRUB_GFXMODE toGRUB_GFXMODE=2560x1440


                  • add line GRUB_GFXPAYLOAD_LINUX=keep


                  • Add remove splash and add nosplash noplymouth nomodeset to your GRUB_CMDLINE_LINUX_DEFAULT. After cahnges mine looks like GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash noplymouth intel_idle.max_cstate=1 nomodeset"


                  • save the file


                  • update grub sudo update-grub


                  • reboot


                  • use Ctlr+Alt+F2 to switch immediately after boot







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 2 days ago









                  y.selivonchyky.selivonchyk

                  1214




                  1214



























                      draft saved

                      draft discarded
















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid


                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.

                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f162535%2fwhy-does-switching-to-the-tty-give-me-a-blank-screen%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

                      Tamil (spriik) Luke uk diar | Nawigatjuun

                      Align equal signs while including text over equalitiesAMS align: left aligned text/math plus multicolumn alignmentMultiple alignmentsAligning equations in multiple placesNumbering and aligning an equation with multiple columnsHow to align one equation with another multline equationUsing \ in environments inside the begintabularxNumber equations and preserving alignment of equal signsHow can I align equations to the left and to the right?Double equation alignment problem within align enviromentAligned within align: Why are they right-aligned?

                      Training a classifier when some of the features are unknownWhy does Gradient Boosting regression predict negative values when there are no negative y-values in my training set?How to improve an existing (trained) classifier?What is effect when I set up some self defined predisctor variables?Why Matlab neural network classification returns decimal values on prediction dataset?Fitting and transforming text data in training, testing, and validation setsHow to quantify the performance of the classifier (multi-class SVM) using the test data?How do I control for some patients providing multiple samples in my training data?Training and Test setTraining a convolutional neural network for image denoising in MatlabShouldn't an autoencoder with #(neurons in hidden layer) = #(neurons in input layer) be “perfect”?