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 did a fresh install of Slackware64 14.2 on a ThinkPad X220 (broken screen ATM). During install the keyboard and trackball connected to the dock worked fine. After install I got nothing from them, so I decided to use the built in hardware. The keyboard works fine but the track point doesn't work when I enter the GUI.
I tried installing Salix, which I wanted to try anyway, and pretty much the same thing except after install even the onboard keyboard didn't work.
Obviously there is something I need to do. Under 14.1 I didn't have any input issues.
Are you using the 'huge' kernel or the 'generic' kernel? It might be a good idea to boot from the installation media and verify the keyboard and mouse work. You can mount your hard disk and chroot into a bash shell. Try starting up /etc/rc.d/rc.gpm to verify the mouse works, and type in the console to verify the keyboard. If this is successful, you should create a initrd and set up the 'generic' kernel to boot your machine using the kernel modules displayed by /usr/share/mkinitrd/mkinitrd_command_generator.sh.
I have a similar issue with my old laptop and the 'huge' kernel on Slackware-current.
It was still huge, as I didn't get a chance to clean everything up after installation. I will boot from the USB drive to test it, however I know things are working as it works before booting (for bios and such) as I was looking in there earlier. I figured huge would have more, so it wouldn't have as many hardware issues as generic.
I will try what you said and be back with the results later.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.