I just confirmed with trust.
Loading memtest with
> knetbsd /boot/memtest86+.elf console=ttyS0,115200n8
Ignores the serial console option.
Loading memtest with
> linux16 /boot/memtest86+.bin console=ttyS0,115200n8
Works, but the above issue would still exist on some machines.
Loading memtest with
> multiboot /boot/memtest86+_multiboot.bin console=ttyS0,115200n8
Displays to both serial and console, but only sees the first 640k of ram.
So I think we need to change the console line to use the old method ie.
> linux16 /boot/memtest86+.bin console=ttyS0,115200n8
This is unfortunate, as people who are using machines with the BIOS issue will not be able to memtest over serial, but that's the state of things at the moment.
I just confirmed with trust. +.elf console= ttyS0,115200n8
Loading memtest with
> knetbsd /boot/memtest86
Ignores the serial console option.
Loading memtest with +.bin console= ttyS0,115200n8
> linux16 /boot/memtest86
Works, but the above issue would still exist on some machines.
Loading memtest with +_multiboot. bin console= ttyS0,115200n8
> multiboot /boot/memtest86
Displays to both serial and console, but only sees the first 640k of ram.
So I think we need to change the console line to use the old method ie. +.bin console= ttyS0,115200n8
> linux16 /boot/memtest86
This is unfortunate, as people who are using machines with the BIOS issue will not be able to memtest over serial, but that's the state of things at the moment.