SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
after installing slackware 11 with 2.6 test-kernel, mouse (ms intellimouse ps/2) did not work.
I then replaced 2.6 kernel with the (thanks pat!) also present 2.4-kernel:
(System.map, config, vmlinuz in /boot).
the mouse worked.
from the output of the x window system I read that x window is compiled under 2.4. can this be the source of the problem?
how to use the mouse with a 2.6-kernel?
I just installed slack 11 yesterday, my first return to slack after having started with linux on slack 11 years ago ... just like old times, except it was much easier to get things going
I think it was a large oversight to allow the 2.6 kernel to install without the modules, but that was the only hitch I found. Both kde and dropline went on smoothly and everything works very well.
Anyway, to fix my mouse (and net conn) I installed the kernel-modules from /extra, just as others have stated, and grabbed the kernel sources while I was at it. After that, a simple reboot fixed everything.
I was just curious about the state of slack after all this time; my assessment is that I like it and will keep it.
Hey TNWestTex, thanks for the info. I always compile my own 2.6 from kernel.org, so the rc.modules-2.6 file was never in /etc/rc.d. I downloaded the linux-modules package and copied the file over, and it works without having to manually modprobe the mouse module. I still need to modprobe all of the acpi stuff though (ac, battery, etc). Oh well.