Announcement

Collapse
No announcement yet.

no access to virtual consoles

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    no access to virtual consoles

    When I try to get to my virtual consoles (i.e., ctrl+alt+F1), instead of the terminal, I get a screen with some sort of pattern on it. Let me know what kind of info I can provide to further debug
    Tags: None
    • Top
    • Bottom
    #2
    Re: no access to virtual consoles

    1) What does the pattern look like? Is it a ghost of some previous screen?
    2) Is your system working properly in the GUI?
    3) What happens if you try to start a console login from the KDM menu at login time?
    4) Are all the consoles started in /etc/inittab?
    • Top
    • Bottom

    Comment

      #3
      Re: no access to virtual consoles

      First, thanks for your response.  See below for my responses:

      1) What does the pattern look like? Is it a ghost of some previous screen?

      It is not a ghost of some previous screen.  It is a white background with a small pattern that is repeated.  Can't do much better than that. The pattern changes on every boot, though.

      2) Is your system working properly in the GUI?

      Yes.

      3) What happens if you try to start a console login from the KDM menu at login time?

      I actually use GDM, and it doesn't have an option for a console login.

      4) Are all the consoles started in /etc/inittab?

      I believe so.  The contents of inittab:

      Code:
      # /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:2:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.
~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin

# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now

# Action on special keypress (ALT-UpArrow).
#kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."

# What to do when the power fails/returns.
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop

# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
#  <id>:<runlevels>:<action>:<process>
#
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6

# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100

# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
      • Top
      • Bottom

      Comment

        #4
        Re: no access to virtual consoles

        (1) seems to imply that your monitor is losing sync when it goes into console mode. Normally, (or abnormally) that would happen in the GUI and would be caused by a badly composed xorg.conf file, but I don't understand how or why you can be losing sync in a console. (2) implies that your xorg.conf is, in fact, properly configured for your hardware. (3) would have told me whether this problem occurred no matter how you got into the console. (4) I can't see anything wrong with your inittab. Offhand, I can't think of a cause for this behavior.
        • Top
        • Bottom

        Comment

          #5
          Re: no access to virtual consoles

          The one thing I can think of is that the virtual consoles are not just simple virtual consoles but have some sort of framebuffer or something that lets you put a nice background or lets you use your mouse.
          • Top
          • Bottom

          Comment

            #6
            Re: no access to virtual consoles

            Your not using nvidia drivers are you?
            • Top
            • Bottom

            Comment

              #7
              Re: no access to virtual consoles

              I am not using the nvidia driver. In my xorg.conf, I am using the via driver:

              Code:
              Section "Device"
	Identifier	"VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video"
	Driver		"via"
	BusID		"PCI:1:0:0"
EndSection
              • Top
              • Bottom

              Comment

                #8
                Re: no access to virtual consoles

                As far as I know they are just ordinary consoles, i.e. no background, no mouse, just 25 lines x 80 chars.
                • Top
                • Bottom

                Comment

                Previous template Next
                Working...
                X