On 11/09/2026 16:22, Michael Kelly wrote:
On 11/09/2026 15:55, Michael Kelly wrote:
These 2 changes allow gnumach to launch the pci-arbiter which fails because of the same issue above. I've had a quick look at libacpica and there's no obvious sign that it considers UEFI. Perhaps there is a more recent version that might be used? Further investigation required.

It might actually be simpler to just change acpi_os_get_root_pointer() to either consult gnumach for the root pointer physical address or else retrieve it from somewhere supplied to the process via a command line argument. In such case the libacpica is probably OK as is.

I wanted to quickly reach the point where Hurd has completed boot so I hard coded the required physical address of the root pointer into libacpica as a quick hack. The next issue arises where the acpi server tries to read all the ACPI tables for creating its file system. It uses the 'Extended System Configuration Data' memory region which does not apply here, I think. Another method needs to be found to populate the file system, but commenting out that part of the acpi function reaches the boot of rumpkernel.

runpkernel in turn is hanging at the point after:

[   1.2700050] wd0(ahcisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) (using DMA), NCQ (31 tags)

I've run out of time today but it seems like I'm quite close to getting to a login.

Would you expect rumpkernel and/or Hurd to cope with a gpt partitioned disk? Perhaps this is the block but I'll look tomorrow.

Mike.


Reply via email to