Open sawcce opened 6 months ago
I did check: https://github.com/limine-bootloader/limine-c-template/issues/5 Both links aren't broken for me, it just seems that the nightly builds aren't working as intended.
Well I just tried it and it works for me... Maybe it doesn't work on older QEMU?
I'll check my qemu version once I have access to my PC although I did update qemu before cloning the repo so not sure if that's the issue
Even then, an updated QEMU on Ubuntu 22.04 is still bound to be an old QEMU...
Yeah I deleted the ovmf folder, ran make ovmf
then make run-uefi
and still having the same issue
Even if I just clone the repo without changing anything the same thing happens
I'm suffering something similar: OVMF is able to load, but when it boots from the ISO or HDD (via run-uefi-hdd or run-uefi) it says "booting from HDD"/"booting from DVD" but then just halts. Limine doesn't even show anything. I'm not sure why since I've even enabled VERBOSE
to see if that fixed it, and it just doesn't print anything on the framebuffer or serial port. The ISO and HDD seem to be set up correctly, so I'm a bit confused.
I found that updating OVMF fixed the bug I mentioned but now Limine is saying that it didn't find any requests, which is weird since I did pub export var
them.
Okay, getting this bug again. Running on latest Limine. When I boot the vm with make run/run-uefi/run-hdd/run-hdd-uefi`, I get the initial firmware boot messages and such, then a completely blank screen. Running it in GDB shows it's working but I don't know if the debugger is having some kind of influence on the execution of the code or something else.
I wanted to try zig osdev with limine again with the updated template but for some odd reason the updated download link (Commit with the update) doesn't seem to provide a working firmware?
I tried using the old link and it worked without any issue (although it would seem that it hasn't been updated for a while?).
My current issue is that limine doesn't even boot, it gets stuck on "Guest has not initialized display (yet)".
-d in_asm
does show that the firmware seem to be running.Software info: