Hi Forum. I would like to figure out why I have about a 50% chance of having this laptop recognize AD3 when I first connect provided USB cable to one of the Thunderbolt 4 ports. If not recognized I see the following:
Quote
[425340.653069] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[425344.749443] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[425344.749651] usb usb2-port3: attempt power cycle
[425349.157601] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[425353.245976] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[425353.246202] usb usb2-port3: unable to enumerate USB device
at which point I wait a few seconds and unplug and replug and deal with the same 50% chance again. Eventually AD3 is recognized and kernel ring buffer shows the following:
Quote
[425429.542535] usb 3-4: new high-speed USB device number 30 using xhci_hcd
[425429.768413] usb 3-4: New USB device found, idVendor=1443, idProduct=7003, bcdDevice= 9.00
[425429.768424] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[425429.768428] usb 3-4: Product: Digilent USB Device
[425429.768431] usb 3-4: Manufacturer: Digilent
[425429.768434] usb 3-4: SerialNumber: 210415B9A169
I've had similar issues with other devices on this laptop ( showing the same "Maybe the USB cable is bad" error ) on this laptop and have zero suspicion this is an AD3 issue. But I mention here on the chance that somebody in forum might know of this problem ( e.g. Linux has not so great Thunderbolt 4 drivers or USB 2/3 support over Thunderbolt 4 is wonky...).
This same configuration will also occasionally reveal an overcurrent dialog after sleeping with no supplies/waveforms enabled which is most likely related. Screenshot of that image below.
Question
nurber3
Hi Forum. I would like to figure out why I have about a 50% chance of having this laptop recognize AD3 when I first connect provided USB cable to one of the Thunderbolt 4 ports. If not recognized I see the following:
at which point I wait a few seconds and unplug and replug and deal with the same 50% chance again. Eventually AD3 is recognized and kernel ring buffer shows the following:
I've had similar issues with other devices on this laptop ( showing the same "Maybe the USB cable is bad" error ) on this laptop and have zero suspicion this is an AD3 issue. But I mention here on the chance that somebody in forum might know of this problem ( e.g. Linux has not so great Thunderbolt 4 drivers or USB 2/3 support over Thunderbolt 4 is wonky...).
This same configuration will also occasionally reveal an overcurrent dialog after sleeping with no supplies/waveforms enabled which is most likely related. Screenshot of that image below.
Thank you.
Link to comment
Share on other sites
2 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now