Erling,
:) can happen to anyone. I supposed there was something like this going
on as if usbhidctl shows the keys, there's basically no way for
usbhidaction not to work for some internal issue as uhid devices are
sort of character pseudo-devices and you can even read some keypress
events with doas
Stupid me. The keyboard is working! For some reason I don't yet
understand, the usbhidaction(1) config file I created was set to "dos"
by vim(1) early in the process. Perhaps I copied in something I found on
the web. Anyway; hidden ^M's prevented mixerctl command executions, and
moreover; when Anat
On Thu, Oct 03, 2019 at 03:08:54PM -0300, Anatoli wrote:
> Hi Erling,
Hi Anatoli, sorry for the late reply. Your answer somehow ended up in
in Gmail spam.
> Your problem is probably with the page name. Check it with usbhidctl -r
> -f /dev/uhid0 (the value you're interested in is what is shown for
Hi Erling,
Your problem is probably with the page name. Check it with usbhidctl -r
-f /dev/uhid0 (the value you're interested in is what is shown for
"Collection page").
Also, it's probably required for the actions to go on new lines in the
action config. And for dubugging I'd use something like
Hi,
I am unable to get the four multimedia keys (Play/Pause, Volume
Decrement/Increment, Mute) on my old'ish USB Microsoft Wired Keyboard
600 to respond.
I have tried to do my homework by reading man pages, like
usbhidaction(1) and usbhidctl(1), and I've been looking at how-tos on
the net [1], but
5 matches
Mail list logo
