On Friday, April 19, 2024 3:46:07 PM CDT Elizabeth Figura wrote:
On Friday, 19 April 2024 11:16:11 CDT Peter Zijlstra wrote:
On Tue, Apr 16, 2024 at 05:18:56PM -0500, Elizabeth Figura wrote:
On Tuesday, 16 April 2024 16:18:24 CDT Elizabeth Figura wrote:
On Tuesday, 16 April 2024 03:14:21 CDT Peter Zijlstra wrote:
I don't support GE has it in his builds? Last time I tried, building Wine was a bit of a pain.
It doesn't seem so. I tried to build a GE-compatible ntsync build, uploaded
here (thanks Arek for hosting):
https://f002.backblazeb2.com/file/wine-ntsync/ntsync-wine.tar.xzOops, the initial version I uploaded had broken paths. Should be fixed now.
(It's also broken on an unpatched kernel unless explicitly disabled with
WINE_DISABLE_FAST_SYNC=1. Not sure what I messed up there—it should fall back
cleanly—but hopefully shouldn't be too important for testing.)
So I've tried using that wine build with lutris, and I can't get it to start EGS or anything else.
I even added a printk to the ntsync driver for every open, to see if it gets that far, but I'm not even getting that :/
That's odd, it works for me, both as a standalone build and with lutris...
Does /dev/ntsync exist (module is loaded) and have nonzero permissions? I forgot to mention that's necessary, sorry.
Otherwise I can try to look at an strace, or a Wine debug log. I don't think there's an easy way to get the latter with Lutris, but something like `WINEDEBUG=+all ./wine winecfg 2>log` should work.
It's also possible I made that build against a too-new distribution. I've created a new build against Debian 12, which is hopefully better, and it has some extra debug logging:
https://f002.backblazeb2.com/file/wine-ntsync/ntsync-wine2.tar.xz
Hopefully that's functional enough to test with, or at least give more a hint as to why it doesn't work?