Alt meta keys do not respond on PRERELEASE 14" Pinebook

[MarkHaysHarris777]

The production units DO NOT have this problem, apparently; several have tested.

If you have a pre release pinebook, please read on !

I first noticed this problem on the 14" pinebook while using weechat irc client;  the meta key combination alt-L to pull up the raw window does not work on my client... I used the manual command and moved on (forgot about it frankly)

Tonight after update and upgrade I tried to pull up one of the fbcon (black screen) terminals with Ctrl+Alt+F1 and it did not work.  In fact none of my fbcon terminals will come up ( Ctrl+Alt+F1 - F7 ).

Next I tried using xev ( as well evtest ) to get the keycodes of the Ctrl key, as well the Alt meta keys (left and right). And to my surprise the meta keys on my 14" do not produce valid keycodes ( neither Alt key ) on either of the test instruments ( xev nor evtest ).

So, I'm interested to know whether anyone else with a Pinebook 14" with the new production keyboard has this issue too?  To test just start  xev  tool and then press and release several of the keys on you keyboard , but specifically the left Alt and right Alt keys;  do you get a valid keycode for each Alt key, or does it not respond ??

Thank you.

---

---

Update:   note:   evtest and scancode show similar results;  the Alt keys are not present !

---

Update:   note:   I plugged in my usb wireless K360 from logitech (right port) and the Alt keys are visible there, and the Ctrl+Alt+F1  does pull up the fbcon black screen;  so, again, the input method on this 14" Pinebook keyboard is producing NO scancode for either Alt key.  Hoping to here soon whether other Pinebook users are seeing this .

---

Update:   note:   using  System -> Prefs -> Hardware -> Keyboard ; layouts tab  

   ...  alt key behavior:   I swapped the win key with the alt key...  


   Now  Ctrl+win+F1  takes me to the fbcon black screen, and  win+F7 takes me back

However;  I still need to get to the bottom of why this pre release model has no alt key scancodes.

---

[MarkHaysHarris777]

It seems that there is some mfg defect in the keyboard module scan matrix lines.  I did reseat the connectors, but the Alt keys are still dead;  no scancodes even.

So, we have a new bottom case top bezel on order ;  see if we can move the guts over and correct this problem;  in the mean time, I'm mapping the DEL key to be the pipe key, and mapping the old pipe key to be the right Alt key.  The win key is now the left Alt key;  so have good work around.

[tllim]

It seems that there is some mfg defect in the keyboard module scan matrix lines.  I did reseat the connectors, but the Alt keys are still dead;  no scancodes even.

So, we have a new bottom case top bezel on order ;  see if we can move the guts over and correct this problem;  in the mean time, I'm mapping the DEL key to be the pipe key, and mapping the old pipe key to be the right Alt key.  The win key is now the left Alt key;  so have good work around.

My guess amy due to there is mismatch between previous keyboard and the current HID microcontroller (8051) firmware mismatch.

[MarkHaysHarris777]

It seems that there is some mfg defect in the keyboard module scan matrix lines.  I did reseat the connectors, but the Alt keys are still dead;  no scancodes even.

So, we have a new bottom case top bezel on order ;  see if we can move the guts over and correct this problem;  in the mean time, I'm mapping the DEL key to be the pipe key, and mapping the old pipe key to be the right Alt key.  The win key is now the left Alt key;  so have good work around.

My guess amy due to there is mismatch between previous keyboard and the current HID microcontroller (8051) firmware mismatch.

Thanks TLLim,  I suspect you are correct.  I am not finding any damage to the matix scanlines on the module ( you know me, I would try to fix them ).  It would be interesting to be able to flash the 8051 firmware if needed !  

Thanks again.

[pfeerick]

I changed the topic title to be more accurate to the thread

Didn't you also mention on IRC that the Alt key woke the pinebook up or something?

[MarkHaysHarris777]

I changed the topic title to be more accurate to the thread

Didn't you also mention on IRC that the Alt key woke the pinebook up or something?

It seems like firmware mismatch is the best explanation at this point.  In the beginning of this exercise I believed that the Alt key might be waking the pinebook;  however, this was just vibration towards the touchpad.  The Alt keys don't seem to be having any consequence whatever.

[MarkHaysHarris777]

---

If your Alt keys are dead the full functionality of the keyboard can be restored with preferences-->hardware-->keyboard-->layouts | options:

both shift keys together = capslock;  either shift releases

left Alt is swapped with left Win

capslock is third level chooser  ;   this is AltGr

compose key = third level left ctrl

fbcon is ctrl+Win+F1

unicode is still  second level ctrl + u    ctrl+shift+u  [number]

---