I've been using this gamepad with numerous FreeBSD versions for years and at some point in the past year it stopped working. It's seen but then immediately disconnects:
Jul 20 15:09:21 coral kernel: ugen0.2: <Logitech Logitech Dual Action> at usbus0
Jul 20 15:09:21 coral kernel: uhid1 on uhub2
Jul 20 15:09:21 coral kernel: uhid1: <Logitech Logitech Dual Action, class 0/0, rev 1.10/3.00, addr 12> on usbus0
Jul 20 15:09:21 coral kernel: uhid1: at uhub2, port 4, addr 12 (disconnected)
Jul 20 15:09:21 coral kernel: uhid1: detached
Problem is the same on 11.2-RELEASE and 12.0-RELEASE.
FreeBSD coral.acadix.biz 12.0-RELEASE-p6 FreeBSD 12.0-RELEASE-p6 GENERIC amd64
It still works on my PowerMac G5:
ugen2.2: <Logitech Logitech Dual Action> at usbus2
uhid0 on uhub2
uhid0: <Logitech Logitech Dual Action, class 0/0, rev 1.10/3.00, addr 2> on usbus2
FreeBSD powermacg5.acadix bacon ~ 482: hexdump /dev/uhid0
[ move left joystick ]
0000000 807f 807f 0800 04fc 807d 807f 0800 04fc
0000010 8679 807f 0800 04fc 8d77 807f 0800 04fc
0000020 8977 807f 0800 04fc 8477 807f 0800 04fc
0000030 8077 807f 0800 04fc 807b 807f 0800 04fc
FreeBSD powermacg5.acadix.biz 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC powerpc
The problem goes away on all systems if I remove or comment out the following in /etc/rc.conf:
I do not need to stop the service, just edit rc.conf and the problem immediately ceases.
Likely webcamd attaches and create /dev/input/evdevX devices.
Thanks for the suggestion, but nope:
ugen0.4: <Logitech Logitech Dual Action> at usbus0 (disconnected)
ugen0.4: <Logitech Logitech Dual Action> at usbus0
uhid1 on uhub0
uhid1: <Logitech Logitech Dual Action, class 0/0, rev 1.10/3.00, addr 9> on usbus0
uhid1: at uhub0, port 4, addr 9 (disconnected)
<<<ROOT@coral.acadix>>> /home/bacon 1046 # ls /dev/input/
FYI, this happens on systems with or without webcam hardware.
That is the expected behaviour.
I'm not clear what you mean by expected behavior. Did you mean /dev/eventX rather than /dev/evdevX?
The js0 and event0 device is for your webcamd supported device. Currently there is no blacklisting of devices webcamd should not attach to.
When webcamd attaches it will detach other kernel drivers like uhid.
But this system doesn't have a webcam. Are you saying webcamd will attach to my gamepad and push the uhid driver out of the way in the process? I.e. webcamd considers a gamepad to be a supported device?
webcamd is for multiple USB based devices. Not just webcams. See "make config" in /usr/ports/multimedia/webcamd .
I see now... Maybe time for a name change? I never would have imagined that a daemon called webcamd would support my gamepad. Thanks.