Docs: update hardware compatibility notes

Author: xlz

README.md

@@ -26,6 +26,8 @@ No. It's a pure USB3 device due to the high bandwidth requirements.
 
 Either your device is connected to an USB2-only port (see above), or you don't have permissions to access the device. On Linux, try running Protonect as root (e.g. using `sudo`). If that fixes things, place `rules/90-kinect2.rules` into `/etc/udev/rules.d/` and re-plug the device.
 
+On Linux, also check `dmesg`. If there are warnings like `usb 4-1.1: Not enough bandwidth for new device state.` it means the hardware does not have the capacity for USB3 even if it claims so, or its capacity is not well supported.
+
 On Mac OS X, open "System Information" from Spotlight, go to the USB section, and verify "Xbox NUI Sensor" is under "USB 3.0 SuperSpeed Bus" not "High-Speed Bus". If this is not the case, try unplugging the Kinect from power source with the USB cable connected, and plug the power again, then verify.
 
 ### I'm getting lots of USB transfer errors, and/or only blank windows.
@@ -37,6 +39,13 @@ USB3 as a whole is a flaky thing. If you're running Linux, try upgrading to a re
 
 Probably not working:
 * ASMedia Technology Inc. Device 1142
+* ASMedia Technology Inc. ASM1042
+
+Messages in `dmesg` like this means bugs in the USB driver. Updating kernel might help.
+```
+[  509.238571] xhci_hcd 0000:03:00.0: xHCI host not responding to stop endpoint command.
+[  509.238580] xhci_hcd 0000:03:00.0: Assuming host is dying, halting host.
+```
 
 Finally, it's also possible that your executable is not actually using the patched libusb from the depends/ folder which is required at the moment. Check this using `ldd | grep libusb` (shows libusb-1.0 under `depends/`), and adjust your `LD_LIBRARY_PATH` if necessary.