Spontaneous numlock

[dsimic]

My apologies for the delayed response.  I went through all replies posted in the meantime, and here are a few comments from my side.

Probably everybody has localectl since it's command line, My Debian and Manjaro both have it without installing anything special.  In Debian I see:

Code:

System Locale: LANG=C.UTF-8
      VC Keymap: n/a
      X11 Layout: us
      X11 Model: pc105

I was just booted into Manjaro and I was seeing a UK keyboard layout.  " displayed as @ was the first thing I noticed about it.

On my PineBook Pro with ANSI keyboard, running Manjaro ARM, this is the output of localectl:

Code:

   System Locale: LANG=en_US.UTF-8
       VC Keymap: us
      X11 Layout: us
       X11 Model: pc105+inet
     X11 Options: terminate:ctrl_alt_bksp

If you want, I can find the Manjaro ARM setup script that configures the keyboard layout, although it should contain no "magic".

I was carefully pushing Fn, then a key, then letting up the key, then Fn because I was trying to see the Fn key.  And redirecting the output to a file so I wasn't actually seeing anything.  And I had rebooted and done this before I started X.

But I don't see a scancode for Fn.  There should be one hex number that's in all of them and there isn't..  I'm not sure what the pairings of scancodes are, maybe press and release.

The Fn key is also "invisible" on my PineBook Pro, and it should be that way because the Fn key is supposed to be handled entirely by the keyboard controller.  In other words, the Fn keys on laptop keyboards have been invented as a space-saver feature, and the effects of pressing an Fn key (i.e. changes to the generated scancodes) should be handled entirely by the keyboard itself.

What I can gather (barely) is that you get the same results on different operating systems, with different U-boots.  So the problem is in the keyboard itself.  It's either the keyboard firmware, or the keyboard switches.

I'm also inclined to think that something is wrong with the keyboard.  Updating the keyboard firmware again changed nothing, so there almost certainly must be something wrong with the keyboard.

I can hardly find any good information on this.  I'm starting to think it's on the main board, but I can't find any high resolution images to look for the chip.  I'm not able to take my PBP apart to lol for it right now.

According to page 20 of the PineBook Pro schematic, the SH68F83Q IC is located on the main board.  The schematic puts it behind the J6 connector (#7 in the picture), which receives the keyboard's ribbon cable.