Cosmos
Cosmos copied to clipboard
CosmosOS
Limine bootloader broke VBE Multiboot
Area of Cosmos - What area of Cosmos are we dealing with?
Bootloader / Graphics
Expected Behaviour - What do you think that should happen?
It shoulds work
Actual Behaviour - What unexpectedly happens?
The VM boot, Limine boots the OS, but the VM unexpectedly reboots.
Reproduction - How did you get this error to appear?
Create a Cosmos Kernel with the latest DevKit and add a VBE Graphics Library (SipaaGL, PrismGraphics...) and add the PrismOS's VBE Console
Version - Were you using the User Kit or Dev Kit? And what User Kit version or Dev Kit commit (Cosmos, IL2CPU, X#)?
DevKit v106027
Video explaining the bug
https://user-images.githubusercontent.com/81994075/216007774-1ee5ad5c-8e28-4dee-9b5c-ac6d3ebfa03d.mp4
It triple faults so it means that the ISRs dont fire so I don't think that the issue comes from limine, why do you say that it comes from limine? It reboots vbefire it gets to the VBE
Maybe because SipaaGL is based on a outdated Prism Graphics version
For me. i have this issue. but instead of restarting. its just a black screen
maybe cosmos overrides framebuffer or limine specific things? if so we need to change a little bit our memory map or create issue on limine repo
This must be a limine-side or a cosmos-side problem
Limite side because it worked correcty on GRUB
This must be a limine-side or a cosmos-side problem
Limite side because it worked correcty on GRUB
true, while it was in grub for me worked as well with Syslinux
We can't say its on limine's side without being sure you guys should know that cosmos is unpredictable so we have to further investigate