[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Keyboards, was Is there a way to corrupt the BIOS …, Some keys … do not work



These problems sound somewhat similar.

On Sat 08 Aug 2020 at 16:24:59 (+0200), Albretch Mueller wrote:
>  I found those links but not thorough Information:
>  https://linux.slashdot.org/story/02/06/15/1416224/a-web-browser-in-your-bios
>  https://stackoverflow.com/questions/7531000/javascript-access-to-hardware
> 
>  Here is my problem:
> 
>  I browse the Internet using a USB wifi dongle and Windows and then
> take out the drive and use Linux for my own business.
> 
>  I removed the network and bluetooth cards, as well as the wireless
> antenna of that laptop, but I still notice that when I writing both
> code and on to the shell characters are miswritten or not written at
> all or apparently charaters get written in "temperamental" ways that
> hit to some "memory"/"intelligence".
> 
>  I also know that keyboards have internal memory chips.
>  https://en.wikipedia.org/wiki/Keyboard_controller_(computing)
> https://reverseengineering.stackexchange.com/questions/6388/storing-files-on-keyboard-memory
>  How can you reset/wipe the keyboard controller?
> 
>  How could this be explained "technically"?
> 
>  What do you think might be "technically" going on?

On Mon 10 Aug 2020 at 13:56:43 (+0200), Eugen Dedu wrote:
> 
> I have a Dell Latitude 5580 laptop, and have been a happy debian
> unstable user for 20 years.  I have a very weird problem with its
> builtin keyboard which slows down my work significantly (ctrl-c,
> ctrl-x, ENTER etc. do not work):
> 
> Since several months ago some keys on my keyboard do not work, in all
> the applications (e.g. gnome-terminal, emacs, thundebird, firefox).
> When I press on them, very often nothing happens (usually, I press on
> them for 10 seconds to make appear the character), sometimes the key
> appears twice, and sometimes it works flawlessly.  When it works, it
> works for several minutes or several hours; similarly, when it does
> not work, it does not for several minutes or hours or days.  I use
> very often suspend/resume, I also use xmodmap and awesome window
> manager, but I suppose this is irrelevant.
> 
> The problematic keys are found on the last row: xcvm,. (but zbn work)
> and the bottom keys (ctrl, alt, window, however space works always
> correctly), plus ENTER key.
> 
> I have always thought that it is a X problem which will get fixed.
> Interesting, a few days ago I noticed that on grub I have the same
> problem: c and ENTER did not work.  So now I wonder if it is not a
> hardware problem, however sometimes it works for a long time!
> 
> I have looked at Xorg.0.log, without seeing anything wrong.
> 
> How can I track down where the problem is, and fix it?

Both these sound rather hardware-ish to me. I hope Albretch hasn't
zapped something with static when making the modifications.

Take a look at this reference. The user suspected the keyboard and
even replaced it twice without fixing the problem. It turned out
that the connection between the keyboard ribbon and the mobo was
bad. So Albretch might want to reseat some of the connectors.
I hope Eugen's Dell laptop is simpler to open up than the Lenovo
I'm typing on, if that's the course of action chosen.

https://www.dell.com/community/Laptops-General-Read-Only/XPS-M1330-laptop-keyboard-bottom-row-enter-spacebar-not-working/td-p/5163670

Cheers,
David.


Reply to: