Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 04 Mar 2025 20:45:38 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 285083] emulators/wine-proton: request for port config option --with-udev for DualShock4 support
Message-ID:  <bug-285083-7788-rN6Mnbofny@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-285083-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-285083-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285083

Kevin Reinholz <kreinholz@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Closed
         Resolution|---                         |Works As Intended

--- Comment #4 from Kevin Reinholz <kreinholz@gmail.com> ---
(In reply to Stefan Schlosser from comment #3)

Per your reply, I set the following in /boot/loader.conf:

  usbhid_load=3D"YES"
  hw.usb.usbhid.enable=3D1

After a reboot, my DualShock4 is picked up by the usbhid driver instead of
uhid, and rebuilding wine-proton WITHOUT udev enabled causes Game Controlle=
rs
to show up in wine control, where I can verify button/joystick presses under
either DInput or XInput.

Interestingly, WITH udev enabled, Game Controllers doesn't show up in wine
control, even though the DualShock4 functions fine in games.

So if usbhid is enabled in the bootloader, I would say enabling udev is
unnecessary and actually a net negative. But I suppose if someone can't or
won't enable usbhid in the boot loader, then udev does indeed allow the
DualShock4 to function with the uhid driver.

Here's my dmesg output with uhid driver:

ugen0.7: <Sony Computer Entertainment Wireless Controller> at usbus0
uhid0 numa-domain 0 on uhub3
uhid0: <Sony Computer Entertainment Wireless Controller, class 0/0, rev
2.00/1.00, addr 6> on usbus0

And here's my dmesg output with usbhid driver:

ugen0.7: <Sony Computer Entertainment Wireless Controller> at usbus0
usbhid4 numa-domain 0 on uhub0
usbhid4: <Sony Computer Entertainment Wireless Controller, class 0/0, rev
2.00/1.00, addr 6> on usbus0
hidbus4: <HID bus> numa-domain 0 on usbhid4
hgame0: <Sony Computer Entertainment Wireless Controller Gamepad> numa-doma=
in 0
on hidbus4

To answer your question re Windows games, I don't run them through Steam. I
only have a couple of games I purchased through GOG, which I run directly
through wine-proton (using 32bit wine prefix, as they're old).

Thanks for pointing me in the right direction on this! I'm going to close t=
his
request, but maybe this conversation will prove helpful to a fellow
/boot/loader.conf minimalist who misses out on better gamepad support as a
result. (Or a brave soul who wants to try uhid + udev to try to use a DualS=
hock
with Steam).

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-285083-7788-rN6Mnbofny>