Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm running Debian Wheezy and I don't know why, but when I switch to console F1 (Ctrl+Alt+f1) I can't enter login information. It's like Debian didn't have completely starting and wait always.
I don't know how to explain it but F1 is like your primary console. When a window manager is running on F7, it is run from your console. If you logout to console you'll probably find that F1 is free to use. Then if you change to F2 and startx, F2 will then be running that window manager on F7. I say that F1 is your primary because if you automatically enter run level 5 it is run from console 1 (F1).
When a window manager is running on F7, it is run from your console. If you logout to console you'll probably find that F1 is free to use. Then if you change to F2 and startx, F2 will then be running that window manager on F7. I say that F1 is your primary because if you automatically enter run level 5 it is run from console 1 (F1).
Sorry, but Wheezy is currently in development. The only thing I can tell you is file a bug report.
The current stable version is Debian "Squeeze".
Yes I know, but Wheezy is as stable as Ubuntu... And on my laptop or my Debian server, I haven't this problem.
Quote:
Originally Posted by themanwhowas
I don't know how to explain it but F1 is like your primary console. When a window manager is running on F7, it is run from your console. If you logout to console you'll probably find that F1 is free to use. Then if you change to F2 and startx, F2 will then be running that window manager on F7. I say that F1 is your primary because if you automatically enter run level 5 it is run from console 1 (F1).
Make sense?
I'm not an expert, but on my laptop or on my Debian server or on my Debian PC (before I notice this problem), I could always been able to login into console F1, F2,... even if a window manager is running. I don't think that F1 and F7 are linked.
The last line in F1 console on my Debian PC is the winbind service. On my laptop or server, the last line in F1 console before the login prompt is the winbind service too.
Maybe the winbind service don't start completely and wait for something?
I don't know how to explain it but F1 is like your primary console. When a window manager is running on F7, it is run from your console. If you logout to console you'll probably find that F1 is free to use. Then if you change to F2 and startx, F2 will then be running that window manager on F7. I say that F1 is your primary because if you automatically enter run level 5 it is run from console 1 (F1).
Make sense?
I have used Debian quite some time, and were always able to login on any virtual console from 1 to 6. On a normal system boot to runlevel 2 (in Debian runlevels 2 to 5 are the same in a standard install) the X-server is not started with startx, but from the display-manager of your choice (GDM in a standard install). GDM is started from your init-system in the background and therefore doesn't block a virtual console.
@gagou7: Please post the content of the file /etc/inittab (for better readability please use code-tags).
# /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
Now e know that your system is correctly configured to boot to runlevel 2 and start login managers (getty) on all virtual consoles from 1 to 6. Since it doesn't do this I would assume that it is not correctly booting to that runlevel and hangs somewhere.
Maybe we can see something in the log files /var/log/messages and /var/log/syslog.
I watched /var/log/messages and /var/log/syslog but I didn't see any errors. I removed Winbind (sudo apt-get remove winbind) and user/password are correctly prompted in F1-F6 console. So, the problem is Winbind... I try to reinstall it, but the problem come back. Try a "dpkg-reconfigure" but nothing changed.
Very strange because my Debian laptop has winbind too and yet it has no problem...
The winbind log:
Code:
[2011/04/19 09:42:43, 0] winbindd/winbindd.c:1105(main)
winbindd version 3.5.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/04/20 22:18:12, 0] winbindd/winbindd.c:1105(main)
winbindd version 3.5.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/04/21 09:27:40, 0] winbindd/winbindd.c:1105(main)
winbindd version 3.5.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/04/21 20:25:21, 0] winbindd/winbindd.c:1105(main)
winbindd version 3.5.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/04/21 20:28:11, 0] winbindd/winbindd.c:1105(main)
winbindd version 3.5.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/04/21 20:36:17, 0] winbindd/winbindd.c:1105(main)
winbindd version 3.5.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/04/21 23:39:39, 0] winbindd/winbindd.c:1105(main)
winbindd version 3.5.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/04/22 18:39:03, 0] winbindd/winbindd.c:1105(main)
winbindd version 3.5.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/04/23 09:24:12, 0] winbindd/winbindd.c:1105(main)
winbindd version 3.5.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/04/23 09:33:04, 0] winbindd/winbindd.c:1105(main)
winbindd version 3.5.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
Yes, that is very strange. Even when I tried experimenting with Samba and NFS (which my router doesn't like), having winbind installed did not produce a problem for me. However, I recently noticed a strange phenomenon on my netbook (which runs Arch). This may seem unrelated, but keep reading. Whenever I plug in a USB device and try to boot the machine, it appears to hang upon detection of the device, but when I enter my password(I use dm_crypt), it unlocks and mounts the partition correctly and then continues to boot. What I am suggesting is that the login prompt could somehow be hidden, like the password prompt on my netbook gets hidden. I know it's a shot in the dark, but try logging into one of those consoles as if the prompt was visible.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.