#StackBounty: #keyboard #input-device Simulating a Keypad with Raspberry PI

Bounty: 100

I have an electronic Lock I want to open with my Raspberry PI 3B+. Therefore I measured the Voltage that is sent from the Keypad to the Lock. Each Number has its own Voltage. (0 = 0.00V, 1 = 0.06V… etc). If no Signal is sent the Voltage is 3.46V. When I send the Code 1-1-1-1-1-1 (= 6 x 0.06V) with the keypad, the Lock unlocks. But when I send the same Voltage with the Raspberry PI it doesnt unlock. I measured it with my Multimeter and the Voltage is the same like with the Keypad.

The Python Script I use is very simple:

sgn = PWMLED(26) 
sgn.value = 1    # 3.28V

Depending on the Voltage I want to send I change the value.

I also connected a Capacitator to stabilize the Signal.

Does anyone have a clue what could be wrong?

Please help me get this working!


Get this bounty!!!

#StackBounty: #keyboard #keyboard-layout #language How to type the 'ro' kana and yen symbol directly with US keyboard?

Bounty: 50

I recently brought the Japanese 106/109 keyboard stickers for my US keyboard. I applied stickers and changed my hardware keyboard layout from English 101/102 to Japanese 106/109. Then I realized that I can’t type the Japanese ‘ro’ and yen symbol directly. After a bit of research, I found this guide. Unfortunately, this guide doesn’t work because I don’t own the Japanese keyboard. I tried powertoys to remap a certain key to type the ‘ro’ kana but I have no idea what is the virtual key number for this kana. I looked up this documentation and it doesn’t help because it didn’t include the ‘ro’ kana and yen symbol. Any ideas on how to configure my keyboard so I can type the ‘ro’ kana and yen symbol directly?

I use Windows 10 and Google IME to type Japanese.


Get this bounty!!!

#StackBounty: #kernel #keyboard #xorg #xserver #dead-keys Keyboard buffer issue with multi-byte characters (latin, diacritics) / dead k…

Bounty: 50

I write in Spanish and sometimes I use diacritics (ie multi-byte chars) with dead keys, for example "liberación" ("liberation" in Spanish). Usually I don’t have any problem, but when the GUI freeze or for any reason it can’t handle more input, when the text shows up the diacritic char jump to the first position on the/a keyboard buffer, displaying something like "óliberacin", which is very annoying since occur very often while chatting or writing an email (easier to test: aaaááaaa). Maybe a xserver or GNOME Shell or a kernel bug?

I have this problem since more than four years now, with several kernels, Ubuntu versions, hardware and versions of Firfeox and Chorme. I couldn’t find any pattern neither something strange on dmesg/journalctl//var/log files…

Setup: This happened to me since Ubuntu 16.04 LTS fresh install, kernel 4.4.0-62-generic; and even recently with 18.04 and 4.15.0-134-generic, GNOME Shell 3.28.4.

$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=es_AR.UTF-8
[...]
$ im-config -l
ibus xim
$ im-config -m
default
missing
ibus 

ibus
$ env | grep "XMODIFIERS|IM_"
XMODIFIERS=@im=ibus
CLUTTER_IM_MODULE=xim
QT_IM_MODULE=ibus
IM_CONFIG_PHASE=1
QT4_IM_MODULE=xim
GTK_IM_MODULE=ibus

How can I debug to find where the problem might be?

Update 2021-01-23

I didn’t cross with this issue for a while, until today, typing from Desktop to Android (GSconnect→KDE Connect Keyboard).

screenshot


Get this bounty!!!

#StackBounty: #freebsd #keyboard-shortcuts #keyboard #keyboard-layout Configuring kbdmap on FreeBSD for Meta+Left/Right key combinations

Bounty: 50

I have a FreeBSD 12.1 installation, and the problem is that on a syscons or vt virtual terminal (rather than, say, an XTerm emulated terminal), both the keys ← Left and ⎇ Alt+← Left (and the same for → Right) get mapped to the same escape sequence: <ESC>[D (I have verified this using the showkey utility).

However, this means that within the shell, ← Left and ⎇ Alt+← Left perform the same actions (move left by one character), and no configuration of .inputrc can change that (so that ⎇ Alt+← Left moves left a whole word).

Now, I believe that kbdmap can help solve this issue, but I have no idea how to correctly configure it. There seems to be some information here, but it makes no sense to me whatsoever.


Get this bounty!!!

#StackBounty: #windows-8 #usb #keyboard #mouse Windows 10 laptop, no USB, keyboard and mouse

Bounty: 100

Today when I wanted to use my computer again (it was still running from the day before), I noticed my mouse cursor was gone. Moving the mouse did not reveal the cursor, neither did using the trackpad.
The keyboard from my laptop worked fine so I used that to reboot.

Then after the reboot my keyboard did not work either. So I can not login.

When I go to the bios, then the keyboard and trackpad work fine. Also an external keyboard and mouse work, so it seems like this is a software issue.

After a lot of attempts, I managed that I can boot to "safe mode with networking", but the keyboard does not work their either. Also the mouse does not work, the led won’t even go on.

What can I do at this point?

—- UPDATE

When I boot with the recovery options and try to go to Command Prompt there then it says my password is wrong…

—- UPDATE 2

I can not find a way to boot from a usb. I have a asus zenbook pro duo.

  • fast boot is disabled
  • secure boot is disabled

I have a usb with ubuntu and one with windows 10, they both show up on my mac when booting. For windows I get nothing…

— UPDATE 3

I noticed that sometimes I have to reboot several times before the laptop can see the USB with windows 10 on it.

I was able to Enable built in Admin Account, atleast it sayed the command was executed correctly, or something among those lines.
However, If I boot, I don’t see it to log in with it.

I tried a startup repair from the usb, I get:

Startup Repair coulnd’t repair your PC
Press "Advanced options" to try other options to repair your PC or "Shut down" to turn off your PC.
Log file: C:WINDOWSSystem32LogfilesSrtSrtTrial.txt

At this point I’m the most interested in recovering my data. It ain’t much, but it’s still worth it. Any help is welcome.
A repair would also be nice, but at this point I have no clue of what to do.


As for the steps that John pointed out in what is at the moment the first answer:

  • I did enable the built in admin account. But not sure if this went ok. I did not get any errors.

First: Try Windows 10 Initial Repairs.

I cannot run CMD as an Administrator, cause my password is wrong.

Second: If the above does not solve the issue, run a Windows 10 Repair Install

This gives me "Startup Repair couldn’t repair your pc".

enter image description here

Third:

No idea how to backup the data.

Finally:

Same as step Third, no Idea of what to do.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!

#StackBounty: #20.04 #keyboard #systemd #udev #microsoft-keyboard Can't remap keys on a Microsoft Keyboard with HWDB

Bounty: 50

I’m trying to remap LCtrl and CapsLock on my Microsoft Wired Keyboard 600 with HWDB but for whatever reason the system does not see the changes that I make.

This is how my hwdb rule looks like:

evdev:input:b*v045Ep07F8*
 KEYBOARD_KEY_3a=leftctrl
 KEYBOARD_KEY_1d=capslock

The vendor and the model codes come from lsusb and were reconfirmed in /sys/devices/pci0000:00/*

After copying the config file to /etc/udev/hwdb.d, running systemd-hwdb update and issuing udevadm trigger no changes in the keyboard config are present.

I’ve also tried:

  • Rebooting — didn’t help.
  • Specifying the bus explicitly as 0003 — didn’t help.
  • Confirming with evtest that the key codes I’m using are correct for my keyboard — yep, those are the correct keycodes.
  • Confirming the applied rules are listed in sudo udevadm info /sys/class/input/eventX — yes, the new rules are listed, which should mean they were applied successfully? Yet the keys behave the same way they did before.
E: KEYBOARD_KEY_1d=capslock
E: KEYBOARD_KEY_3a=leftctrl
E: ID_USB_DRIVER=usbhid

When I use evdev:atkbd:dmi:* as the device identifier instead the change is correctly applied to my laptop keyboard so I know the rule and the process I’m using to remap the keys should be correct, it’s got to be an issue with the wrong identifier (though I’ve quintuple checked it).

Any help will be appreciated.


Get this bounty!!!