mpons

Members
  • Content Count

    1
  • Joined

  • Last visited

  1. Hi, I've had similar problems with my C2. USB would not power up any device except the internal hub. The above workaroud seems to work for me. Questions : Considering this : dmesg [...] [ 2.804560] phy phy-c0000020.phy.1: Linked as a consumer to regulator.3 [ 2.804955] dwc2 c9000000.usb: c9000000.usb supply vusb_d not found, using dummy regulator [ 2.805002] dwc2 c9000000.usb: Linked as a consumer to regulator.0 [ 2.805009] dwc2 c9000000.usb: c9000000.usb supply vusb_a not found, using dummy regulator [ 2.806314] phy phy-c0000000.phy.0: USB ID detect failed! [ 2.806322] phy phy-c0000000.phy.0: phy poweron failed --> -22 [ 2.806395] dwc2: probe of c9000000.usb failed with error -22 [ 2.806604] dwc2 c9100000.usb: c9100000.usb supply vusb_d not found, using dummy regulator [ 2.806627] dwc2 c9100000.usb: Linked as a consumer to regulator.0 [ 2.806633] dwc2 c9100000.usb: c9100000.usb supply vusb_a not found, using dummy regulator [ 2.867643] dwc2 c9100000.usb: dwc2_check_params: Invalid parameter lpm=1 [ 2.867648] dwc2 c9100000.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [ 2.867651] dwc2 c9100000.usb: dwc2_check_params: Invalid parameter besl=1 [ 2.867655] dwc2 c9100000.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [...] I wonder if this patch is actually applied in the latest armbian version (I expect not seeing the latest github commit, but I can really tell) https://patchwork.kernel.org/patch/10785943/ On a side note I also have another dmesg error but inconsistent (not on every boot sequence) [ 19.535969] meson-i2s-dai meson-i2s-dai.0.auto: Unable set to set i2s description [ 19.535980] meson-i2s-dai meson-i2s-dai.0.auto: ASoC: can't set meson-i2s-dai.0.auto hw params: -22 This is repeated 20 times Best,