> This is how I have it in Raspbian as per the case that I am using for > RPI4. Regardless - I moved it under [cm4] and now dwc2 doesn't show up > at all, so I have moved it back to [all]
Ahhh! This is indeed expected. On the CM4, dwc2 is used for the type A ports on the IO board (and presumably a few other boards that the CM4 plugs into), so dwc2 in host mode is supported there. On the Pi4, dwc2 can *theoretically* be used in host mode, but defaults to device mode. However, operating it in host mode isn't an officially supported option (in other words, you can do it but if it breaks you get to keep the pieces). This thread (and in particular, the linked reply from one of the Pi engineers) is an interesting read on the subject: https://forums.raspberrypi.com/viewtopic.php?t=246348#p1504603 (and trejan's earlier reply about the CC pins) > ok so strange. All along I was doing a soft reboot. It just occurred > to me that since the ports are part of the USB-C (power port) - I > unplugged the power cable. And plugged it back in and now I can see > the ports! It does sound like something on that port got itself into a bad state and needed a hard-reset to get it back to a good one. IIRC (and I'm probably wrong on some of this), the Pi doesn't cut power to the USB-C port when being back-powered thru the GPIO pins and rebooted. By contrast I *think* in some board revisions (1.4 onwards?) the VL805 controller (for the type A ports) *does* get the power cut during part of the boot sequence (I have a vague recollection of this causing problems for USB booting at some point). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973648 Title: Raspberry Pi - Ubuntu Jammy - USB Not Working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1973648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
