[SOLVED] Slackware 14 - Keyboard now requires acpi to be off
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.
Slackware 14 - Keyboard now requires acpi to be off
I just upgraded my Dell XPS 15z from 13.37 to 14 following the instructions in UPGRADE.txt. Things seemed to go smoothly until I booted into runlevel 3 using the generic kernel (initrd is working, I guess) and found that I get absolutely no keyboard function. I mean they keyboard doesn't work at all, I can't even log in. Booting using the huge kernel made no difference.
I rebooted and turned off acpi, and that restores keyboard function to normal. However, this is a change as 13.37 didn't need acpi to be off for the keyboard to function.
Any ideas or have I missed something about the way 14 handles keyboards?
Ok, this will probably not help, because keyboards are not attached to PCI, but since you have a lot more experience with Linux than I, it might make you think of other ideas
I also was passing noacpi to the kernel, because my motherboard wouldn't boot many distributions (Slack included). I did some reading and people suggested passing pci=nocrs instead of noacpi. Apparently it just reverts the default method for finding PCI resources. And remember what I wrote at the beginning :P
Thanks all, that thread allend linked to did the trick. Running with "acpi=off" wasn't tenable long term since this laptop really needs bumblebee to function properly, and bumblebee requires acpi to be functional. I also had success using 'noapic', which was probably a better option than acpi=off, but I'm not good enough enough with hardware-level problems to really know.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.