Vesion 1.6 : illegal instruction 4, the AVX2 case for old CPU

[DasFicus]

Hello, I have been a user of DisplayLink products since 2011.
Back then, I used a USB 2 to DVI adapter, a PCMCIA to DVI card, and a Kensington USB 2 docking station with DVI output on an old laptop; everything worked perfectly.

Recently, I decided to purchase a new StarTech USB 3.0 (Type-A) docking station with dual DVI output.
I attempted to install the latest version of the software, granting "Screen Recording" permissions and following all the recommendations in the user manual.

With version 1.6.x, I was unpleasantly surprised to find that the application would not launch; system logs indicated an "ILLEGAL INSTRUCTION 4" error.

When reverting to version 1.5.x, the application opens and correctly detects the device, but no image is displayed, no screen in system preferences, tryed option key + button "detect screen" too do nothing.

When trying with my old Kensington dock (which used to work very well), an image appears briefly for two seconds, and then the screen loses the video signal.

I analyzed the situation:
- version 1.6 uses the compiler's default processor optimizations (for a 2013 processor with AVX2);
- version 1.5 uses the compiler's default processor optimizations (for a 2009 processor with AVX).

However, I have a processor from 2010 that does not support AVX2.
- Try on old CPU from 2010 with MacOS Sequoia (as Host), no video at all, no screen detected, no option on DisplayManager.
- Try on old CPU from 2010 with Windows 11 (as VM on MacOS), it works 3 screens.
- Try on old CPU from 2010 with Linux, doing fine.

The use of AVX2 is an option within the developers' build system, and I have noticed that this trend is becoming widespread among developers today.

Configuration : MacOS Sequoia, Intel X5690, USB3

There have a lack of support for MacOS ...
PS: i'm Freelance Sofware Developper, so i can build and provide what lack on MacOS support

[Szymon]

Hello,

While we appreciate the detailed analysis, the reported configuration is outside our supported SW/HW matrix. The issue is observed on unsupported hardware running an unsupported OS configuration using DisplayLink Manager versions that do not support Sequoia. As such, the report cannot be used as evidence of a macOS Sequoia compatibility issue in supported environments.

Regards,
Szymon