OSDev.org

ACPICA works fine on vms, but it halts on real hardware.

Is there anything wrong with my ACPI Initialization.

https://github.com/NXTdevosc1/acpica/bl ... main.c#L48

Where does it halt?

Wait actually it halted before, the OS still doesnt fully work on real hardware but now the problem isnt in ACPICA as I did a 10 color test because i still do not debug directly in the frame buffer through writing text.

And ACPICA seems to work fine, i need to investigate other drivers.

This is the 10 color test if you wonder:

https://ibb.co/KXV1c2j

Sorry, I thought it was ACPICA problem because it was before I unmap the 0 page and discover some bugs.
The ACPICA driver works fine, but it gives a page fault after the driver is ran so it may be the kernel or some other driver. I will see about that, I think Ill keep working on vms until I finish the drivers then after making the 3D driver and font driver i will just display logs on the screen and see whats the problem.

For now, thanks and sorry for wasting your times.

Actually I quite didn't figure out how to use acpi to see if there is an RTC and how to see PCI Routing table because i will need it in EHCI.

Remember, sometimes just writing it down makes you think about it potentially different. The action of asking for help sometimes just gives you insight.

Yeah it always does. I'm feeling a bit rude in this forum because most of the time I get the answer myself just by writing a question lol.

Let's change it to this:

Enumerate the ACPI namespace. An RTC device might have the PnP ID ACPI000E, PNP0B00, PNP0B01, or PNP0B02 depending on how it's meant to be accessed. If you find none of these devices, check if the FADT says you can probe for a legacy RTC.

Also, UEFI provides a runtime service for accessing the RTC.


Do what the ACPI spec says to do.