SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The problem:
Virtual terminals will not work at all when in X. Virtual terminals DO work while at the init 3 login prompt but NOT in init 4 login
What I've tried:
Editing /etc/inittab and changing:
# Default runlevel. (Do not set to 0 or 6)
id:3:initdefault:
to
# Default runlevel. (Do not set to 0 or 6)
id:4:initdefault:
and
# These are the standard console login getties in multiuser mode:
c1:1235:respawn:/sbin/agetty 38400 tty1 linux
c2:1235:respawn:/sbin/agetty 38400 tty2 linux
c3:1235:respawn:/sbin/agetty 38400 tty3 linux
c4:1235:respawn:/sbin/agetty 38400 tty4 linux
c5:1235:respawn:/sbin/agetty 38400 tty5 linux
c6:12345:respawn:/sbin/agetty 38400 tty6 linux
to
# These are the standard console login getties in multiuser mode:
c1:12345:respawn:/sbin/agetty 38400 tty1 linux
c2:12345:respawn:/sbin/agetty 38400 tty2 linux
c3:12345:respawn:/sbin/agetty 38400 tty3 linux
c4:12345:respawn:/sbin/agetty 38400 tty4 linux
c5:12345:respawn:/sbin/agetty 38400 tty5 linux
c6:12345:respawn:/sbin/agetty 38400 tty6 linux
Doing xorgconfig 2 different ways:
setting my keyboard as
3 Generic 104-key PC
and
64 Logitech Internet Navigator Keyboard
I am not sure why none of this works since Virtual Terminals worked in Mandrake 10.1, Knoppix 3.4, Slax 4.2 and BeatrIX 2005.1.
My system is Slackware 10.1, Full install, running the bareacpi kernel (2.4.29).
Thank you in advance for your help.
P.S. My window manager is XFCE 4.2.0 and my Nvidia driver is 7174
Originally posted by Kruncher The problem:
Virtual terminals will not work at all when in X. Virtual terminals DO work while at the init 3 login prompt but NOT in init 4 login
init 4 starts X straight to the GUI............kdm, gdm, xfce, etc.............
When I set the /etc/inittab default runlevel to 4 it will start up the gdm login manager, from there on virtual terminals do not work.
If I set the default runlevel to 3 the virtual terminals work untill I login AND run startx
When I set the /etc/inittab default runlevel to 4 it will start up the gdm login manager, from there on virtual terminals do not work.
What do you mean by "virtual terminals do not work" ? If you set in xorg.conf appropriate generic keyboard model, Ctrl+Alt+F7 key combination won't you bring to virt. terminal ? If you log in from gdm and start some X-terminal like xterm, gnome-terminal, konsole, aterm etc. and type
Code:
ps xa|grep agetty
do you recognize some instances of agetty login running ?
ps ax | grep agetty:
2611 tty1 Ss+ 0:00 /sbin/agetty 38400 tty1 linux
2612 tty2 Ss+ 0:00 /sbin/agetty 38400 tty2 linux
2613 tty3 Ss+ 0:00 /sbin/agetty 38400 tty3 linux
2614 tty4 Ss+ 0:00 /sbin/agetty 38400 tty4 linux
2615 tty5 Ss+ 0:00 /sbin/agetty 38400 tty5 linux
2616 tty6 Ss+ 0:00 /sbin/agetty 38400 tty6 linux
I mean when I hit Ctrl+Alt+F# in X my pc does nothing at all, it just stays on the current desktop, no flash of black, no console at all.
Normal consoles work fine (xterm, konsole, etc).
When the default runlevel is set at 3 Alt+F# works fine, I can switch to all my virtual consoles with no problem.
Originally posted by Kruncher ps ax | grep agetty:
2611 tty1 Ss+ 0:00 /sbin/agetty 38400 tty1 linux
2612 tty2 Ss+ 0:00 /sbin/agetty 38400 tty2 linux
2613 tty3 Ss+ 0:00 /sbin/agetty 38400 tty3 linux
2614 tty4 Ss+ 0:00 /sbin/agetty 38400 tty4 linux
2615 tty5 Ss+ 0:00 /sbin/agetty 38400 tty5 linux
2616 tty6 Ss+ 0:00 /sbin/agetty 38400 tty6 linux
Agettys are running, so problem is likely caused by wrong keyboard configuration for X window - like Alt key as Meta key mapping. Try to change /usr/X11R6/lib/X11/xorg.conf in section for input device - keyboard. The most basic setting would look like following
Section "InputDevice"
Identifier "Keyboard"
Driver "kbd"
Option "XkbModel" "pc104" # set to your real kbd layout
EndSection
Just for curiosity you can make sure programaticaly that logins are running by calling chvt utility from X-terminal.
Code:
chvt 6
should switch you to terminal on /dev/tty6. Depending on permission settings in device tree, it has to be likely run under root login.
I ran chvt 6 as root and it switched to tty6, so what does that mean?
I tried editing /usr/X11R6/lib/X11/xorg.conf but the file does not exist.
My xorg.conf is located at /etc/X11/xorg.conf and this is the part that I belive your talking about:
Code:
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
Option "XkbVariant" "us"
EndSection
Could this have anything to do with the part in xorgconfig where it asks you "Do you want to select additional XKB options (group switcher, group indicator, etc.)?" and I said No?
Please just set minimal config for keyboard as I wrote in my previous post, ie. comment out with hash ('#') XkbRules, XkbLayout and XkbVariant lines and restart X server (ctrl+alt+backspace). Then try to switch again to some running virtual terminal (ctr+alt+f6) and let me know if it did help.
It seems the problem was in XkbVariant option, because "us" variant, at least in xorg 6.8.2 official package, doesn't exist. Existing variants are "basic" and "intl" for example, but if you don't wish special behaviour, you need not to use this option.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
