Ctrl-Alt-F1 = Black,blank screen?

timkarwoski · 11-21-2005, 11:27 PM

I was looking at another help topic and I saw that someone mentioned that pressing Ctrl-Alt-F1 will bring up some kind of console window. I tried that out but I got a strange result.

Right when I press it the screen turns off for about a second, and then it comes back on, although it is just solid black. I cannot do anything in this state, theres no prompt or text or anything, just solid black. If I press Ctrl-Alt-F7 again it flashes off a second like before and brings me back to the desktop and everything is fine. (I'm running Mandrake 10.1, Kernel 2.6.14.2 with an ATI x800 graphics card)

Any Ideas? I can supply any relevant console outputs or file contents if it will help, just let me know.

btmiller · 11-22-2005, 12:53 AM

You probably don't have a getty process running on tty1 (the first console). Check your /etc/inittab to see if getty is started on that console in runlevel 5.

timkarwoski · 11-22-2005, 09:10 AM

Ok Im not real familiar with getty, heres whats in my /etc/inittab

Code:

#
# inittab       This file describes how the INIT process should set up
#               the system in a certain run-level.
#
# Author:       Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
#               Modified for RHS Linux by Marc Ewing and Donnie Barnes
#

# Default runlevel. The runlevels used by Mandrakelinux are:
#   0 - halt (Do NOT set initdefault to this)
#   1 - Single user mode
#   2 - Multiuser, without NFS (The same as 3, if you do not have networking)
#   3 - Full multiuser mode
#   4 - unused
#   5 - X11
#   6 - reboot (Do NOT set initdefault to this)
# 
id:5:initdefault:

# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit

l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6

# Trap CTRL-ALT-DELETE

# When our UPS tells us power has failed, assume we have a few minutes
# of power left.  Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.  
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"

# If power was restored before the shutdown kicked in, cancel it.
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"


# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6

ca::ctrlaltdel:/sbin/shutdown -t3 -r now

Any suggestions?

brainiac · 11-22-2005, 09:17 AM

One of my systems had issues with Ctrl-Alt-F1 terminal. F2-F6 worked just fine, now out of habit I use them only. It appeared to be some sort of system use thing. Sometimes it would display a boot log, sometimes not.

timkarwoski · 11-22-2005, 09:48 AM

F2-F6 also do nothing for me. They all just take me to a blank screen. F7 still brings me back to desktop though.

jh559 · 12-18-2005, 04:49 PM

Hi, i've got the same problem as you described and was wondering if you've had any success fixing it and if so, what you did.

thanks
James

btmiller · 12-18-2005, 07:31 PM

From the /etc/inittab file posted, it looks like mingetty should be running on each terminal. Can you verify (using ps) that the mingetty processes are actually running?

jh559 · 12-18-2005, 08:39 PM

hi. i managed to fix the problem on my computer by updating xorg-x11 (i'm using fedora core 4 so i used yum to update it). hope that helps.
James

m_yates · 12-18-2005, 11:28 PM

The problem you are experiencing is most likely due to:

(1) the kernel framebuffer video driver. Do you have bootsplash, usplash, splashy, etc for a graphical boot process? If so, you may need to disable it. Look in /boot/grub/menu.lst (if using grub) and look for vga=XXX where XXX is a number, change it to vga=normal or delete vga altogether. If vga isn't listed, look for "silent" or "verbose" and delete that to avoid using graphics during boot up.

(2) the video driver that xorg is using. In particular Nvidia drivers often cause that. The only way I have found to completely get rid of the blank screen problem is to not use the Nvidia drivers, but that means my TV-out functionality is gone

I just load the nvidia driver when I want to watch a movie and use "nv" the rest of the time.

loxodonta · 01-23-2007, 03:34 PM

Quote:

Originally Posted by m_yates

The problem you are experiencing is most likely due to:

(1) the kernel framebuffer video driver. Do you have bootsplash, usplash, splashy, etc for a graphical boot process? If so, you may need to disable it. Look in /boot/grub/menu.lst (if using grub) and look for vga=XXX where XXX is a number, change it to vga=normal or delete vga altogether. If vga isn't listed, look for "silent" or "verbose" and delete that to avoid using graphics during boot up.

(2) the video driver that xorg is using. In particular Nvidia drivers often cause that. The only way I have found to completely get rid of the blank screen problem is to not use the Nvidia drivers, but that means my TV-out functionality is gone

I just load the nvidia driver when I want to watch a movie and use "nv" the rest of the time.

I was experiencing the same problem on a Dell Inspiron 5150 with an Nvidia graphics card, running Ubuntu 6.06 (Dapper) with Grub. What I needed to do was replace the line

Code:

  # defoptions=quiet splash

to

Code:

  # defoptions=""

and run update-grub.
(N.B. simply '# defoptions=' didn't work, it was replaced by the old one.)

Thank you, now it's working!

bfg1971 · 01-30-2007, 09:12 AM

@loxodonta - Thanks for that tip. I am using Ubuntu 6.1 in a Virtual PC and was having the same issues with blank terminals (ctrl + alt + Fn). I used your suggestion about editing /boot/grub/menu.lst and then changing "# defoptions=quiet splash" to "# defoptions=""" and it worked great for me!!

Since I'm new at linux, could you tell me what I actually did?

pr0t0s · 05-23-2011, 01:34 AM

As pointed out in a previous post, this can be as a result of 1)boot splash screen messing up the framebuffer OR 2) nvidia/ati driver issues.

Luckily in my case it turned out to be (1).

However editing grub turned out to be more an ordeal than I imagined. Interestingly there are significant methodology changes in grub2 (which Ubuntu 9.04+ uses by default) vs grub. The easy way to figure out which grub version you have is to check for existence of the menu.lst file in /boot/grub

No menu.lst implies grub2, which will then require more work (not too much though). If you have menu.lst you are using grub v1.x and you can easily remove the vga line or turn it to vga=normal

For grub2 users, the following steps are required:
1. Edit the /etc/default/grub file and change the vga value to vga=normal
2. run sudo update-grub - this will generate/re-gen your grun.cfg file
3. Check the grub.cfg file (under /boot/grub) to ensure that the vga setting is set to nromal

You may need to edit the grub.cfg again to the right value if it ends up appending noslpash to it. This means that you will need to edit it after every kernel launch. But that is okay, now you atleast know how to fix it.

This link may help too http://norootsquash.wordpress.com/20...r-ubuntu-10-2/

acampbell · 10-22-2011, 04:33 AM

Many thanks for posting this. I'm using Debian Sid and I've struggled with it on my Thinkad Z61M for ages. Working fine now

shikha.punyani@gmail.com · 11-20-2011, 09:45 AM

Hello All,
I have seen the issue you guys were discussing below.
I just bought dell Inspiron laptop i3 processor, 500GB hard drive and 4 GB ram.
I have installed vmware on my lappy and then Linux RHEL6.
with ctrl+alt+F1, my computer hangs and do weiered things.
As per your discussion in below frum, I checked the file:
/etc/grub.conf/menu.list and I cant see any entry with vga or silent or verbose.
However I can see one entry which is
splash image=(hd0,0)/grub/splash.xpm.gz
Do I need to change here? If yes what do I need enter here?
I cant see my new lappy getting hung because of this . Please help asap..

pcardout · 02-03-2012, 04:13 PM

I used the advice of pr0to0s above to solve my problem, but it was a bit more involved
so I wanted to add to the pool of good advice on this relatively common problem.

There is general agreement on the net that

1) The problem may be that mingetty or getty are not configured properly in inittab.
2) The problem is most likely a video problem that can often be solved by changing the grub configuration.
3) Nvidia drivers are implicated.

I have a shiny new system with a hot nvidia card and I did not want to go disable the drivers (solution 3).
My experience is it was not necessary ... and I would say in general that it should not be
necessary. Fundamentally, grub is trying to use video modes that don't work. The solution
is not to fix the video modes, but rather to make grub behave in a more basic fashion (it's a ruddy boot loader ... let's
not go overboard with the graphics!).

OK here's what worked and did not work for me.

1) I first discovered that Ubuntu does not use /etc/inittab ... so workaround suggesting modifications thereof are unhelpful.
2) (1) is not a problem if it turns out that getty is running. I did a top and saw that getty was running.
3) To be really sure getty was running, I typed ctrl-alt-f1 and assumed that I was at a login screen even though screen was blank.
I logged in as root (on Ubuntu I always enable root) and typed reboot. It worked. That meant that I did have a functioning
terminal, I just could not see it!
4) I tried to modify /etc/default/grub looking to delete "quiet splash" as has been suggested several places.
There is nothing like that in the file. There was nothing to change. I made no changes.
5) I modified /boot/grub/grub.cfg as follows:

Code:

menuentry 'Ubuntu, with Linux 3.0.0-15-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	set gfxpayload=$linux_gfx_mode
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='(hd0,msdos1)'
	search --no-floppy --fs-uuid --set=root 244649d8-08c4-426c-a8ae-074abab1d239
#	linux	/boot/vmlinuz-3.0.0-15-generic-pae root=UUID=244649d8-08c4-426c-a8ae-074abab1d239 ro quiet splash  vt.handoff=7
	linux	/boot/vmlinuz-3.0.0-15-generic-pae root=UUID=244649d8-08c4-426c-a8ae-074abab1d239 ro nomodeset
	initrd	/boot/initrd.img-3.0.0-15-generic-pae
}

Note that I commented out the line with quiet splash vt.handoff=7 and replaced it with nomodeset.
I only made the change to one of my boot entries, on the theory that if I messed up I could boot with some other entry.
I got the nomodeset idea by looking at some of my recovery entries. I figured that the recovery stuff would
be the most stripped down. It seemed to have worked. I know have Oneiric Ocelot running with standard nvidia graphics
and Ctrl-Alt-F1 -- Ctrl-Alt-F6 all open terminals as they should.

AFTERNOTE: As noted by impert below, changes to grub.cfg are volatile and will be wiped next time update-grub is run
(as happens when you upgrade your kernel).
I could not figure out how to modify /etc/default/grub to accomplish this task, but using imperts advice I figured it out and
note it two posts further on.