Re: wistron_btns

Hi,

On 27/02/2016 19:44, Didier Spaier wrote:
> 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.


Yep, I gathered that from my google fu'ing which seemed to point to 
kernel + PAE with no real working suggestions as to get around it, 
though, I did give up after googles page 4 which was becoming even less 
relevant about the issue.

> 
> Google quickly told me there have been bugs filed: wistron_btns fails
> on PAE kernels at least with some kernel versions.

Yep,  I saw this, I also saw some were from 2005 (or was it 2009?), 
which is where I got the idea to boot with huge.s instead.

> 
> So the easiest workaround is to blacklist bistron-btns (modularized in
> all Slackware kernels, fortunately).

On my servers I run custom compiled kernels for what, nearly 20 years, 
but on my desktops
and this laptop I've always opted for distro kernels.. maybe I need to 
rethink that approach now :)

> 
> You'll have to append this to your kernel command line the first time
> you boot: modprobe.blacklist=bistron-btns

Thanks, will give that a shot s/b/w/  .. Going to a bistro for dinner 
were we ? :)


> If this doesn't work you'll need to install a non-SMP kernel (huge.s).

Hrmm I thought that's what I am using, not the smp one.

> 
> 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.

I'm technically using 14.2 , built the ISO from current on Friday. It's 
also not critical, I have a spare partition, so I can re-install 
opensuse from rsync backup on it, and play with slackware when there's a 
change, or I get bored and want to try building own kernels if Pat 
doesn't update to an allegedly fixed one.

Thanks again for your modprobe suggestion, I'll try that out and let you 
know how it goes..

Cheers

Noel


-- 
If you have the urge to reply to all rather than reply to list, you best
first read  http://members.ausics.net/qwerty/