[Bug 218901] LG Gram Laptop Extra Features not working on 2024 models (16Z90S)

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=218901

--- Comment #27 from Agathe Boutmy (agathe@boutmy.com) ---
(In reply to Armin Wolf from comment #25)
> Does dmesg report any debug messages like "Type: XX Eventcode: 0xXX"?
> 
> If yes, then please send me the output of dmesg after pressing the FN-keys.
> Should the wifi issue happen again, please send me the dmesg output too.

Yes, here they are:

FN key pressed: [ 8437.457099] lg_laptop: Type: 1    Eventcode: 0x30010000
FN key released: [ 8469.382650] lg_laptop: Type: 1    Eventcode: 0x30010001 //
also happens when pressing and after releasing FN-F1..4 (twice when releasing
since 2 keys are being released I guess)
FN-F1: [ 8491.979548] lg_laptop: Type: 1    Eventcode: 0xf070002
FN-F2: [ 8545.037702] lg_laptop: Type: 1    Eventcode: 0x9000087
FN-F3: [ 8561.170853] lg_laptop: Type: 1    Eventcode: 0x9000086
FN-F4: [ 8642.087767] lg_laptop: Type: 1    Eventcode: 0x10300100

FN-F5 has a different behaviour than the previous four: Here is the full list
of code sent when pressing them:
[ 8737.235169] lg_laptop: Type: 1    Eventcode: 0x30010000 // here only fn is
pressed
[ 8739.068108] lg_laptop: event guid 2
[ 8739.068163] lg_laptop: Type: 1    Eventcode: 0x30010001 // fn held and F5
pressed
[ 8739.091282] lg_laptop: event guid 2
[ 8739.091331] lg_laptop: Type: 1    Eventcode: 0x30020000
[ 8739.117827] lg_laptop: event guid 2
[ 8739.117872] lg_laptop: Type: 1    Eventcode: 0x30020001
[ 8739.145947] lg_laptop: event guid 0
[ 8739.146019] lg_laptop: Type: 1    Eventcode: 0x74
[ 8739.231070] lg_laptop: event guid 2
[ 8739.231127] lg_laptop: Type: 1    Eventcode: 0x30010001 //both key released
[ 8740.811039] lg_laptop: event guid 2
[ 8740.811101] lg_laptop: Type: 1    Eventcode: 0x30010001

FN-F6: [ 8938.295301] lg_laptop: Type: 1    Eventcode: 0xf000002 //behaves like
F1..F4

FN-F7 doesn't seem to have a unique code, here's what I get (it does what it's
supposed to though):
[ 9016.134096] lg_laptop: event guid 2
[ 9016.134153] lg_laptop: Type: 1    Eventcode: 0x30010000
[ 9017.160755] lg_laptop: event guid 2
[ 9017.160813] lg_laptop: Type: 1    Eventcode: 0x30010001
[ 9017.183855] lg_laptop: event guid 2
[ 9017.183905] lg_laptop: Type: 1    Eventcode: 0x30020000
[ 9017.210594] lg_laptop: event guid 2
[ 9017.210644] lg_laptop: Type: 1    Eventcode: 0x30020001
[ 9017.260458] lg_laptop: event guid 2
[ 9017.260507] lg_laptop: Type: 1    Eventcode: 0x30010001
[ 9017.537250] lg_laptop: event guid 2
[ 9017.537335] lg_laptop: Type: 1    Eventcode: 0x30010001

FN-F8, the keyboard brightness control key seems to be the one starting a loop
of disconnecting the wifi and activating bluetooth, pressing it once leads to
having to deactivate the module if I want to return to a stable state, here's
the output:

[ 9104.362389] lg_laptop: Type: 1    Eventcode: 0x30010000
[ 9106.929029] lg_laptop: event guid 2
[ 9106.929083] lg_laptop: Type: 1    Eventcode: 0x30010001
[ 9106.952201] lg_laptop: event guid 2
[ 9106.955362] lg_laptop: Type: 1    Eventcode: 0x10000000
[ 9107.059296] lg_laptop: event guid 2
[ 9107.059390] lg_laptop: Type: 1    Eventcode: 0x30010001
[ 9107.799205] ACPI: \_SB_.XINI: notify: 192
[ 9107.821281] wlp0s20f3: deauthenticating from 68:3f:7d:36:0b:15 by local
choice (Reason: 3=DEAUTH_LEAVING)
[ 9108.098842] lg_laptop: event guid 2
[ 9108.098888] lg_laptop: Type: 1    Eventcode: 0x30010001
[ 9108.815812] ACPI: \_SB_.XINI: notify: 192
[ 9108.829467] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
[ 9108.985519] iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for
RT uCode
[ 9108.985633] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[ 9108.985651] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 9108.985658] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x80
[ 9108.985666] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[ 9108.986425] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[ 9112.617854] wlp0s20f3: authenticate with 68:3f:7d:36:0b:15 (local
address=e4:c7:67:24:ee:74)
[ 9112.618541] wlp0s20f3: send auth to 68:3f:7d:36:0b:15 (try 1/3)
[ 9112.648263] wlp0s20f3: authenticated
[ 9112.648833] wlp0s20f3: associate with 68:3f:7d:36:0b:15 (try 1/3)
[ 9112.652551] wlp0s20f3: RX AssocResp from 68:3f:7d:36:0b:15 (capab=0x1511
status=0 aid=74)
[ 9112.655106] wlp0s20f3: associated
[ 9112.668475] wlp0s20f3: Limiting TX power to 23 (23 - 0) dBm as advertised by
68:3f:7d:36:0b:15
[ 9114.722923] lg_laptop: event guid 2
[ 9114.722982] lg_laptop: Type: 1    Eventcode: 0x30010000
[ 9114.899608] ACPI: \_SB_.XINI: notify: 192

My understanding of what happens looking at dmesg in follow mode is that it
sends the even once when pressing FN-F8 and then any keyboard use after that
sends the event again (fn key or not) which means any input results in the
network connecting or disconnecting.
It doesn't turn airplane mode on though.

FN-F9: [ 9658.815309] lg_laptop: Type: 1    Eventcode: 0xf020000

FN-F10..12 same behaviour as FN-F7 which makes me think this is handled
somewhere which would make sense since it's not a functionnality exclusive to
the LG Gram.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.