Closed Stay1444 closed 1 year ago
This apparently is a bug in the bootloader crate, which was mentioned in issue #1138, which is apparently fixed in its pull request #234. I currently have a branch that bumps up everything to the latest, and apparently, everything seems to work just fine the system seems to boot, but I still am a tad hesitant to create a PR because bumping everything to the latest might just open another can of worms.
EDIT: I delete the branch mentioned by me because it contained way too many changes and it was getting hard to trace them.
Amazing! Will check it out and see if i can contribute. Any recommendations?
Any recommendations?
I just tested it on an older toolchain and seems like bumping the version for bootloader
crate to 0.9.23
seems to be enough. You can try doing that and testing even further. I unfortunately cannot ATM since it is 12:00AM here and I need to get some sleep.
This issue has been fixed in PR #25.
Thank you @tomshoo. I'm closing this issue.
Describe the bug After running
cargo run --release
i getpanicket at 'assertion failed: max_phys_addr < (1 << 48) / 512'
(build success, and running in QEMU)To Reproduce Steps to reproduce the behavior:
Expected behavior The system boots
Screenshots
Additional information