Opened 10 years ago
Last modified 6 years ago
#10776 closed bug
[haiku_loader] relocating kernel failed: 80001304! — at Initial Version
| Reported by: | diver | Owned by: | bonefish |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | System/Boot Loader | Version: | R1/Development |
| Keywords: | Cc: | diger | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
hrev47162 in VirtualBox.
gcc4 haiku built on x86_gcc2 can't load itself. Upon boot it enters bootloader by itself where I can see my boot partition, but not the other partition with x86_gcc2 Haiku install. Selecting Continue booting returns it back to the bootloader immediately . I should also note that "Blacklist entries" menu lists files on this partition.
x86_gcc2 Haiku bootloader can't see the other (with gcc4 Haiku) partition either.
Haiku was built using these steps:
git clone git://git.haiku-os.org/haiku cd haiku ./configure --target-arch x86 jam -q haiku-image mkdir /haiku-image mount generated/haiku-image /haiku.image
I then used Installer to install from the mounted image to a partition.
Note:
See TracTickets
for help on using tickets.
