Hi
I'm new to Wine. I installed Wine 6.0 in hope that the new USB drivers would work with a Windows software called PCLinq5 for connecting two PC's via a USB bridge-cable. I can run PCLinq5 in Wine, but it can't "see" the USB device.
How do I "forward" the USB so it can be accessed via Wine 6.0? The USB doesn't seem to show up as a 'serial device', at least I can't see any /dev/ttyUSB on my pc.
The USB bridge cable is a Startech USBLink3, PL27A1. It can easily be used between two Linux computers or two Windows computers, but not between a Linux and a Windows computer. Was hoping Wine could solve that by running PCLinq5 on Linux.
Using Ubuntu 20.04.
Thanks
Kris
Access USB in Wine 6.0?
Re: Access USB in Wine 6.0?
If it's supposed to be a serial device over USB you probably need the linux usb to serial driver. Please have the device connected and post the output of and the output of . This should show (1) if the device has a driver and (2) the details of the manufacture/device codes for the device. Can work from that to give you a suggestion to try.
Please keep in mind I'm just a novice here so someone with so much knowledge than I can ever hope for may post back.
Code: Select all
lsusb -t
Code: Select all
lsusb
Please keep in mind I'm just a novice here so someone with so much knowledge than I can ever hope for may post back.
Re: Access USB in Wine 6.0?
Hi
Thanks a lot for the response.
This device (Prolific Technology, Inc. USB-To-USB Cable Bridge) uses 'winusb' driver in Windows. I was hoping that the new USB kernel drivers in Wine 6.0 would support 'winusb' devices, but I might be wrong.
and
I found that when plugging in the device it automatically uses the linux drivers/modules 'usbnet' http://www.linux-usb.org/usbnet/ and 'plusb' http://www.linux-usb.org/USB-guide/x555.html. I tried to blacklist those to see if 'wineusb' would pick it up, but didn't help.
Thanks a lot for the response.
This device (Prolific Technology, Inc. USB-To-USB Cable Bridge) uses 'winusb' driver in Windows. I was hoping that the new USB kernel drivers in Wine 6.0 would support 'winusb' devices, but I might be wrong.
Code: Select all
lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
|__ Port 3: Dev 5, If 0, Class=Vendor Specific Class, Driver=, 5000M
|__ Port 3: Dev 5, If 1, Class=Mass Storage, Driver=usb-storage, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 7: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 7: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 8: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 8: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
Code: Select all
lsusb
Bus 002 Device 005: ID 067b:27a1 Prolific Technology, Inc. USB-To-USB Cable Bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f2:b52c Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Code: Select all
dmesg | grep 'USB'
[ 0.424253] ACPI: bus type USB registered
[ 1.017366] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.017428] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.017475] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.448694] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[ 1.450309] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08
[ 1.450310] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.450543] hub 1-0:1.0: USB hub found
[ 1.453421] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[ 1.453423] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
[ 1.453454] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.08
[ 1.453455] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.453570] hub 2-0:1.0: USB hub found
[ 1.788336] usb 1-7: new full-speed USB device number 2 using xhci_hcd
[ 1.942715] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b, bcdDevice= 0.01
[ 1.942721] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.068293] usb 2-3: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 2.104540] usb 2-3: New USB device found, idVendor=067b, idProduct=27a1, bcdDevice= 1.00
[ 2.104545] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.104548] usb 2-3: Product: USB-To-USB Cable Bridge
[ 2.118818] usb-storage 2-3:1.1: USB Mass Storage device detected
[ 2.216236] usb 1-8: new high-speed USB device number 3 using xhci_hcd
[ 2.416943] usb 1-8: New USB device found, idVendor=04f2, idProduct=b52c, bcdDevice= 0.29
[ 2.416948] usb 1-8: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 3.131690] scsi 2:0:0:0: Direct-Access USB 3.0 SD Card Reader 1.00 PQ: 0 ANSI: 0
[ 7.402062] USB Video Class driver (1.1.1)
[ 82.184865] usb 2-3: USB disconnect, device number 2
[ 92.096371] usb 2-3: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 92.133900] usb 2-3: New USB device found, idVendor=067b, idProduct=27a1, bcdDevice= 1.00
[ 92.133908] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 92.133913] usb 2-3: Product: USB-To-USB Cable Bridge
[ 92.138663] usb-storage 2-3:1.1: USB Mass Storage device detected
[ 93.142977] scsi 2:0:0:0: Direct-Access USB 3.0 SD Card Reader 1.00 PQ: 0 ANSI: 0
[ 565.981777] usb 2-3: USB disconnect, device number 3
[ 727.971750] usb 2-3: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[ 728.009544] usb 2-3: New USB device found, idVendor=067b, idProduct=27a1, bcdDevice= 1.00
[ 728.009552] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 728.009558] usb 2-3: Product: USB-To-USB Cable Bridge
[ 728.013645] usb-storage 2-3:1.1: USB Mass Storage device detected
[ 729.034879] scsi 2:0:0:0: Direct-Access USB 3.0 SD Card Reader 1.00 PQ: 0 ANSI: 0
[ 745.423122] usb 2-3: USB disconnect, device number 4
[19178.680321] usb 2-3: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[19178.716899] usb 2-3: New USB device found, idVendor=067b, idProduct=27a1, bcdDevice= 1.00
[19178.716908] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[19178.716914] usb 2-3: Product: USB-To-USB Cable Bridge
[19178.720982] usb-storage 2-3:1.1: USB Mass Storage device detected
[19179.731174] scsi 2:0:0:0: Direct-Access USB 3.0 SD Card Reader 1.00 PQ: 0 ANSI: 0
Re: Access USB in Wine 6.0?
You mentioned not showing as a serial device. From what I could find on the net it doesn't appear as a serial device but rather as a high speed USB device. winusb is a Windows platform driver. I could be wrong, but I don't believe device drivers for Windows work in wine because wine is using the linux device and hence the linux driver. If the Windows program is written to actually "talk" to winusb then it won't work. Any tech documentation for the program online that I could look at?
On Windows does it show as a USB or a serial device?
On Windows does it show as a USB or a serial device?
Re: Access USB in Wine 6.0?
Hi
Yes in Windows it shows as using 'winusb'. I was under the impression that the new USB kernel ('wineusb'?) would detect 'winusb'-devices, but I could have misinterpreted that. Here is the specification https://prolificusa.com/app/uploads/201 ... PL27A1.pdf
Article from Phoronix wineusb vs winusb https://www.phoronix.com/scan.php?page= ... usb-Merged
Thanks for helping me.
Yes in Windows it shows as using 'winusb'. I was under the impression that the new USB kernel ('wineusb'?) would detect 'winusb'-devices, but I could have misinterpreted that. Here is the specification https://prolificusa.com/app/uploads/201 ... PL27A1.pdf
Article from Phoronix wineusb vs winusb https://www.phoronix.com/scan.php?page= ... usb-Merged
Thanks for helping me.
Re: Access USB in Wine 6.0?
It looks like in Windows it uses an interface WET - Windows Easy Transfer. I couldn't find a linux equivalent, however it does look like linux is seeing you device correctly
At lear rhar what I *think* it is showing. Given that, I *think* it is recognizing it here as well: The lsusb -t does show a driver:
So. how to access it? Not sure. Does anything show in the linux version of file manger as a new device? I would think that since it is showing the driver as usb-storage that maybe it might show as a device or maybe under network. Either way you'll need both devices connect on the cable to see.
Also, I can find no reference to "wineusb" on my pc. Doen't show as a module, does show as a loadable module and it isn't in the default repositories in linux mint anywhere that i can find. i'll keep looking. in the mean try connecting a device to each end of the cable and check as per above
Having read a little about PCLinq software and found it looks like a graphical ssh session. to that end, it might be possible to install a graphical shh app such as putty on the Windows pc and on the linux pc, set them up according to each machines tcpip address and skip trying to use it in wine - it would be a native app.
Code: Select all
[ 82.184865] usb 2-3: USB disconnect, device number 2
[ 92.096371] usb 2-3: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 92.133900] usb 2-3: New USB device found, idVendor=067b, idProduct=27a1, bcdDevice= 1.00
[ 92.133908] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 92.133913] usb 2-3: Product: USB-To-USB Cable Bridge
[ 92.138663] usb-storage 2-3:1.1: USB Mass Storage device detected
[
Code: Select all
|__ Port 3: Dev 5, If 0, Class=Vendor Specific Class, Driver=, 5000M
|__ Port 3: Dev 5, If 1, Class=Mass Storage, Driver=usb-storage, 5000M
Also, I can find no reference to "wineusb" on my pc. Doen't show as a module, does show as a loadable module and it isn't in the default repositories in linux mint anywhere that i can find. i'll keep looking. in the mean try connecting a device to each end of the cable and check as per above
Having read a little about PCLinq software and found it looks like a graphical ssh session. to that end, it might be possible to install a graphical shh app such as putty on the Windows pc and on the linux pc, set them up according to each machines tcpip address and skip trying to use it in wine - it would be a native app.