I have never seen that kind of log before. It's coming from the composite driver, which means the device interfaces are never made available on the system.
Our driver does not even get a chance to connect to the device, so we can only focus on the device, the cable or the OS.
To check the device you could try a different computer. The cable is unlikely to be the problem: would be a rare coincidence to always fail at that stage.
The OS might be the problem since you are mentioning that this issue did not happen with a different version. I have not seen this reported elsewhere so you may have an issue. I'd repair permissions and if fails reinstall on top of the current OS.
Any other ideas welcome.
Carlo
|