SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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 read that to make SUSE work faster unnecessary things might be disabled in the runlevel editor. So that's what I've done: I disabled the joystich there assuming that I wont need it. Now Linux doesn't boot, I mean graphical interface doesn't come up. I just see the invitation to enter login and passworg in the console regime. I'm not a very experienced user, can someone give me a hint how do I get into graphical interface back? Or do I have to reinstall the system completely?
Not sure I follow how disabling the joystick service could have caused this.... Sure you didn't disable something else? xdm (or whatever SuSE uses)?
Short answer: A simple
Code:
startx
should get you your graphical environment back. Then you can play around with YaST again to get your graphical environment at boot time again. (I'm guessing you either told it to boot to runlevel 3 - text mode - or you stopped xdm/gdm/whatever.)
I could be able to get into yast as you told me, but trying to enable xdm didn't change anything. I looked more attentively at what is written when system is booting, it is that D-BUS is not running and that services in runlevel 2 were failed. When I come into graphical environment it sais that there's a problem with power management and also sound doesn't work.
Thank you for a hint, but how do I do it in suse 10.0? That's what my manual sais:
To check the runlevel configuration, log in as the root user and check whether the machine is configured to boot into runlevel 5 (graphical desktop). A quick way to check this is to examine the contents of /etc/inittab, as follows:
nld-machine:~ # grep "id:" /etc/inittab
id:5:initdefault:
nld-machine:~ #
The returned line indicates that the machine's default runlevel (initdefault) is set to 5 and that it should boot to the graphical desktop. If the runlevel is set to any other number, use the YaST Runlevel Editor module to set it to 5.
In my case it's on runlevel 2. But there is no initdefault entry in the yast runlevel editor so I can change it! There is a whole list of things like:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.