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.
Hi guys, sorry could not introduce myslf, but I have this huge problem with my SUSE 10.2 distro. Everytime when i try login in console mode i'm always directed to the failsafe console mode not too sure why? Everything went wrong when I made Gnome my default desktop, but i changed back to KDE, and it still does the same thing(ie directing me to the failsafe console).
Any idea why it does that? And I would love to know how to fix it?
Distribution: Mandriva 2009 X86_64 suse 11.3 X86_64 Centos X86_64 Debian X86_64 Linux MInt 86_64 OS X
Posts: 2,369
Rep:
Welcome at LQ
First Suse come up mostly with two options starting GUI or Failsafe Try find out if you have really change it back to KDE 3
Second when you,re in the failsafe mode did the command Startx works or not ?
If not post again and we try to help you
While in failsafe edit /etc/inittab and
change the line:
id:5:initdefault: to [B][id:3:initdefault:/B]
As I recall from several years ago, Yast2 will
overwrite manual changes to configuration upon
shutdown, but if you run yast2 as root from the
console you should be able to find an option to
disable this overwrite, making your change stick.
I had a similar issue with a different distribution. I had to install via text mode because X would not work with a Nvidia 7300GT PCI express card. After installation I was able at least get the vesa driver to work with it, but nothing else. And for that, I had to kiss Debian stable goodbye when I got the new system and switched over to Slackware, installed the binary nvidia driver, not issues since then.
Try starting X using the vesa driver to start with? Might work.
Another thing that can lead to a failsafe console popping up is when the shared library and system directories such as /usr and /lib and /usr/lib have the wrong permissions. They should be readable by everyone (not writeable by everyone though) and I have seen on occasion (usually by my own carelessness) that after having installed an improperly permissioned package into /usr or /usr/lib the permissions of these directories have changed to RWX------ causing the regular user trying to log in to be unable to access the libraries needed to start the desktop environment. Then a failsafe console appears next time I try to log in.
Long story short: Check the permissions of your filesystem, particularly the above mentioned folders, as well as /home/user and /etc.
(I remember way back when I installed Gnome for Slackware; what a mess I had on my hands after I removed it.. I have been told that great improvements have since been made on that Gnome system for Slack, but I still won't try it again.)
Best of luck fixing the issue,
Sasha
Last edited by GrapefruiTgirl; 05-12-2008 at 10:52 PM.
Reason: typo
Another thing that can lead to a failsafe console popping up is when the shared library and system directories such as /usr and /lib and /usr/lib have the wrong permissions. They should be readable by everyone (not writeable by everyone though) and I have seen on occasion (usually by my own carelessness) that after having installed an improperly permissioned package into /usr or /usr/lib the permissions of these directories have changed to RWX------ causing the regular user trying to log in to be unable to access the libraries needed to start the desktop environment. Then a failsafe console appears next time I try to log in.
Long story short: Check the permissions of your filesystem, particularly the above mentioned folders, as well as /home/user and /etc.
(I remember way back when I installed Gnome for Slackware; what a mess I had on my hands after I removed it.. I have been told that great improvements have since been made on that Gnome system for Slack, but I still won't try it again.)
Best of luck fixing the issue,
Sasha
I think thats only dropline-gnome, I haven't installed any other gnome packages for slackware, but I'm pretty sure the other ones are alot better
Thnx guys, but I'm away on business so I can't make configurations right away since my PC is at home but I'll do that as soon as I touch down in South Africa this coming weekend.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.