Opened 2 years ago
Last modified 2 years ago
#17938 new bug
Surface Book: did not find any boot partitions!
Reported by: | warpdesign2 | Owned by: | waddlesplash |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/USB/XHCI | Version: | |
Keywords: | boot-failure | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
When attempting to boot from USB on a Surface Book, it crashes and bring the kernel debugger with the following message:
PANIC: did not find any boot partitions!
Build: 56417 (x64)
Some details about Surface Book:
- has nvme
- has sdcard slot (with a card in it I cannot remove: it's stuck :p)
- has integrated intel GPU + discrete Nvidia GPU
- keyboard is inactive in kernel debugger
Attachments (3)
Change History (33)
by , 2 years ago
Attachment: | PXL_20220908_085558776.jpg added |
---|
comment:1 by , 2 years ago
Unfortunately without more complete tracing it will likely be impossible to determine what has gone wrong here.
comment:2 by , 2 years ago
Keywords: | boot-failure added |
---|
I note you have an earlier #15035. Is this the same device?
comment:3 by , 2 years ago
What can I do to make a more complete tracing?
Yes, it is the same device: do I still need to use an USB2 stick (I guess it was an USB 3 one) for this ticket.
comment:5 by , 2 years ago
More complete tracing: You can take more screenshots of pages for the syslog KDL command.
comment:6 by , 2 years ago
The author noted keyboard does not work in the kernel debugger in the ticket description.
comment:7 by , 2 years ago
Right, does the keyboard work in the bootloader menu? Then on-screen debug output can be video-recorded.
comment:8 by , 2 years ago
If that's the text menu where we can exclude kernel modules,... yes.
If so what option can I set to enable on-screen debug output?
comment:9 by , 2 years ago
See https://www.haiku-os.org/docs/userguide/en/bootloader.html
That would be "Enable on screen debug output" and "Disable on screen paging"
comment:10 by , 2 years ago
Here is a video of the boot process: https://www.youtube.com/shorts/PBVjUMvsbVU
by , 2 years ago
Attachment: | usb_stall.PNG added |
---|
comment:11 by , 2 years ago
There is indeed a USB stall in the middle of the boot. However I don't know if this is the problem itself. Did you attach the USB drive to a USB hub? Try connecting it to a root port and disconnecting unrelated devices.
comment:12 by , 2 years ago
I have already plugged the drive to a root port in this video.
There is a "Surface" dock (it's a proprietary connector: no idea if it appears as USB hub in the end) but that's not being used. I'll disconnect it: you never know.
comment:13 by , 2 years ago
Here is a video without the dock: https://youtube.com/shorts/bXewwZg1axA
Note that there is also an SDCard that I cannot unplug because its stuck in the computer.
comment:15 by , 2 years ago
Component: | - General → Drivers/USB |
---|---|
Owner: | changed from | to
comment:16 by , 2 years ago
You can try with a recent nightly of hrev56511+, it's possible some of the USB fixes the past few days shook something loose here.
Otherwise I don't really have any great ideas. If you could track down precisely when it stopped working, that would be helpful.
comment:17 by , 2 years ago
I'm closely watching commits and have already tested this rev but it did not change anything: still stops with the "PANIC: did not find any boot partitions!" message.
I can't track when it stopped working since it never worked, at least with USB3.
I'll give it a try with an older USB2 key: maybe this will help track down the problem?
comment:18 by , 2 years ago
I did some tests with hrev56521:
- USB2 stick: boots to the welcome screen, but I have no keyboard nor trackpad working
- USB3 stick: "PANIC: did not find any boot partitions!"
There is definitely something wrong with USB3. I'll create a separate ticket for the keyboard/trackpad not working when booting with USB2.
I attached a copy of the USB treeview as seen in Windows: maybe this will help.
comment:19 by , 2 years ago
Can someone update the issue's title to include "USB3"? It seems I cannot modify it.
comment:20 by , 2 years ago
Component: | Drivers/USB → Drivers/USB/XHCI |
---|---|
Owner: | changed from | to
comment:22 by , 2 years ago
@korli: how can I do that? The keyboard is non functional in the kernel debugger. If you mean providing a video of the on-screen boot messages with paging disabled, I already did that in the video above. I'm afraid that's all I can do.
comment:23 by , 2 years ago
Boot to the desktop, press the shutdown button. There should be a syslog file in system/var/log.
comment:24 by , 2 years ago
I cannot boot to desktop: as I said it crashes before reaching the desktop screen with the error message "did not find any boot partitions!".
comment:26 by , 2 years ago
It does, but since there are two distinct problems:
- USB2: boot, but no mouse/keyboard
- USB3: boot panic
I created a new ticket related to the mouse/keyboard not working here.
And I suggested to add "USB3" in the title of this ticket.
comment:27 by , 2 years ago
The ticket is in the "xhci" component, that means USB3. There is no need to repeat it in the ticket title I think.
comment:28 by , 2 years ago
Having a syslog of a successful usb2 boot can be useful to understand the usb3 problem. See https://dev.haiku-os.org/wiki/ReportingBugs#KernelBugs for more info. You could try to plug in the usb3 stick while having booted with the usb2 stick, maybe something of interest could be seen in the syslog.
comment:29 by , 2 years ago
I think some of korli's fixes following the last noted hrev might have affected things here. Please test with a recent nightly, again.
comment:30 by , 2 years ago
Just tried with hrev56627: same message "Did not find any boot partitions!" when booting using USB3.
Kernel log