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!
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.
Since a couple of weeks or so, I just can't get to the console by holding Ctrl + Alt + Fx no more... I could do it, but now it doesn't work... It just does nothing... From the login screen (in X) pressing Ctrl + Alt + Fx takes me to the console, but as soon as I log in (with any of the existing users, or as root), this sequence of keys does just nothing, so I suppose that I or some program I installed have changed something in the configuration of the X session, but I don't know what... Does anybody now how to get this working back again?
When it started to be like that? What did you do in this period of time. Any particular things like editing conf files, install program, or upgrade kernel? What run level do you use for default logon? Try editing init.conf and change run level to 3. Just try anything you can think of.
I said "Ctrl + Alt + F1" to give an example... none of them works.. (F2, F3, F4...).
I think it happened since I tried to activate num Lock by default at startup... (I copied a script from a page that used "setleds +num (....)" but it didn't work for X, since as soon as X started, Num Lock was turned off again. Since it was some weeks ago, and I was looking how to do it in many places at the same time, I don't know if I installed a program (as numlockx) or changed some conf file... I've tried "rpm -qa | grep numlock" but none of my packages has "numlock" in its name (I've even tried "rpm -qa > rpms.txt", and then opening that with gedit and searching for "numlock"), and if I modified a conf file, I didn't keep a record of that, so I don't know which one it was, and what changes did I make (though I don't remember changing conf files...)
I boot up by default in runlevel 5. Another thing I don't understand and that maybe it's connected somehow with my problem, is that if I switch to runlevel 3 ("/sbin/telinit 3"), and then I log in and from the console I type "startx", it seems as if the X-Windows were starting (i even see the cursor as an X for an instant) and then I get back to the console and I get something like:
/home/kn0t/.Xclients: line 8: /home/kn0t/.Xclients-default: No such file or directory
/home/kn0t/.Xclients: line 8: exec: /home/kn0t/.Xclients-default: cannot execute: No such file or directory
And I DO remember that "before" (when Ctrl +Alt + Fx worked), I could do it that way, or even, having the X in the F7 terminal, open a new X-Windows from the console in other terminal (either by typing all the parameters, or by using a program called "x" that calls those parameters automatically depending on how many X you have already open)
# Trap CTRL-ALT-DELETE
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# 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
# Run xdm in runlevel 5
hmmmmm, your inittab looks all right. My guess is that the thing you tried to do with num-lock somehow disabled the key-combination ctrl-alt-Fn. You should find out first what you did and see if you can reverse it.
As for the startx from runlevel 3, I'm not sure what ~/.Xclients is for but I don't think it's needed. You could temporily rename it and see if you can then startx.
for users, the X related ones are the the one named .xsomething in the home directory. There are also global ones in /etc/X11. Then there are .bashrc and .bash_profile in the home directory and their global counterparts in /etc. And then there are the init scripts.
If you can use CTRL-ALT-Fn in run level 3 (have you checked? you should get 6 different login screens), then the problem is most likely with the X config files.
Yes, I've checked... It works in runlevel 3, and also in runlevel 5, from the (X) login screen. (That's were you can change the language for the next session, shutdown the computer, and so). From there, Ctrl-Alt-Fn works for the six different login screens (console). But when I log in an X-session (that's, when I introduce my user and pass) from that moment, Ctrl-Alt-Fn doesn't work... in fact, if I press them with a terminal window open, i get this:
[kn0t@localhost kn0t]$ ;7~
The NumLock led is off, but I can use the numpad and I get numbers... and if I press the num Lock button, the led doesn't turn on... I always have numbers there, and the period doesn't work... (the period in the numpad).... that's why I think it has something to do with the config files... I'll look for something "unusual", but the problem is that I might not find something "unsual" even though it is, so if someone has any ideas on what to look for...
you could try getting rid of all the files/directory in your home directory that start with an .x or .X; all of these are hidden files (except, ones you know are for programs like xine an xmms) - or just move them somewhere else. X should recreate the files with the default settings if it does not find them.
In my home dir I don't have any files/directories that start with .x or .X, except xmms, xemacs, xscorch (a game) and xscreensaver... So I must have changed the system-wide conf files, and I don't know what their names are, so I can't just go and delete them (well... move them, better, just in case), and I don't think It'll be a good idea to move away ANYTHING that starts with x or X under /etc/X11... or should I? I
I could post here a copy of my /etc/X11 tree, if that helps, but until you say it could be helpful, I don't think it's a good idea to fill this thread with "ls"'s... ;-)
I didn't think that would work, and it didn't It happens to the three users I have in the machine (also root), so I think it must be one of the system-wide config files, but I've looked through them and haven't found anything (it's possible though, that the problem has been under my nose and I haven't seen it, since I don't know much about lots of those config files...)