Opened 5 years ago
Closed 5 years ago
#15570 closed bug (duplicate)
Cannot boot/ install from USB 3.0 thumbdrive (or use coldplugged)
| Reported by: | phoenixuk | Owned by: | waddlesplash |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Drivers/USB/XHCI | Version: | R1/Development |
| Keywords: | xhci | Cc: | |
| Blocked By: | #15000 | Blocking: | |
| Platform: | x86-64 |
Description
Tested versions: R1beta1, hrev53633, hrev53639
Cannot boot installer from the pre-built anyboot image written to a USB 3.0 SanDisk "Ultra Flair" when connected to a USB 3.0 port. Boot process starts, and after the forth icon (Hard Drive) lights, Kernel Debug Land appears with a message to the effect of "cannot find bootable partition". Tried in both Legacy and EFI boot modes - same result.
Disabling USB 3.0 controller in the system firmware allowed the thumbdrive to boot normally and complete the installation.
After re-enabling the USB 3.0 controller in the system firmware, and booting into the installed environment, the thumbdrive does not appear in the mount list if it was inserted prior to the OS booting; but does appear if plugged in afterwards (or removed and re-plugged).
The computer is a Dell Latitude E5450 with firmware A21, with an Intel i5-5300U CPU, and an Intel (ven=0x8086) "Wildcat Point-LP" USB 2 (Id=0x9ca6) and USB 3 (Id=0x9cb1) controller.
Attached are two sets of syslog, listdev, listusb, and listimage from the installed environment. The first set (without suffix) are with the USB key inserted prior to booting; the second set (with suffix "-post-replug") are from the same session, but after removing and re-inserting the USB key.
Attachments (8)
Change History (9)
by , 5 years ago
| Attachment: | syslog.txt added |
|---|
by , 5 years ago
| Attachment: | syslog-post-replug.txt added |
|---|
syslog - after unplugging and re-plugging USB key
by , 5 years ago
| Attachment: | listdev.txt added |
|---|
listdev - after booting Haiku with USB key already plugged in
by , 5 years ago
| Attachment: | listdev-post-replug.txt added |
|---|
listdev - after unplugging and re-plugging USB key
by , 5 years ago
| Attachment: | listusb.txt added |
|---|
listusb - after booting Haiku with USB key already plugged in
by , 5 years ago
| Attachment: | listusb-post-replug.txt added |
|---|
listusb - after unplugging and re-plugging USB key
by , 5 years ago
| Attachment: | listimage-drivers.txt added |
|---|
listimage | grep drivers - after booting Haiku with USB key already plugged in
by , 5 years ago
| Attachment: | listimage-drivers-post-replug.txt added |
|---|
listimage | grep drivers - after unplugging and re-plugging the USB key
comment:1 by , 5 years ago
| Blocked By: | 15000 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
KERN: usb hub 2: port 7: new device connected KERN: usb error device 12: Corrected invalid interface_number! KERN: usb error device 12: Corrected invaKERN: lid interface_number! KERN: usb error device 12: Corrected invalid interface_number!
I don't know that I've ever seen these before ... but I'm not sure if they are from the USB 2 or USB 3 controller.
All your other symptoms are identical to #15000 -- that is, the drive never appears when plugged in before booting, but always appears when plugged in after booting (so booting always fails.) If you use a USB2 drive on the USB3 controller, then booting will probably work.
I guess I really need to sit down and try to debug this. Since it only occurs on bare metal, though, I'm not sure where to begin with it; I guess I just need to add more tracing and figure out where things are going wrong...
syslog - booted into Haiku with USB key already plugged in