Why does switching to the tty give me a blank screen?
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
67
down vote
favorite
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
add a comment |Â
up vote
67
down vote
favorite
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
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
add a comment |Â
up vote
67
down vote
favorite
up vote
67
down vote
favorite
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
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
command-line virtual-console
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
add a comment |Â
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
add a comment |Â
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:
- Open the terminal with Ctrl+Alt+T
Paste the below, and enter your password when asked:
sudo sed -i -e 's/#GRUB_TERMINAL/GRUB_TERMINAL/g' /etc/default/grub
Then type
sudo update-grub
- Reboot and the virtual terminals should now work.
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 withctrl-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
toGRUB_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
 |Â
show 11 more comments
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:
Type in terminal:
gksu gedit /etc/default/grub
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"
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.
2
Worked for me. Be sure to read the last paragraph above, about runningsudo 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
 |Â
show 2 more comments
up vote
5
down vote
This is for newer version of Ubuntu:
Edit the GRUB configuration file:
sudo nano /etc/default/grub
Locate the line
#GRUB_GFXMODE=640x480
change it to
GRUB_GFXMODE=auto
and save the file.
Then update grub
sudo update-grub
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
add a comment |Â
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"
add a comment |Â
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
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
add a comment |Â
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:
- Open the terminal with Ctrl+Alt+T
Paste the below, and enter your password when asked:
sudo sed -i -e 's/#GRUB_TERMINAL/GRUB_TERMINAL/g' /etc/default/grub
Then type
sudo update-grub
- Reboot and the virtual terminals should now work.
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 withctrl-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
toGRUB_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
 |Â
show 11 more comments
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:
- Open the terminal with Ctrl+Alt+T
Paste the below, and enter your password when asked:
sudo sed -i -e 's/#GRUB_TERMINAL/GRUB_TERMINAL/g' /etc/default/grub
Then type
sudo update-grub
- Reboot and the virtual terminals should now work.
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 withctrl-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
toGRUB_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
 |Â
show 11 more comments
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:
- Open the terminal with Ctrl+Alt+T
Paste the below, and enter your password when asked:
sudo sed -i -e 's/#GRUB_TERMINAL/GRUB_TERMINAL/g' /etc/default/grub
Then type
sudo update-grub
- Reboot and the virtual terminals should now work.
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:
- Open the terminal with Ctrl+Alt+T
Paste the below, and enter your password when asked:
sudo sed -i -e 's/#GRUB_TERMINAL/GRUB_TERMINAL/g' /etc/default/grub
Then type
sudo update-grub
- Reboot and the virtual terminals should now work.
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 withctrl-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
toGRUB_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
 |Â
show 11 more comments
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 withctrl-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
toGRUB_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
 |Â
show 11 more comments
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:
Type in terminal:
gksu gedit /etc/default/grub
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"
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.
2
Worked for me. Be sure to read the last paragraph above, about runningsudo 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
 |Â
show 2 more comments
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:
Type in terminal:
gksu gedit /etc/default/grub
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"
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.
2
Worked for me. Be sure to read the last paragraph above, about runningsudo 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
 |Â
show 2 more comments
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:
Type in terminal:
gksu gedit /etc/default/grub
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"
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.
What fixed this for me was adding nomodeset
to the GRUB_CMDLINE_LINUX_DEFAULT
line in the /etc/default/grub
file. Here's how:
Type in terminal:
gksu gedit /etc/default/grub
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"
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.
edited Aug 22 '17 at 19:53
![](https://i.stack.imgur.com/eVuAv.png?s=32&g=1)
![](https://i.stack.imgur.com/eVuAv.png?s=32&g=1)
wjandrea
7,25842256
7,25842256
answered Jan 18 '16 at 20:15
![](https://i.stack.imgur.com/7DpBm.png?s=32&g=1)
![](https://i.stack.imgur.com/7DpBm.png?s=32&g=1)
Mina Michael
3,8691754114
3,8691754114
2
Worked for me. Be sure to read the last paragraph above, about runningsudo 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
 |Â
show 2 more comments
2
Worked for me. Be sure to read the last paragraph above, about runningsudo 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
 |Â
show 2 more comments
up vote
5
down vote
This is for newer version of Ubuntu:
Edit the GRUB configuration file:
sudo nano /etc/default/grub
Locate the line
#GRUB_GFXMODE=640x480
change it to
GRUB_GFXMODE=auto
and save the file.
Then update grub
sudo update-grub
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
add a comment |Â
up vote
5
down vote
This is for newer version of Ubuntu:
Edit the GRUB configuration file:
sudo nano /etc/default/grub
Locate the line
#GRUB_GFXMODE=640x480
change it to
GRUB_GFXMODE=auto
and save the file.
Then update grub
sudo update-grub
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
add a comment |Â
up vote
5
down vote
up vote
5
down vote
This is for newer version of Ubuntu:
Edit the GRUB configuration file:
sudo nano /etc/default/grub
Locate the line
#GRUB_GFXMODE=640x480
change it to
GRUB_GFXMODE=auto
and save the file.
Then update grub
sudo update-grub
This is for newer version of Ubuntu:
Edit the GRUB configuration file:
sudo nano /etc/default/grub
Locate the line
#GRUB_GFXMODE=640x480
change it to
GRUB_GFXMODE=auto
and save the file.
Then update grub
sudo update-grub
edited Oct 2 '17 at 18:30
![](https://i.stack.imgur.com/eVuAv.png?s=32&g=1)
![](https://i.stack.imgur.com/eVuAv.png?s=32&g=1)
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
add a comment |Â
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
add a comment |Â
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"
add a comment |Â
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"
add a comment |Â
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"
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"
edited Jun 22 '17 at 3:50
![](https://i.stack.imgur.com/U1Jy6.jpg?s=32&g=1)
![](https://i.stack.imgur.com/U1Jy6.jpg?s=32&g=1)
Sergiy Kolodyazhnyy
65.7k9134287
65.7k9134287
answered Jun 19 '17 at 5:59
Jiawan ÃÂÂê°Â맠Yovan
114
114
add a comment |Â
add a comment |Â
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
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
add a comment |Â
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
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
add a comment |Â
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
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
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
add a comment |Â
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
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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