3 Oct
2019
3 Oct
'19
8:26 a.m.
Hello
Le mercredi 2 octobre 2019 22:26:17 CEST, vous avez écrit :
This is weird, I haven't seen this issue before.
Which USB host
controller are you using, which OS and which version of libusb?
This is with debian buster (=stable)
with libusb 1.0 :
libusb-1.0-0:amd64 version 2:1.0.22-2
What do you mean by USB Host Controller ?
I attached a few files
When connected to
rear USB 3.1gen1 : OK
rear USB 3.1gen2 : KO
front USB 2 : KO
front USB 3.1gen1 : KO
according to MB specs (asus PRIME b450M-a:
rear USB3.1 gen1 is controlled by CPU : Athlon200GE
the 3 other are controlled by chipset B450M
How often does this problem occur?
Quite often. For ex when running welle.io 2.0 beta3 the ferquency gets set
once and never changes again.
A way to get around it, is to call cancel_async before setting the frenquency.
But I have that error also without reading any data. with the sample test code
attached.
Regards