Re: Rumpdisk errors on boot

[João Pedro Malhado <phlogiston@sapo.pt>]

Hello again,

Is the acpi translator necessary to run rumpdisk?
Some of the error messages reported on my previous message
(namely piixide0:0:0: lost interrupt) go away if I exclude the acpi part of the
grub entry.

Using the following grub entry:

menuentry "GNU/Hurd (pci-arbiter+rumpdisk)" {
        set root=(hd0,msdos1)
        multiboot /boot/gnumach.gz root=part:1:device:wd0 noide -s
        module /hurd/pci-arbiter.static pci-arbiter \
                --host-priv-port='${host-port}' \
                --device-master-port='${device-port}' \
                --next-task='${disk-task}' \
                '$(task-create)' '$(task-resume)'
        module /hurd/rumpdisk.static rumpdisk \
                --next-task='${fs-task}' \
                '$(disk-task=task-create)'
        module /hurd/ext2fs.static ext2fs \
                --multiboot-command-line='${kernel-command-line}' \
                --exec-server-task='${exec-task}' -T typed '${root}' \
                '$(fs-task=task-create)'
        module /hurd/exec.static exec '$(exec-task=task-create)'
}


I get the following messages during boot:

[     1.0200050] piixide0 at pci0 dev 31 function 2: Intel 82801GB/GR Serial ATA/Raid Controler (ICH7) (rev. 0x02)
[     1.0200050] piixide0: bus-master DMA support present
[     1.0200050] piixide0: primary channel configured to compatibility mode
irqhandler [14]:new delivery port f61bfe88 entry f5d15e40
[     1.2200050] atabus0 at piixide0 channel 0
[     1.2200050] piixide0: secondary channel configured to compatibility mode
[     1.2200050] wd0 at atabus0 drive 0
irqhandler [15]: new delivery port f61bfac8 entry f5d15ee0
[    10.3700050] atabus1 at piixide0 channel 1
[    10.3700050] vendor 8086 product 27da (SMbus serial bus, revision 0x02) at pci0 dev 31 function 3 not configured
[    10.3900050] wd0: <Hitachi HTS545025B9A300>
[    10.3900050] wd0: driver supports 16-sector PIO transfers, LBA48 addressing
[    10.3900050] wd0: 232 GB, 484521 cyl, 16 head, 63 sec, 512 bytes/sect x
488397168 sectors
[    10.4200050] wd0: 32-bit data port
random init open failed
warning: dmalloc(4096) requested with 10000 alignment, bumping up size
[    10.4200050] wd0(piixide0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA), WRITE DMA FUA EXT
[    10.4300050] blake2s: self-test passed
[    10.4300050] chacha: Portable C ChaCha

But then nothing happens, and ext2fs does not seem to start.
Should this configuration without acpi work?

There might be an issue with the BIOS and ACPI on this netbook as when I run
linux on this machine I get in the logs

ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0._OSC.CAPB], AE_ALREADY_EXISTS (20220331/dsfield-184)
ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477)
ACPI Error: Aborting method \_SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529)

But these errors are not critical as linux still boots.

I also don't manage to boot using the in-gnumach drivers. I am actually unsure
of the correct way to specify the root device in this case.
If I use the grub command 

        multiboot /boot/gnumach.gz root=part:1:device:hd0 -s

I get

start pci-arbiter: pci ext2fs: part:1:device:hd0: Input/output error

And if I use

        multiboot /boot/gnumach.gz root=device:hd0s1 -s

I get

start pci-arbiter: pci Hurd server bootstrap: ext2fs[device:hd0s1] exec startupext2fs: Executing '/hurd/startup': No such file or directory

Which is the right way of specifying the root device?

Best regards,
João