[Bug 1973648] Re: Raspberry Pi - Ubuntu Jammy - USB Not Working
** Changed in: linux-raspi (Ubuntu) Status: Incomplete => Invalid -- 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
[Bug 1973648] Re: Raspberry Pi - Ubuntu Jammy - USB Not Working
Hi No none of the attached USB Devices are self powered. But I have done a few soft reboot and the issue is no longer there. -- 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
[Bug 1973648] Re: Raspberry Pi - Ubuntu Jammy - USB Not Working
Is one of your attached USB devices self-powered (i.e. has its own power supply)? Maybe the Pi was somehow back-powered that way and a soft reset didn't fully reset some devices on the Pi. -- 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
[Bug 1973648] Re: Raspberry Pi - Ubuntu Jammy - USB Not Working
> 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
[Bug 1973648] Re: Raspberry Pi - Ubuntu Jammy - USB Not Working
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! pi@raspberrypi:/opt$ lsusb Bus 003 Device 004: ID 1a86:7523 QinHeng Electronics CH340 serial converter Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 17ef:608d Lenovo Optical Mouse Bus 001 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@raspberrypi:/opt$ lsusb -t /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 4: Dev 4, If 0, Class=Vendor Specific Class, Driver=ch341, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M |__ Port 4: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M pi@raspberrypi:/opt$ sudo dmesg | grep dwc2 [sudo] password for pi: [1.889792] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [1.889919] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [1.941003] dwc2 fe98.usb: DWC OTG Controller [1.941030] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [1.941057] dwc2 fe98.usb: irq 20, io mem 0xfe98 [1.941253] usb usb3: Manufacturer: Linux 5.15.0-1006-raspi dwc2_hsotg [2.375265] usb 3-1: new high-speed USB device number 2 using dwc2 [2.979316] usb 3-1.3: new low-speed USB device number 3 using dwc2 [3.363309] usb 3-1.4: new full-speed USB device number 4 using dwc2 pi@raspberrypi:/opt$ -- 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
[Bug 1973648] Re: Raspberry Pi - Ubuntu Jammy - USB Not Working
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] Just for comparison sake: In Raspbian under lsusb -t : pi@raspberrypi:~ $ lsusb -t /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 4: Dev 3, If 0, Class=Vendor Specific Class, Driver=ch341, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M However under Ubuntu Jammy I see: pi@raspberrypi:/opt$ lsusb -t /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M Bus 03 should have additional ports show up with driver ch341 -- 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
[Bug 1973648] Re: Raspberry Pi - Ubuntu Jammy - USB Not Working
No, it seems a 4B is happy with dtoverlay=dwc2,dr_mode=host loaded. I had a suspicion this might be the case as it should only affect the mode of the dwc2 port, which is the USB-C power socket on the 4B, and I assume the USB ports you're having trouble with are the type A USB2 and USB3 ports -- still, it was worth a shot. -- 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
[Bug 1973648] Re: Raspberry Pi - Ubuntu Jammy - USB Not Working
That's a slightly odd config.txt; why is "dtoverlay=dwc2,dr_mode=host" under [all] instead of [cm4] where it usually sits? I'm not sure this would disable the USB ports on a 4B (will test this), but it shouldn't be there normally. -- 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
[Bug 1973648] Re: Raspberry Pi - Ubuntu Jammy - USB Not Working
Thanks for assisting - I am running the server version. See below my config.txt ``` pi@raspberrypi:/opt$ cat /boot/firmware/config.txt [all] kernel=vmlinuz cmdline=cmdline.txt initramfs initrd.img followkernel [pi4] max_framebuffers=2 arm_boost=1 [all] # Enable the audio output, I2C and SPI interfaces on the GPIO header. As these # parameters related to the base device-tree they must appear *before* any # other dtoverlay= specification dtparam=audio=on dtparam=i2c_arm=on dtparam=spi=on # Comment out the following line if the edges of the desktop appear outside # the edges of your display disable_overscan=1 # If you have issues with audio, you may try uncommenting the following line # which forces the HDMI output into HDMI mode instead of DVI (which doesn't # support audio output) #hdmi_drive=2 # Enable the serial pins enable_uart=1 # Autoload overlays for any recognized cameras or displays that are attached # to the CSI/DSI ports. Please note this is for libcamera support, *not* for # the legacy camera stack camera_auto_detect=1 display_auto_detect=1 # Config settings specific to arm64 arm_64bit=1 [cm4] # Enable the USB2 outputs on the IO board (assuming your CM4 is plugged into # such a board) [all] dtoverlay=dwc2,dr_mode=host ``` -- 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
[Bug 1973648] Re: Raspberry Pi - Ubuntu Jammy - USB Not Working
apport information ** Tags added: apport-collected arm64-image jammy raspi-image staging uec-images ** Description changed: Hi Running RPI4B with Jammy and cannot get the USB Ports to work. uname -r output: 5.15.0-1006-raspi dmesg output: pi@raspberrypi:~$ sudo dmesg | grep dwc2 [ 1.842505] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [ 1.842665] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [ 1.895846] dwc2 fe98.usb: DWC OTG Controller [ 1.895873] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [ 1.895904] dwc2 fe98.usb: irq 21, io mem 0xfe98 [ 1.896089] usb usb3: Manufacturer: Linux 5.15.0-1006-raspi dwc2_hsotg In Raspbian Bullseye it works without issue. Output of uname -r 5.15.32-v7l+ dmesg output: pi@raspberrypi:~ $ sudo dmesg | grep dwc2 [ 6.571855] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [ 6.623458] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [ 6.745506] dwc2 fe98.usb: DWC OTG Controller [ 6.745560] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [ 6.745624] dwc2 fe98.usb: irq 36, io mem 0xfe98 [ 6.747266] usb usb3: Manufacturer: Linux 5.15.32-v7l+ dwc2_hsotg [ 7.182279] usb 3-1: new high-speed USB device number 2 using dwc2 [ 7.872295] usb 3-1.4: new full-speed USB device number 3 using dwc2 + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-1006-raspi. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu82 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + CRDA: N/A + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + ImageMediaBuild: 20220419 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller + Package: linux-raspi 5.15.0.1006.6 + PackageArchitecture: arm64 + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:CD:3F:7F vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash + ProcVersionSignature: Ubuntu 5.15.0-1006.6-raspi 5.15.30 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-1006-raspi N/A + linux-backports-modules-5.15.0-1006-raspi N/A + linux-firmware 20220329.git681281e4-0ubuntu3 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + StagingDrivers: bcm2835_codec bcm2835_v4l2 bcm2835_mmal_vchiq bcm2835_isp snd_bcm2835 vc_sm_cma + Tags: arm64-image raspi-image jammy uec-images staging + Uname: Linux 5.15.0-1006-raspi aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout docker games input netdev plugdev render sudo users uucp video + _MarkForUpload: True + acpidump: ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1973648/+attachment/5590259/+files/AlsaDevices.txt -- 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
