| View previous topic :: View next topic |
| Author |
Message |
dman777
Veteran
Joined: 10 Jan 2007
Posts: 1004
|
 Posted: Sat Jul 17, 2010 10:24 am Post subject: Problems with Console/Linux Terminal/tty |
 |
|
I have two problems with my console:
1) I only have tty1 available. If I ctrl-alt to other tty's I don't have any login prompts.
2) in tty1 my ascii control characters are taken literally. This means I can not ctrl-c, escape, etc. For instance, if I am reading a man page I can not q for quit or ctrl-c out of it.
Here is my /etc/inittab:
| Code: | root@localhost /home/three # cat /etc/inittab
#
# /etc/inittab: This file describes how the INIT process should set up
# the system in a certain run-level.
#
# Author: Miquel van Smoorenburg, <miquels@cistron.nl>
# Modified by: Patrick J. Volkerding, <volkerdi@ftp.cdrom.com>
# Modified by: Daniel Robbins, <drobbins@gentoo.org>
# Modified by: Martin Schlemmer, <azarah@gentoo.org>
# Modified by: Mike Frysinger, <vapier@gentoo.org>
# Modified by: Robin H. Johnson, <robbat2@gentoo.org>
#
# $Header: /var/cvsroot/gentoo-x86/sys-apps/sysvinit/files/inittab-2.87,v 1.1 2010/01/08 16:55:07 williamh Exp $
# Default runlevel.
id:3:initdefault:
# System initialization, mount local filesystems, etc.
si::sysinit:/sbin/rc sysinit
# Further system initialization, brings up the boot runlevel.
rc::bootwait:/sbin/rc boot
l0:0:wait:/sbin/rc shutdown
l0s:0:wait:/sbin/halt -dhp
l1:1:wait:/sbin/rc single
l2:2:wait:/sbin/rc nonetwork
l3:3:wait:/sbin/rc default
l4:4:wait:/sbin/rc default
l5:5:wait:/sbin/rc default
l6:6:wait:/sbin/rc reboot
l6r:6:wait:/sbin/reboot -dk
#z6:6:respawn:/sbin/sulogin
# new-style single-user
su0:S:wait:/sbin/rc single
su1:S:wait:/sbin/sulogin
# TERMINALS
c1:12345:respawn:/sbin/agetty 38400 tty1 linux
c2:2345:respawn:/sbin/agetty 38400 tty2 linux
c3:2345:respawn:/sbin/agetty 38400 tty3 linux
c4:2345:respawn:/sbin/agetty 38400 tty4 linux
c5:2345:respawn:/sbin/agetty 38400 tty5 linux
c6:2345:respawn:/sbin/agetty 38400 tty6 linux
# SERIAL CONSOLES
#s0:12345:respawn:/sbin/agetty 9600 ttyS0 vt100
#s1:12345:respawn:/sbin/agetty 9600 ttyS1 vt100
# What to do at the "Three Finger Salute".
ca:12345:ctrlaltdel:/sbin/shutdown -r now
# Used by /etc/init.d/xdm to control DM startup.
# Read the comments in /etc/init.d/xdm for more
# info. Do NOT remove, as this will start nothing
# extra at boot if /etc/init.d/xdm is not added
# to the "default" runlevel.
|
Here is my rc-update:
| Code: |
root@localhost /home/three # rc-update
udev-postmount | default
bootmisc | boot
hwclock | boot
modules | boot
hostname | boot
mtab | boot
procfs | boot
local | default nonetwork
killprocs | shutdown
mount-ro | shutdown
hald | default
localmount | boot
rsyslog | default
alsasound | boot
udev | sysinit
anacron | default
swap | boot
sysctl | boot
savecache | shutdown
dmesg | sysinit
device-mapper | boot
devfs | sysinit
keymaps | boot
termencoding | boot
netmount | default
urandom | boot
consolefont | boot
root | boot
vixie-cron | default
fsck | boot
root@localhost /home/three # |
Here is my /etc/rc.conf:
| Code: | root@localhost /home/three # cat /etc/rc.conf
# Global OpenRC configuration settings
# Set to "YES" if you want the rc system to try and start services
# in parallel for a slight speed improvement. When running in parallel we
# prefix the service output with its name as the output will get
# jumbled up.
# WARNING: whilst we have improved parallel, it can still potentially lock
# the boot process. Don't file bugs about this unless you can supply
# patches that fix it without breaking other things!
#rc_parallel="NO"
# Set rc_interactive to "YES" and you'll be able to press the I key during
# boot so you can choose to start specific services. Set to "NO" to disable
# this feature.
#rc_interactive="YES"
# If we need to drop to a shell, you can specify it here.
# If not specified we use $SHELL, otherwise the one specified in /etc/passwd,
# otherwise /bin/sh
# Linux users could specify /sbin/sulogin
rc_shell=/sbin/sulogin
# Do we allow any started service in the runlevel to satisfy the depedency
# or do we want all of them regardless of state? For example, if net.eth0
# and net.eth1 are in the default runlevel then with rc_depend_strict="NO"
# both will be started, but services that depend on 'net' will work if either
# one comes up. With rc_depend_strict="YES" we would require them both to
# come up.
#rc_depend_strict="YES"
# rc_hotplug is a list of services that we allow to be hotplugged.
# By default we do not allow hotplugging.
# A hotplugged service is one started by a dynamic dev manager when a matching
# hardware device is found.
# This service is intrinsically included in the boot runlevel.
# To disable services, prefix with a !
# Example - rc_hotplug="net.wlan !net.*"
# This allows net.wlan and any service not matching net.* to be plugged.
# Example - rc_hotplug="*"
# This allows all services to be hotplugged
rc_hotplug="net.wlan !net.*"
# rc_logger launches a logging daemon to log the entire rc process to
# /var/log/rc.log
# NOTE: Linux systems require the devfs service to be started before
# logging can take place and as such cannot log the sysinit runlevel.
rc_logger="YES"
# By default we filter the environment for our running scripts. To allow other
# variables through, add them here. Use a * to allow all variables through.
#rc_env_allow="VAR1 VAR2"
# By default we assume that all daemons will start correctly.
# However, some do not - a classic example is that they fork and return 0 AND
# then child barfs on a configuration error. Or the daemon has a bug and the
# child crashes. You can set the number of milliseconds start-stop-daemon
# waits to check that the daemon is still running after starting here.
# The default is 0 - no checking.
#rc_start_wait=100
# rc_nostop is a list of services which will not stop when changing runlevels.
# This still allows the service itself to be stopped when called directly.
#rc_nostop=""
# rc will attempt to start crashed services by default.
# However, it will not stop them by default as that could bring down other
# critical services.
#rc_crashed_stop=NO
#rc_crashed_start=YES
##############################################################################
# MISC CONFIGURATION VARIABLES
# There variables are shared between many init scripts
# Set unicode to YES to turn on unicode support for keyboards and screens.
unicode="YES"
# Network fstypes. Below is the default.
net_fs_list="afs cifs coda davfs fuse fuse.sshfs gfs glusterfs lustre ncpfs nfs nfs4 ocfs2 shfs smbfs"
##############################################################################
# SERVICE CONFIGURATION VARIABLES
# These variables are documented here, but should be configured in
# /etc/conf.d/foo for service foo and NOT enabled here unless you
# really want them to work on a global basis.
# Some daemons are started and stopped via start-stop-daemon.
# We can set some things on a per service basis, like the nicelevel.
#export SSD_NICELEVEL="-19"
# Pass ulimit parameters
#rc_ulimit="-u 30"
# It's possible to define extra dependencies for services like so
#rc_config="/etc/foo"
#rc_need="openvpn"
#rc_use="net.eth0"
#rc_after="clock"
#rc_before="local"
#rc_provide="!net"
# You can also enable the above commands here for each service. Below is an
# example for service foo.
#rc_foo_config="/etc/foo"
#rc_foo_need="openvpn"
#rc_foo_after="clock"
# You can also remove dependencies.
# This is mainly used for saying which servies do NOT provide net.
#rc_net_tap0_provide="!net"
##############################################################################
# LINUX SPECIFIC OPTIONS
# This is the number of tty's used in most of the rc-scripts (like
# consolefont, numlock, etc ...)
rc_tty_number=12
RC_VERBOSE="YES"
root@localhost /home/three # |
|
|
| Back to top |
|
 |
thegeezer
n00b
Joined: 11 Jul 2010
Posts: 38
|
| Posted: Thu Jul 22, 2010 10:55 pm Post subject: curious |
|
|
| what does show? |
|
| Back to top |
|
|
Jacekalex
Guru
Joined: 17 Sep 2009
Posts: 553
|
| Posted: Wed Aug 18, 2010 2:26 pm Post subject: |
|
|
Hi
At least two days I have a strange symptom in the system: I can not log in the console, there is no question of the normal login and password, as if fired init failed consoles.
It is so strange that I did not do any crazy updates, and everything worked before.
I noticed the case - when compiling the kernel, when I wanted to install the nvidia helm.
Before you turn off the computer - after the changes in grub, I forgot to throw xorg.conf.
After starting on a new kernel, xorg nvidia not found the rudder, and gdm
error.
I think no problem, I want to sign - I think - turn off xdm, install the driver for the card and the shouting.
And here the question is not logged.
Symptom occurs both on 2.6.35 kernel without any patches, as well as on 2.6.34 with the Zen and IMQ patches.
kernels - "vanilla-sources ", without grsecurity or PAX.
And I have the impression that the kernel does not have this much in common except during take-off displays everything correctly, I can write to the console, console mouse works (gpm), but can not login.
After running - logged by gdm, gnome-terminal it normally, so a problem with the bash shell is also not the case.
| Code: | ~ $ sudo -i
(System) localhost ~ # ls /dev/tty* -alh
crw-rw-rw- 1 root tty 5, 0 08-18 11:02 /dev/tty
crw--w---- 1 root root 4, 0 08-18 11:02 /dev/tty0
crw------- 1 duch tty 4, 1 08-18 16:15 /dev/tty1
crw--w---- 1 root tty 4, 10 08-18 11:02 /dev/tty10
crw--w---- 1 root tty 4, 11 08-18 11:02 /dev/tty11
crw--w---- 1 root tty 4, 12 08-18 11:02 /dev/tty12
crw--w---- 1 root tty 4, 13 08-18 11:02 /dev/tty13
crw--w---- 1 root tty 4, 14 08-18 11:02 /dev/tty14
crw--w---- 1 root tty 4, 15 08-18 11:02 /dev/tty15
crw--w---- 1 root tty 4, 16 08-18 11:02 /dev/tty16
crw--w---- 1 root tty 4, 17 08-18 11:02 /dev/tty17
crw--w---- 1 root tty 4, 18 08-18 11:02 /dev/tty18
crw--w---- 1 root tty 4, 19 08-18 11:02 /dev/tty19
crw------- 1 root root 4, 2 08-18 16:15 /dev/tty2
crw--w---- 1 root tty 4, 20 08-18 11:02 /dev/tty20
crw--w---- 1 root tty 4, 21 08-18 11:02 /dev/tty21
crw--w---- 1 root tty 4, 22 08-18 11:02 /dev/tty22
crw--w---- 1 root tty 4, 23 08-18 11:02 /dev/tty23
crw--w---- 1 root tty 4, 24 08-18 11:02 /dev/tty24
crw--w---- 1 root tty 4, 25 08-18 11:02 /dev/tty25
crw--w---- 1 root tty 4, 26 08-18 11:02 /dev/tty26
crw--w---- 1 root tty 4, 27 08-18 11:02 /dev/tty27
crw--w---- 1 root tty 4, 28 08-18 11:02 /dev/tty28
crw--w---- 1 root tty 4, 29 08-18 11:02 /dev/tty29
crw------- 1 duch tty 4, 3 08-18 16:15 /dev/tty3
crw--w---- 1 root tty 4, 30 08-18 11:02 /dev/tty30
crw--w---- 1 root tty 4, 31 08-18 11:02 /dev/tty31
crw--w---- 1 root tty 4, 32 08-18 11:02 /dev/tty32
crw--w---- 1 root tty 4, 33 08-18 11:02 /dev/tty33
crw--w---- 1 root tty 4, 34 08-18 11:02 /dev/tty34
crw--w---- 1 root tty 4, 35 08-18 11:02 /dev/tty35
crw--w---- 1 root tty 4, 36 08-18 11:02 /dev/tty36
crw--w---- 1 root tty 4, 37 08-18 11:02 /dev/tty37
crw--w---- 1 root tty 4, 38 08-18 11:02 /dev/tty38
crw--w---- 1 root tty 4, 39 08-18 11:02 /dev/tty39
crw------- 1 root root 4, 4 08-18 16:15 /dev/tty4
crw--w---- 1 root tty 4, 40 08-18 11:02 /dev/tty40
crw--w---- 1 root tty 4, 41 08-18 11:02 /dev/tty41
crw--w---- 1 root tty 4, 42 08-18 11:02 /dev/tty42
crw--w---- 1 root tty 4, 43 08-18 11:02 /dev/tty43
crw--w---- 1 root tty 4, 44 08-18 11:02 /dev/tty44
crw--w---- 1 root tty 4, 45 08-18 11:02 /dev/tty45
crw--w---- 1 root tty 4, 46 08-18 11:02 /dev/tty46
crw--w---- 1 root tty 4, 47 08-18 11:02 /dev/tty47
crw--w---- 1 root tty 4, 48 08-18 11:02 /dev/tty48
crw--w---- 1 root tty 4, 49 08-18 11:02 /dev/tty49
crw------- 1 root root 4, 5 08-18 16:15 /dev/tty5
crw--w---- 1 root tty 4, 50 08-18 11:02 /dev/tty50
crw--w---- 1 root tty 4, 51 08-18 11:02 /dev/tty51
crw--w---- 1 root tty 4, 52 08-18 11:02 /dev/tty52
crw--w---- 1 root tty 4, 53 08-18 11:02 /dev/tty53
crw--w---- 1 root tty 4, 54 08-18 11:02 /dev/tty54
crw--w---- 1 root tty 4, 55 08-18 11:02 /dev/tty55
crw--w---- 1 root tty 4, 56 08-18 11:02 /dev/tty56
crw--w---- 1 root tty 4, 57 08-18 11:02 /dev/tty57
crw--w---- 1 root tty 4, 58 08-18 11:02 /dev/tty58
crw--w---- 1 root tty 4, 59 08-18 11:02 /dev/tty59
crw------- 1 root root 4, 6 08-18 16:15 /dev/tty6
crw--w---- 1 root tty 4, 60 08-18 11:02 /dev/tty60
crw--w---- 1 root tty 4, 61 08-18 11:02 /dev/tty61
crw--w---- 1 root tty 4, 62 08-18 11:02 /dev/tty62
crw--w---- 1 root tty 4, 63 08-18 11:02 /dev/tty63
crw--w---- 1 root tty 4, 7 08-18 11:02 /dev/tty7
crw--w---- 1 root root 4, 8 08-18 11:02 /dev/tty8
crw--w---- 1 root tty 4, 9 08-18 11:02 /dev/tty9
crw-rw---- 1 root uucp 4, 64 08-18 11:02 /dev/ttyS0
crw-rw---- 1 root uucp 4, 65 08-18 11:02 /dev/ttyS1
crw-rw---- 1 root uucp 4, 66 08-18 11:02 /dev/ttyS2
crw-rw---- 1 root uucp 4, 67 08-18 11:02 /dev/ttyS3 |
My emerge --info: http://wklej.org/id/378336/
Original post: https://forums.gentoo.org/viewtopic-t-840674-highlight-.html
Some idea 
EDIT:
I was able to restore the console login
as follows
| Code: | ~ # killall -9 console-kit-daemon
~ # / etc / init.d / hald start
* Starting ConsoleKit daemon ... [Ok]
* Starting Hardware Abstraction Layer daemon ... [Ok] |
But I still do not know - how to automatically stood up on boot.
But the solution is not far.
Yours
-----------------------------------------------------------
My native language - is Polish, sorry for bad English. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
