Kai-Heng: I just tested your kernel, but it didn't solve the keyboard
issue. However, it seemed to screw up the mouse, which of course has the
same vendor and device id, since they operate through the same usb
connector. With this kernel the mouse was making large erratic jumps and
generating click
Ok, I think I understand how to add IDs to the code. What should I do
with the modified code? Commit and do a pull request?
Should I only add the ID for the keyboard that I have and can test (the
HP one) or should I also add the other ones?
While researching the problem, I also found someone else
@Tj
"Currently the driver only supports the device ID 0461:4e05 and will
need the IDs of other devices adding in order to work with them."
Here are device IDs for a few models that I have found among the many
reports of similar problems with Primax wireless keyboard + mouse
combos:
0461:60a9 - L
3 matches
Mail list logo
