Variety of issues with bootable USB devices

[brs17]

The Darter Pro fails to boot from a variety of USB devices. All of the below listed devices were recognized and mounted within the OS on all 3 USB ports.

For reference when referring to specific USB ports on the Darter Pro:
USB port 1: Port closest to the power button
USB port 2: Port next to USB port 1
USB port 3: Port on the other side of the machine

The following are the devices tried. They all had a bootable OS installed. The usb drive was plugged in while the machine was off and then the system was cold booted (checkbox checked if boot was successful):

• SanDisk Cruzer Blade 8GB

• SanDisk Cruzer Micro 8GB

  • This USB for some reason has a second "drive" a "SanDisk Cruzer CD Drive" at /dev/sr0.

  • Two options are therefore shown in the bios menu, USB Device and USB Device

  • USB Device goes to a grub shell

  • USB Device 1 fails and goes back to the main BIOS menu. Very quickly an error message is shown (but practically impossible to read without the aid of a camera):

  • 

  • It is a little concerning to me that this error mentions pressing a key to continue but I was never given the opportunity to do so.

  • This happened connected to each usb port.

• SanDisk Ultra USB 3.0 32GB

  • All 3 USB ports booted the drive to a grub shell

• DataStick Pro by Centon

  • When connected to any of the USB ports, the drive was not recognized in the bios menu

• ASUS Republic of Gamers giveaway flash drive

  • When plugged in to the USB port 1 or 3, the drive was not recognized in the bios menu
  • When plugged into port 2, the system booted to a GRUB shell

• USB 3.0 System76 Pop!_OS Flash drive

  • All 3 USB ports booted the drive to a grub shell

This may be similarly related to #10

[jackpot51]

Errors of booting into a GRUB shell appear to only occur when the Pop!_OS recovery partition exists on a drive. This interaction is hopefully something we can solve before launch

[jackpot51]

May be fixed by system76/edk2@d820716

[brs17]

Still not working

ASUS Republic of Gamers giveaway flash drive is now not recognized at all in the BIOS boot menu.
DataStick pro is not recognized.

Working

M.2 enclosures connected via usb type c or type A now function properly.
USB 3.0 System76 Pop!_OS Flash drive now works.
SanDisk Cruzer Micro 8GB works.
SanDisk Ultra USB 3.0 32GB

[brs17]

I am seeing that both the USB 3.0 System76 Pop!_OS Flash drive and M.2 enclosures are having difficulty being recognized as boot devices, while they finally do get noticed at all, it is quite inconsistent and potentially a cause of some of the issues described here: #50

[brs17]

I have noticed the usb devices are recognized quite consistently when Esc is pressed when the splash screen appears and not before (from previous machines, I have developed a habit of pressing Esc as soon as the system begins a reboot/starts booting.

[enkidulan]

same here with lemur pro, usb-3 devices cannot be booted from, but woks fine with usb-2

[JanZerebecki]

I have a few usb2 sticks and most do not show up as a device in the boot order settings on a galp4.

Edit: This was because the image (Tails dvd iso) on these sticks works only with legacy boot. The usb image of Tails 4.11 works on the same sticks.

[crawfxrd]

Error from edk2 when using a USB 3 device on gaze15:

PROGRESS CODE: V02020006 I0
XhcClearRootHubPortFeature: status Success
UsbEnumeratePort: port 16 state - 00, change - 10 on 98B90998
UsbEnumeratePort: device disconnected event on port 16
UsbBusStart: usb bus started on 98CE1818, root hub 98B90998
InstallProtocolInterface: 864E1CA8-85EB-4D63-9DCC-6E0FC90FFD55 98B96618
PROGRESS CODE: V02060000 I0
PROGRESS CODE: V02060004 I0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 98B04698
InstallProtocolInterface: 215FDD18-BD50-4FEB-890B-58CA0B4739E9 98B04238
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 98B04618
InstallProtocolInterface: 215FDD18-BD50-4FEB-890B-58CA0B4739E9 98B043B8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 98B03B18
InstallProtocolInterface: 215FDD18-BD50-4FEB-890B-58CA0B4739E9 98B03F38
XhcClearRootHubPortFeature: status Success
UsbEnumeratePort: port 0 state - 01, change - 01 on 98B90998
UsbEnumeratePort: Device Connect/Disconnect Normally
UsbEnumeratePort: new device connected at port 0
XhcUsbPortReset!
XhcSetRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
XhcSetRootHubPortFeature: status Success
UsbEnumerateNewDev: hub port 0 is reset
UsbEnumerateNewDev: device is of 0 speed
UsbEnumerateNewDev: device uses translator (0, 0)
XhcControlTransfer: error - Device Error, transfer - 100
UsbEnumerateNewDev: failed to set device address - Device Error
PROGRESS CODE: V01010004 I0

Occasionally see this one, but can still boot from the device:

UsbEnumerateNewDev: No device present at port 0

---

Drive is also not detected most of the time when using SeaBIOS.

[crawfxrd]

This hasn't been updated in a while. Open specific issues when new problems are found.

[enkidulan]

I think it has been fixed some time ago. At least I can confirm that usb-3 devices can be booted from.