LyricalRain wrote:
I actually tried using BOOTBOOT to surpass bootloading altogether and get directly to the kernel. I got it working too. However, no matter what resolution I set in the config file, Qemu always runs at 640x480, and the resolution in the bootboot structure also says 640x480. [...] Any idea what might be causing the issue?
Have you recreated the disk image? The config file in your source repo has no use when you run qemu, only the config file inside the disk image matters.
Other than that, if BOOTBOOT can't find the config file, it sets up the native resolution of the display, or if that can't be found either, then 1024 x 768. This suggests either you have an (un-updated) config in the disk image that tells to set up 640 x 480, or you have configured qemu with a very few RAM, so there's not enough memory for bigger than 640 x 480 resolutions. I had issues with certain Tianocore versions that it couldn't run properly with default qemu configuration, I had to specify "-m 64" (at least 64 MB RAM, but 128 more likely) on the qemu's command line to avoid these issues. You can also try to use different VGA ROMs, see "-vga" option, I use cirrus and it works for me.
To locate the problem, first comment out the "screen" in the config file and recreate the disk image. If it still sets up 640 x 480, then the problem is in your qemu configuration (or Tianocore is explicitly told to use 640 x 480 as native resolution). If it sets up 1024 x 768, then you forgot to update the disk image with the new config file.
If everything else fails, set
GOP_DEBUG define to 1, and recompile (only standard GNU toolchain needed). With that it will dump all the available modes that Tianocore reports, with the native resolution marked by an asterisk, so you'll be able to see if it reports higher than 640 x 480 resolutions at all (use "-serial stdio" on qemu's command line to see the debug messages). Alternatively use the same qemu configuration, but replace EFI/BOOT/BOOTX64.EFI in the disk image with
this. It should list the available modes too, and no BOOTBOOT recompilation necessary.
Hope this helps.
Cheers,
bzt