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.
Hi there, have finished my Slackware install, and would like to use the KDE desktop environment. When I boot up the pc, it ends up at the normal login screen, ie black background. In order to get into KDE, I have to type 'startx' which then takes me into the KDE environment. What I would like to do is have KDE automatically load up on startup, so that when I get to the login screen, it is the KDE login splash screen. Anyone know what files I need to edit to set this up?
What you have to dois change inittab's default runlevel to 4. its location is /etc/inittab heres what you want
Code:
# These are the default runlevels in Slackware:
# 0 = halt
# 1 = single user mode
# 2 = unused (but configured the same as runlevel 3)
# 3 = multiuser mode (default Slackware runlevel)
# 4 = X11 with KDM/GDM/XDM (session managers)
# 5 = unused (but configured the same as runlevel 3)
# 6 = reboot
# Default runlevel. (Do not set to 0 or 6)
id:4:initdefault:
Thanks a lot. That has solved it. I didn't realise there are now about 9 different window managers I can choose from. I like Blackbox, if it actually worked properly. One last question, I use lilo to boot up linux, but I have Windows as well, so wanted to add it to the lilo menu. I added the lines:
other = /dev/hda1
label=Windows XP Pro
to the bottom of the lilo.conf and saved it. But Windows XP Pro still doesn't show up in the lilo startup? Do I need to execute a script or update something to get it to work?
Thanks, got it working now. Lilo doesn't like any spaces in the label then? Never mind, have got Windows-XP-Pro instead
One last thing, I can't reboot or shutdown the computer anymore. If I logout of any of the window managers, it just takes me back to a graphical login screen, where all I can do is login again or change what session I want to use.
you can use the shutdown command, as root - "shutdown -h now". see manpage for flags and options
also iirc, KDM has a shutdown option - you can select to use KDM by commenting /etc/rc.d/rc.4, and set options for KDM in /opt/kde/share/config/kdm/kdmrc
Thanks for that. But still no luck.
How do I find out if I've got APM or ACPI installed, and if I have got them, how do i go about configuring them. I know my laptop can power off by itself because I had Gentoo and it worked in that. At the moment, it finishes on Power Down, and then I have to turn it off myself.
I know my laptop can power off by itself because I had Gentoo and it worked in that. At the moment, it finishes on Power Down, and then I have to turn it off myself.
Open /etc/rc.d/rc.modules in an editor, and look for this bit:
Code:
#### APM support ###
# APM is a BIOS specification for saving power using several different
# techniques. This is mostly useful for battery powered laptops.
# /sbin/modprobe apm
Uncomment that last line. Then either reboot, or run 'modprobe apm' yourself.
Last edited by AxelFendersson; 05-27-2004 at 03:41 AM.
Have done all this. I also recompiled the kernel and made sure apm support was built in and acpi was not installed at all. Hooray, my laptop does shut itself off now. The only thing is it doesn't recognize my battery. It always thinks there is ac-online even when its running on batteries. Is it worth me recompiling and removing apm support and putting acpi instead?
I would say yes (however much of a pain it is which isn't much if you're using the 2.6 kernel). Otherwise you'll be running on full battery power all the time (no low power mode and no sleep mode).
You can add the ability to Shut Down and Reboot to the KDM or the GDM as by going into the Menu>Applications>System Tools>Login Screen Setup.
Ok, I've got KDM as the login manager now, which comes with a shutdown button in it
And changing to KDM has added shutdown and reboot to the logoff option in KDE which is also what I wanted. I'm using the 2.4 kernel at the moment which I recompiled and added in the APM support. So you reckon I should upgrade kernel, or install acpi instead. And I am pretty new to linux, so if I was to recompile the kernel or put a 2.6 one on, how do I go about keeping the setup I've got, since I know it kind of works. Obviously I would delete the 2.4 kernel if I get another working one, but if the acpi or 2.6 kernel doesn't work, I would like to be able to boot up the system I have at the moment.
There's a really great sticky thread for recompiling your kernel. It makes it simple as hell.
For the bare bones of it though, you download the source of the kernel you want from kernel.org and untar it to /usr/src. From a command prompt go into the new directory as root...
type make mrproper (optional for a newly downloaded kernel as it will clean out the default config which I prefer to keep and modify rather than have to go back through and reset everything)
then type make menuconfig
select all the options you need and exit saving the config
For the 2.6 kernels all you have to do then is type 'make' and it'll not only create the bzImage but also make any modules specified
if you added anything as modules just type 'make modules_install'
and you're done with that kernel.
Now go (as root) to the /boot directory and create a symbolic link to the new kernel's bzImage:
ln -s /usr/src/linux-2.6.x/arch/i386/boot/bzImage vmlinuz-2.6.x (you can use whatever name you want for the link, I use vmlinuz-kernel version out of habit)
Go into lilo.conf and just duplicate the existing lines used to boot:
so you'll have a second set of the same lines only change the image from vmlinuz to the link you created vmlinuz-2.6.5 and change the label to something unique. Save the lilo.conf. Run lilo as root and then reboot. You'll see your new kernel show up as an option when you boot and you'll be able to tweak it as need be without losing the option to boot to the old kernel. The first entry will always be the default.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.