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.
I was having the vertical-only mouse problem with my Logitech EX110 Cordless desktop. I tried editing all sorts of configuration files, but the thing that made the difference was installing the huge2.6.s kernel from the slackware CD.
Now the mouse works in the console and in X.
For anyone having the same problem, installing the new kernel was EASY. Just like Slackbook says, just copy the files from the CD into /boot and edit lilo.conf, then run lilo.
Installing the new kernel has had other nice effects, too. Boot time is way faster, no hotplugging. Very cool.
Exqueeze me? Baking powder? Do you use Slackware? I sincerely hope you're joking, dude. There are plenty of reasons to use Slackware -- the big one is simplicity -- FOR EXAMPLE...
OKay, in all seriousness: on the Slackware install disks there is a big collection of potential kernels; you can choose any of them during installation, however, it's easy enough to change later if you want to. I had trouble with the usual 2.4 kernel when I originally installed -- the subject of this thread. So, I decided to try a 2.6 kernel, since I have mostly brand new hardware. It's as simple as copying a few files from the disks that I had.
PARTICULARLY IF I CAN'T CONNECT TO THE INTERNET ONCE I'VE INSTALLED THE os COPYING THE FILES FROM DISK IS A LOT EASIER THAN USING APT.
I agree with your solution ... all my logitech mice did this with all the 2.4 kernels, installing the 2.6 kernel solved it. I tried multiple other solutions before this one, but none worked.
However, I don't think there is a need to copy files to disk in order to install a new kernel.
However, I don't think there is a need to copy files to disk in order to install a new kernel.
Senor Texmex,
Just curious, how else would I do it in Slackware (or any other computer system)? I mean, the kernel has to be on disk in order to be read...how is the computer going to boot a kernel off of a CD, especially one that's not in the drive? Is it going to extract the file from the disk on a spindle on my desk through some magical data channel?
If I'm sounding terrifically naive about this, just fill me in. One of us has miscommunicated something
sorry. hating slackware is a tradition of mine going back to 1997. force of habit
I understand I'm developing a healthy loathing of Ubuntu myself. So, did you come to the Slackware forum just to "hate on" Slackware?
Perhaps you forgot that this was posted in the Slackware forum, or that Slackware doesn't have APT, or super cow powers
Btw, dependencies are not really an issue with something as simple as installing a new kernel in Slackware -- it's really as easy as copying files from a CD. I'm curious as to why you think APT is better, or why you'd prefer to have things going on behind your back (my interpretation of the situation; that's why I prefer Slackware -- I know what's going on at every turn).
TO TEXMEX as well: that's how it's described in the Slackbook, so that's why I did it that way.
Well, let's see I just posted it in another thread:
put slackware CD #2 or DVD into your drive and:
Code:
su
<Enter your root password>
mount /dev/cdrom /mnt/tmp
cd /mnt/tmp/extra/linux-2.6.17.13
installpkg kernel-generic-2.6.17.13-i486-1.tgz
installpkg kernel-modules-2.6.17.13-i486-1.tgz
installpkg kernel-source-2.6.17.13-noarch-1.tgz
cd
umount /dev/cdrom
eject /dev/cdrom
Well, let's see I just posted it in another thread:
put slackware CD #2 or DVD into your drive and:
Code:
su
<Enter your root password>
mount /dev/cdrom /mnt/tmp
cd /mnt/tmp/extra/linux-2.6.17.13
installpkg kernel-generic-2.6.17.13-i486-1.tgz
installpkg kernel-modules-2.6.17.13-i486-1.tgz
installpkg kernel-source-2.6.17.13-noarch-1.tgz
cd
umount /dev/cdrom
eject /dev/cdrom
Interesting. That may be why I have had trouble with modules.
You knw the extra volume control buttons on the keyboard... and the play pause media control button.
I dont really need the media buttons but the volume control buttons are really usefull.
As far as I know, those [keyboard] buttons don't work. However, do you want to use them? I never use them. Even in Win$uck I never used them (when they would have worked); I'm saying I would have no way of knowing. If you want to use them, go ahead.
You knw the extra volume control buttons on the keyboard... and the play pause media control button.
I dont really need the media buttons but the volume control buttons are really usefull.
You can do this, but it is a little complicated. (The idea is simple, but implementation is a pain). Maybe you should start a new thread
I was able to do this using "xev" as a starting point. Rough outline:
xev to get keycodes
map keycodes to > F12 keys using ~/.Xmodmap
use your new "imaginary" F keys to perform certain actions using dcop (control centre in KDE).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
