Arch Linux User Repository

Explanation: Winesync is yet another reimplementation of the NT synchronization primitives for Wine, this time using a new kernel module instead of using existing kernel features or a new syscall. This implementation mimics the original from Windows perfectly (bar any bugs), in contrast to esync and fsync which had some hackily implemented operations. Performance shouldn't be much different from esync and fsync.

Why this package depends on linux-headers instead of dkms?

For those who haven't found out themselves yet I think everyones moving to this instead now:

https://aur.archlinux.org/packages/ntsync-header

https://aur.archlinux.org/packages/ntsync-dkms

https://aur.archlinux.org/packages/ntsync-common

I think

I can't seem to get this to work, I'm guessing I need a patched version of wine or proton to use this? And I read somewhere TKG doesn't include it anymore?

Does Proton GE support it?

Information about how to use this is extremely scarce...

Looks like the site is back online.

Same issue here, source URL is inaccessible (https://repo.or.cz/).

Thanks again for this and making it (much!) easier to get working on Arch Linux. I finally got bit further with this. I started using wine-tkg (self-built) instead of wine-ge-custom which has enabled me to enable winesync in wine.

Everything works great with the module but not the udev rule for some reason? Its installed but I still have to manually chmod /dev/winesync before launching wine.

I am wondering if the winesync module is coming up later than when udev runs or something odd...

More details:

$ sudo udevadm test /dev/winesync
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

Trying to open "/etc/systemd/hwdb/hwdb.bin"...
Trying to open "/etc/udev/hwdb.bin"...
Trying to open "/usr/lib/systemd/hwdb/hwdb.bin"...
Trying to open "/usr/lib/udev/hwdb.bin"...
=== trie on-disk ===
tool version:          253
file size:        12343334 bytes
header size             80 bytes
strings            2504246 bytes
nodes              9839008 bytes
Loading kernel module index.
Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
Found container virtualization none.
Using default interface naming scheme 'v253'.
Parsed configuration file "/usr/lib/systemd/network/99-default.link"
Created link configuration context.
Reading rules file: /usr/lib/udev/rules.d/01-md-raid-creating.rules
Reading rules file: /usr/lib/udev/rules.d/10-dm.rules

.. blahblahblah ..

Reading rules file: /usr/lib/udev/rules.d/99-fuse.rules
Reading rules file: /usr/lib/udev/rules.d/99-fuse3.rules
Reading rules file: /usr/lib/udev/rules.d/99-razer.rules
Reading rules file: /usr/lib/udev/rules.d/99-systemd.rules
Reading rules file: /usr/lib/udev/rules.d/99-winesync.rules
sd-device: Failed to chase symlinks in "/sys/dev/char/10:243".
sd-device: Failed to chase symlinks in "/sys/dev/winesync".
Failed to open device '/dev/winesync': No such device
Unload kernel module index.
Unloaded link configuration context.

$ ls -lah /dev/winesync 
crw------- 1 root root 10, 243 Apr  5 21:16 /dev/winesync

Edit: Running:

modprobe winesync

makes everything just work.... could the solution be to add a file to '/etc/modules-load.d/' or ideally '/usr/lib/modules-load.d/' in the package? or should wine be starting this module when it launches? (it doesn't).

Yeah you are right - something weird happened. I've not even heard of winesync for two years but I think I cloned 'winesync-dkms' last time although I'm not sure why it would cause that since it looks like a clone.

Weird...

I've re-cloned and its built fine with the correct version. Apologies for the noise

@rlees85 You haven't updated your clone of this package in almost two years, please build an up-to-date version of the package.

Seems broken...

$ makepkg -s
==> Making package: winesync-dkms 5.11-6 (Wed 22 Feb 2023 22:49:03 GMT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading winesync.c-e97dfb6b3ee6792cd1fe8242df4dafd8f10cca99...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://repo.or.cz/linux/zf.git/blob_plain/e97dfb6b3ee6792cd1fe8242df4dafd8f10cca99:/drivers/misc/winesync.c
    Aborting...

Wondering if it works with wine-ge but I am happy to find that out myself once it is possible to build it

@Hakkaten: You will need a version of wine that actually supports it and I don't think many actually do. Infact I'm finding little conclusive information online - you'd probably need to build wine yourself to take advantage of it. If you read this though you can see if or not your version of Wine is actually using it: https://github.com/Cat-Lady/winesync-dkms

Is having this installed all I need to do to make use of it? Will any Wine on my system take advantage of this without any tweaking on my part? Just discovered this when I was browsing wine packages, I use CachyOS and their repos have this.