Christopher Schramm

You're welcome. :slightly_smiling_face: That message is totally expected as the module is not signed. It's locally built and taints the kernel anyway. I'd actually also expect `irda: loading out-of-tree module...

Perfect, I already wanted to suggest trying an old kernel for comparison. irda-utils might be a source of problems. Using the irda-utils 0.9.18-15ubuntu1 package should be fine, but the `make...

The udev logs clearly indicate that it calls irattach as expected. The second installation always shows the following for that call: ``` executing: '/sbin/modprobe irda0' executing: 'echo DMLaptop > /proc/sys/net/irda/devname'...

Just checked the `irattach` code. The `socket` call should absolutely not fail after `irda` was loaded and the kernel emitted `NET: Registered PF_IRDA protocol family`. It's completely independent of the...

> It gives however the same socket(AF_IRDA) error. > > > The socket(AF_IRDA) errors surprise me. Do you see the same a) when calling irattach manually and b) in Ubuntu...

I think you're absolutely right that you have to set up a custom device mapping in Wine, see https://wiki.winehq.org/index.php?title=Wine_User's_Guide#Serial_and_Parallel_Ports. I tested a trial version of Polar ProTrainer and it seems...

Yeah, running `wine` with `WINEDEBUG=+file` is probably much more helpful here then `strace`. It seems like the connections just might not work as expected in recent wine (out of the...

`CreateFileW` visible when running with `WINEDEBUG=+file`

Aha, it's via sockets. From a quick glance at the Wine code, I'm surprised that Com1 has any influence on that at all. It looks like sockets just get translated...

By the way: `SampleIrDAService` made my day. That name is directly from the Microsoft socket examples. :laughing: