SlackwareThis Forum is for the discussion of Slackware 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.
Greetings
If you plan to do a lot of switching between KDE and Xfce or any of the many other WM/DE's, I recommend trying to use KDM, by issuing the "kdm" command from runlevel 3, root console login. This will bring up a nice Login Greeter page with menus for each WM/DE and even some variations, like "failsafe" or any you write yourself, and in addition to menuitems for reboot and shutdown, also allows returning to runlevel 3 console. However if you do that it's a good idea to issue "killall kdm" if you plan to launch "kdm" again.
Greetings
If you plan to do a lot of switching between KDE and Xfce or any of the many other WM/DE's, I recommend trying to use KDM, by issuing the "kdm" command from runlevel 3, root console login. This will bring up a nice Login Greeter page with menus for each WM/DE and even some variations, like "failsafe" or any you write yourself, and in addition to menuitems for reboot and shutdown, also allows returning to runlevel 3 console. However if you do that it's a good idea to issue "killall kdm" if you plan to launch "kdm" again.
I'm not sure you can have two X sessions at the same time, but if yes that could cause even more overheating
PS I just tried this from my usual Fluxbox session:
Ctrl+Alt+F2 => login as Didier again => xwmconfig (choose XFCE) => startx => XFCE is launched.
I can go back to Fluxbox whit Ctrl+Alt+F7 but don't know how to switch to XFCE again
The second X Server will be started on the lowest available unused virtual console, so most likely ctrl-alt-f8. You can use "ps -fC X" to identify which ttys are running X. Whether multiple X servers can run concurrently might depend on your hardware/driver. My system can certainly do this (nvidia blob).
edit: Ooops, I now see mrclisdue has already answered this above, sorry for the dup.
Unless I wasn't clear about what I meant it isn't. I was referring to what is for me the very first login, in multi-user console, where I login as root. So I did mean runlevel 3. Runlevel 4 is X.
Quote:
Originally Posted by runlevel wiki
Slackware Linux
Slackware Linux uses runlevel 1 for maintenance, as on other Linux distributions; runlevels 2, 3 and 5 identically configured for a console (with all services active); and runlevel 4 adds the X Window System.
Slackware Linux runlevels[9] ID Description
0 Halt
1 Single-user mode
2 Unused but configured the same as runlevel 3
3 Multi-user mode without display manager
4 Multi-user mode with display manager
5 Unused but configured the same as runlevel 3
6 Reboot
@enorbet: what is the advantage of starting the system at runlevel 3 if you want to use kdm at every boot? Why not simply change the default runlevel to 4 that leads to the same result, without having to login as root, then to type "kdm"?
Last edited by Didier Spaier; 03-24-2014 at 03:17 PM.
@enorbet: what is the advantage of starting the system at runlevel 3 if you want to use kdm at every boot? Why not simply change the default runlevel to 4 that leads to the same result, without having to login as root, then to type "kdm"?
^^^^^^^^^
Which is the question that someone whose screen name was something other than mine would post.
@enorbet: what is the advantage of starting the system at runlevel 3 if you want to use kdm at every boot? Why not simply change the default runlevel to 4 that leads to the same result, without having to login as root, then to type "kdm"?
The simple answer is that I do not use kdm at every boot, or at least immediately. It depends totally on what I intend to do that day and on which machine. Example - I have a minecraft server that almost never leaves runlevel 3.
Additionally, I prefer to install proprietary graphics drivers myself and they require either runlevel 3 or dkms on other distros than Slackware, and if there is a way to avoid dkms on a given distro, I do. Similarly, I compile custom kernels for almost every distro and after running "make xconfig", I prefer to drop to runlevel 3 for the last steps. I just like the flexibility and the time delay is just no big deal to me.
Just a reminder, but always check the status of your video card driver support level on AMD's website. Often from time to time, some video chipsets get pushed to legacy support, or passed off to the free driver provided by Xorg.
Running the latest kernel is always recommended as the later kernel versions now have better system control features not available in some earlier kernels including stable ones like those Slackware uses.
For AMD you always want to run the latest versions of each of these:
Linux Kernel
LibDRM
XServer
and
LibMesa+XF86-Video-ATI
or
AMD-Catalyst
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.