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

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








up vote
67
down vote

favorite
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























  • 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














up vote
67
down vote

favorite
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























  • 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












up vote
67
down vote

favorite
35









up vote
67
down vote

favorite
35






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

130k19275470




130k19275470










asked Jul 11 '12 at 19:47









SeanO

491178




491178











  • 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










5 Answers
5






active

oldest

votes

















up vote
63
down vote



accepted










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






  • 7




    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


















up vote
14
down vote













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

















up vote
5
down vote













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 at 12:30

















up vote
1
down vote













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





























    up vote
    0
    down vote













    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










    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',
    convertImagesToLinks: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    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






























    5 Answers
    5






    active

    oldest

    votes








    5 Answers
    5






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    63
    down vote



    accepted










    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






    • 7




      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















    up vote
    63
    down vote



    accepted










    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






    • 7




      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













    up vote
    63
    down vote



    accepted







    up vote
    63
    down vote



    accepted






    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









    ish

    113k27256290




    113k27256290







    • 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






    • 7




      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






    • 7




      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




    7




    7




    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













    up vote
    14
    down vote













    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














    up vote
    14
    down vote













    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












    up vote
    14
    down vote










    up vote
    14
    down vote









    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

    7,25842256




    7,25842256










    answered Jan 18 '16 at 20:15









    Mina Michael

    3,8691754114




    3,8691754114







    • 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










    up vote
    5
    down vote













    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 at 12:30














    up vote
    5
    down vote













    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 at 12:30












    up vote
    5
    down vote










    up vote
    5
    down vote









    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

    7,25842256




    7,25842256










    answered Sep 10 '17 at 18:01









    Michael

    6112




    6112











    • 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 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 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 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 at 12:30










    up vote
    1
    down vote













    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


























      up vote
      1
      down vote













      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
























        up vote
        1
        down vote










        up vote
        1
        down vote









        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

        65.7k9134287




        65.7k9134287










        answered Jun 19 '17 at 5:59









        Jiawan 탁가만 Yovan

        114




        114




















            up vote
            0
            down vote













            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














            up vote
            0
            down vote













            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












            up vote
            0
            down vote










            up vote
            0
            down vote









            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

            13.9k145769




            13.9k145769










            answered Feb 26 '15 at 0:25









            Pat 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

















             

            draft saved


            draft discarded















































             


            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













































































            Popular posts from this blog

            pylint3 and pip3 broken

            Missing snmpget and snmpwalk

            How to enroll fingerprints to Ubuntu 17.10 with VFS491