rdpeake

Members
  • Content Count

    2
  • Joined

  • Last visited

  1. Having run the latest master - which uses kernel 5.0 i was able to get the usb 3.0 hub to register and respond to the connected device. however, i still see the above errors in the dmesg log. On top of that - booting with a device connected to the usb 3.0 socket can cause the device to not boot, until reinstalling the sd card is done (didn't connect a serial monitor at the time so don't have boot logs associated with that unfortunately)
  2. Hey all, I understand these things are in active development at the moment. I was attempting to use the usb 3.0 socket on the lite 2 with stretch, except it did not respond at all - looking at dmesg shows the following error: [ 1.806055] sun4i-usb-phy 5100400.phy: Couldn't get regulator usb0_vbus... Deferring probe [ 1.806320] sun50i-usb3-phy 5210000.phy: failed to get phy clock which from my limited experience with linux kernel seems to indicate that the device tree config may be incorrect for the board - as most searching for these errors show the code added as part of updates to get the pine64 board's usb 3.0 stack working. USB 2.0 socket is working on the board. if need be i can test nightly's (i don't have a linux environment to hand to compile a kernel myself, and i do have a serial device i can connect to get raw output - just need to look up pinouts to ensure i connect it correctly). link to full dmesg if it is useful: https://pastebin.com/4vJDxk9N