Hi Alan
On 11. 03. 24 15:43, Alan Stern wrote:
Well, at least this means you do have a way of using the device, even
if it is rather awkward. It might even work on the Raspberry Pi machine.
Still, I'm looking for a more permanent and robust solution. If it were
only a single device I'm using myself, I could come up with a
workaround. However, this is one of the very few available Z-Wave USB
interfaces and there are more users affected. So far we went with
reverting the patches, but that's surely not the way we want to go forward.
The device is so non-responsive, I'm amazed it ever works at all.
Judging by the usbmon traces, it doesn't look as if it would work on a
Windows system.
Actually, if you have access to a computer running Windows or Mac OSX
and you can try out the device on that computer, it would be good to
get the equivalent of a usbmon trace (something like a Wireshark
capture log would do). If those systems manage to do something that
Linux doesn't, we ought to know what it is.
Fredrik (one of the original reporters) is following this conversation,
here [1] are logs from his machine with some details in the ticket [2].
He also wonders why the initialization doesn't work only on USB2 ports
but works on USB3 if the initialization code is shared between those two.
Also, if needed, I can get more logs from the X220 I was using for my
usbmon traces - I believe I have an HDD with Windows 7 install lying
somewhere.
Regards,
Jan
[1]
https://github.com/home-assistant/operating-system/files/14563813/usbPcap1_USB2-port.txt
[2]
https://github.com/home-assistant/operating-system/issues/2995#issuecomment-1989329739
