Re: wistron_btns
Didier Spaier <[email protected]> Sat, 27 Feb 2016 10:44:35 +0100
| Newsgroups | gmane.linux.slackware |
|---|---|
| Message-ID | <[email protected]> |
Hi, On 27/02/2016 08:58, Noel Butler wrote: > So, today I thought I'd alter my old laptop that was running opensuse > fine and install slackware current (32bit 512mb ram - but hey, it is 13 > years old, and it runs my DJ'ing software "mixxx" perfectly)... > > Everything went great, apart from having to forcepae for install disk to > get to setup :) > > 20 mins later all done, reboot to run... thats where the fun times > ended, the screeen sits there constantly emitting wistron_btns unknown > key code 10, after half an hour I had to hard kill pwr - not good idea > but only way to recover, seems huge.s doesnt use pae, tried it, same > thing... > > Anyone have suggestions on how to get slack to ignore this mess? or must > I downgrade back to my opensuse backup? > > Does 14.1 have the same madness? It's not Slackware but kernel related, so probably yes. Google quickly told me there have been bugs filed: wistron_btns fails on PAE kernels at least with some kernel versions. So the easiest workaround is to blacklist bistron-btns (modularized in all Slackware kernels, fortunately). You'll have to append this to your kernel command line the first time you boot: modprobe.blacklist=bistron-btns If this doesn't work you'll need to install a non-SMP kernel (huge.s). Also, unless you be in a hurry, you could wait for the release of Slackware 14.2 before completing the installation to avoid updating your system often, but that's just my humble and non requested opinion. Didier