I am having some troubles with a Prolific usb serial adapter not showing up in devices. I do see it in dom0 output when plugging it in however:
Dec 01 09:38:05 dom0 kernel: usb 1-9.1: USB disconnect, device number 20
Dec 01 09:38:05 dom0 kernel: pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
Dec 01 09:38:05 dom0 kernel: pl2303 1-9.1:1.0: device disconnected
Dec 01 09:38:16 dom0 kernel: usb 1-9.1: new full-speed USB device number 21 using xhci_hcd
Dec 01 09:38:16 dom0 kernel: usb 1-9.1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 4.00
Dec 01 09:38:16 dom0 kernel: usb 1-9.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 01 09:38:16 dom0 kernel: usb 1-9.1: Product: USB-Serial Controller D
Dec 01 09:38:16 dom0 kernel: usb 1-9.1: Manufacturer: Prolific Technology Inc.
Dec 01 09:38:16 dom0 kernel: pl2303 1-9.1:1.0: pl2303 converter detected
Dec 01 09:38:16 dom0 kernel: usb 1-9.1: pl2303 converter now attached to ttyUSB0
I need to have that device present, so I can attach it to a Windows 7 HVM standalone, which I use to support Ham Radio software in.
Thanks for any insight on this challenge and have a great day!
During the install, it was advised against since I have usb keyboard and mouse… should I install that sys-usb qube? Will it cause my HID’s to stop working?
Hmm, this install is production. Not sure I’m willing to risk getting locked out. It might be something that I test out with another NVME I have to swap with. Perhaps this weekend I might test…
On another note, are there any other means to get this prolific device handed off to the windows vm?
I have since reinstalled to a 2TB NVME and tested. Everything works fine. I have opted to skip USB keyboard support for LUKS passphrase, although I saw that was something that could be achieved as well.
With the addition of the sys-usb qube, I now see all the USB devices including the prolific serial adapter. I’m now ready to move on.
Thanks so much for your help, and have a great weekend everyone! See you around…