Raymond Wales

I have the same problem. These two things together (udev rules and symlinks) are a show-stopper. The platform is Orange Pi Pro 5. First, the udev script is extremely useful for pinning USB-serial devices to a specific name Second, the symlink mechanism is essential for presenting serial devices as "COMxx" in the Wine dosdevices folder. Here is my 48-ttyUSB.rules file, which links manufacturer-specific devices to "tty...." names: KERNEL=="ttyUSB0" SYMLINK+="%k" GROUP="ray" MODE="0666" KERNEL=="ttyUSB[0-9]*", SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", SYMLINK+="tty-F232" GROUP="ray" MODE="0666" KERNEL=="ttyUSB[0-9]*", SUBSYSTEM=="tty", ATTRS{interface}=="USB-COM485 Plus2", ATTRS{bInterfaceNumber}=="00", SYMLINK+="tty-F485A" GROUP="ray" MODE="0666" KERNEL=="ttyUSB[0-9]*", SUBSYSTEM=="tty", ATTRS{interface}=="USB-COM485 Plus2", ATTRS{bInterfaceNumber}=="01", SYMLINK+="tty-F485B" GROUP="ray" MODE="0666" KERNEL=="ttyUSB[0-9]*", SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", SYMLINK+="tty-Pro" GROUP="ray" MODE="0666" KERNEL=="ttyUSB[0-9]*", SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015", SYMLINK+="tty-CHIPIX" GROUP="ray" MODE="0666" This works perfectly on a range of Linux computers: all of them are Mint or Ubuntu, and all are on x86 hardware. As a further diagnostic in the Orange Pi/Armbian scene, any of the USB-serial adapters will come up as /dev/ttyUSB0. Any attempt to establish a symlink in ~.wine/dosdevices installs an entity which looks like a symlink, but which doesn't work: even trying to inspect Properties crashes out. Help please!