linux-kernel - Re: rf kill button not working on hp folio 9470m

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1668082.DN2GrHmhxH@calvin>
Date:	Mon, 14 Jan 2013 08:59:55 +0100
From:	Fabio Coatti <fabio.coatti@...il.com>
To:	joeyli <jlee@...e.com>
Cc:	linux-kernel@...r.kernel.org, Bob Moore <robert.moore@...el.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Feng Tang <feng.tang@...el.com>,
	Len Brown <len.brown@...el.com>, MaChen@...e.com
Subject: Re: rf kill button not working on hp folio 9470m - bisected

In data lunedì 14 gennaio 2013 10:45:27, joeyli ha scritto:

> > Hi all,
> > on my laptop (hp folio 9470m), the rfkill button works fine on 3.6.10
> 
> Does rfkill button means Fn+F12 key on your machine?

No, it is a "out of layout" key (this laptop has two of them, rfkill and mute) 
under Fn+Fx there is several other functions, some working and some not, but 
this is another story :)

> 
> > and 11 (don't know about older kernels), but is not working on 3.7.X
> > (latest tested is 3.7.2).
> > On non working kernel, log shows the following messages:
> > 
> > Jan 13 17:34:33 calvin kernel: atkbd serio0: Unknown key pressed
> > (translated set 2, code 0xf8 on isa0060/serio0).
> > Jan 13 17:34:33 calvin kernel: atkbd serio0: Use 'setkeycodes e078
> > <keycode>' to make it known.
> 
> Looks your machine emit e078 code when it switch to Windows 8 code path.
> Please tail your log and press Fn key for make sure it emit e078 code.
>

Confirmed:

Jan 14 08:51:55 calvin kernel: atkbd serio0: Unknown key pressed (translated 
set 2, code 0xf8 on isa0060/serio0).
Jan 14 08:51:55 calvin kernel: atkbd serio0: Use 'setkeycodes e078 <keycode>' 
to make it known.

 
> I didn't see e078 code in hewlett-packard keymap file in udev, currently
> it define 0xD7 to be the wlan key.
> 
> > Jan 13 17:34:33 calvin kernel: atkbd serio0: Unknown key released
> > (translated set 2, code 0xf8 on isa0060/serio0).
> > Jan 13 17:34:33 calvin kernel: atkbd serio0: Use 'setkeycodes e078
> > <keycode>' to make it known.
> > Jan 13 17:34:34 calvin kernel: atkbd serio0: Unknown key pressed
> > (translated set 2, code 0xf8 on isa0060/serio0).
> > Jan 13 17:34:34 calvin kernel: atkbd serio0: Use 'setkeycodes e078
> > <keycode>' to make it known.
> > Jan 13 17:34:35 calvin kernel: atkbd serio0: Unknown key released
> > (translated set 2, code 0xf8 on isa0060/serio0).
> > Jan 13 17:34:35 calvin kernel: atkbd serio0: Use 'setkeycodes e078
> > <keycode>' to make it known.
> > 
> > On working kernels, same logs shows the following lines:
> > 
> > Jan 13 22:55:59 calvin kernel: atkbd serio0: Unknown key pressed
> > (translated set 2, code 0xf8 on isa0060/serio0).
> > Jan 13 22:55:59 calvin kernel: atkbd serio0: Use 'setkeycodes e078
> > <keycode>' to make it known.
> > Jan 13 22:55:59 calvin NetworkManager[4823]: <info> WiFi now enabled
> > by radio killswitch
> > Jan 13 22:55:59 calvin NetworkManager[4823]: <info> (wlan0): bringing up
> > device. Jan 13 22:55:59 calvin kernel: iwlwifi 0000:03:00.0: L1 Disabled;
> > Enabling L0S Jan 13 22:55:59 calvin kernel: iwlwifi 0000:03:00.0: Radio
> > type=0x2-0x1-0x0 Jan 13 22:55:59 calvin kernel: atkbd serio0: Unknown key
> > released
> > (translated set 2, code 0xf8 on isa0060/serio0).
> 
> hmm... this machine changed wlan0 status on working kernel and also emit
> e078 code like on Windows 8 mode.
> 
> Then I think your machine control RF power by different way but BIOS,
> maybe wmi or other ways.
> 
> Please attached on your DSDT, hope OEM do those things through ACPI.

Done; I've tried to recompile it with iasl and I've got hundreds of errors, 
not a good sign I fear. I'll try to upgrade the firmware, even last time I 
tried the operation failed.


> 
> Please try acpi_osi="!Windows 2012", it will switch back to Windows 2009
> mode. Then look at does things better than before?
> 
> 
> Thanks a lot!
> Joey Lee

Will do that right now and report asap. 
Many thanks for the answer!
 
--
Fabio
Download attachment "dsdt.dat.gz" of type "application/x-gzip" (49280 bytes)