#17004 closed bug (invalid)
The installed EFI bootloader doesn't start automatically (regression)
Reported by: | vidrep | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | System/Boot Loader | Version: | R1/beta2 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
vendor 8086: Intel Corporation device 22b1: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller EFI only
Instead of booting to the desktop after installing to a GPT drive, it first invokes the Haiku boot menu.
I have narrowed down the issue to between hrev53639 (working) and hrev53649 (not working).
Attachments (3)
Change History (18)
by , 4 years ago
Attachment: | FirstBootPrompt-788-debug-11-06-2021-09-53-39.report added |
---|
comment:1 by , 4 years ago
Description: | modified (diff) |
---|
comment:2 by , 4 years ago
comment:3 by , 4 years ago
A nightly install or an update from an earlier installation won’t boot https://dev.haiku-os.org/ticket/16999
This is a second issue I found while investigating the first.
comment:4 by , 4 years ago
Resolution: | → no change required |
---|---|
Status: | new → closed |
As the nightly gets to the chip icon, where EFI already is done, this problem has already been fixed. The other ticket is the one that should be investigated.
comment:5 by , 3 years ago
I wiped my hard drive on this system with Parted magic, and installed hrev55202 x86_64. This problem is not fixed. It brings up the boot menu (same as tapping the space bar) every time, before you can boot the system installed on the hard drive. It appears to be a problem peculiar only to this PC (which is EFI only), as I don't see this issue on any other system I have.
comment:6 by , 3 years ago
Description: | modified (diff) |
---|---|
Resolution: | no change required |
Status: | closed → reopened |
comment:7 by , 3 years ago
Ticket https://dev.haiku-os.org/ticket/16999 has been fixed since this ticket was created. The system now boots, but the problem in the description remains.
comment:8 by , 3 years ago
Please provide syslog. I would also like to know what partitions you have on your system and make sure you copied the .efi file to the EFI system partition.
comment:9 by , 3 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
And I don't think the description is true anymore. Please open a new bug for new issues, don't just change description, the hrev range and the issue is not the same and the comments are about the old issue.
comment:10 by , 3 years ago
33MB EFIBOOT partition FAT32, 149GB Haiku partition BFS - that's it. I'm just about to install hrev53639 again to make absolutely sure. I'll provide a listdev, and syslog of both installations shortly.
by , 3 years ago
by , 3 years ago
Attachment: | IMG_0379.JPG added |
---|
comment:12 by , 3 years ago
What's confusing? "Instead of booting to the desktop after installing to a GPT drive, it first invokes the Haiku boot menu." That's the problem. See photo and syslog.
I see "no boot volume found" quickly flashes on the top left of the screen, just before the boot menu appears.
comment:13 by , 3 years ago
I found another ticket that describes the same issue I’m having. https://dev.haiku-os.org/ticket/16073
comment:14 by , 3 years ago
Yes, but if it is two different bugs and all info is about the bug that was fixed by p-states, you should create a new bug, never reopen or edit description. Reopen is usually bad, but can be done if the exact same problem wasn't fixed. So please stop adding to this ticket and create a new one.
The one you found is about an older version of efi bootloader, so open a new ticket, and make sure you use the efi-loader from the installation medium. It will give me a much easier time to look at things, and I don't have that much energy to spare.
comment:15 by , 3 years ago
For what it’s worth, the problem has been fixed with Beta3 test image hrev55181_32.
Not sure what build you are running. Those changes are from 2019-12 and we changed it since then. Here are the changes
So I don't think this bug is valid with the current tree, maybe you can check a nightly?