04-14-2021, 11:01 AM
(04-12-2021, 05:47 PM)oddsocks Wrote: Yeah I suspected as much. I'm wondering if it's possible to actually disassemble the keyboard itself to access the membrane. It seems to me that the keyboard might be riveted together with plastic rivets so it might not be possible without damaging it anyway...
I haven't disassembled or replaced the keyboard inside the PineBook Pro, but you're right, laptop keyboards are pretty much always made in a way that doesn't allow them to be opened and serviced. There are two pictures of the back side of keyboard in the Pine64 store (ISO variant and ANSI variant), which seem to confirm your assumption.
(04-14-2021, 02:45 AM)oddsocks Wrote: Right, so you're saying a stuck key wouldn't affect any others if that's the case?
Regardless of the keyboard type (USB or PS/2), it should keep sending a "key press" event (i.e. a scancode) for a stuck key that is printable, which excludes "modifier" keys such as Ctrl and Alt. Also, no "key release" scancode would be sent in that case, because a stuck key is never released. In other words, xev should not report a stuck "modifier" key, and there should be no visible effects (except the inability to actually use the stuck "modifier" key), because the once-generated key press scancode would be consumed by U-Boot. That's how the things should work, at least in theory, but it would need to be tested.
Could you, please, shut your PineBook Pro down, press and hold the Ctrl or Shift key, and then power on and boot the laptop? Then, please let us now what happens while using the keyboard, and also please check what is reported by xev.
