Udevadm trigger fails

[portapro]

Hi,

for a couple of months now, my Nvidia Shield bluetooth remote is not pairing at boot. I was working fine before. I discarded an hardware issue since it works fine on another device. I tried Enable standby, I thought it worked at first, but no, the issue is still there.

In trying to refresh the nvidia.hwdb, I get this error :

CoreELEC:~ # systemctl stop kodi
CoreELEC:~ # udevadm trigger -s input
input4: Failed to write 'change' to '/sys/devices/platform/fe084040.meson-remote/input/input4/uevent': Cannot allocate memory

touch works on that file, so I guess it’s not a filesystem issue. Here’s the device list, input4 points to ir_keypad :

CoreELEC:~ # cat /proc/bus/input/devices
I: Bus=0010 Vendor=0001 Product=0001 Version=0100
N: Name="input_ethrcu"
P: Phys=input_ethrcu/input0
S: Sysfs=/devices/platform/soc/fdc00000.ethernet/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=20 10000000000000 0

I: Bus=0010 Vendor=1b8e Product=0cec Version=0001
N: Name="cec_input"
P: Phys=
S: Sysfs=/devices/virtual/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10800000 0 1 10000 117840000000 1e168000000000 10008002

I: Bus=0010 Vendor=0001 Product=0001 Version=0100
N: Name="input_btrcu"
P: Phys=input_btrcu/input0
S: Sysfs=/devices/platform/aml_bt/input/input2
U: Uniq=
H: Handlers=kbd event2
B: PROP=0
B: EV=3
B: KEY=20 10000000000000 0

I: Bus=0010 Vendor=0001 Product=0001 Version=0100
N: Name="vad_keypad"
P: Phys=vad_keypad/input3
S: Sysfs=/devices/platform/soc/fe330000.audiobus/fe330000.audiobus:vad/input/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=3
B: KEY=1 0 0 10000000000000 0

I: Bus=0010 Vendor=0001 Product=0001 Version=0100
N: Name="ir_keypad"
P: Phys=keypad/input0
S: Sysfs=/devices/platform/fe084040.meson-remote/input/input4
U: Uniq=
H: Handlers=sysrq rfkill kbd mouse0 event4
B: PROP=0
B: EV=7
B: KEY=ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffff00000000 70000 ffffffffffffffff ffffffffffffffff ffffffffffffffff fffffffffffffffe
B: REL=103

I: Bus=0005 Vendor=0955 Product=7217 Version=0002
N: Name="NVIDIA SHIELD Remote"
P: Phys=b8:13:32:fa:c9:37
S: Sysfs=/devices/virtual/misc/uhid/0005:0955:7217.0001/input/input5
U: Uniq=48:b0:2d:38:b5:b1
H: Handlers=kbd event5
B: PROP=0
B: EV=1b
B: KEY=10000 11040000000 1c168000000000 4204010800000
B: ABS=10000000000
B: MSC=10

Any clue on what’s going on ?

[portapro]

Still no clue on what happened but I solved both issues. It appears the two things were not correlated. I solved the udevadm trigger by restoring an old backup. For the Shield remote though, it was even stranger, I paired it again with the Nvidia Shield itself, then unpaired, then re-paired again with the CE box and now it works like a charm.