FedoraThis forum is for the discussion of the Fedora Project.
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.
Hi. I'm using Fedora core 6 with NVIDIA-Linux-x86-1.0-8776-pkg1 driver.
Everytime my system boots with /etc/inittab set to "run level 5" the GUI login displays quickly and then just as quickly returns me to a console login. I know that X hasn't crashed, because i hit Ctrl + Alt + f7 and I have my regular login. Of course, I can't restart X from virtual console 1 as it is already running.
Has anybody had this problem? It only happens on occasion. What am I supposed to do?
Just to clarify, your login window displays, then before you can even log in it kicks you over to vc1? Can you log in on vc7 after you switch back over to it? Have you tried quitting X on vc7 then restarting it with startx? Which display manager are you using?(gdm/kdm,etc...) Can you boot to level 3 and startx?
Just to clarify, your login window displays, then before you can even log in it kicks you over to vc1?
Yes, that's exactly what happens.
Quote:
Originally Posted by cheftec
Can you log in on vc7 after you switch back over to it?
Yes. However, it is kind of annoying to have to do that everytime as I am not somebody who leaves my computer on for all hours.
Quote:
Originally Posted by cheftec
Have you tried quitting X on vc7 then restarting it with startx? Which display manager are you using?(gdm/kdm,etc...) Can you boot to level 3 and startx?
Yes, I've tried that and it's kdm. This didn't used to happen but for a while I was using run level 3, then went back to run level 5 and it started.
I checked /var/log/messages and I didn't notice anything out of the ordinary.
Try looking at /var/log/Xorg.0.log for any X-server error messages. (tail /var/log/Xorg.0.log should suffice.)
Do you have something running in /etc/rc.local that might cause the problem? Or in .kde/autostart?
Once you log on to tty7, try a start -- :1 (as a normal user) to start a new X-session on tty8. If that works, switch back to tty7 to see if any interesting errors are displayed. If it doesn't work, you should be bounced back to tty7 where, hopefully, you'll find a message telling you why you were bounced back.
Last edited by PTrenholme; 01-31-2009 at 07:28 PM.
There are no errors in xorg.conf. here's what's at the end:
Quote:
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(WW) <default pointer>: No Device specified, looking for one...
(II) <default pointer>: Setting Device option to "/dev/input/mice"
(--) <default pointer>: Device: "/dev/input/mice"
(==) <default pointer>: Protocol: "Auto"
(**) Option "CorePointer"
(**) <default pointer>: Core Pointer
(==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
(**) <default pointer>: ZAxisMapping: buttons 4 and 5
(**) <default pointer>: Buttons: 9
(II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(--) <default pointer>: PnP-detected protocol: "ExplorerPS/2"
(II) <default pointer>: ps2EnableDataReporting: succeeded
(II) Open ACPI successful (/var/run/acpid.socket)
(II) NVIDIA(0): Setting mode "1024x768"
(II) <default pointer>: ps2EnableDataReporting: succeeded
I don't have a "start" command but I can "Start New session" from KDE and it seems to work OK.
there's nothing in kde auto start and here's what's in rc.local:
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.
touch /var/lock/subsys/local
Basically, it briefly shows the login screen, the system bell rings, and I'm at VC1.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.