Opened 3 years ago
Closed 18 months ago
#17369 closed bug (fixed)
Nightly build hangs at boot
Reported by: | epa1257 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | System/Boot Loader/EFI | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86-64 |
Description
When trying to boot Haiku from disc on my machine, it hangs at the logo screen and the icons don't light up. I'm using the latest nightly build, which as of this writing is [hrev55602]. I'm using the x86_64 build.
I was able to get to the boot options and tried a variety of safe mode toggles, unfortunately none worked. I also tried enabling the debug log instead of the boot logo, this also did not work and just showed the normal boot logo. I did manage to view the current boot log and noted it would end on the same following line: PackageVolumeInfo::LoadOldStates(): failed to open administrative directory: No such file or directory I couldn't find any info on this error looking through the tickets, but I'm guessing it's not normal considering it's the final line of the debug log.
My setup is AMD Ryzen 9 3900X, MSI B550 Tomahawk motherboard, GeForce RTX 2060 and 64gb of RAM. I couldn't find anything saying the above wasn't compatible and I also tried changing BIOS settings to no avail.
Attachments (1)
Change History (15)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
but I'm guessing it's not normal considering it's the final line of the debug log.
It is actually relatively normal on first boots without installs.
comment:3 by , 3 years ago
Hi waddlesplash, thanks for the reply. I'm using the UEFI loader, if my BIOS' boot selector is correct.
comment:4 by , 3 years ago
Component: | - General → System/Boot Loader/EFI |
---|
The problem you describe is known to happen on Ryzen systems with the BIOS loader, but the EFI loader usually works.
A few other people have reported this problem with the EFI loader on very recent hardware (though different from yours.) Not sure when someone will have time to really investigate though.
comment:6 by , 3 years ago
Happens on my system: Lenovo IdeaPad 5 15ARE05 81YQ004SRK (Ryzen 5 4600U)
follow-up: 9 comment:7 by , 3 years ago
This issue is unrelated to this ticket. This ticket is about failing to start the kernel.
comment:8 by , 3 years ago
rv55607 hang after rocket with "UEFI" mode. When Legacy Support is enabled I go further, to the debugger.
Something wrong with radeon_hd accelerant.
comment:9 by , 3 years ago
Replying to diver:
This issue is unrelated to this ticket. This ticket is about failing to start the kernel.
Sorry for that. I'll open another ticket.
follow-up: 12 comment:11 by , 19 months ago
i have same issues on Lenovo Ideapad Flex 10 with 32 bit uefi which make unable to boot haiku OS nightly build x86.
part of log:
line210 PackageVolumeInfo::_InitStates(): failed to parse activated-packages: No such file or directory
line402 PackageVolumeInfo::LoadOldStates(): failed to open administrative directory: No such file or directory
there is info:
Machine: Lenovo ideapad flex 10
CPU: intel baytrail 64 bit.
RAM: 2gb
ROM: 240gb SSD
boot media: haiku OS nightly anyboot hrev 57085 x86 gcc2
comment:12 by , 19 months ago
Replying to Mas4hmad:
boot media: haiku OS nightly anyboot hrev 57085 x86 gcc2
this ticket is about x86_64, you should probably submit another ticket.
comment:13 by , 18 months ago
Replying to waddlesplash:
Please retest on a recent nightly.
Hello, I've retested as requested several months ago, my sincere apologies for no reply!
Using the latest nightly build [hrev57100] flashed to a USB stick, I have good news and bad news. The good news is that the original fault I described in this ticket seems to have been resolved, and Haiku gets past the initial boot screen after a short loading time.
The bad news is that it seems I have now encountered another error - the moment it gets to the Welcome screen (where it asks if you want to Try or Install Haiku) - the kernel immediately crashes and dumps something on the screen in an unreadable garish pink and green. I have been able to get a picture, but since I believe it's unrelated to the initial error I was describing, I'll open another ticket.
comment:14 by , 18 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
You can try booting with "fail-safe video mode" enabled in the loader, and see if that helps. At least it might be readable.
Are you using the EFI or BIOS loader?